This section describes the maintenance procedure when running temporarily with a single system, such as when updating the firmware version.
See
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 maintaining the Primary Storage
Change to "Manual" when operating the Failback mode in "Auto".
If there is a TFO group that satisfies either of the following conditions when maintaining ETERNUS-A, perform a Manual Failover to ETERNUS-B for that TFO group.
Condition 1
The TFO group is operated with the Active-Active configuration.
The TFOG Role of the ETERNUS-A side is "Local".
Condition 2
The TFO group is operated with the Active-Standby configuration.
The TFO status of the ETERNUS-A side is "Active".
This procedure is not required for TFO groups that do not satisfy the above conditions.
Maintain ETERNUS-A.
When stopping ETERNUS-A and when ETERNUS-A is being operated using the AdvancedCopy Manager Copy Control Module function, stop ETERNUS-A first and then stop the management service of AdvancedCopy Manager CCM.
Refer to "(g) Stopping management service" of "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Check that the TFO group operating status is "Failback Ready".
Check that the copy session status matches 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 1, change to "Auto".
When maintaining the Secondary Storage
If there is a TFO group that satisfies either of the following conditions when maintaining ETERNUS-B, 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.
Maintain ETERNUS-B.
When stopping ETERNUS-B and when ETERNUS-A is being operated using the AdvancedCopy Manager Copy Control Module function, stop ETERNUS-B first and then stop the management service of AdvancedCopy Manager CCM.
Refer to "(g) Stopping management service" of "Table 9.11 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Check that the TFO group operating status is "Normal".
Check that the copy session status matches 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.
When updating the firmware version
Change to "Manual" when operating the Failback mode in "Auto".
Perform a Manual Failover to ETERNUS-B for all of the Primary TFO groups of ETERNUS-A.
Restart ETERNUS-A after applying the firmware to ETERNUS-A.
Perform a Manual Failback to ETERNUS-A for all of the Secondary TFO groups of ETERNUS-B.
Perform a Manual Failover to ETERNUS-A for all of the Primary TFO groups of ETERNUS-B.
Restart ETERNUS-B after applying the firmware to ETERNUS-B.
Perform a Manual Failback to ETERNUS-B for all of the Secondary TFO groups of ETERNUS-A.
If the Failback mode is changed to "Manual" in Step 1, change to "Auto".
