IBM XIV Storage System Copy Services and Migration

Example 5-8 List mirror couplingsFigure 5-15 on page 139 shows that the synchronization status is still consistent for thecouplings that are yet to be changed. This is because this is the last known state. Whenthe role is changed the coupling is automatically deactivated.Role changeover at the secondary site using the XCLIWe now change roles for the slave volumes at the secondary site and make them mastervolumes so that the standby server can write to them.1. On the secondary XIV open an XCLI session and run the mirror_change_role command(Example 5-7).Example 5-7 Remote mirror change role>> mirror_change_role vol=itso_win2008_vol2 new_role=masterWarning: ARE_YOU_SURE_YOU_WANT_TO_CHANGE_THE_PEER_ROLE_TO_MASTER Y/N: YCommand executed successfully.2. To view the status of the coupling run the mirror_list command, as shown inExample 5-8.>> mirror_listName Mirror Type Mirror Object Role Remote System Remote Peer Active Status Link Upitso_win2008_vol1 sync_best_effort Volume Master XIV MN00019 itso_win2008_vol1 no Unsynchronized yesitso_win2008_vol2 sync_best_effort Volume Master XIV MN00019 itso_win2008_vol2 no Unsynchronized yesitso_win2008_vol3 sync_best_effort Volume Slave XIV MN00019 itso_win2008_vol3 yes Consistent yesExample 5-8 shows that the synchronization status is still consistent for one of thecouplings that is yet to be changed. This is because this reflects the last known state.When the role is changed, the coupling is automatically deactivated.3. Repeat steps 1–2 to change roles on other volumes.140 IBM XIV Storage System: Copy Services and Migration