Upgrading on z/OS

Edit online

You can upgrade from Tivoli® Storage Productivity Center for Replication to Copy Services Manager on z/OS, or you can upgrade Copy Services Manager from a different version.

Upgrading from Tivoli Storage Productivity Center for Replication to Copy Services Manager

Edit online

Before you begin

During the upgrade, the Tivoli Storage Productivity Center for Replication 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.

See your Tivoli Storage Productivity Center for Replication product documentation for instructions on how to set up a standby management server if you do not have one already.

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. The standby management server continues to manage sessions during the upgrade process, which ensures disaster recovery capability and minimizes downtime if the upgrade fails.

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 Tivoli Storage Productivity Center for Replication only for monitoring purposes and are not managing sessions. If you use this method, it is more difficult to restore your Tivoli Storage Productivity Center for Replication configuration if the upgrade fails.

Note: When you upgrade from Tivoli Storage Productivity Center for Replication to Copy Services Manager, the port assignments are not preserved unless you set them in IWNINSTL before the upgrade. For more information, see Configuring the IWNINSTL job.

About this task

To upgrade from Tivoli Storage Productivity Center for Replication to Copy Services Manager on z/OS, ensure that all Copy Services Manager installation and postinstallation tasks are complete. When you run the IWNINSTL script, all optional values can be updated, including port assignments and the time zone designation. There are two new values in the IWNINSTL script for this type of upgrade:

TPCR_ProductionRoot=path_prefix/opt/Tivoli/RM: Specifies the production root that was used when Tivoli Storage Productivity Center for Replication was installed. Update this path to indicate what directory path for Copy Services Manager to use for the upgrade.
KEEP_TPCR (optional) TRUE/FALSE: Default is KEEP_TPCR=false. If set to true, when you upgrade from Tivoli Storage Productivity Center for Replication to Copy Services Manager, the TPCR directory structure is not deleted.

After you process the IWNINSTL script, and you start IWNSRV and IWNAUTH, Copy Services Manager is accessible at: https://<host name>:<GUI_PORT>/CSM/

To upgrade from Tivoli Storage Productivity Center for Replication to Copy Services Manager 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

Verify that the synchronization of the standby server is complete and that the Tivoli Storage Productivity Center for Replication sessions are not in a transitory state, such as Preparing, Suspending, or Recovering.
Move the management of the Tivoli Storage Productivity Center for Replication on the secondary server by issuing the Takeover command.
On the primary server, remove the secondary standby server from the HA relationship definition. The active Tivoli Storage Productivity Center for Replication on the secondary server continues to manage sessions during the upgrade process on the primary server.
Stop Tivoli Storage Productivity Center for Replication on the primary server.
Install Copy Services Manager Version 6.1 or later on the primary server by using the SMP/E tool for installing and maintaining software on z/OS systems.

Note: For more information, see the IBM Program Directory for Copy Services Manager for z Systems® or the IBM Program Directory for Copy Services Manager Basic Edition for z Systems.
Complete the postinstallation steps for z/OS® after you install IBM® Copy Services Manager. Before you run the IWNINSTL script, update it to use the value TPCR_ProductionRoot (optionally use KEEP_TPCR). For more information, see Postinstallation tasks for IBM Z.
When the sessions are not in a transitory state, start Copy Services Manager on the primary server. Verify that it shows all sessions in the same state as they were before the upgrade.
Repeat steps 4 through 7 that were completed on the primary server, but now perform them on the secondary server.
Reestablish the high availability (HA) relationship that was originally set up between the primary and secondary servers.

Results

When all of these tasks are finished, the upgrade from Tivoli Storage Productivity Center for Replication to Copy Services Manager is complete.

Upgrading from a different version of Copy Services Manager

Edit online

Before you begin

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

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

For more information on setting up a standby management server, see 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 z/OS 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

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.
Move the management of the Copy Services Manager to the standby on the secondary server by issuing the Takeover command.
On the primary server, remove the secondary standby server from the HA relationship definition. The active Copy Services Manager on the secondary server continues to manage sessions during the upgrade process on the primary server.
Stop Copy Services Manager on the primary server.
Upgrade the primary server to Copy Services Manager Version 6.1 or later by using the SMP/E tool for installing and maintaining software on z/OS systems.

Note: For more information, see the IBM Program Directory for Copy Services Manager for z Systems or the IBM Program Directory for Copy Services Manager Basic Edition for z Systems.
Run the IWNINSTL job again to complete the upgrade on the primary server. For more information, see Configuring the IWNINSTL job.

Note: For information on other postinstallation steps for z/OS after Copy Services Manager is installed or upgraded, see Postinstallation tasks for IBM Z. The only postinstallation step that is required for an upgrade is IWNINSTL. The other steps were run for the previous installation. However, if you want to change your RACF configuration, then you can update and run the RACF jobs.
When the sessions are not in a transitory state, start Copy Services Manager on the primary server. Verify that it shows all sessions in the same state as they were before the upgrade.
Repeat steps 4 through 7 that were completed on the primary server, but now perform them on the secondary server.
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.