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