Upgrade from BEWS 9.1 to 10 possible?

[Matej_Mikuz]

I am testing upgrade procedure from 9.1 to 10 on clean test machines. So far the upgrade was not succesfull, tried on 3 clean W2k3 machines.

The error is: Catalog Index Upgrade Failed
After upgrade and restart I have to recreate backup accounts, jobs, media pools, etc...

Some interesting lines from bkupinst.log:
05-18-2005,11:00:28 : Property(S): RedirectedDllSupport = 2

05-18-2005,11:00:28 : Property(S): Time = 11:00:28

05-18-2005,11:00:28 : Property(S): Date = 18.5.2005

05-18-2005,11:00:28 : Property(S): Privileged = 1

05-18-2005,11:00:28 : Property(S): DATABASE = C:\WINDOWS\Installer\2e62bb.msi

05-18-2005,11:00:28 : Property(S): OriginalDatabase = D:\WINNT\INSTALL\BE\VERITAS Backup Exec For Windows Servers.msi

05-18-2005,11:00:28 : Property(S): UILevel = 3

05-18-2005,11:00:28 : Property(S): Preselected = 1

05-18-2005,11:00:28 : Property(S): MIGRATE = {201E698C-B88E-41AE-8C46-3BBACADCD6E7}

05-18-2005,11:00:28 : Property(S): CostingComplete = 1

05-18-2005,11:00:28 : Property(S): SourcedirProduct = {300301A1-EA9E-4BC2-B267-5E323A9B23E0}

05-18-2005,11:00:28 : Property(S): BEUpgBackupFolder = C:\Program Files\VERITAS\Backup Exec\NT\DataBackup\

05-18-2005,11:00:28 : Property(S): BEUpgBackupFolderData = C:\Program Files\VERITAS\Backup Exec\NT\DataBackup\Data\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE1 = C:\Program Files\VERITAS\Backup Exec\NT\Data\

05-18-2005,11:00:28 : Property(S): MoveFileIdCounter = 31

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE2 = D:\WINNT\INSTALL\SAPR3Inst\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE3 = D:\WINNT\INSTALL\SAPR3Inst\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE4 = D:\WINNT\INSTALL\SAPR3Inst\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE5 = D:\WINNT\INSTALL\SAPR3Inst\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE6 = D:\WINNT\INSTALL\SAPR3Inst\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE7 = D:\WINNT\INSTALL\SAPR3Inst\

05-18-2005,11:00:28 : Property(S): DupFileIdCounter = 4

05-18-2005,11:00:28 : Property(S): RegIdCounter = 257

05-18-2005,11:00:28 : Property(S): RAWS32Dir = C:\Program Files\VERITAS\Backup Exec\NT\Agents\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE8 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE9 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE10 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE11 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE13 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE12 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE15 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE14 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE16 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE17 = D:\WINNT\INSTALL\RANT32\

05-18-2005,11:00:28 : Property(S): RemFileIdCounter = 3

05-18-2005,11:00:28 : Property(S): MOVETABLE_SOURCE18 = D:\WINNT\INSTALL\VxPush\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE19 = D:\WINNT\INSTALL\VxPush\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE20 = D:\WINNT\INSTALL\VxPush\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE22 = D:\WINNT\INSTALL\VxPush\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE21 = D:\WINNT\INSTALL\VxPush\

05-18-2005,11:00:29 : Property(S): RAWS64Dir = C:\Program Files\VERITAS\Backup Exec\NT\Agents\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE24 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE23 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE25 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE26 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE27 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE28 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE30 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE29 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): MOVETABLE_SOURCE31 = D:\WINNT\INSTALL\RANT64\

05-18-2005,11:00:29 : Property(S): RENAMED_PATH.380C600C_E17D_459C_91FA_D5C4585F8825 = \oemtap0.inf

05-18-2005,11:00:29 : Property(S): SQLServiceName = MSSQL$BKUPEXECDLO

05-18-2005,11:00:29 : Property(S): OutOfDiskSpace = 0

05-18-2005,11:00:29 : Property(S): OutOfNoRbDiskSpace = 0

05-18-2005,11:00:29 : Property(S): PrimaryVolumeSpaceAvailable = 0

05-18-2005,11:00:29 : Property(S): PrimaryVolumeSpaceRequired = 0

05-18-2005,11:00:29 : Property(S): PrimaryVolumeSpaceRemaining = 0

05-18-2005,11:00:29 : Property(S): DLOBUILDINFOINSTALLED = TRUE

05-18-2005,11:00:29 : Property(S): ProductToBeRegistered = 1

05-18-2005,11:00:29 : 1: INSTALL 2: 1

05-18-2005,11:01:05 : WARNING: Unable to remove service BackupExecNamingService. The service does not exist.

05-18-2005,11:01:05 : Upgrade state set to 5

05-18-2005,11:01:05 : Starting BE services after 9.x upgrade.

05-18-2005,11:01:05 : A reboot is required to successfully configure Backup Exec. Backup Exec services will not start until this system is rebooted.

05-18-2005,11:19:34 : Validating install complete

