Migrating on distributed systems

Edit online

Migrate to Copy Services Manager on distributed systems by running the installation setup file that is provided with your license.

Before you begin

You need to issue the mkbackup command on the existing Tivoli® Storage Productivity Center for Replication or Copy Services Manager server before you start the migration. The name of the compressed (.zip) file that is created by the mkbackup command is used during the migration to identify the path to the backup archive file. The Copy Services Manager migration function uses the information in the backup file to load in all storage system connections, session configurations, and so on.

You can view the mkbackup topic for more information. For more information on the mkbackup command, see the IBM® Copy Services Manager online product documentation (http://www-01.ibm.com/support/knowledgecenter/SSESK4).

Starting with Copy Services Manager version 6.1.2, you can also use the GUI to issue a backup. In the Copy Services Manager GUI, go to Settings > Advanced Tools, and find the Create Backup section to proceed.

About this task

The following steps are used to migrate from Tivoli Storage Productivity Center for Replication to Copy Services Manager, or to migrate from one Copy Services Manager server to another.

Procedure

  1. Run the installation setup file.
    Silent migration: You can also migrate by using the silent installation, by inserting CSM_BACKUP in the response file. See Installing on distributed systems for details.
  2. On the Choose Installation Method page, select Migrate/Restore using existing backup.
  3. Identify the path to the backup archive file that is created by the mkbackup command, or by creating the backup file from the GUI.
  4. Click Validate to verify that the selected backup archive file is valid.
  5. Click Next to enter other installation details and complete the migration to Copy Services Manager.