How to upgrade and migrate (move) Backup Exec 11d/12.0/12.5 standard, CASO and SAN/SSO environments to Backup Exec 2010 with a different server name and version of Windows (automatic and manual upgrade options)

Article:TECH137015  |  Created: 2010-01-26  |  Updated: 2011-01-18  |  Article URL http://www.symantec.com/docs/TECH137015
Article Type
Technical Solution


Issue



How to upgrade and migrate (move) Backup Exec 11d/12.0/12.5  standard, CASO and SAN/SSO environments to Backup Exec 2010 with a different server name and version of Windows (automatic and manual upgrade options)

Solution



 AUTOMATIC LOCAL UPGRADE WITH MANUAL MIGRATION OF BACKUP EXEC

1.    Prepare the original 11d/12.0/12.5 server
Complete a backup of the local media server
If CASO environment, make each MMS and the CAS a stand alone
If SSO environment, uninstall the SSO option
 
2.    Use the Backup Exec 2010 installation to upgrade
http://www.symantec.com/docs/HOWTO22461  - About upgrading from previous versions of Backup Exec
http://www.symantec.com/docs/TECH137024  - How to: Direct upgrade path from Backup Exec 11d, 12.0 or 12.5 for Windows Servers to Backup Exec 2010
http://www.symantec.com/docs/TECH74415  - How to: Multi-step upgrade path from Backup Exec 10.x for Windows Servers to Backup Exec 2010
http://www.symantec.com/docs/TECH74418  - How to: Multi-step upgrade path from Backup Exec 9.x for Windows Servers to Backup Exec 2010
 
3.    Reboot the original server (required)
 
4.    Stop all of the Backup Exec services on the original server (including the SQL(BKUPEXEC) service)
 
5.    Install Backup Exec 2010 on the new server and run LiveUpdate to ensure the latest patches/hotfixes are installed
http://www.symantec.com/docs/HOWTO31075  - Installing a typical installation of Backup Exec
http://www.symantec.com/docs/TECH124432  - Step By Step guide to download and install Backup Exec 2010
NOTES: 
                  i.    Remember to use the same account for the new installation as the original
                ii.    Do NOT install or configure CASO or SSO yet
 
6.    Reboot the new server (required)
 
7.    Stop all of the Backup Exec services on the new server (including the SQL(BKUPEXEC) service)
 
8.    Copy the DATA folder from the original 11d/12.0/12.5 server to the new Backup Exec 2010 desktop
 
9.    Copy the CATALOGS folder from the original 11d/12.0/12.5 server to the new Backup Exec 2010 installation directory. Example: <volume>:\Program Files\Symantec\Backup Exec
 
10. On the new 2010 server, use BEUtility to copy the upgraded 11d/12.0/12.5 database into the new 2010 installation
 
11. All of the Backup Exec services should be started
 
12. Open the Backup Exec console and confirm all jobs/history/settings have upgraded and migrated correctly
NOTE: Shared storage devices will need to be manually created for the new Backup Exec 2010 server
 
*At this point, remote agents can be installed/updated as well as additional options like CASO and SSO on the new 2010 server.
 
ADDITIONAL ISSUES EXPERIENCED AFTER THIS TYPE OF UPGRADE AND MIGRATION:
1.    The original server name and it's devices show offline in the Devices tab
a.    Right-click each offline device and select delete and then right-click and delete the server name
2.    Restore selections are blank
3.    Console fails to load and give "Specified cast is not valid"
 
 
 
 
MANUAL MIGRATION THEN UPGRADE OF BACKUP EXEC
 
1.    Prepare the original 11d/12.0/12.5 server
Complete a backup of the local media server
If CASO environment, make each MMS and the CAS a stand alone
If SSO environment, uninstall the SSO option
 
2.    Install Backup Exec 2010 on the new server and run LiveUpdate to ensure the latest patches/hotfixes are installed
http://www.symantec.com/docs/HOWTO31075 - Installing a typical installation of Backup Exec
a.    http://www.symantec.com/docs/TECH124432  - Step By Step guide to download and install Backup Exec 2010
NOTES: 
                  i.    Remember to use the same account for the new installation as the original
                ii.    Do NOT install or configure CASO or SSO yet
 
