Migrating a Backup Exec Central Administration Server to new hardware.

Article:TECH178277  |  Created: 2012-01-04  |  Updated: 2014-10-29  |  Article URL http://www.symantec.com/docs/TECH178277
Article Type
Technical Solution


Issue



 Migrating a Backup Exec Central Administration Server (CASO Server) to new hardware.


Environment



Backup Exec 12.5
Backup Exec 2010
Backup Exec 2012


Solution



The information in this document provides instructions on how to migrate a central administration server to new hardware.
 

Do not follow the instructions in this document if any of the following are true: 

  • Backup Exec is clustered.
  • The Backup Exec Shared Storage Option (SSO) is installed. 
  • The Backup Exec Server Free Option is installed.
  • You are planning to move Backup Exec to a different drive/directory on the server.
  • You are upgrading from one version/revision (build) of Backup Exec to another.
     

Note: If any of the above mentioned conditions are true, this procedure cannot be performed and Backup Exec will need to be re-installed and re-configured. 
 

Note: When moving from a 32-bit system to a 64-bit system, Symantec recommends that you upgrade on the 32-bit system first and then follow the instructions in this document.
 

When you set up the new server, you can either retain the name of the old server or use a different server name. However, you cannot move deduplication storage folders or Archive Option databases and configuration information if the new server’s name is different. Symantec recommends that you retain the original server name for the best compatibility.
 

Important Note: Do not remove Backup Exec from the original computer until the migration of data and media to the new Backup Exec media server is complete. It must be verified that the new Backup Exec installation matches the original installation.


