This section describes the maintenance procedure for the Storage Cluster environment.
This section, for the purpose of convenience, defines and explains the following names.
Defined Names Used in Explanation in This Section | Meaning of Defined Names |
|---|---|
ETERNUS-A | Primary Storage |
ETERNUS-B | Secondary Storage |
ETERNUS-C | ETERNUS Disk storage system prepares to restructure the Storage Cluster environment after the Primary storage or Secondary storage is removed |
Point
The TFO group status is automatically updated. Re-check it after waiting for a while or manually updating the TFO group status by referring to "9.4.2.2 Updating TFO Group Status" when the status which is different from the procedure is displayed.
Refer to the ETERNUS Disk storage system manuals for the command name and the format of ETERNUS CLI used in the procedure.
For the Advanced Copy maintenance contents when operating the AdvancedCopy Manager, refer to "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" and "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
When the AdvancedCopy Manager Copy Control Module function is in use, refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for Copy Control Module for information on the commands.
When the AdvancedCopy Manager replication management function is in use, refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for information on the commands.
Maintenance Contents | Type of Copy Being Executed | ||
|---|---|---|---|
OPC/QuickOPC | SnapOPC+ | EC/REC | |
(a) Stopping the copy session | Confirms the copy session by using the acopc query command and stops the copy session by using the acopc cancel command. | Confirms the copy session by using the acsnap query command and stops the copy session by using the acsnap cancel command. | Confirms the copy session by using the acec query command and stops the copy session by using the acec cancel command. |
(b) Stopping copy sessions when the TFO status is in "Standby" | By using the accopy query command this execution confirms that the TFO status of the copy session for the ETERNUS Disk storage system is in "Standby", and stops the copy session by using the accopy fcancel command. | ||
(c) Deleting AdvancedCopy Manager environment settings | Deletes copy pairs by using the acpair remove command. | ||
(d) Configuring the AdvancedCopy Manager environment | Adds copy pairs by using the acpair add command. | ||
(e) Starting a copy session | Starts copy sessions by using the acopc start command. | Starts copy sessions by using the acsnap start command. | Starts copy sessions by using the acec start command.
|
(f) Checking the status of the copy session | Confirms copy session status confirmation and performs recovery, referring to "When Recovering Storage Cluster Continuous Copy Function" in the ETERNUS SF AdvancedCopy Manager Operation Guide for Copy Control Module. | ||
(g) Stopping management service | Stops the management service with the acservice stop command. | ||
Maintenance Contents | Type of Copy Being Executed | ||
|---|---|---|---|
OPC/QuickOPC | SnapOPC+ | EC/REC | |
(a) Stopping the copy session | Confirms the copy session by using the swsrpstat command and stops the copy session by using the swsrpcancel command. | ||
(b) Stopping copy sessions when the TFO status is in "Standby" | Confirms the copy session with the accopy query command and stops the copy session with the accopy fcancel command on the Management Server. In the case of the replication management function commands, this operation cannot be executed in relation to storage device where the TFO status is in "Standby". For this reason, use the AdvancedCopy Manager Copy Control function commands only when stopping the copy session in the storage device where the TFO status is in "Standby". | ||
(c) Deleting AdvancedCopy Manager environment settings | Deletes reproduction volume information by using the swsrpdelvol command. When there are copy sessions in the ETERNUS Disk storage system where the TFO status is "Active", delete the reproduction volume information by specifying the -e option for the swsrpdelvol command. | ||
(d) Configuring the AdvancedCopy Manager environment | Configures the AdvancedCopy Manager environment by using the swsrpsetvol command. | ||
(e) Starting a copy session |
| Starts the copy session by specifying the -C option or -P option for the swsrpmake command. | Starts the copy session by using the swsrpstartsync command.
|
(f) Checking the status of the copy session | Confirms copy session status and performs recovery, referring to "When Recovering Storage Cluster Continuous Copy Function" in the ETERNUS SF AdvancedCopy Manager Operation Guide for Copy Control Module. | ||
When recovering, the initial copy takes place between the pair volumes. For an estimate of the initial copy required time, refer to "Table 9.5 Time Required for Initial Copy (Standard Value of 1TB Physical Capacity Volume)".
This section describes the procedure for replacing the ETERNUS Disk storage system for each cabinet.
When Replacing Primary Storage
When a fault occurs when the ETERNUS-A is operating with the ETERNUS-A TFO status in "Active", if the Failover mode is "Auto", the Automatic Failover is performed. When the Failover mode is "Manual", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
Remove the fiber channel cable connected to the ETERNUS-A CA port.
When 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.6 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Delete the TFO group, referring to "9.4.3.6 Deleting Storage Cluster Environment". At this time, in order to take over the logical WWPN/WWNN set in the ETERNUS-B, click WWPN takeover and delete the TFO group.
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.
Connect the fiber channel disconnected in step 2 to the CA port of ETERNUS-C and hard wire the connection with the business server.
After confirming that the ETERNUS-B TFO group phase is "Normal", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
Remove the fiber channel cable connected to the ETERNUS-B CA port.
Delete the TFO group, referring to "9.4.3.6 Deleting Storage Cluster Environment". At this time, in order to take over the logical WWPN/WWNN set in ETERNUS-C, click WWPN takeover and delete the TFO group.
Configure the Storage Cluster environment with ETERNUS-B as the Secondary Storage and ETERNUS-C as the Primary Storage.
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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the configuration procedure.
Note
Do not reconnect ETERNUS-A after deleting the TFO group set in ETERNUS-B in step 4. There is a possibility that data corruption may occur due to WWPN/WWNN duplication.
When Replacing Secondary Storage
Delete ETERNUS-B from the product and remove it so that it will not be managed.
When 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.6 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Delete the TFO group, referring to "9.4.3.6 Deleting Storage Cluster Environment".
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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the configuration procedure.
See
Execute steps 4 and 5 in the Secondary Storage, referring to "Figure 9.8 Adding Secondary Storage Where Only Primary Storage is used" in "9.3 Work Flow".
Check on the following conditions whether any RAID failure is occurring in the Primary Storage or Secondary Storage:
On the Web Console, the device status is not "Normal", and
On the Web Console, the status of RAID group is "Broken".
When RAID's Primary Storage Breaks Down
When ETERNUS-A operates it with the TFO status in "Active", the Failover method when the RAID breakdown occurs is different depending on the Failover mode. When the Failover mode is "Auto", the Automatic Failover is performed. When the Failover mode is "Manual", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
This step is not necessary when the ETERNUS-A TFO status is operating in "Standby".
When 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 the AdvancedCopy Manager, stop the volume copy session belonging to the defect RAID.
Refer to "(a) Stopping the copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
When using the Storage Cluster Continuous Copy function and when the Automatic Failover has been performed, it is possible to just stop copy sessions on the ETERNUS-A volume. For the procedure for stopping ETERNUS-A copy sessions, refer to "(b) Stopping copy sessions when the TFO status is in "Standby"" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
In ETERNUS-B, use the ETERNUS CLI command to release the TFO pair.
Maintain the ETERNUS-A RAID.
For ETERNUS-B, use the ETERNUS CLI command to recover the TFO pair.
Wait for the initial copy from ETERNUS-B to ETERNUS-A to complete.
From the Storage Cluster overview screen, check that the TFO group phase is set to "Failback Ready".
When operating the AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback".
When the Failback mode is changed to "Manual" in step 2, change to "Auto".
When RAID's Secondary Storage Breaks Down
When an ETERNUS-B RAID failure occurs while operating with the ETERNUS-B TFO status in "Active", perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback".
This step is not necessary when the ETERNUS-B TFO status is operating in "Standby".
When operating AdvancedCopy Manager, stop the volume copy session belonging to the defect RAID.
Refer to "(a) Stopping the copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
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 ETERNUS-B volume. For the procedure for stopping ETERNUS-B copy sessions, refer to "(b) Stopping copy sessions when the TFO status is in "Standby"" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
In ETERNUS-B, use the ETERNUS CLI command to release the TFO pair.
Maintain the ETERNUS-B RAID.
For ETERNUS-B, use the ETERNUS CLI command to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
From the Storage Cluster overview screen, check that the TFO group phase is "Normal".
When operating the AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Check on the following conditions whether any RAID blocking is occurring in the Primary Storage or Secondary Storage:
On the Web Console, the device status is not "Normal", and
On the Web Console, the status of RAID group is "No Disk Path".
When RAID's Primary Storage Is Blocked
When ETERNUS-A RAID blocking occurs while the ETERNUS-A TFO status is operating in "Active", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
This step is not necessary when ETERNUS-A TFO status is operating in "Standby".
When 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 sessions on the volume to which the closed RAID belongs.
Refer to "(a) Stopping the copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
When using the Storage Cluster Continuous Copy function and when the Manual Failover has not been performed in step 1, it is possible to just stop copy sessions on the ETERNUS-A volume. For the procedure for stopping ETERNUS-A copy sessions, refer to "(b) Stopping copy sessions when the TFO status is in "Standby"" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
In ETERNUS-B, use the ETERNUS CLI command to release the TFO pair.
Maintain ETERNUS-A RAID.
For ETERNUS-B, use the ETERNUS CLI command to recover the TFO pair.
Wait for the copy from ETERNUS-B to ETERNUS-A to complete.
From the Storage Cluster overview screen, check that the TFO group phase is set to "Failback Ready".
When operating the AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback".
When the Failback mode is changed to "Manual" in step 2, change to "Auto".
When RAID's Secondary Storage Is Blocked
When ETERNUS-B RAID blocking occurs when the ETERNUS-B TFO status is operating in "Active", perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback".
This step is not necessary when the ETERNUS-B TFO status is operating in "Standby".
When AdvancedCopy Manager is operating, stop the copy sessions on the volume to which the closed RAID belongs.
Refer to "(a) Stopping the copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
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 ETERNUS-B volume. For the procedure for stopping ETERNUS-B copy sessions, refer to "(b) Stopping copy sessions when the TFO status is in "Standby"" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
In ETERNUS-B, use the ETERNUS CLI command to release the TFO pair.
Maintain the ETERNUS-B RAID.
For ETERNUS-B, use the ETERNUS CLI command to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
From the Storage Cluster overview screen, check that the TFO operating group is set to "Normal".
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Check on the following conditions whether any bad sectors are occurring in the Primary Storage or Secondary Storage:
The following message is displayed in Overview of the ETERNUS Web GUI:
Bad Sector has occurred. Please check the details by the volume navigation.
The bad sector areas are recovered from devices for which TFO status is "Active" to the Standby device.
If the Status column on Volume tab of the TFO group details screen is set to anything other than "Active", contact a Fujitsu customer engineer.
When Bad Sector Occurs in Primary Storage Copy Source
When a bad sector occurs when ETERNUS-A is operating with the ETERNUS-A TFO status in "Active", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
This step is not necessary when the ETERNUS-A TFO status is operating in "Standby".
When 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 on volumes that have bad sectors.
Refer to "(a) Stopping the copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
When using the Storage Cluster Continuous Copy function, it is possible to just stop copy sessions on the ETERNUS-A volume. For the procedure for stopping ETERNUS-A copy sessions, refer to "(b) Stopping copy sessions when the TFO status is in "Standby"" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
In ETERNUS-B, use the ETERNUS CLI command to release the TFO pair.
For ETERNUS-B, use the ETERNUS CLI command to recover the TFO pair.
Wait for the copy from ETERNUS-B to ETERNUS-A to complete.
From the Storage Cluster overview screen, check that the TFO group phase is "Failback Ready".
Delete the bad sector information for the target LUN from the ETERNUS Web GUI.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback".
When the Failback mode is changed to "Manual" in step 2, change to "Auto".
When Bad Sector Occurs in Secondary Storage Copy Source
When ETERNUS-B bad sectors occur while the ETERNUS-B TFO status is operating in "Active", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
This step is not necessary when the ETERNUS-B TFO status is operating in "Standby".
When operating AdvancedCopy Manager, stop the copy session on volumes on which there are bad sectors.
Refer to "(a) Stopping the copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
When using the Storage Cluster Continuous Copy function, it is possible to just stop copy sessions on the ETERNUS-B volume. For the procedure for stopping ETERNUS-B copy sessions, refer to "(b) Stopping copy sessions when the TFO status is in "Standby"" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.7 When Using AdvancedCopy Manager Replication Management Function".
In ETERNUS-B, use the ETERNUS CLI command to release the TFO pair.
For ETERNUS-B, use the ETERNUS CLI command to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
From the Storage Cluster overview screen, check that the TFO group phase is "Normal".
Delete the bad sector information for the target LUN from the ETERNUS Web GUI.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
This section describes the procedure when running temporarily with a single system, such as when updating the firmware version.
When Maintaining Primary Storage
Change to "Manual" when operating Failback mode in "Auto".
When maintaining ETERNUS-A while the ETERNUS-A TFO status is operating in "Active", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
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.6 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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback".
When the Failback mode is changed to Manual as in step 1, change to "Auto".
When Maintaining Secondary Storage
When maintaining ETERNUS-B while the ETERNUS-B TFO status is operating in "Active", perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback".
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.6 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.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
When Updating Firmware Version
Change to "Manual" when operating Failback mode in "Auto".
Perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback" for the ETERNUS-A Primary TFO group.
Restart ETERNUS-A after applying the firmware to ETERNUS-A.
Perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback" for the ETERNUS-B Secondary TFO group.
Perform the Manual Failover, referring to "9.4.2.4 Manual Failover/Failback" for the ETERNUS-B Primary TFO group.
Restart the ETERNUS-B after applying the firmware to the ETERNUS-B.
Perform the Manual Failback, referring to "9.4.2.4 Manual Failover/Failback" for the ETERNUS-A Secondary TFO group.
When the Failback mode is changed to Manual as in step 1, change to "Auto".
To delete the Storage Cluster environment, delete TFO Groups.
Deleting TFO Groups clears the Storage Cluster operation, clearing the synchronization of volumes, too.
Also, when removing Primary Storage after failover to Secondary Storage, the Storage Cluster operation must be canceled and the logical WWPN/WWNN set for the ports to Secondary Storage must not be canceled but inherited. At that stage, specify "WWPN Handover".
Note
Do not specify "WWPN takeover" when the Primary storage is in a connected state.
Delete TFO Groups in the following steps:
When operating AdvancedCopy Manager, stop the copy session and delete the AdvancedCopy Manager environment.
Refer to "(a) Stopping the copy session" and "(c) Deleting AdvancedCopy Manager environment settings" in "Table 9.6 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.7 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of a target ETERNUS Disk storage system.
On the Category pane, click Storage Cluster.
The items on the Category pane switch to those associated with Storage Cluster, and created TFO Groups are displayed on the Main pane.
Select one TFO Group on the Main pane and click Delete under TFO Group on the Action pane.
The TFO Group Deletion Wizard screen is displayed.
The Option Selection/Confirmation screen is displayed.
When WWPN is inherited to Secondary Storage, click WWPN Handover.
Click Delete.
On completion of deletion, make sure on the FC Port List screen that WWPN is inherited. The procedure is as follows:
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of the ETERNUS Disk storage system specified as Secondary Storage for Storage Cluster.
On the Category pane, click Connectivity.
A list of port types is displayed on the Main pane.
On the Main pane, click No. of Ports whose type is FC.
A list of FC ports is displayed on the Main pane. When a value is displayed in the Logical WWPN column and TFO Status is "-" (hyphen), that port inherited the logical WWPN/WWNN when TFO Group was deleted.
