Top
ETERNUS SF Storage Cruiser V16.1 Operation Guide
FUJITSU Storage

9.4.3 Maintenance

Deleting Storage Cluster Environment

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".

Delete TFO Groups in the following steps:

  1. Click Storage on the global navigation tab.
    Registered ETERNUS Disk storage systems are displayed on the Main pane.

  2. On the Main pane, click the Name of a target ETERNUS Disk storage system.

  3. 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.

  4. 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.

  5. The Option Selection/Confirmation screen is displayed.
    When WWPN is inherited to Secondary Storage, click WWPN Handover.

  6. Click Delete.

On completion of deletion, make sure on the FC Port List screen that WWPN is inherited. The procedure is as follows:

  1. Click Storage on the global navigation tab.
    Registered ETERNUS Disk storage systems are displayed on the Main pane.

  2. On the Main pane, click the Name of the ETERNUS Disk storage system specified as Secondary Storage for Storage Cluster.

  3. On the Category pane, click Connectivity.
    A list of port types is displayed on the Main pane.

  4. 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.

Note

Do not specify "WWPN Handover" with Primary Storage connected.

Corrective Action in Case of Trouble

The following is a description of the procedure to continue operations on Secondary Storage in case of trouble with Primary Storage and the procedure to recreate a Storage Cluster environment with two ETERNUS Disk storage systems. Actions vary depending on whether or not Primary Storage is replaced.

Of the two ETERNUS Disk storage systems setting up the Storage Cluster environment, take Primary Storage as ETERNUS-A and Secondary Storage as ETERNUS-B. And, take as ETERNUS-C an ETERNUS Disk storage system provided after removal of ETERNUS-A to reconfigure the Storage Cluster environment.

When replacing Primary Storage:
  1. In the case of Manual Failover mode, make sure that ETERNUS-A is not connected to business servers and refer to "Force-Failover" to execute Force-Failover.

  2. For ETERNUS-B, refer to "Updating TFO Group Status" to update the status of TFO Groups. At this step, check that TFO status of ETERNUS-B is "Active" and that TFO setting status is "Failovered".

  3. Make sure that ETERNUS-A is not connected to business servers and then refer to "Deleting Storage Cluster Environment" to delete the TFO Groups configured to ETERNUS-B. At this step, click WWPN Handover so as to inherit the logical WWPN/WWNN configured to ETERNUS-B, and delete the TFO Groups.

  4. Take ETERNUS-B as Primary Storage and ETERNUS-C as Secondary Storage to create a Storage Cluster environment.

  5. Refer to "Manual Failover/Failback" to execute Manual Failover.

  6. Remove the Fibre Channel cable connected to the CA port on ETERNUS-B and make sure that business servers cannot see ETERNUS-B.

  7. Refer to "Deleting Storage Cluster Environment" to delete the TFO Groups configured to ETERNUS-B and ETERNUS-C. At this step, click WWPN Handover so as to inherit the logical WWPN/WWNN configured to ETERNUS-C and delete the TFO Groups.

  8. Take ETERNUS-B as Secondary Storage and ETERNUS-C as Primary Storage to create a Storage Cluster environment.

  9. Reconnect the connection between business servers and ETERNUS-B disconnected at Step 6.

When continuing to use Primary Storage:
  1. In the case of Manual Failover mode, make sure that ETERNUS-A is not connected to business servers and then refer to "Force-Failover" to execute Force-Failover.

  2. For ETERNUS-B, refer to "Updating TFO Group Status" to update the status of TFO Groups. At this step, check that TFO status of ETERNUS-B is "Active" and that TFO Group setting status is "Failovered".

  3. Remove the cause of trouble with ETERNUS-A, and refer to "Updating TFO Group Status" to update the status of TFO Groups. At this step, check that TFO Group setting status of ETERNUS-B is "Failback Ready".

  4. Refer to "Manual Failover/Failback" to execute Manual Failback.