Recovering from offline volumes
You can use the management GUI or issue commands to recover from an offline volume after a node or an I/O group fails.
About this task
Procedure
Recovering from data loss scenario 1
About this task
One node in an I/O group is failed and the failover process is started on the second node. During the failover process, the second node in the I/O group fails before the data in the write cache is written to the backend. The first node is successfully repaired. However, because the hardened data is not the most recent version that is committed to the data store, it cannot be used. The second node is replaced but lost data. Therefore, the node cannot recognize that it is part of the cluster.
Complete steps 1 through 4 to recover from offline volumes when one node has earlier-level hardened data and the other node lost hardened data.
Procedure
- Recover the node and add it back into the cluster.
- Delete all FlashCopy®, Metro Mirror, and Global Mirror mappings and relationships that use the offline volumes.
- Run the recovervdisk, recovervdiskbyiogrp, or recovervdiskbycluster command.
- Re-create all FlashCopy, Metro Mirror, and Global Mirror mappings and relationships that use the volumes.
Recovering from data loss scenario 2
About this task
Both nodes in the I/O group failed and were repaired. Because the nodes lost their hardened data, they have no way of recognizing that they are part of the cluster.
Complete steps 1 through 3 to recover from offline volumes when both nodes lose their hardened data and cannot be recognized by the cluster.
Procedure
- Delete all FlashCopy, Metro Mirror, and Global Mirror mappings and relationships that use the offline volumes.
- Run the recovervdisk, recovervdiskbyiogrp, or recovervdiskbycluster command.
- Re-create all FlashCopy, Metro Mirror, and Global Mirror mappings and relationships that use the volumes.