Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Backup and Recovery Community Blog

Refer this Tip If you faced Error during (Unable to prep database instances for upgrade)

Created: 07 Oct 2010 • 1 comment
Mahesh Roja's picture
-2 2 Votes
Login to vote

 

Refer this Tip If you faced Error during (Unable to prep database instances for upgrade)Upgrade from Backup Exec 2010 to 2010 R2

 

  1. Read ou the SCL list from Symantec site before start migrating.
  2. Back up all your data: in SQL server an your backup server.
  3. Prepare new OS and install there Backup Exec 2010 with default preferences (it installs local MSSQL 2005 Express).
  4. Stop Backup Exec services on old machine and on new machine.
  5. Copy DB(through Backup-Restore or Detach-Attach) from remote server to your local MSSQL installation on new machine.
  6. Edit tables [Device] and [DataPartition] and change old machine name to new one there.
  7. Delete in registry HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DataPartitionGUID key.
  8. Launch services on new machine, they shoud start up and you can see all you tasks, devices and media.
  9. If all seems to work than you can begin upgrade process.
  10. Run Backup Exec 2010 R2 installer. 
  11. After it completes check again your system and backup processes.
  12. Finally, the last step: migrate to remote SQL server.
  13. Stop Backup Exec services on new machine.
  14. Edit Registry settings:
  15. 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.
  16. In HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Adamm you must create two keys: "Database Server Name" and "Database Instance Name" .
  17. In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BackupExecDeviceMediaService\DependOnServiceremove MSSQL line.
  18. Uninstall MSSQL Express from new machine.
  19. REBOOT!
  20. 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.

 Note : Few things need to keep in mind

  1. Remote SQL and local MSSQL express installations MUST be of the same version (2005 or 2008); edition type doesn't matter.
  2. 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.
  3. If our remote SQL installation is not on default Instance than appropriate registry settings shouldn't be empty  
  4. 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
  5. You can copy Catalog data to new machine or you can simply regenerate it later

Comments 1 CommentJump to latest comment

CraigV's picture

...not that this matters much, but the guy above plagiarised this directly from the OP's solution below:

https://www-secure.symantec.com/connect/forums/upgrade-backup-exec-2010-r2-fails

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

+3
Login to vote