Note the following when planning to migrate GAD+UR pairs using GAD:
- The GAD+UR pair migration is possible by using GAD only in the configuration with the models and DKCMAIN firmware versions of the source GAD pair and target GAD pair that follow. There are no restrictions on the combinations of the models and DKCMAIN microcode versions at the UR secondary site.
The following table specifies the supported configurations for GAD+UR migration when the target storage system is VSP One Block 85.
Source storage system Target storage system VSP 5000 series (90-09-29 or later)
VSP One Block 85 (all versions)
The following table specifies the supported configurations for GAD+UR migration when the target storage system is VSP One Block 20 series.
Source storage system Target storage system Storage system DKCMAIN version Storage system DKCMAIN version VSP E590, VSP E790, VSP E990 93-07-24 or later VSP One B26, VSP One B28
A3-03-01 or later VSP E1090 93-07-27 or later VSP One B20 series A3-04-21 or later VSP G/F350, G/F370, G/F700, G/F900 88-08-14 or later VSP One B26, VSP One B28 A3-03-01 or later VSP G200, G/F400, G/F600, G/F800 83-06-25 or later VSP One B26, VSP One B28 A3-04-01 or later * Only unpaired volumes can be used. If the volume is part of any of the following, the volume cannot be used for online data migration:
- ShadowImage pair
- Thin Image pair
- Thin Image Advanced pair
- Universal Replicator pair
- Global-active device pair
- Environments in which both global-active device and Universal Replicator are used
- When migrating GAD+UR pairs using GAD, you can use VSM manual configuration only. VSM auto-configuration cannot be used.
- After starting operations on the migration target GAD+UR pair, remove the migration source GAD+UR pair and delete the temporary GAD pair used for migration. If the pair status of the S-VOL of the temporary GAD pair used for migration remains SSWS, you cannot resynchronize the target UR pair.
- Each UR journal group provides the different consistency management at the source and target UR sites. The restoration cannot be linked between the source and target UR sites.
- If you are migrating a UR pair by using GAD and a GAD+UR pair by using GAD, you cannot migrate the GAD+UR pair after migrating the UR pair. Migrate the GAD+UR pair first.
- The MP usage rate might temporarily increase during data migration.
For additional information about GAD pair migration that might be useful, see Requirements for GAD pair migration and Restrictions and behavior when migrating GAD pairs.