If such a trouble as requires storage device replacement occurs and an ETERNUS Disk storage system should be replaced, deconstruct the Storage Cluster environment by deleting TFO groups.
This section describes the maintenance procedure for replacing the ETERNUS Disk storage system for each cabinet.
See
For the execution method of "Manual Failover" that is 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 replacing Primary Storage
If there is a TFO group that satisfies all the following conditions when ETERNUS-A fails, 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.
Remove the fiber channel cable connected to the CA port of ETERNUS-A. For iSCSI connection environments, remove the LAN cable.
If ETERNUS-A is being operated using the AdvancedCopy Manager Copy Control Module function, stop the management service of AdvancedCopy Manger 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.
Perform the procedure in "9.5.12 Temporarily Deleting the Storage Cluster Environment for Recovery" to delete all of the TFO groups.
When TFO groups are operated with the Active-Standby configuration in FC connection environments, in order to take over the logical WWPN/WWNN set in ETERNUS-B, check the WWPN Handover checkbox and delete all of the TFO groups.
When TFO groups are operated with the Active-Standby configuration in iSCSI connection environments or when TFO groups are operated with the Active-Active configuration, the WWPN Handover checkbox is displayed but grayed out.
Note
Do not reconnect ETERNUS-A after deleting the TFO group set in ETERNUS-B in this step. When TFO groups are operated with the Active-Standby configuration in FC connection environments, there is a possibility that data corruption may occur due to WWPN/WWNN duplication. For iSCSI connection environments, there is a possibility that data corruption may occur due to duplication of the iSCSI IP address.
Remove ETERNUS-A.
In ETERNUS-C, create the same business volume as ETERNUS-A that is in the process of being removed. At this time, do not hard wire the business server and ETERNUS-C.
Configure the Storage Cluster environment with ETERNUS-B as the Primary Storage and ETERNUS-C as the Secondary Storage.
For iSCSI connection environments, be sure to configure the CA port of ETERNUS-C after configuring a TFO group.
Connect the fiber channel disconnected in Step 2 to the CA port of ETERNUS-C and hard wire the connection to the business server. For iSCSI connection environments, connect the LAN cable and hard wire the connection to the business server.
After confirming that the phases of all of the TFO groups of ETERNUS-B are "Normal", perform a Manual Failover by selecting all of the TFO groups.
Remove the fiber channel cable connected to the CA port of ETERNUS-B. For iSCSI connection environments, remove the LAN cable.
Perform the procedure in "9.5.12 Temporarily Deleting the Storage Cluster Environment for Recovery" to delete all of the TFO groups.
When TFO groups are operated with the Active-Standby configuration in FC connection environments, in order to take over the logical WWPN/WWNN set in ETERNUS-C, check the WWPN Handover checkbox and delete all of the TFO groups.
When TFO groups are operated with the Active-Standby configuration in iSCSI connection environments or when TFO groups are operated with the Active-Active configuration, the WWPN Handover checkbox is displayed but grayed out.
Configure the Storage Cluster environment with ETERNUS-B as the Secondary Storage and ETERNUS-C as the Primary Storage.
For iSCSI connection environments, be sure to configure the CA port of ETERNUS-B after configuring a TFO group.
Reconnect the business server to ETERNUS-B which was disconnected in Step 10.
An initial copy from ETERNUS-C to ETERNUS-B is completed, and it returns to former state of the operation.
When operating AdvancedCopy Manager, configure the AdvancedCopy Manager environment.
Refer to "(d) Configuring the AdvancedCopy Manager environment" 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 configuration procedure.
When replacing Secondary Storage
Delete ETERNUS-B from the product and remove it so that it is not managed.
If ETERNUS-B is being operated using the AdvancedCopy Manager Copy Control Module function, stop the management service of AdvancedCopy Manger 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.
Perform the procedure in "9.5.12 Temporarily Deleting the Storage Cluster Environment for Recovery" to delete all the TFO groups.
Register ETERNUS-C to the product as the new Secondary Storage.
Reconstruct the Storage Cluster environment by using ETERNUS-A and ETERNUS-C.
When operating AdvancedCopy Manager, configure the AdvancedCopy Manager environment.
Refer to "(d) Configuring the AdvancedCopy Manager environment" 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 configuration procedure.
See
Execute Steps 4 and 5 in the Secondary Storage, referring to the following sections.
When operating a TFO group with the Active-Active configuration: "When adding Secondary Storage where only Primary Storage is used" in "9.2.1 Work Flow in Active-Active Configuration"
When operating a TFO group with the Active-Standby configuration: "When adding Secondary Storage where only Primary Storage is used" in "9.2.2 Work Flow in Active-Standby Configuration"