3.    Stop all of the Backup Exec services on the new 2010 server (including the SQL(BKUPEXEC) service)
 
4.    Open the registry and make the following changes:
a.    Navigate to HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\13.0\Install
b.    Create (if necessary) and modify the values of the following keys:
                  i.    DWord = Upgrade and change the value to 1 (32-bit servers)
                ii.    QWord = Upgrade and change the value to 1 (64-bit servers)
               iii.    String Value = Upgrade Version and change the value to the version you are upgrading from:
BE Version
Registry key value
11d 6235 11.0.6235.0
11d 7070
11.0.7170.0
12
12.0.1364.0
12.5
12.5.2213.0

              Refer to the full BEMig document for the most updated version list.  http://www.symantec.com/docs/TECH50537  

5.    Stop all of the Backup Exec services on the original 11d/12.0/12.5 server (including the SQL(BKUPEXEC) service)
 
6.    On the original 11d/12.0/12.5 server, copy the DATA and CATALOGS folders to the desktop of the new 2010 server
 
7.    On the new 2010 server, copy the bedb_dat.bak and bedb_log.bak from <volume>:\Program Files\Symantec\Backup Exec\Data into the DATA folder on the desktop
NOTE: When prompted by Windows, select the option to copy and replace the old 11d/12.0/12.5 bedb_dat.bak and bedb_log.bak files
 
8.    Copy the DATA and CATALOGS folder from the desktop to the new Backup Exec 2010 installation directory. 
Example: <volume>:\Program Files\Symantec\Backup Exec
 
9.  Start ONLY the SQL(BKUPEXEC) service
 
10. Open a command prompt and complete the following to change the name of the server in the Backup Exec database (BEDB)
a.    Change the directory to C:\
b.    Type sqlcmd -E -S new_server_name\BKUPEXEC <press enter>
c.    At the 1> prompt, type use bedb <press enter>
d.    At the 2> prompt, type go <press enter>
e.    At the next 1> prompt, type select partitionname from datapartition <press enter>
f.     At the next 2> prompt, type go <press enter>
NOTE: This will show the original 11d/12.0/12.5 server name
g.    At the next 1> prompt, type update datapartition set partitionname = 'new_server_name' where partitionid = 0 <press enter>
h.    At the next 2> prompt, type go <press enter>
i.      At the next 1> prompt, type select partitionname from datapartition <press enter>
j.      At the next 2> prompt, type go <press enter>
NOTE: This should now show the new 2010 server name
k.    At the next 1> prompt, type Exit
 
11. Leaving the command prompt open, complete the following to manually upgrade the database from 11d/12/12.5
a.    Change the directory to <volume>:\Program Files\Symantec\Backup Exec
b.    Type bemig <press enter>
c.    Close the command prompt when the bemig completes
 
12. Stop the SQL(BKUPEXEC) service
 
13. Copy the bedb_dat.mdf and bedb_log.ldf from <volume>:\Program Files\Symantec\Backup Exec\Data to the desktop
 
14. Use BEUtility to copy the upgraded 11d/12.0/12.5 database into the new 2010 installation
 
15. All of the Backup Exec services should be started
 
16.Open the Backup Exec console and confirm all jobs/history/settings have upgraded and migrated correctly
NOTE: Shared storage devices will need to be manually created for the new Backup Exec 2010 server
 
*At this point, remote agents can be installed/updated as well as additional options like CASO and SSO on the new 2010 server.
 
ADDITIONAL ISSUES EXPERIENCED AFTER THIS TYPE OF UPGRADE AND MIGRATION:
1.    The original server name and it's devices show offline in the Devices tab
a.    Right-click each offline device and select delete and then right-click and delete the server name
2.    Restore selections are blank
3.    Console fails to load and give "Specified cast is not valid"

 




Legacy ID



358100


Article URL http://www.symantec.com/docs/TECH137015


Terms of use for this information are found in Legal Notices