Upgrading on distributed systems

You can upgrade Copy Services Manager to a different version by running the latest installation setup file.

Before you begin

During the upgrade, the Copy Services Manager management server is not available. Therefore, the capability for disaster recovery during the upgrade process is not available unless you establish a high-availability environment. A high-availability environment includes an active and standby management server.

If you want to maintain disaster recovery capability, you must complete the steps to perform a takeover on the standby management server before you upgrade the active management server. At this stage, the active and standby management servers must be on the same level. The standby management server continues to manage sessions during the upgrade process, which ensures disaster recovery capability and minimizes downtime if the upgrade fails.

For more information on setting up a standby management server, see the IBM Copy Services Manager User's Guide chapter titled "Managing management servers."

If you do not want to maintain disaster recovery capability during the migration process, a standby management server is not required. In general, this migration method is used only if you are using Copy Services Manager only for monitoring purposes and are not managing sessions. If you use this method, it is more difficult to restore your Copy Services Manager configuration if the upgrade fails.
Note: When you upgrade to a newer version of Copy Services Manager, the port assignments are preserved as they were before the upgrade.

About this task

To upgrade Copy Services Manager on a distributed system while you maintain disaster recovery capability, complete all of the following steps. To upgrade without maintaining disaster recovery capability, complete steps 4, 5, 6, and 7.

Procedure

  1. Verify that the synchronization of the standby server is complete and that the Copy Services Manager sessions are not in a transitory state such as Preparing, Suspending, or Recovering.
  2. Move the management of the Copy Services Manager to the secondary server by issuing the Takeover command while it has the standby role. After the takeover, the primary server is removed and Copy Services Manager on the secondary server has an active role. Note that because the secondary server is now active, any enabled scheduled tasks will automatically start running from the secondary server.
  3. After the Takeover is issued on the secondary server, the primary server will attempt to automatically reconnect to the secondary. When the primary server sees that a Takeover was issued on the secondary, it will immediately enter a Standby mode. This Standby mode will prevent the primary server from running any enabled Scheduled Tasks and all session management will be run from the secondary, now active, server.
  4. On the primary server, run the installation setup file for the version to which you are upgrading.
    Note: During an upgrade of Copy Services Manager, you are not presented with the Select Installation Type page that is displayed during an initial installation, or a migration or restoration from a backup.
  5. The Upgrade IBM Copy Services Manager page displays the currently installed version and the version that you will upgrade to. Click Next to continue the upgrade.
  6. On the Software License Agreement page, agree to the terms and click Next.
  7. The Pre-installation Summary page is displayed. Click Next to complete the upgrade on the primary server.
  8. Verify that the upgraded primary server restarted Copy Services Manager and the version indicates it is now running at the new level.
    Note: The primary server will still be in a Standby mode after the upgrade completes.
  9. From the primary server issue the Takeover command. This will make the primary server an active server again. Validate that all session information and states are correct after the upgrade.
    Note: Once the Takeover is complete, both the primary and secondary servers may run any enabled scheduled tasks. To avoid this you can choose to manually shut down the secondary server while you validate the upgrade on the primary server was successful
  10. Repeat steps 4 through 7 that were completed on the primary server, but now perform them on the secondary server.
  11. Reestablish the high availability (HA) relationship that was originally set up between the primary and secondary servers.

Results

When all tasks are finished, the upgrade from a previous version of Copy Services Manager is complete.