Installing and Upgrading CA ARCserve Backup in a Cluster-aware Environment › Deploy CA ARCserve Backup Server on MSCS › Upgrade CA ARCserve Backup from r11.5 to r15 in an MSCS Cluster Environment

Upgrade CA ARCserve Backup from r11.5 to r15 in an MSCS Cluster Environment

This section describes the steps that you must perform to upgrade earlier software versions to the current release. Upgrade procedures differ depending on the software version you are upgrading:

• If you are upgrading BrightStor ARCserve Backup r11.5, including the latest services packs, in an MSCS cluster-aware environment, directly to CA ARCserve Backup r15, follow this procedure.
• If you are upgrading CA ARCserve Backup r12 or CA ARCserve Backup r12.5, including the latest service packs, in an MSCS cluster-aware environment, follow the steps in Upgrade CA ARCserve Backup from r12 and r12.5 to r15 in an MSCS Cluster Environment.

Before you begin, ensure you have read the information in Upgrade CA ARCserve Backup from a Previous Release.

When upgrading CA ARCserve Backup from r11.5 to r15 in an MSCS cluster environment, the following procedure must be performed to protect your clustered backup data. If you are not already using CA ARCserve Backup r11.5 in a cluster environment, you do not need to perform this procedure. The procedure supports the following CA ARCserve Backup r11.5 upgrade scenarios in an MSCS cluster environment:

• Primary server upgrade RAIMA to SQL Express
• Primary server upgrade RAIMA to SQL Server
• Primary server upgrade SQL Server to SQL Server
• Member server upgrade RAIMA to r15
• Member server upgrade SQL Server to r15

This upgrade procedure is assuming that you are operating in a two-node cluster environment, with Node A representing the initial Active Node and Node B representing the initial Passive Node.

To upgrade CA ARCserve Backup from r11.5 to r15 in an MSCS cluster environment

On Node A:

The following diagram provides a graphic overview of the initial tasks being performed for Node A during this upgrade procedure.

1. Delete the ARCserve cluster resources for r11.5 as follows:
   1. Access the Cluster Administrator.

      The Cluster Administrator dialog appears.

      Note: Cluster Administrator is a utility provided by Microsoft and is accessed from the Administrative Tools group of the Start menu.

   2. Select the ARCserve Group that the ARCserve server is deployed in, and locate the corresponding ARCserve cluster resources. Right-click on each ARCserve cluster resource and from the pop-up menu, select Delete.

   The ARCserve cluster resources for r11.5 are deleted.

2. Copy the CA ARCserve Backup r11.5 installation directory files into a temporary location.

   A backup copy of the CA ARCserve Backup r11.5 files is located in another location from the original files.

3. Perform CA ARCserve Backup r15 upgrade installation for Node A. See Upgrade CA ARCserve Backup from a Previous Release.

   Important! During the upgrade installation, you will be prompted to specify the installation path location for r15. Do not specify the same location where the r11.5 is currently located. To avoid difficulties during the upgrade and possible loss of information (job scripts saved in the queue), you must select a different location for the CA ARCserve Backup r15 installation.

   Results:

   • CA ARCserve Backup for Node A is upgraded from r11.5 to r15. Do not set up new ARCserve cluster resources at this time.
   • When the upgrade is complete, the Server Data Migration dialog appears. The Server Data Migration dialog allows you to migrate information stored in the previous ARCserve database into a new ARCserve database. Do not launch the data migration process at this time.

   Note: For primary server upgrades, the CA ARCserve Backup database engine must be manually started prior to migrating the data.

4. For primary server upgrades only, do the following:
   1. Open the Windows Computer Management console.
   2. Expand Services and Applications and then click Services.
   3. Right-click CA ARCserve Database Engine, and click Start on the pop-up menu.
   4. Right-click CA ARCserve Domain Server, and click Start on the pop-up menu.
   5. Right-click CA ARCserve Message Engine, and click Start on the pop-up menu.
   6. Close the Windows Computer Management console.

   Note: When CA ARCserve Backup services start, the corresponding status indicates Started.

