Use this page to set up Metro Mirror relationships between source (primary) volumes and target (secondary) volumes to allow for application data recovery, failover to remote sites for disaster recovery, and remote migration of data and offsite backups.
This page also displays existing established volume pairs that are assigned to the storage complex (storage unit and LSS, for example) that you selected. It displays the type of relationship for which the specified volume pair is participating, and the current state of that volume pair. If your storage enterprise includes an ESS 2105 and you have configured a Copy Services domain to use ESS volumes, the source ESS and target ESS serial numbers from which those volumes are assigned are displayed. If the table is empty, no volume pairs have been defined for the selected storage complex.
The Metro Mirror feature is accessible only from the Real-time Manager; the Metro Mirror feature is not accessible from the Simulated Manager.
A storage complex describes a group of storage units such as the DS6000™s that is managed by a single management console. If you have only one DS6000 storage unit, then your storage complex consist of one storage unit.
For the zSeries® environments, the data that is stored in a storage unit is arranged in a count-key-data (CKD) format. For the open system environments, the data that is stored in the storage unit is arranged in a fixed-block (FB) format.
Select the Metro Mirror relationship that you want to work with from the table.
If you click on a link for a particular relationship in the table, the Metro Mirror properties page is displayed. If no relationship exists, the table is empty.