cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade Backup Exec 2010 to R2 fails

Mongi
Level 2

Hello. 

During upgrade from BackupExec 2010 to 2010 R2 occures some strange error: 

09-19-2010,22:57:20 : Действие 22:57:20: RB_RollbackBEDB.
09-19-2010,22:57:21 : Действие 22:57:21: Migrate_BEDB.
09-19-2010,22:57:24 : GetClusterUpgradeState returning 0
09-19-2010,22:57:24 : Kicking off data migration in UPG_InstallMigrate
09-19-2010,22:57:24 : C:\Program Files\Symantec\Backup Exec\
09-19-2010,22:57:24 : BEServer registry key value has been set to current BEServer.exe version 13.0.4164.0
09-19-2010,22:57:24 : GetClusterUpgradeState returning 0
09-19-2010,22:57:24 : C:\Program Files\Symantec\Backup Exec\
09-19-2010,22:57:24 : m_bUseNativeClient = 1
09-19-2010,22:57:24 : Executing Attach_BEDB.
09-19-2010,22:57:24 : DRIVER={SQL Native Client};SERVER=ARIEL;Trusted_Connection=Yes;DATABASE=master
09-19-2010,22:57:25 : Connected to SQL Server.
09-19-2010,22:57:25 : Unsuccessful return code from SQL statement: select filename from master..sysdatabases where name='BEDB'
09-19-2010,22:57:25 : Attaching BEDB to SQL Server.
09-19-2010,22:57:25 : EXEC sp_attach_db 'BEDB',@filename1 = N'S:\mssql\Databases\BEDB_Dat.mdf', @filename2 = N'S:\mssql\Databases\BEDB_Log.ldf'
09-19-2010,22:57:25 : BEDB has been succesfully attached to SQL Server.
09-19-2010,22:57:25 : Change BEDB owner to SA user.
09-19-2010,22:57:25 : Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\Upgrade: 1)
09-19-2010,22:57:25 : Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\Upgrade Version: 13.0.2896.0)
09-19-2010,22:57:25 : m_bUseNativeClient = 1
09-19-2010,22:57:25 : Executing BEDB data migration.
09-19-2010,22:57:25 : C:\Program Files\Symantec\Backup Exec\
09-19-2010,22:57:25 : DRIVER={SQL Native Client};SERVER=ARIEL;Trusted_Connection=Yes;DATABASE=master
09-19-2010,22:57:25 : SQL Server version 9
09-19-2010,22:57:25 : SQL version returned: 9
09-19-2010,22:57:25 : DRIVER={SQL Native Client};SERVER=ARIEL;Trusted_Connection=Yes;DATABASE=master
09-19-2010,22:57:26 : Unable to prep database instances for upgrade.
09-19-2010,22:57:26 : ERROR: User cancelled after unsuccessful migration
09-19-2010,22:57:26 : V-225-134: Error Migrating BEDB ***To search for information about this error, click here
09-19-2010,22:57:26 : Завершение действия 22:57:26: InstallExecute. Возвращенное значение 3.
09-19-2010,22:57:26 : Действие 22:57:26: Rollback. Откат действия:
09-19-2010,22:57:27 : Migrate_BEDB
09-19-2010,22:57:27 : RB_RollbackBEDB
09-19-2010,22:57:29 : Rolling back BEDB files during upgrade rollback in UPG_RollbackBEDB
09-19-2010,22:57:29 : GetClusterUpgradeState returning 0
09-19-2010,22:57:29 : m_bUseNativeClient = 1 

after which installation goes rollback and fails. I tied to google some information on "V-225-134", but found nothing. 

System config:

  • Main server: Windows 2003 R2
  • Remote SQL: SQL server 2005 SP3  x64

Any suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions

Mongi
Level 2

Thanks everyone for replies.

I've launched setup process on clean server installation and found out that it doesn't ask for any custom SQL such as remote SQL server. Previous version (BE 2010) setup program asks for SQL location.

