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

Article:TECH148403  |  Created: 2011-01-18  |  Updated: 2013-08-23  |  Article URL http://www.symantec.com/docs/TECH148403
Article Type
Technical Solution

Product(s)

Issue



How to upgrade and migrate (move) Backup Exec 11d/12.0/12.5/2010 Standard, CASO and SAN/SSO environments to Backup Exec 2010 R2 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/2010 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

    http://www.symantec.com/docs/HOWTO23417

     
  2. Use the Backup Exec 2010 R2 installation to upgrade

    http://www.symantec.com/docs/HOWTO22461 - About upgrading from previous versions of Backup Exec

    http://www.symantec.com/docs/TECH148394 - How to: Direct upgrade path from Backup Exec 11d/12.0/12.5/2010 to Backup Exec 2010 R2

    http://www.symantec.com/docs/TECH74415 - How to: Multi-step upgrade path from Backup Exec 10.x for Windows Servers to Backup Exec 2010 or 2010 R2

    http://www.symantec.com/docs/TECH74418 - How to: Multi-step upgrade path from Backup Exec 9.x for Windows Servers to Backup Exec 2010 or 2010 R2

     
  3. Reboot the original server (required)
     
  4. Stop all of the Backup Exec services on the original server (including the SQL SERVER (BKUPEXEC) service)
     
  5. Install Backup Exec 2010 R2 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/TECH138264 - Step By Step guide to download and install Backup Exec 2010

    NOTES:

    • Remember to use the same account for the new installation as the original
       
    • 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 SERVER (BKUPEXEC) service)
     
  8. Copy the DATA folder from the original 11d/12.0/12.5/2010 server to the new Backup Exec 2010 R2 desktop
     
  9. Copy the CATALOGS folder from the original 11d/12.0/12.5/2010 server to the new Backup Exec 2010 R2 installation directory.

    Example: <volume>:\Program Files\Symantec\Backup Exec

  10. On the new 2010 R2 server, use BEUtility to copy the upgraded 11d/12.0/12.5/2010 database into the new 2010 R2 installation

    http://www.symantec.com/docs/TECH49757
     
  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 R2 server

    *At this point, remote agents can be installed/updated as well as additional options like CASO and SSO on the new 2010 R2 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

    • Right-click each offline device and select delete and then right-click and delete the server name  
       
  2. Restore selections are blank
     
    http://www.symantec.com/docs/TECH60830
     
  3. Console fails to load and give "Specified cast is not valid"

    http://www.symantec.com/docs/TECH141925

     

 

 

MANUAL MIGRATION THEN UPGRADE OF BACKUP EXEC

 

  1. Prepare the original 11d/12.0/12.5/2010 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

    http://www.symantec.com/business/support/index?page=content&id=HOWTO23417
     
  2. Install Backup Exec 2010 R2 on the new server and run LiveUpdate to ensure the latest patches/hotfixes are installed

    http://www.symantec.com/business/support/index?page=content&id=HOWTO31075 - Installing a typical installation of Backup Exec

    http://www.symantec.com/docs/TECH138264 - Step By Step guide to download and install Backup Exec 2010 R2

    NOTES:

    • Remember to use the same account for the new installation as the original

       
    • Do NOT install or configure CASO or SSO yet

       
  3. Stop all of the Backup Exec services on the new 2010 R2 server (including the SQL SERVER (BKUPEXEC) service)

     
  4. Open the registry and make the following changes:

    • Navigate to HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\13.0\Install
       
    • Create (if necessary) and modify the values of the following keys:

      • DWord = Upgrade and change the value to 1 (32-bit servers)
         
      • QWord = Upgrade and change the value to 1 (64-bit servers)
         
      • Upgrade Version and change the value to the version you are upgrading from:
         

    BE Version

    Registry key value

    11d

    11.0.7170

    12

    12.0.1364

    12.5

    12.5.2213

    2010

    13.0.2896.0


     
  5. Stop all of the Backup Exec services on the original 11d/12.0/12.5/2010 server (including the SQL SERVER (BKUPEXEC) service)

     
  6. On the original 11d/12.0/12.5/2010 server, copy the DATA and CATALOGS folders to the desktop of the new 2010 R2 server

     
  7. On the new 2010 R2 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/2010 bedb_dat.bak and bedb_log.bak files

     
  8. Copy the DATA and CATALOGS folder from the desktop to the new Backup Exec 2010 R2 installation directory.

    Example: volume>:\Program Files\Symantec\Backup Exec

     
  9. Start ONLY the SQL SERVER (BKUPEXEC) service

     
  10. Open a command prompt and complete the following to change the name of the server in the Backup Exec database (BEDB)

    1. Change the directory to C:\

       
    2. Type sqlcmd -E -S new_server_name\BKUPEXEC <press enter>

       
    3. At the 1> prompt, type use bedb <press enter>

       
    4. At the 2> prompt, type go <press enter>

       
    5. At the next 1> prompt, type select partitionname from datapartition <press enter>

       
    6. At the next 2> prompt, type go <press enter>

      NOTE: This will show the original 11d/12.0/12.5/2010 server name

       
    7. At the next 1> prompt, type update datapartition set partitionname = 'new_server_name' where partitionid = 0 <press enter>

       
    8. At the next 2> prompt, type go <press enter>

       
    9. At the next 1> prompt, type select partitionname from datapartition <press enter>

       
    10. At the next 2> prompt, type go <press enter>

      NOTE:This should now show the new 2010 R2 server name

       
    11. 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/2010

    • Change the directory to <volume>:\Program Files\Symantec\Backup Exec

       
    • Type bemig <press enter>

       
    • Close the command prompt when the bemig completes 

       
  12. Stop the SQL SERVER (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/2010 database into the new 2010 R2 installation

    http://www.symantec.com/docs/TECH49757

     
  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 R2 server

    *At this point, remote agents can be installed/updated as well as additional options like CASO and SSO on the new 2010 R2 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

    • 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"





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


Terms of use for this information are found in Legal Notices