05-18-2005,11:19:35 : SUCCESS: Installation has completed successfully. (Reboot required!)
05-18-2005,11:19:35 : Shuts down the Window, and starts the Window again.


Please advise!

[Patrick_Tavares]

I would highly recommend not upgrading to 10. We've had nothing but problems running 10.0.

We have two identical environments with a mix of Solaris, Linux, and Windows machines. In one environment, we run a BE 9.0 server with 9.x agents to backup all of our servers. Everything works perfectly. In the other environment we run BE 10, and have had nothing but issues. For starters the 10.0 Unix backup agent (which you now have to pay for) does not seem to allow you to choose a specific NIC to bind to, whereas the 9.x agent had a config option for that.

My 2 cents.

[Deepali_Badave]

Hello,

To upgrade from Backup Exec v9.x to Backup Exec 10.0 refer to the following steps:

1.Run Setup.exe, which is located in the installation CD or in the extracted folder

2. The VERITAS Backup Exec (TM) 9.x for Windows Servers dialog will be displayed. The Welcome screen is displayed.Click Next to proceed further

3.Select Local Install, and then select Install Backup Exec software and options

4.Additionally, Remote Install can be selected so that Remote Agent for Windows Server and Options can be pushed to remote systems.

5. Listed below are the installation versions you can select from:

a. Evaluation: To install Backup Exec in Evaluation Mode for 60 days, leave the Serial Number field empty, and click Next to continue
b. Licensed: To install a licensed version of Backup Exec, insert the Product Activation Code in the Serial Number field, click Add, and then click Next to continue

Based on the serial number entered, various pre-selected options will be displayed

Options with the red X indicate that these options will not be installed, as the serial number is not entered.

The destination folder can changed if needed. The default destination folder is SystemDrive\Program Files\VERITAS\Backup Exec.


7. While performing the upgrade, Backup Exec sets the option to store the Data and the Catalog folder of the earlier version on to a different folder

8. It is recommended to give the Backup Exec Service Account (BESA) a new domain user account belonging to the Domain Admins and Local Administrators groups. Insert the domain user account to be used for the Backup Exec services. If the account does not exist, Backup Exec will create it and add it to the Domain Admins and Local Administrators groups and the Logon as a Service right. Click OK to continue with the installation of the Backup Exec services

The following rights are granted to BESA:

Logon as a service
Act as a part of the operating system
Create a token object
· ·
9. After creating the Backup Exec Service Account, it gives an option to either install the Backup Exec MSDE instance on the existing SQL instance or create a separate MSDE instance

Note: The new feature in Backup Exec 10.0 is that the MSDE instance can be either stored locally or can be redirected to a local or remote SQL 2000 instance.

10. The process gives an option to install the latest Veritas Drivers
The Backup Exec installation Overview is displayed

After the upgrade is over, the server has to be rebooted.



Note: The catalog files, the job definitions, the job history, the media set are all preserved and are upgraded. Also the templates that existed in Backup Exec v9.x will be upgraded to Backup Exec 10.0 as policies. They will be seen under the policy tab.

=======================================
Refer the following steps

-- Use BEMIG.EXE to upgrade Backup Exec 9.x MSDE DB to Backup Exec 10.0

Start with a blank Backup Exec version 10.0 Database.
Determine the revision for the Backup Exec version 9.x
Navigate to the Registry
HKEY_LOCAL_MACHINE | SOFTWARE | VERITAS | Backup Exec | Install
Create a new string value key called 'Upgrade Version' and set the value as 9.1.4691.0 or 9.0.4454.0 according to the revision for Backup Exec 9.x
Stop the SQL service to which the Backup Exec database belongs. By default, the SQL service Backup Exec uses is “MSSQL$BKUPEXEC”.
Rename the following files in \Program Files\VERITAS\Backup Exec\NT\Data
BEDB_DAT.MDF to BEDB_DATA_MDF.10
BEDB_LOG.LDF to BEDB_LOG_LDF.10
From the Data/Backup folder copy BEDB_DAT.MDF to the \Program Files\VERITAS\Backup Exec\NT\Data folder
Restart the above SQL Server service.
From a command line, run Backup Exec migration program “BEMIG.EXE”. BEMIG.EXE can be found in the \Program Files\VERITAS\Backup Exec\NT directory.


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.Message was edited by:
deepali

[Matej_Mikuz]

Due to upgrade I lost:
- job definitions
- account configuration
- job history
- media sets

Fortunatelly, it was a test machine.

Anyway, I decided NOT TO UPGRADE.

[Deepali_Badave]

Hello,

This could happen if the installation completes with errors.

Upgrade to BEv 10.0 was successful or was it completed with errors?



NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Matej_Mikuz]

"Database upgrade did not complete succesfully. All devices, media and jobs will not be migrated from your previous version."

[Gauri_Ketkar]

Hi,

We would like know whether you have saved "DATA" folder of old Backup exec version while upgrading to 10.0?

Please refer to the technote given below :

Step by Step installation instructions for the upgrade to Backup Exec 10.0 from Backup Exec 9.x
http://seer.support.veritas.com/docs/276479.htm

Thank you.

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.