Skip to main content

We've Moved!

Product Documentation has moved to
Hitachi Vantara Knowledge

Data migration

You can use TrueCopy to migrate data from one storage system to another.

Migration overview

TrueCopy can be used to move data from one volume to another.

You do not need to use host migration software for data migration when using TrueCopy. Also, TrueCopy data migration does not affect the host.

In a data migration, the entire contents of a volume are copied to the secondary volume (P-VOL to S-VOL). The volumes are identical when the copy operation completes. The volumes are then usually released from the TrueCopy pair.

If you need to migrate data from other vendors' storage system, contact customer support.

Migrating data

You typically migrate data to copy data to a new volume, to temporarily move data from an LU to accommodate other activities (for example, to make repairs), or to relocate LUs in order to balance workloads and distribute I/O activity evenly within or across storage systems.


  1. Make sure that the data path is installed, and TrueCopy configuration procedures are completed.

  2. Verify the target volume (S-VOL) is offline from all attached hosts. The source volume (P-VOL) can remain online.

  3. (VSP 5000 series) Connect to the storage system that contains the volume to be migrated, and then start Device Manager - Storage Navigator.

    Set a data path, change the port attribute to Bidirectional, and then register the target storage system.

    (VSP G/F350, G/F370, G/F700, G/F900, VSP E series) Add a remote connection in a storage system that contains the volume to be migrated, and then register storage systems in the secondary site.

  4. In the Create Pairs window of HDvM - SN, create a TrueCopy pair.

    You can perform this task using the paircreate command of CCI.
  5. When pair status changes to PAIR, the operation is completed.

    You can monitor the progress of the operation from the Remote Replication window of HDvM - SN.

    To perform this task in CCI, use the pairdisplay command.

  6. If you use CCI commands to migrate data, first delete the TC pair by the pairsplit command, then reset the pair in the reverse direction by specifying the -f never option of the paircreate command.

  7. If you are not using CCI commands and host software to complete the migration, continue the following procedure to stop using the P-VOLs and switch to the S-VOLs:

    1. Stop all host updates to the P-VOLs.

    2. When all update activity to the P-VOLs has stopped, connect to the primary system, select the correct CU, and release the TrueCopy pairs.

    3. If the P-VOL and S-VOL are attached to the same host, vary the P-VOL offline, and then vary the S-VOL online. Use this order because the P-VOL and S-VOL have the same volume labels and cannot be online to the same host at the same time.

    4. If you want to keep the volumes synchronized, establish the same TrueCopy pairs in the reverse direction using the None initial copy option. If the original P-VOLs will be temporarily unavailable for update copy operations, you can split the new pairs (pairsplit-r) so that the new primary system keeps track of changes.

    5. Start the applications with the S-VOLs. When the original P-VOLs become available, you can resynchronize the pairs.


If the original P-VOL is temporarily unavailable for update copy operations, split the new pair so that the new primary system keeps track of changes.