So, it seems that upgrade cannot be done while using remote SQL server and our goal was to migrate DB to local installation, upgrade and move back. We decided to combine this process with platform upgrade to Windows 2008 R2 and here are full steps to proceed:
  1. Back up all your data: in SQL server an your backup server
  2. Prepare new OS and install there Backup Exec 2010 with default preferences (it installs local MSSQL 2005 Express)
  3. Stop Backup Exec services on old machine and on new machine
  4. Copy DB(through Backup-Restore or Detach-Attach) from remote server to your local MSSQL installation on new machine
  5. Edit tables [Device] and [DataPartition] and change old machine name to new one there
  6. Delete in registry HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DataPartitionGUID key
  7. Launch services on new machine, they shoud start up and you can see all you tasks, devices and media 
  8. If all seems to work than you can begin upgrade process
  9. Run Backup Exec 2010 R2 installer 
  10. After it completes check again your system and backup processes
  11. Finally, the last step: migrate to remote SQL server
  12. Stop Backup Exec services on new machine
  13. Edit Registry settings:
  14. In HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase you create Keys: "Catalog Database Instance Name", "Server Database Instance Name" -- empty; "Catalog Database Server Name", "Server Database Server Name" -- SQL server name; "Server Database Log Path", "Server Database Path" -- paths to DB files on remote SQL server
  15. In HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Adamm you must create two keys: "Database Server Name" and "Database Instance Name" 
  16. In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BackupExecDeviceMediaService\DependOnService remove MSSQL line
  17. Uninstall MSSQL Express from new machine
  18. REBOOT!
  19. After restart all services should work fine

And that`s it. However, this guide worked for our simple installation with no clusters or complicated media services installed, so your experience may and will be slightly different.

More information on migrating can be found here  

Finally, some tips you should keep in mind:

  • Remote SQL and local MSSQL express installations MUST be of the same version (2005 or 2008); edition type doesn't matter
  • If our Remote SQL server is 2008 then you MUST install SQL 2008 Express to new machine prior step 2 and use it when asked in installer.
  • If our remote SQL installation is not on default Instance than appropriate registry settings shouldn't be empty  
  • When creating and moving BEDB database files MUST be named "bedb_dat.mdf" and "bedb_log.ldf", otherwise Media Service won't start at all
  • You can copy Catalog data to new machine or you can simply regenerate it later

View solution in original post

3 REPLIES 3

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi Mongi,

 

Have you tried to install the version of SQL that is on the BE 2010 R2 disc first manually, and THEN trying to upgrade the software?
Also, if you have an antivirus active, try disabling that and running the upgrade again.

 

Laters!

Mahesh_Roja
Level 6

Read the compatibility and follow the doc in below KB

http://www.symantec.com/business/support/index?page=content&id=TECH73057

Mongi
Level 2

Thanks everyone for replies.

I've launched setup process on clean server installation and found out that it doesn't ask for any custom SQL such as remote SQL server. Previous version (BE 2010) setup program asks for SQL location.

So, it seems that upgrade cannot be done while using remote SQL server and our goal was to migrate DB to local installation, upgrade and move back. We decided to combine this process with platform upgrade to Windows 2008 R2 and here are full steps to proceed:
  1. Back up all your data: in SQL server an your backup server
  2. Prepare new OS and install there Backup Exec 2010 with default preferences (it installs local MSSQL 2005 Express)
  3. Stop Backup Exec services on old machine and on new machine
  4. Copy DB(through Backup-Restore or Detach-Attach) from remote server to your local MSSQL installation on new machine
  5. Edit tables [Device] and [DataPartition] and change old machine name to new one there
  6. Delete in registry HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DataPartitionGUID key
  7. Launch services on new machine, they shoud start up and you can see all you tasks, devices and media 
  8. If all seems to work than you can begin upgrade process
  9. Run Backup Exec 2010 R2 installer 
  10. After it completes check again your system and backup processes
  11. Finally, the last step: migrate to remote SQL server
  12. Stop Backup Exec services on new machine
  13. Edit Registry settings:
  14. In HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase you create Keys: "Catalog Database Instance Name", "Server Database Instance Name" -- empty; "Catalog Database Server Name", "Server Database Server Name" -- SQL server name; "Server Database Log Path", "Server Database Path" -- paths to DB files on remote SQL server
  15. In HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Adamm you must create two keys: "Database Server Name" and "Database Instance Name" 
  16. In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BackupExecDeviceMediaService\DependOnService remove MSSQL line
  17. Uninstall MSSQL Express from new machine
  18. REBOOT!
  19. After restart all services should work fine

And that`s it. However, this guide worked for our simple installation with no clusters or complicated media services installed, so your experience may and will be slightly different.

More information on migrating can be found here  

Finally, some tips you should keep in mind:

  • Remote SQL and local MSSQL express installations MUST be of the same version (2005 or 2008); edition type doesn't matter
  • If our Remote SQL server is 2008 then you MUST install SQL 2008 Express to new machine prior step 2 and use it when asked in installer.
  • If our remote SQL installation is not on default Instance than appropriate registry settings shouldn't be empty  
  • When creating and moving BEDB database files MUST be named "bedb_dat.mdf" and "bedb_log.ldf", otherwise Media Service won't start at all
  • You can copy Catalog data to new machine or you can simply regenerate it later