Copy export merge

Edit online

The copy export merge function allows a copy of selected virtual volumes that are stacked to tape to be merged into an existing TS7700 that already contains data and that may be part of a grid.

Copy export merge enhances the copy export function by expanding the range of possible restore points to include an existing TS7700 Cluster, regardless of whether that cluster is empty or part of an existing grid. Scenarios that would use this function include disaster recovery to an existing TS7700 Cluster, as well as moving content from one datacenter to another.
Note: A partial workload move (leaving some workload data behind) may not be recommended due to the complexities of host environment changes and source cleanup required.
The following restrictions apply:
  • You must coordinate with your IBM Service Representative to initiate a copy export merge operation. Recovery into a stand-alone, empty TS7700 Cluster is still supported without additional IBM coordination.
  • Only virtual volumes targeting the copy export recovery pools are restored, unless you use the option to restore an entire TS7700 Cluster.
    Note: An option is available to restore the entire contents of a TS7700 Cluster independent of whether all source data existed in a copy export pool at the time of export. At least one copy export tape is required to provide the database that defines all tapes previously contained within the source TS7700 Cluster. All pools being restored, independent of whether they were copy export pools, can be redirected to unused pools during the restore process.
  • Recovered virtual volumes cannot conflict with virtual volumes in the existing TS7700 Cluster.
    • If any virtual volumes conflict, the restore operation is canceled before the restore point is changed.
    • If the primary or secondary pool for any virtual volume conflicts with an existing primary or secondary pool, the restore operation is canceled before the restore point is changed.
  • The existing TS7700 Cluster can be a member of a grid, however:
    • Only the TS7700 Cluster that is used as the restore point contains restored volume data. This data does not automatically replicate to any peer location. You must coordinate with your IBM Service Representative to use tools such as VESYNC to replicate restored content to any peer locations.
    • The restore TS7700 Cluster must be put into service then offline during the restore.
    • All other clusters in the grid must remain online during the restore operation.
  • The Copy Export Disaster recovery test mode cannot be used during a copy export restore merge scenario. Disaster recovery test mode is only available as an option if the restore operation targets an empty TS7700 Cluster.
  • The total number of virtual volumes that follow the restore merge operation cannot exceed the total number available as designated by FC 5270. If the total number of virtual volumes does exceed the number available by FC 5270, the restore operation is canceled before the restore location is changed.

Following a copy export merge operation, data is restored into a distributed and composite library that is different from the source. You must update host catalogues to reflect the new data location.