If an event other than a RAID failure, RAID close, CA port Linkdown, or bad sectors occurs and the session status of the TFO pair becomes "Error Suspend", perform a recovery with this procedure.
Check the following conditions to determine whether the session status of the TFO pair is "Error Suspend".
The TFO group phase is "Maintenance".
The volume session information is "Error Suspend" in the TFO pair session information.
See
For details of the TFO group status, refer to the following sections.
When operating a TFO group with the Active-Active configuration: "9.3.2.10 Confirming the Status on the Storage Cluster Overview Screen"
When operating a TFO group with the Active-Standby configuration: "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen"
For details of the TFO pair session information, refer to the following sections.
When operating a TFO group with the Active-Active configuration: "9.3.2.11 Confirming the Status on the TFO Group Details Screen"
When operating a TFO group with the Active-Standby configuration: "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
For the execution method of "Manual Failover" and "Manual Failback" that are described in this section, refer to the following.
When operating a TFO group with the Active-Active configuration: "9.3.2.7 Manual Failover/Failback"
When operating a TFO group with the Active-Standby configuration: "9.4.2.6 Manual Failover/Failback"
When the session status of the TFO pair in the Primary Storage becomes error suspend due to an event
If there is a TFO group that satisfies all the following conditions when the session status of the TFO pair in ETERNUS-A becomes "Error Suspend", perform a Manual Failover to ETERNUS-B for that TFO group.
The TFO group is operated with the Active-Standby configuration.
The TFO status of the ETERNUS-A side is "Active".
The Failover mode is "Manual".
This procedure is not required for TFO groups that do not satisfy the above conditions.
If the Failback mode is operating in "Auto", as it is necessary to perform Failback after confirming the copy session status, change this to "Manual".
When operating AdvancedCopy Manager, stop the copy session of the volume whose TFO pair session becomes "Error Suspend".
Refer to "(a) Stopping the copy session" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.12 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-A is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-A. When using the Storage Cluster Continuous Copy function and when the fail over has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-A.
For the procedure for stopping the copy sessions of ETERNUS-A, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.12 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-A, perform the procedure in "9.5.8 Releasing TFO Pair" to release the TFO pair.
Depending on the phenomenon, maintain ETERNUS-A.
For ETERNUS-A, perform the procedure in "9.5.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-B to ETERNUS-A to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Failback Ready".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
After checking that the TFO group phase is "Maintenance" on the Storage Cluster overview screen, check the TFO pair session information and resolve the problem events of the TFO pair sessions that are not in the "Active" status.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.12 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.12 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 2, change to "Auto".
When the session status of the TFO pair in the Secondary Storage becomes error suspend due to an event
If there is a TFO group that satisfies either of the following conditions when the session status of the TFO pair in ETERNUS-B becomes "Error Suspend", perform a Manual Failback to ETERNUS-A for that TFO group.
Condition 1
The TFO group is operated with the Active-Active configuration.
The TFOG Role of the ETERNUS-B side is "Local".
Condition 2
The TFO group is operated with the Active-Standby configuration.
The TFO status of the ETERNUS-B side is "Active".
This procedure is not required for TFO groups that do not satisfy the above conditions.
When operating AdvancedCopy Manager, stop the copy session of the volume whose TFO pair session becomes "Error Suspend".
Refer to "(a) Stopping the copy session" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.12 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-B is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-B. When using the Storage Cluster Continuous Copy function and when the Manual Failback has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-B.
For the procedure for stopping the copy sessions of ETERNUS-B, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.12 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-B, perform the procedure in "9.5.8 Releasing TFO Pair" to release the TFO pair.
Depending on the phenomenon, maintain ETERNUS-B.
For ETERNUS-B, perform the procedure in "9.5.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Normal".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
After checking that the TFO group phase is "Maintenance" on the Storage Cluster overview screen, check the TFO pair session information and resolve the problem events of the TFO pair sessions that are not in the "Active" status.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.12 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.12 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
