Managing geographic mirroring
Use the following information to help you manage geographic
mirroring. Geographic mirroring is a sub-function of cross-site mirroring,
where data is mirrored to independent disk pools in an 
IBM® i
environment.
- Suspending geographic mirroring
If you need to end TCP communications for any reason, such as placing your system in restricted state, you should suspend geographic mirroring first. This action temporarily stops mirroring between systems in a high-availability solution. - Resuming geographic mirroring
If you suspend geographic mirroring, you must resume it in order to reactivate mirroring between the production and mirrored copies again. - Detaching mirror copy
If you are using geographic mirroring and want to access the mirror copy to perform save operations or data mining, or to create reports, you must detach the mirror copy from the production copy. - Reattaching mirror copy
If you detached the mirror copy and have completed your work with the detached mirror copy, you must reattach the detached mirror copy to resume using geographic mirroring. - Deconfiguring geographic mirroring
If you no longer want the capability to use geographic mirroring for a specific disk pool or disk pool group, you can select to Deconfigure Geographic Mirroring. If you deconfigure geographic mirroring, the system stops geographic mirroring and deletes the mirror copy of the disk pools on the nodes in the mirror copy site. - Changing geographic mirroring properties
All geographic mirroring properties can be changed when the production copy of the independent disk pool is varied off. The Synchronization Priority property can be also changed with the independent disk pool is Available and geographic mirroring is Suspended.
Parent topic: Managing PowerHA