5. Open the CA ARCserve Backup installation directory on the CA ARCserve Backup server.

   In the CA ARCserve Backup installation directory, locate and double-click servermigration.exe.

   The Server Data Migration dialog opens.

6. From the Server Data Migration dialog, click Start.

   The specified CA ARCserve Backup data is migrated from r11.5 to r15.

7. For SQL Express upgrades only. Using the Windows Service manager, right-click the SQLE instance (mssql$arcserve_db) and from the pop-up window, select Stop.

   When the SQLE instance is stopped, the corresponding status will become blank and no longer indicate Started.

8. For SQL Express primary server upgrades only. Copy the SQL ARCserve database directory (SQLASDB) into a temporary location.

   A backup copy of the SQLASDB directory is located in another location from the original directory.

9. Move the active node from Node A to Node B as follows:
   1. Access the Cluster Administrator.

      The Cluster Administrator dialog opens.

   2. Select the ARCserve Group for Node A. Right-click on the group name from the pop-up menu and select Move Group.
      • If there are only two nodes in the cluster, the active node status will automatically be transferred from the initial active node (Node A) to the other node (Node B) and making Node B the active node and Node A the passive node.
      • If there are more than two nodes in the cluster, a pop-up screen will appear, allowing you to select which node you want to transfer the active status to. When you select the node for transfer, the specified node will become the active node and the previously-selected node will become the passive node. Repeat this procedure for each node in the cluster.

On Node B:

The following diagram provides a graphic overview of the initial tasks being performed for Node B during this upgrade procedure.

1. Copy the CA ARCserve Backup r11.5 installation directory files from the temporary location back into the original location.

   The CA ARCserve Backup r11.5 files are now located back in the original location.

2. Uninstall CA ARCserve Backup r11.5 from Node B.

   CA ARCserve Backup r11.5 is uninstalled.

   Important! During the CA ARCserve Backup r15 new installation on Node B, do not select the "Overwrite DB" option to prevent overwriting the ARCserve database that was migrated during the r15 upgrade to Node A.

3. Perform CA ARCserve Backup r15 new installation for Node B with the same settings selected for Node A (domain name, server type, install path, installed options …). For example, if CA ARCserve Backup r15 was installed on Node A as a primary server, then r15 must be installed on Node B also as a primary server. See Install CA ARCserve Backup.

   CA ARCserve Backup r15 is installed on Node B. Do not set up new ARCserve cluster resources at this time.

4. Move the active node from Node B back to Node A as previously described.

   Node B is now the passive node and Node A is the active node.

On Node A:

The following diagram provides a graphic overview of the final tasks being performed for Node A during this upgrade procedure.

1. For SQL Express primary server upgrades only. Copy the SQL ARCserve database directory (SQLASDB) from the temporary location back into the original location.

   The backed-up copy of the SQLASDB directory replaces the SQLASDB directory created during the CA ARCserve Backup r15 installation.

2. From the command line console, run the "babha -postsetup" utility to set up new ARCserve cluster resources. The babha -postsetup utility is located in the %bab_home% directory.

   The new ARCserve cluster resources (ARCserve HA, ARCserve ASDB, ARCserve Registry, and ARCserve Share) are created.

   To ensure that all CA ARCserve Backup services start properly on the CA ARCserve Backup server, you must execute the cstop and cstart scripts on the CA ARCserve Backup server before you open the CA ARCserve Backup Manager Console. The cstop and cstart batch files are stored in the CA ARCserve Backup installation directory on the CA ARCserve Backup server. For more information about using cstop and cstart, see the Administration Guide.

Note: CA ARCserve Backup does not support recovering the CA ARCserve Backup database when the last backup of the CA ARCserve Backup database was completed before you upgraded to this release. As a best practice, you should back up the CA ARCserve Backup database as soon as possible after the upgrade is complete. For information about backing up the CA ARCserve Backup database, see the Administration Guide.