542 IBM System Storage DS6000 Series: Copy Services in Open Environments
Implementation and usage
This solution is implemented as a service included with System i Copy Services Toolkit. The
installation steps for the Toolkit for Global Mirror are similar to those steps explained for Metro
Mirror in “Implementation and usage” on page 542.
After the Toolkit for Global Mirror is installed and tested, you are able to perform the switch to
the remote site during planned and unplanned outages. The switch to the remote site and
Failback to the production site are achieved with a series of actions performed by the Toolkit.
They are started by toolkit commands swpprc and falovrgmir.
The Global Mirror status and Toolkit setup status can be checked by issuing the commands
chkpprc and dspessdta respectively.
Results of Toolkit actions during the switch, or for checking the status after the switch, can be
observed in the Toolkit log by using a viewlog command.
The Toolkit triggers different tasks by communicating with the System i5 HMC, performing
System i5 commands within the partition, and communicating with external disk systems by
using the DSCLI. This is illustrated in Figure B-7 on page 514.
Checking status
For a description of how to check the IASP status, refer to “Implementation and usage” on
page 513.
Switch to the remote site during planned outages
To switch to the remote system during planned outages, use the command swpprc
*scheduled. For information about how to enter this command, refer to “Implementation and
usage” on page 513.
Switch to the remote site during unplanned outages
To switch to the remote site in case of a failure of the System i5 or the DS storage at the local
site, or a disaster at the local site, use the following commands:
1. In the remote partition, perform the command swpprc *unscheduled. This command
places the cluster and IOPs in partitions in the appropriate status for a failover.
2. In the remote partition, enter the Toolkit command falovrgmir. In the Global Mirroring
Failover panel, specify the IASP name shown in Figure B-45 on page 543.
Important: When using Copy Services functions, such as Metro Mirror, Global Mirror, or
FlashCopy for the replication of the load source unit or other i5/OS disk units within the
same DS6000 or DS8000 or between two or more DS6000 or DS8000 systems, the
source volume and the target volume characteristics must be identical. The target and
source must have matching capacities and matching protection types.
Additionally, once a volume is assigned to an i5/OS partition and added to that partition’s
configuration, its characteristics must not be changed. If there is a requirement to change
some characteristic of a configured volume, it must first be completely removed from the
i5/OS configuration. After the characteristic changes are made, for example, protection
type, capacity, and so on, by destroying and recreating the volume or by utilizing the DS
CLI, the volume can be reassigned to the i5/OS configuration. To simplify the configuration,
we recommend a symmetrical configuration between two IBM storage systems, creating
the same volumes with the same volume ID that decides the LSS_ID.

Get IBM System Storage DS6000 Series: Copy Services in Open Environments now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.