Troubleshooting mirroring relationships

Edit online

There are some questions that might arise when implementing IBM® Storage Protect Snapshot and storage systems with mirroring technologies. The following information is provided to help you answer questions unique to your environment.

Question
Why are some remote mirroring relationships missing?
Answer

The target volumes that are referenced in this solution are part of the remote mirror relationship. The target volumes are used as the source for the snapshot operation.

Before you start the snapshot backup that uses the target volumes, verify that the remote mirroring relationships are established. You can verify the relationships by using either the graphical user interface or the command-line interface. For example, if using SAN Volume Controller global mirror, you can enter the following command to verify the mirroring relationship: 
ssh -i/<dir>/ssh-identity <username>@<hostname> 
	svctask mkrcrelationship -master <vdiskname local> -aux <vdiskname remote> 
	-cluster <clusterid> -name <relation name> -consistgrp <consgrp name> 
	-global
Question
The remote mirroring relationships are not in the state consistent_synchronized. How does the state for remote mirroring relationship get updated?
Answer
Go to the storage solution. Synchronize the consistency groups. For more information about synchronizing consistency groups, see the documentation that is provided with the storage hardware.
Question
(SAN Volume Controller only) One or more of the FlashCopy® target volumes for the remote site are missing. Where is the FlashCopy target volume?
Answer
Use either the graphical user interface or command-line interface to start the Metro Mirror or Global Mirror consistency group. For example, you can enter the following command from the command-line interface:
ssh -i/<di>ssh-identity <username>@<hostname of the cluster> svctask 
	startrcconsistgrp conist group id>
Question
(XIV® only) One of the following issues exists.
  • The remote mirroring is not operational.
  • For XIV synchronous mirroring, the state of the consistency group is not consistent synchronized.
  • For XIV asynchronous mirroring, the state of the consistency group is not RPO_OK.
How are these issues resolved?
Answer
Verify that the consistency groups meet the following requirements:
  • Consistency groups need to be enabled and synchronized.
  • The volumes that are assigned to the consistency groups need to be correctly identified and enabled.
One consistency group per database partition is needed.