To migrate a central administration server to new hardware:
 

  1. Obtain your current Backup Exec version and revision number.
        a. On the Help menu, select About Symantec Backup Exec.
        b. Write down the version and revision number.
     
  2. Install all of the current updates for your current version of Backup Exec. 
        a. On the Tools menu, select LiveUpdate.
     
  3. Determine the options, license keys, and installation path that you are using for the current version of Backup Exec.
        a. On the Tools menu, select Install Options and License Keys on this Media Server.
        b. Click Next until you reach the Enter License Keys panel.
        c. Write down the license keys.
        d. Click Next until you reach the installation path panel.
        e. Write down the installation path.
         f. Cancel the installation.
     
  4. Determine the path for all backup-to-disk folders and for deduplication storage folders (if you use the Deduplication Option).
        a. On the navigation bar, click Devices.
        b. Right-click a backup-to-disk folder or deduplication storage folder, and then select Properties.
        c. Write down the path.
        d. Repeat steps 'a' through 'c' for each device.
     
  5. Use the Windows Services applet to stop the following Backup Exec services.
        a. Backup Exec Agent Browser
        b. Backup Exec Device and Media Service
        c. Backup Exec Job Engine
        d. Backup Exec Remote Agent for Windows Servers
        e. Backup Exec Server
     
  6. Use the Windows Services applet to stop the Backup Exec SQL service that the Backup Exec database is using.
        a. SQL Server (BKUPEXEC) is the SQL Express instance.
        b. SQL Server (MSSQLSERVER) is the local or remote SQL Server instance. This is the default instance. It can be a SQL 2000, SQL 2005, or SQL 2008 instance.
        c. SQL Server (instance name) is the local or remote SQL Server named instance. It can be a SQL 2000, SQL 2005, or SQL 2008 instance.
     
  7. Use Windows Explorer to copy the following Backup Exec directories to a temporary location. Keep the directories separate.
        a. C:\Program Files\Symantec\Backup Exec\Data 
            Warning: Do not copy the msgq*.*.dat files to the temporary location.
        b. C:\Program Files\Symantec\Backup Exec\Catalogs 
            Note: Copy the Catalogs folder for each managed media server. These folders should be listed under the Catalogs folder.
        c. C:\Program Files\Symantec\Backup Exec\IDR (if present)
        d. C:\Program Files\Symantec\Backup Exec\Reports\Saved
        e. Backup-to-disk folders (if present)
     
  8. On the new server, install the same version and revision of Backup Exec that is installed on the original Backup Exec media server. If you are migrating from a 32-bit server to a 64-bit server, use the 64-bit version of the installation media.

    Note: When you are prompted for license keys and the installation path, use the same license keys and installation path from the original Backup Exec media server. You obtained these items in step 3.

    Note: You can change the SQL install path. If the Backup Exec database was installed to a SQL Express instance, the database can be moved to another SQL instance. The database files can be moved to any SQL 2000, 2005, or 2008 instance as long as the database files are being moved to the same or newer version of SQL.
     
  9. Restart the computer. Do not open Backup Exec after the computer restarts.
     
  10. Install all of the Backup Exec updates that are available for the version of Backup Exec that you installed. 
     
  11. Restart the computer. Do not open Backup Exec after the computer restarts.
     
  12. On the new server, stop the Backup Exec services, and then stop the SQL service.
     
  13. Copy the Backup Exec files from the temporary directories. This will overwrite the data, catalogs, and IDR folders on the new server.
     
  14. On the new server, create a folder where the new backup-to-disk folders will reside. Copy the saved .bkf files from the temporary location to this folder.
     
  15. If you are moving the installation to a server with a different computer name, do the following to rename the DataPartition name for the Backup Exec database that was copied. If the new server has the same name as the original server, skip to step 16.
        a. Start the SQL Server service or the SQL service where Backup Exec is installed.
        b. From a command prompt, type Sqlcmd –E –S servername\instance name.
        c. Run the following query from either Sqlcmd or from the SQL Managed tools:
                i.   Use bedb
                ii.  <Press Enter>
                iii.  Type go
                iv.  <Press Enter>
                v.   SELECT PartitionName FROM DataPartition
                vi.  <Press Enter>
                vii.  Type go
                vii.  <Press Enter>
        d. Run the following command to change the original server name to the new server name:
                i.   UPDATE DataPartition SET PartitionName=’<this server name>’ WHERE PartitionID=0
                ii.  <Press Enter>
                iii.  Type go
                iv.  <Press Enter>
        e. Run the following command to verify that the name was changed:
                i.   SELECT PartitionName FROM DataPartition
                ii.  <Press Enter>
                iii.  Type go
                iv.  <Press Enter>
                v.   Type quit to exit Sqlcmd.

    Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Registry modification should be performed only by someone who is experienced in the use of the registry editor. Symantec recommends that you back up the registry and the server before you make any registry changes.

        f. Edit the registry key HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server, and then delete the following keys: DataPartitionGUID and DataPartitionID.
     
  16. Start all Backup Exec services. 
     
  17. Start Backup Exec and verify that the data was move correctly.
        a.  Verify that jobs, selection lists, policies, alerts, and job history are correct.
     
  18. Delete the older server and its devices.
        a.  On the navigation bar, select Devices.
        b.  Right-click the old server name, and then select Delete.
     
  19. Move all offline media that will no longer be used to the retired media set.
     
  20. Create a new folder for the backup-to-disk media and configuration files.
     
  21. Copy the backup-to-disk media from the temporary location to the folder that you created in step 20.
     
  22. Create the backup-to-disk folder and use the path of the new folder.
     
  23. If the previous central administration server was backed up to itself and the new central administration server has a new name, you must change the selection list on the new central administration server. 
     
  24. On each remote computer that is backed up, run vxmon.exe to update the publishing information.
        a.  Open C:\Program Files\Symantec\Backup Exec for Windows\RAWS\Vxmon.exe
        b.  On the Publishing tab, add the new server and remove the old server (if it is listed).
     
  25. On the managed media server, navigate to the folder where the msgq files are located, and then delete the current msgq files.
    Note: The default location for the msgq files is C:\Program Files\Symantec\Backup Exec\Data.
     
  26. On the managed media server, do one of the following to enable communication with the new central administration server:
        a.  If the new central administration server has the same name as the old server:
             Start the services on the managed media server, and then proceed to step 27.
             The managed media server should be online and ready to be managed by the new central administration server.

        b.  If the new central administration server has a new name, you must change the following registry keys:

    Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Registry modification should be performed only by someone who is experienced in the use of the registry editor. Symantec recommends that you back up the registry and the server before you make any registry changes.

    Note: If the managed media server is not sharing the database on the central administration server, then changing the ADAMM registry key should not be necessary.
     
    • HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\ - Change the Database Server Name key to the new server name. If the instance name has changed, then also change the Database Instance Name key to the new instance name. If the old server used a named SQL instance, but the new server now uses a default instance, then the instance name should be removed from the instance name key.
    • HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server – Change the DjmPrimaryServer key to the name of the new server. 
       
  27. Start all of the Backup Exec services on the managed media servers.
     
  28. Inventory and catalog all media on the central administration server.
     
  29. Review the restore selections to verify that the media from the managed Backup Exec servers appears. If the media does not appear, then inventory and catalog the media on the managed Backup Exec server. 

 




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


Terms of use for this information are found in Legal Notices