Top
ETERNUS SF Storage Cruiser V16.9.1 Operation Guide
FUJITSU Storage
Chapter 9 Storage Cluster Function > 9.4 Operation Method in Active-Standby Configuration > 9.4.2 Operation
PreviousNext

9.4.2 Operation

9.4.2.1 Allocating Business Volume

To start or change the operation of the Storage Cluster function, perform the following steps.

For FC connection environments, the example of structure regarding allocation of business volumes is shown in "Figure 9.29 Storage Cluster Function: Structure Example of Allocating Business Volume (for FC connection environment)".
For iSCSI connection environments, the FC switch in the following figure serves as a network switch and no zoning setting exists.

Figure 9.29 Storage Cluster Function: Structure Example of Allocating Business Volume (for FC connection environment)

9.4.2.1.1 Preparing Business Volume

Prepare volumes to be switched in the Storage Cluster function on Primary and Secondary ETERNUS Disk storage systems respectively. The volumes to be switched by Storage Cluster must meet all of the conditions described in "Required Conditions for TFOV".

Point

  • If the type of volume using Storage Cluster is "Standard", "TPV", or "FTV", the volume capacity can be expanded. Refer to "9.4.2.4 Expanding Business Volume Capacity" for information on how to expand the volume capacity.
    If the volume type is "WSV", the volume capacity cannot be expanded.

  • If the total capacity of business volumes exceeds the total capacity of TFOVs per storage device, expand the total capacity of TFOVs. Refer to "Expanding Total Capacity of TFOVs" for the procedure to expand the total capacity of TFOVs.

If there is no space in RAID group, Thin Provisioning pool or Tier pool, refer to "Operations for RAID Group", "Operations for Thin Provisioning" or "Operations for Automated Storage Tiering" in the Web Console Guide to secure areas.

When starting from a new volume creation for both the Primary Storage and the Secondary Storage, a volume that satisfies the conditions described in "Required Conditions for TFOV" can be created easily with Web Console.
The operation procedure using Web Console is shown below.

  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 that is specified as the Primary Storage.

  3. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  4. Create a volume.

    • When creating a volume with a volume type of "Standard" or "TPV"

      1. On the Action pane, click Create Volume under Allocating Business Volume.

      2. From the TFO Group drop-down list, select the TFO group to be used by the Storage Cluster function.
        On the left side of the screen, the information input screen of the volume to be created in the Primary Storage is displayed.
        On the right side of the screen, the information input screen of the volume to be created in the Secondary Storage is displayed.

      3. Enter the required information for the Primary Storage portion on the left side of the screen.

      4. Make sure that the Create the same Volume as the Primary Storage checkbox in the Secondary Storage portion on the right side of the screen is checked.

        Point

        If the Create the same Volume as the Primary Storage checkbox is checked, the following items can be omitted since they will have the same setting value as the Primary Storage.

        - Name
        - Capacity
        - Type
        - Encryption
        - Deduplication
        - Compression
        - Deduplication/Compression
        - Allocation

        Note that a value must be entered for "Number of Volumes" regardless of the checkbox selection state.

      5. Enter the required information for the Secondary Storage portion on the right side of the screen.

      6. Click Next.
        The information confirmation screen is displayed.

      7. Confirm the information, and then click Create.

    • When creating a volume with a volume type of "FTV"

      1. On the Action pane, click Create FTV under Allocating Business Volume.

      2. From the TFO Group drop-down list, select the TFO group to be used by the Storage Cluster function.
        On the left side of the screen, the information input screen of the volume to be created in the Primary Storage is displayed.
        On the right side of the screen, the information input screen of the volume to be created in the Secondary Storage is displayed.

      3. Enter the required information for the Primary Storage portion on the left side of the screen.

      4. Make sure that the Create the same Volume as the Primary Storage checkbox in the Secondary Storage portion on the right side of the screen is checked.

        Point

        If the Create the same Volume as the Primary Storage checkbox is checked, the following items can be omitted since they will have the same setting value as the Primary Storage.

        - FTV Name
        - Total Capacity
        - Number of Volumes
        - Allocation
        - Caution Threshold of FTV
        - Automated QoS Enable/Disable
        - Automated QoS:Priority
        - Target Response Time

        Note that a value must be entered for the following items regardless of the checkbox selection state.

        - Tier Pool Name
        - Priority FTSP
        - Low Quota Share
        - Middle Quota Share
        - High Quota Share
        - Tune by Quota Share

      5. Enter the required information for the Secondary Storage portion on the right side of the screen.

      6. Click Next.
        The information confirmation screen is displayed.

      7. Confirm the information, and then click Create.

For the information how to create a new volume in cases other than those listed above, refer to "Create Volume" or "Create FTV" in the Web Console Guide to create a new volume.

When using the volumes already allocated to servers for the Storage Cluster function, create volumes in an ETERNUS Disk storage system as the Secondary Storage so that the conditions described in "Required Conditions for TFOV" are satisfied.
In addition, if Advanced Copy is in operation, stop it.

See

To stop Advanced Copy, refer to either of the following sites in accordance with the function in use:

  • When the Copy Control Module function of AdvancedCopy Manager is in use:
    Refer to "Operations Started from Storage Tab" in the Web Console Guide.

  • When the backup operation or replication operation of AdvancedCopy Manager is in use:
    Refer to "Operations Started from Server Tab" - "Operations for Advanced Copy" in the Web Console Guide.

When the operations up to this point are completed, proceed to the following sections:

9.4.2.1.2 Configuring Access Path (when performing the procedure from a new volume creation with the Primary/Secondary Storage)

Connect the volumes to be switched by Storage Cluster function to servers.
The following three operations described in this section are required to configure access paths:

Point

Adding a host

The procedure for adding a host in Web Console is shown below.

Point

  • By following this procedure, the Primary Storage port and Secondary Storage port that are specified for the port pair can be associated to the same HBA without being aware of the WWPN/iSCSI name.

  • The hosts that are connected to the storage device and automatically detected are shown on the host list screen during this procedure. To automatically detect the target hosts to add, the zoning setting must be performed on the FC switch in advance, and the storage device must be able to communicate with the target hosts to add. Refer to the storageadm zone command for details on the zoning setting of the FC switch.

  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 that is specified as the Primary Storage.

  3. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  4. Add a host.

    • When adding an FC host

      1. On the Action pane, click Add FC Host under Allocating Business Volume.
        The information input screen is displayed.

      2. From the TFO Group drop-down list, select the TFO group to be used by the Storage Cluster function.
        From the Port drop-down list on the left side of the screen, a Primary side port in the TFO group can be selected.

      3. From the Port drop-down list, select a Primary side port that is assigned to the host.
        The two ports (Primary Storage port and Secondary Storage port) that are specified for the pair in the TFO group are displayed.

      4. In the host list, only the hosts that are connected to the Primary Storage port are displayed. Check the WWPN and select the host that is assigned to the port.

      5. Enter the necessary information, and then click Next.

      6. Confirm the information, and then click Add.

    • When adding an iSCSI host

      1. On the Action pane, click Add iSCSI Host under Allocating Business Volume.
        The information input screen is displayed.

      2. From the TFO Group drop-down list, select the TFO group to be used by the Storage Cluster function.
        From the Port drop-down list on the left side of the screen, a Primary side port in the TFO group can be selected.

      3. From the Port drop-down list, select a Primary side port that is assigned to the host.
        The two ports (Primary Storage port and Secondary Storage port) that are specified for the pair in the TFO group are displayed.

      4. In the host list, only the hosts that are connected to the Primary Storage port are displayed. Check the iSCSI name and select the host that is assigned to the port.

      5. Enter the necessary information, and then click Next.

      6. Confirm the information, and then click Add.

Creating an Affinity / LUN group

The procedure for creating an Affinity/LUN Group in Web Console is shown below.

Point

By following this procedure, the required conditions for the Storage Cluster switchover volume of the Primary/Secondary Storage in the Affinity/LUN Group can be satisfied. For the required conditions, refer to "Required Conditions for TFOV".

Note

When setting the Primary/Secondary Storage LUN mapping, set the same number for the host LUN. Of the volumes for which host affinity is set for the two ports of CA port pair, volumes for which host LUN No.(HLU) and volume capacity match are the target for synchronization.

  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 that is specified as the Primary Storage.

  3. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  4. On the Action pane, click Create Affinity /LUN Group under Allocating Business Volume.
    The information input screen is displayed.

  5. From the TFO Group drop-down list, select the TFO group to be used by the Storage Cluster function.
    On the left side of the screen, the information input screen for the Affinity/LUN Group that is created in the Primary Storage specified for the selected TFO group is displayed.
    On the right side of the screen, the information input screen for the Affinity/LUN Group that is created in the Secondary Storage specified for the selected TFO group is displayed.

  6. Input the Affinity/LUN group name in the Name field.

  7. Input the host LUN starting number in the Start Host LUN Number field.

  8. Select the volume assigned to the Affinity/LUN Group and click Add.
    In the assigned volume list, make sure the selected volume is displayed.

  9. Make sure that the Create the same Affinity/LUN Group as the Primary Storage checkbox in the Secondary Storage portion on the right side of the screen is checked.

  10. Click Next.
    The information confirmation screen is displayed.

  11. Confirm the information, and then click Create.

Configuring Host Affinity

The procedure for setting the host affinity in Web Console is shown below.

Point

By following this procedure, the host affinity between each port of the selected port pair and the selected host can be set.

  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 that is specified as the Primary Storage.

  3. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  4. On the Action pane, click Create Host Affinity under Allocating Business Volume.
    The information input screen is displayed.

  5. From the TFO Group drop-down list, select the TFO group to be used by the Storage Cluster function.
    On the left side of the screen, the information input screen for the host affinity that is created in the Primary Storage specified for the selected TFO group is displayed.
    On the right side of the screen, the information input screen for the host affinity that is created in the Secondary Storage specified for the selected TFO group is displayed.

  6. For the Primary Storage and the Secondary Storage, select a host to be set in the host affinity.

  7. Select a TFO group port pair to be set in the host affinity.

  8. For the Primary Storage and the Secondary Storage, select an Affinity/LUN Group to be set in the host affinity from the Affinity/LUN Group drop-down list.

  9. Click Create.

When the operations up to this point are completed, proceed to "9.4.2.1.4 Confirming Configuration".

9.4.2.1.3 Configuring Access Path (when allocating volumes to each storage or when adding the Secondary Storage where only the Primary Storage is used)

When starting from a new volume creation for both the Primary Storage and the Secondary Storage, refer to "9.4.2.1.2 Configuring Access Path (when performing the procedure from a new volume creation with the Primary/Secondary Storage)" for information on how to configure the access path.

When performing procedures other than those listed above, connect the volumes to be switched with the Storage Cluster function to the servers by performing the operations in this section on the Primary and Secondary ETERNUS Disk storage systems. However, if the configuration is already completed for the Primary Storage, perform the operations only for the Secondary Storage.

The following operations are required to configure access paths in the Storage Cluster structure:

It is recommended to use the volume allocation function to configure access paths that can perform the above operations all at one time and configure multiple access paths between a certain server and a certain ETERNUS Disk storage system at the same time.

If you configure access paths to the Primary Storage and the Secondary Storage with Web Console or the storageadm zone command, after the access path setting for the Secondary Storage is executed, the TFO port pair is configured and a volume synchronization with the Storage Cluster function is started.

Note

With the volume allocation function, multiple access paths cannot be set to the same ETERNUS Disk storage system from one HBA. When setting multiple access paths, add the access paths one by one using the procedure for adding access paths.

Point

The host affinity which Affinity/LUN groups that have 513 or more volumes is associated can be set in a BS2000 environment.

See

  • Refer to "Assign ETERNUS Disk Storage System Volumes to Server" in the Web Console Guide for the procedure for allocating volumes.

  • Refer to "Add Access Path to ETERNUS Disk Storage System" in the Web Console Guide for the procedure for adding access paths.

Configure access path in the following steps:

Note

  • If access path configuration does not meet the requirements, error occurs on the device side and the operation log is displayed. Refer to the Messages for corrective actions.

  • When setting the Primary/Secondary Storage LUN mapping, set the same number for the host LUN. Of the volumes for which host affinity is set for the two ports of CA port pair, volumes for which host LUN No.(HLU) and volume capacity match are the target for synchronization.

When the operations up to this point are completed, proceed to "9.4.2.1.4 Confirming Configuration".

9.4.2.1.4 Confirming Configuration

Confirm that the Storage Cluster function is configured correctly.

Point

When all the following requirements are met, the access state data between the Primary/Secondary Storage can be synchronized.

  • It is configured that the synchronization of the volume by the Storage Cluster function can begin between FTV.

  • Automated Storage Tiering control function on ETERNUS Disk storage system is used.

Refer to "Access Status Data Synchronization" in the Storage Cruiser Operation Guide for Optimization Function for the synchronization procedure of the access state data.

Note

  • In host affinity groups under a pair of CA ports, the volumes that have the same HLU number and capacity can be a synchronized pair. Match those volumes with the same HLU number and capacity.

  • In volume synchronization, an initial copy is done between paired volumes. The time required for initial copy is affected by line speed of transfer, quality, data compression ratio (depending on data contents), being greatly varied.
    An indication of time required is as follows:

    Table 9.10 Time Required for Initial Copy (Standard Value of 1 TB Physical Capacity Volume)

    Requirements for Initial Copy

    Time needed

    FC-RA port and IP network: one line (1 Gbit/sec) connection, Typical throughput of FC switch: 114 MB/sec (=114,000,000 byte/sec) (data compression ratio 50%, no delay)

    1.5 hrs

    FC-RA port and IP network: one line (100 Mbit/sec) connection, Typical throughput of FC switch: 12 MB/sec (=12,000,000 byte/sec) (data compression ratio 50%, no delay)

    13 hrs

    iSCSI-RA port and IP network: one line (1 Gbit/sec) connection, Typical throughput of iSCSI-RA port: 26 MB/sec (no data compression, 30 msec delayed)

    12 hrs

Figure 9.32 Storage Cluster Function: Example of Synchronized Volumes

The above figure represents the following matters:

  • A pair of Vol#0 of Storage A and Vol#10 of Storage B is the same in HLU number and size, so that they are synchronized (failover enabled) volumes.

  • A pair of Vol#1 of Storage A and Vol#11 of Storage B is different in HLU number, so that they cannot be synchronized.

  • A pair of Vol#2 of Storage A and Vol#12 of Storage B is different in size, so that they cannot be synchronized.

Trying to make a pair of CA ports correlated to the volumes that are the same in HLU number but different in size terminates the processing abnormally.

When the operations up to this point are completed, proceed to "9.4.2.1.5 Recognition of iSCSI IP Address to Business Server due to Manual Failover and Manual Failback".

9.4.2.1.5 Recognition of iSCSI IP Address to Business Server due to Manual Failover and Manual Failback

Use this procedure for iSCSI connection environments and when using Storage Cluster with a different iSCSI IP address.

The following procedure describes how to recognize the iSCSI IP address of the Secondary Storage in the business server.

  1. Recognize the iSCSI IP address of the Primary Storage in the business server.
    If the business server has already recognized it, this procedure is not required.

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

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

  4. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  5. On the Main pane, select a TFO group created with a different iSCSI IP address. After it, click Failover on the Action pane.
    The warning dialog box is displayed.

  6. Click OK.

  7. Recognize the iSCSI IP address of the Secondary Storage in the business server.

  8. On the Main pane, select a TFO group created with a different iSCSI IP address. After it, click Failback on the Action pane.
    The warning dialog box is displayed.

  9. Click OK.

9.4.2.2 Updating TFO Group Status

The TFO group status is automatically updated.
Perform the following procedure when you need to update it to its most recent state right away.

  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.
    Created TFO groups are displayed on the Main pane.

  4. On the Action pane, click Update under TFO Group Status.
    A dialog box is displayed. Click Done.
    When this operation is performed, the TFO status of the other device paired with the selected device is also updated.

    Note

    If communication is disabled between paired devices, the operation terminates abnormally with error status. Even in this case, the TFO status of the selected device is updated.

See

Refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" for details of the TFO group status and its meaning.

9.4.2.3 Adding and Deleting Business Volume

To change a volume enabled with the Storage Cluster function, delete that volume, add a new volume, or do both.
Either of the following methods can be performed for the work.

The following describes the work procedure for each method.

Method for simultaneously performing the work for the Affinity/LUN Group in both devices of the Primary Storage and Secondary Storage

  1. Confirm that the volume is in a state in which an addition/deletion operation can be performed.

    • When adding a volume

      Confirm that the TFO group where the volume is to be added has the following state.

      • Primary Storage side: The Active/Standby column is "Active".

      • Secondary Storage side: The Active/Standby column is "Standby".

    • When deleting a volume

      To continue using a volume that is not enabled with the Storage Cluster function and without using the Storage Cluster function, make sure all the following conditions are satisfied.

      • The TFO group phase is "Normal".

      • In the session information of the TFO pair related to the volume, the session status is "Active" and the session phase is "Equivalent".

    See

    For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".

  2. Change Affinity/LUN groups.

    Note

    In the procedure described here, for both devices of the Primary Storage and Secondary Storage, an affinity/LUN group that satisfies all the conditions of "[Required Conditions for Affinity/LUN Groups]" can be selected/set.

    [Required Conditions for Affinity/LUN Groups]

    • Corresponding volumes between the Primary Storage and the Secondary Storage have the same host LUN No. (HLU).

    • Corresponding volumes between the Primary Storage and the Secondary Storage have the same volume capacity.

    • Corresponding volumes between the Primary Storage and the Secondary Storage have the same volume type.

    Note that for either of the following, all the requirements described in "[Required Conditions for Affinity/LUN Groups]" are satisfied, so the procedure here can be performed.

    If the requirements described in "[Required Conditions for Affinity/LUN Groups]" are not satisfied, the procedure here cannot be performed. Perform the procedure in "Method for performing the work for each device of the Primary Storage and Secondary Storage".

    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 to specify as the Primary Storage.

    3. On the Category pane, click Storage Cluster.
      Created TFO groups are displayed on the Main pane.

    4. On the Main pane, select the TFO group whose setting is to be changed. And then, click Modify Affinity/LUN Group under Allocating Business Volume on the Action pane.
      The information input screen is displayed.

    5. In the [Port] drop-down on the left side of the screen, the ports on the Primary Storage side that are paired in the selected TFO group are displayed. Select the port with the access path setting to the affinity/LUN group to be changed.
      If the port is selected, the paired port of the Secondary Storage is displayed for the selected port.

    6. After a port is selected, a list of affinity/LUN groups with the access path setting to the selected port is displayed in the [Name] drop-down. Select the target affinity/LUN group to change in the Primary Storage and Secondary Storage.

      Point

      • If the affinity/LUN group name on the Primary Storage side is the same as the corresponding affinity/LUN group name on the Secondary Storage side

        For the volume that has the same name as the volume selected on the Primary Storage side, volume selection is omitted on the Secondary Storage side and the volume with the same name on the Primary Storage side is automatically selected.
        If the Modify the same Affinity/LUN Group as that of the Primary Storage checkbox is checked, the volume information that is selected on the Primary Storage is applied on the Secondary Storage side.

      • For cases other than the above

        The volumes in each affinity/LUN group of the Primary Storage and Secondary Storage must be selected.

    7. To add a volume to the affinity/LUN group, select the volume to assign and click Add. In the list of "Assigned Volumes", confirm that the selected volume is displayed.
      To delete a volume from the affinity/LUN group, select the volume to delete from the list of "Assigned Volumes" and then click Remove.

      Note

      If a port or an Affinity/LUN group on the Primary Storage side is reselected while a volume is selected, the volume selection of the Primary Storage and Secondary Storage returns to the state before transitioning to this screen. If it returns to the that state, the procedure must be started over from the volume selection.

    8. Click Next.
      The information confirmation screen is displayed.

    9. Confirm the information, and then click Modify.

  3. If a volume of the Secondary Storage that is not enabled with the Storage Cluster function is continued to be used without using the Storage Cluster function, use ETERNUS CLI to revert the information of that volume to the state prior to the data synchronization.
    Refer to the ETERNUS Disk storage system manuals for the command name and the format of ETERNUS CLI used.

    Note

    If this procedure is not performed, the volume information of the Secondary Storage may conflict with the volume information of the Primary Storage and data corruption may occur.


After changing a volume enabled with the Storage Cluster function, it takes a certain period of time for volumes to be synchronized and for failover to be enabled.
Refer to "9.4.2.1.4 Confirming Configuration" in "9.4.2.1 Allocating Business Volume" for the procedure to see if the volume synchronization is completed and failover can be executed.

Note

  • There is an upper limit to the number of volumes that can be defined to one Affinity/LUN group. Refer to the manual for the ETERNUS Disk storage system in use for the upper limit.

  • The format of a volume enabled with the Storage Cluster function is not supported.

  • The following volumes cannot be added:

    • The volume type is "SDV" or "SDPV".

    • Volumes that are used for the Non-disruptive Storage Migration.

    • Volumes whose External LU Information is "Inherited".

    • Volumes in which the Usage column in the screen of Web Console is "Veeam"

    • Volumes for which Advanced Copy is running.

Method for performing the work for each device of the Primary Storage and Secondary Storage

  1. Confirm that the volume is in a state in which an addition/deletion operation can be performed.

    • When adding a volume

      Confirm that the TFO group where the volume is to be added has the following state.

      • Primary Storage side: The Active/Standby column is "Active".

      • Secondary Storage side: The Active/Standby column is "Standby".

    • When deleting a volume

      To continue using a volume that is not enabled with the Storage Cluster function and without using the Storage Cluster function, make sure all the following conditions are satisfied.

      • The TFO group phase is "Normal".

      • In the session information of the TFO pair related to the volume, the session status is "Active" and the session phase is "Equivalent".

    See

    For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".

  2. Change Affinity/LUN groups for Primary and Secondary ETERNUS Disk storage systems.

    The procedure to see which Affinity/LUN group to change 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 a target ETERNUS Disk storage system.

    3. On the Category pane, click Connectivity.
      The items on the Category pane switch to those associated with Connectivity.

    4. On the Category pane, click Host Affinity.
      A list of host affinities is displayed on the Main pane.
      Check in the Port column, host affinity including ports specified as pairs in TFO groups. The Affinity/LUN group configured to the host affinity must be changed.

    See

    Refer to "Change Affinity/LUN Group Settings" in the Web Console Guide for the procedure to change Affinity/LUN group.

  3. If a volume of the Secondary Storage that is not enabled with the Storage Cluster function is continued to be used without using the Storage Cluster function, use ETERNUS CLI to revert the information of that volume to the state prior to the data synchronization.
    Refer to the ETERNUS Disk storage system manuals for the command name and the format of ETERNUS CLI used.

    Note

    If this procedure is not performed, the volume information of the Secondary Storage may conflict with the volume information of the Primary Storage and data corruption may occur.


After changing a volume enabled with the Storage Cluster function, it takes a certain period of time for volumes to be synchronized and for failover to be enabled.
Refer to "9.4.2.1.4 Confirming Configuration" in "9.4.2.1 Allocating Business Volume" for the procedure to see if the volume synchronization is completed and failover can be executed.

Note

  • There is an upper limit to the number of volumes that can be defined to one Affinity/LUN group. Refer to the manual for the ETERNUS Disk storage system in use for the upper limit.

  • The format of a volume enabled with the Storage Cluster function is not supported.

  • The following volumes cannot be added:

    • The volume type is "SDV" or "SDPV".

    • Volumes that are used for the Non-disruptive Storage Migration.

    • Volumes whose External LU Information is "Inherited".

    • Volumes in which the Usage column in the screen of Web Console is "Veeam"

    • Volumes for which Advanced Copy is running.

9.4.2.4 Expanding Business Volume Capacity

To expand the capacity of volumes enabled with the Storage Cluster function, all the following conditions must be satisfied:

Point

  • If the session status of the TFO pair is not "Active", the following causes are possible:

    • Temporary session pending by a failover or a failback

    • REC path close

    • Occurrence of a RAID failure, a RAID close, or a bad sector

    Check the status of the ETERNUS Disk storage system, and then perform the steps in "9.5 Maintenance" as required.

  • Only one volume pair can be specified for a single capacity expansion operation.

  • To provide against the unexpected, it is recommended that you expand the volume capacity after backing up the data of the target volumes.

  • Note that when expanding the capacity, a synchronization between paired volumes is temporarily desynchronized until the capacity expansion is completed. Upon completion of the capacity expansion, a synchronization between the paired volumes is performed with the initial copy. Refer to "Table 9.10 Time Required for Initial Copy (Standard Value of 1 TB Physical Capacity Volume)" for the time required for an initial copy.

  • After the capacities of the business volumes have been expanded, you must recognize the expanded volume capacities to the business server.

If the volume type is "Standard", expand the capacity of the business volumes with LUN Concatenation. A volume capacity expansion using LUN Concatenation can realize the following:

Note

  • To expand the capacity of a business volume whose volume type is "Standard", all the following conditions must be satisfied:

    • Conditions for specifiable business volumes

      • Current volume capacity is 1 GB or more.

      • The capacity of the concatenated volumes is less than 128 TB.

      • The number of concatenated volumes is less than 16.

      • The volume status is neither "Broken" nor "Data Lost" nor "Not Ready" nor "Readying".

      • RAID migration is not running.

      • No Advanced Copy session exists in which "Totally" is specified for the copy range.

        The following are the cases where "Totally" is specified for the copy range:

        - LUN to LUN copy of AdvancedCopy Manager CCM

        - Copy using ETERNUS SF AdvancedCopy Manager SRA

        - Copy using ETERNUS VSS Hardware Provider

        - SnapOPC+ that is set from ETERNUS Web GUI or ETERNUS CLI

    • Conditions for specifiable RAID groups

      • The number of concatenated volumes after an expansion is 16 or less.

      • The status of a RAID group is not "Broken".

      • Standard, WSV, SDP, or SDPV is registered in the RAID group or there are no volumes registered in the RAID group.

      • The RAID group does not belong to a Thin Provisioning Pool or a Flexible Tier Pool.

      • The RAID group is not registered as an Extreme Cache Pool.

      • The number of volumes that are registered in the RAID group is less than 128.

      • There is a free space of 1 GB or more in the RAID group.

      • The type of drive that constitutes the RAID groups to which the source volume belongs and the type of drive that constitutes the destination RAID groups are the same.

      • A RAID close does not occur in the RAID group.

  • To expand the capacity of a business volume whose volume type is "TPV" or "FTV", all the following conditions must be satisfied:

    • Current capacity is less than 128 TB.

    • If the target volume is TPV, a Thin Provisioning Volume balancing is not running.

    • If the target volume is FTV, a Tier pool balancing is not running.

    • RAID migration is not running.

    • The total capacity of all TPVs and all FTVs in the storage device does not exceed the maximum pool capacity of the storage device.

      The total capacity of all TPVs and FTVs that can be created in a storage device depends on the maximum pool capacity of the storage device. Refer to the ETERNUS Disk storage system manuals for the maximum pool capacity that can be created.

    • No Advanced Copy session exists in which "Totally" is specified for the copy range.

      The following are the cases where "Totally" is specified for the copy range:

      - LUN to LUN copy of AdvancedCopy Manager CCM

      - Copy using ETERNUS SF AdvancedCopy Manager SRA

      - Copy using ETERNUS VSS Hardware Provider

      - SnapOPC+ that is set from ETERNUS Web GUI or ETERNUS CLI

If you perform a capacity expansion for the business volumes of either the Primary Storage or the Secondary Storage, the business volume capacity is expanded for both the Primary Storage and the Secondary Storage.

The procedure to expand the capacity of a business volume with Web Console 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 a target ETERNUS Disk storage system.

  3. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  4. On the Main pane, click the Name of a target TFO group.
    The TFO group details screen is displayed on the Main pane.

  5. On the Main pane, click the Volume tab.
    The information for a pair of local volume and remote volume is displayed.

  6. After checking the target volume checkbox to be expanded the capacity, click Expand Capacity under TFOV on the Action pane.
    The Expand TFOV wizard screen is displayed.

  7. Perform the following procedures according to the volume type.

    For Standard

    1. Enter the expanded capacity in the Post-Expansion Volume Capacity field in the Expand TFOV on Primary storage site page.

      Point

      The maximum number of characters that can be entered in the item field is 15 including a decimal point. If you select "MB" (megabytes) as the unit, the digits after the decimal point are rounded off. If you select "GB" (gigabytes) or "TB" (terabytes) as the unit, the digits after the decimal point of a value converted to megabytes are rounded off.

      For the capacity, enter a value that is 2 GB or more, and less than the free space of the RAID group.
      Also, the maximum volume size of 128 TB must not be exceeded.

      Entering the same capacity as Maximum Free Space of the RAID group with the same format (same number of digits in gigabytes or terabytes) adds the corrected capacity so that all the free space in the RAID group is used. If you want to add the entered capacity without making a correction, enter it in megabytes.

    2. Select a RAID group for which to secure capacity from a list of RAID groups in the Primary Storage.

    3. Click Next.
      The Expand TFOV on Secondary storage site page is displayed.

    4. Select a RAID group for which to secure capacity from a list of RAID groups in the Secondary Storage.

    5. Click Next.
      The Confirm page is displayed.

    6. After checking that the setting is correct, click Expand.

    For TPV or FTV

    1. Enter the expanded capacity in the Post-Expansion Volume Capacity field in the Expand TFOV (TPV/FTV) page.

      Point

      The maximum number of characters that can be entered in the item field is 15 including a decimal point. If you select "MB" (megabytes) as the unit, the digits after the decimal point are rounded off. If you select "GB" (gigabytes) or "TB" (terabytes) as the unit, the digits after the decimal point of a value converted to megabytes are rounded off.

      For the capacity, enter a value between 25 MB and 128 TB.

    2. After checking that the setting is correct, click Expand.

9.4.2.5 Changing Total Capacity of TFOVs

The total capacity of TFOVs can be changed. Refer to "Expanding Total Capacity of TFOVs" for the procedure to change the total capacity of TFOVs.

Point

If any paired TFO group exists, the total capacity of TFOVs cannot be reduced. If you reduce the total capacity of TFOVs, perform the following actions:

  1. Perform the procedure in "9.5.8 Releasing TFO Pair" to release all TFO pairs.

  2. Perform the procedure in "9.4.2.3 Adding and Deleting Business Volume" to delete unnecessary business volumes. Set the total capacity of all TFOVs to a value below the total capacity of TFOVs to be set in Step 3.

  3. Change the total capacity of TFOVs.

  4. If you continue to use Storage Cluster, perform the procedure in "9.5.9 Recovering TFO Pair" to recover all the TFO pairs that were released in Step 1.

9.4.2.6 Manual Failover/Failback

If Storage Cluster Controller is placed and Automated Failover is set when configuring TFO groups, any failure in ETERNUS Disk storage systems are detected and failover is automatically performed. In the case the Storage Cluster Controller is not placed or switchover is needed right now for switching test, failover can be done manually. When performing Failover manually, Normal mode and Forced mode can be selected. Refer to "9.4.2.7 Force-Failover" for Forced mode.

When setting automatic Failback with a TFO group setting, after the Primary Storage ETERNUS Disk storage system has recovered, failback is performed automatically after detecting that it has moved into a state where failback is possible. When it is recovered from RAID failure and you wish to switchover at an arbitrary time, it is possible to perform manual failback.

Point

When performing a manual failover/failback, make sure that the operation can be performed and the data integrity is consistent by checking the status of the TFO group to switch and the session information of the TFO pair.
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".

Note

  • If a manual failover/failback is performed when the TFO group phase is not normal or when the session status of the TFO pair is not normal, the integrity of the data may become inconsistent.

  • In an environment that uses the following storage devices, a failover/failback cannot be performed when the TFO group phase is "Maintenance". If an attempt is made, it results in an error.

    • ETERNUS DX S6 series

    • ETERNUS DX S5 series, ETERNUS DX8900 S4, or ETERNUS AF S3 series that has firmware version V11L40-5000 or later

    • ETERNUS DX S4/S3 series (excluding the ETERNUS DX8900 S4), or ETERNUS AF S2 series, AF series that has firmware version V10L90-1000 or later

The following is the procedure to perform a manual failover/failback. Failover/failback can be performed from either Primary/Secondary Storage.

  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.
    Created TFO groups are displayed on the Main pane.

  4. After confirming the status of the TFO group and the session information of the TFO pair, select a TFO group to enable failover or failback on the Main pane and click Failover or Failback on the Action pane.
    A warning dialog box is displayed.

  5. When enabling failover or failback, click OK.

Point

  • If the Primary ETERNUS Disk storage system is down or removed and communication is not enabled with that storage system, Manual Failover is not possible. Make sure that the Primary disk storage system is stopped to execute Force-Failover.

  • While a restore process from Veeam Storage Integration is running, a failover cannot be performed manually. After confirming that the restore process is completed, perform the failover manually.

9.4.2.7 Force-Failover

Execute Force-Failover by performing the following procedure only when instructed by your maintenance engineer when the Primary ETERNUS Disk storage system is down or removed and becomes inaccessible from business servers:

  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.
    Select a Primary ETERNUS Disk storage system.

  3. On the Category pane, click Storage Cluster.
    Created TFO groups are displayed on the Main pane.

  4. On the Main pane, select a TFO group for which you want to enable Force-Failover and click Force-Failover on the Action pane.
    A warning dialog box is displayed.

  5. When executing Force-Failover, click OK.

Note

  • If the ETERNUS Disk storage system as the Primary Storage is connected to business servers, do not execute this function.
    If this function is executed, the Secondary ETERNUS Disk storage system is forced to be active. At this stage, if the Primary ETERNUS Disk storage system is connected to servers, both the Primary Storage and the Secondary Storage are caused to be active, possibly leading to data corruption due to access to both the Primary Storage and the Secondary Storage.

  • If a recovery can be performed with the procedure described in "9.5 Maintenance", do not execute this function.

  • Even if this function is executed, a normal mode failover may be executed depending on the state of the ETERNUS Disk storage system and the state of Primary Storage may become "Standby".

9.4.2.8 Failover/Failback Limited to the Maintenance State

Follow the instructions of your maintenance engineer and perform a failover (Maintenance state only) or a failback (Maintenance state only) using the following procedure only if a manual failover/failback must be performed while the TFO group phase is "Maintenance".

Point

  • To perform the procedure in this section, the target storage device and the firmware version must satisfy the following conditions.

    Storage Device

    Firmware Version

    ETERNUS DX S6 series

    All versions

    ETERNUS DX S5 series
    ETERNUS DX8900 S4
    ETERNUS AF S3 series

    V11L40-5000 or later

    ETERNUS DX S4/S3 series (excluding the ETERNUS DX8900 S4)
    ETERNUS AF S2 series
    ETERNUS AF series

    V10L90-1000 or later

  • The procedure in this section can be performed for either the Primary Storage or the Secondary Storage.

Note

The procedure in this section has a risk of causing data corruption. Because of that, make sure to carefully follow the instructions of your maintenance engineer.

  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.
    Created TFO groups are displayed on the Main pane.

  4. On the Main pane, click the Name of a target TFO group for which you want to failover or failback.
    Information of the selected TFO group is displayed on the Main pane.

  5. On the Action pane, click Advanced Operations.
    The Failover(Maintenance state only) and Failback(Maintenance state only) are displayed on the Action pane.

  6. On the Action pane, click Failover(Maintenance state only) or Failback(Maintenance state only).
    A warning dialog box is displayed. Check the contents displayed on the warning dialog box.

  7. When enabling failover or failback, click OK.

9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen

The meaning and action plan of each status for TFO groups that are displayed on the Storage Cluster overview screen are as follows.

Phase

This displays the status of TFO group. The phase varies with the configuration of TFO groups, operation of failover/failback and state of volume synchronization.

Status

Meaning and Action Plan

Initial

Indicates that TFO group is configured but no volume is allocated.
Refer to "9.4.1 Installation" and "9.4.2 Operation" to continue configuration.

Maintenance

Indicates that copy sessions between TFO port pairs and volumes are forcibly cleared. Perform the following actions:

  • When there is an abnormality in the TFO pair session

    Refer to "9.4.2.10.2 Session Information of TFO Pairs" and confirm whether there is an abnormality in the TFO pair session. When an abnormality occurs, take action according to the procedure that matches the applicable case described in "9.5 Maintenance".
    If there is no applicable case, perform the following operations.

    1. To eliminate the abnormal state of the TFO pair session, perform the procedure in "9.5.8 Releasing TFO Pair" to release the TFO pair.

    2. If necessary, eliminate the cause of the abnormal state in the TFO pair session.

    3. Perform the procedure in "9.5.9 Recovering TFO Pair" to recover the TFO pair.

  • When there is a TFOV that is not set with a TFO pair within the TFO group

    Refer to "9.4.1 Installation" and "9.4.2 Operation" and review the setting status of the applicable TFOV.

  • When a restore process is executed from Veeam Storage Integration

    Wait until the restore process is completed.

If a failover/failback is performed when the TFO group phase is "Maintenance", note that the integrity of the data may become inconsistent.

In an environment that uses the following storage devices, a failover/failback cannot be performed when the TFO group phase is "Maintenance". If an attempt is made, it results in an error. Take action to recover from the "Maintenance" state. If a failover/failback must be performed for maintenance while the TFO group phase is "Maintenance", contact your maintenance engineer in advance.

  • ETERNUS DX S6 series

  • ETERNUS DX S5 series, ETERNUS DX8900 S4, or ETERNUS AF S3 series that has firmware version V11L40-5000 or later

  • ETERNUS DX S4/S3 series (excluding the ETERNUS DX8900 S4), or ETERNUS AF S2 series, AF series that has firmware version V10L90-1000 or later

Copying

Indicates that volumes are being synchronized from the Primary Storage to the Secondary Storage. Wait until the synchronization process is completed.

Normal

Indicates that volume synchronization is completed and failover is ready to be done.

Failovered

Indicates the status immediately after failover is completed. Update after a while.

Copying Back

Indicates that after recovery of the Primary Storage, volumes are being synchronized from the Secondary Storage to the Primary Storage. Wait until the synchronization process is completed.

Failback Ready

Indicates that after recovery of the Primary Storage, the volume synchronization process is completed and failback is ready to be done.

Failbacked

Indicates the status immediately after failback is completed. Update after a while.

Failed

This state indicates that the ETERNUS Disk storage system is down or the REC route is disconnected. During the failover/failback sequence, if this phase is displayed, wait a while before updating.

Attention
(*1)

There is a phase inconsistency for the Primary TFO group and the Secondary TFO group. After confirming the Phase column value from the TFO group details screen for both the Primary Storage and the Secondary Storage, follow each direction on this table.

Unknown
(*2)

Trouble with network is causing status update to fail. A disk storage switched due to a failure becomes "Unknown" because status update is sure to fail. Refer to "9.4.2.2 Updating TFO Group Status" to update the status of TFO group.

*1: This is only displayed on the Storage Cluster overview screen.
*2: For the "Unknown" status, because a common meaning is shown in all the columns, the meaning is omitted in the columns that follow.

Status

This displays whether TFO group status is normal or error.

Status

Meaning and Action Plan

Halt

Indicates that there is a fault in TFO group. Refer to "Halt Factor" in "9.4.2.10.1 TFO Group Information" to take action.

Normal

Indicates that TFO group is in normal status. No action is required.

Disruption
(*1)

There is a phase inconsistency for the Primary TFO group and the Secondary TFO group.
After confirming the Status column value from the TFO group details screen for both the Primary Storage and the Secondary Storage, follow each direction on this table.

*1: This is only displayed on the Storage Cluster overview screen.

TFO Mode

This displays the operational configuration of the TFO group. This item is displayed only for Group A devices in "Table 9.1 Relationship between the Storage Device and the Operable TFO Group Configuration".

Status

Meaning

Active-Active

Indicates that the TFO group is operated with the Active-Active configuration.

Active-Standby

Indicates that the TFO group is operated with the Active-Standby configuration.

Active/Standby

This displays whether the disk storage is connected to the server (active side) or not connected to the server (standby side).

Status

Meaning

Active

Indicates that the disk storage is currently connected to a server (active side).

Standby

Indicates that the disk storage is not connected to a server (standby side).

9.4.2.10 Confirming the Status on the TFO Group Details Screen

9.4.2.10.1 TFO Group Information

The meaning and action plan of each status for the TFO group details screen are as follows.

Active/Standby

The same statuses as the Active/Standby column of the Storage Cluster overview screen are displayed.
Refer to "Active/Standby" in "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen"

Phase

The same statuses as the Phase column of the Storage Cluster overview screen are displayed.
Refer to "Phase" in "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen"

Status

The same statuses as the Status column of the Storage Cluster overview screen are displayed.
Refer to "Status" in "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen"

TFO Mode

The same statuses as the TFO Mode column of the Storage Cluster overview screen are displayed.
Refer to "TFO Mode" in "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen"

Halt Factor

If there is any error in TFO group, its cause is displayed.

Status

Meaning and Action Plan

None

Indicates that TFO group is in normal status. No action is required.

TFO Group Disconnected

Indicates that the path to a destination device is blocked or the device is not started. Remove the factor of path blockage or start the destination device.

Version Mismatch

Indicates that a destination device does not support Storage Cluster function or the firmware version does not support Storage Cluster. If the firmware is not up-to-date, update the firmware.

TFO Group Setting Missing

TFO group settings of a destination device are not found. Refer to "9.4.1 Installation" and "9.4.2 Operation" to review the settings or reconfigure.

TFO Group Setting Mismatch

Indicates that data transfer of Storage Cluster is disabled at all the RA ports of the Secondary Storage or there are some inconsistencies in TFO group settings at a destination device. Take either of the following actions:

Monitoring Server Disconnected

Indicates that the path to Storage Cluster Controller is blocked or Storage Cluster Controller is not started. This status is displayed only when Storage Cluster Controller is set up. Take either of the following actions:

  • Review the communication path between Storage Cluster Controller and ETERNUS Disk storage system.

  • Refer to "9.6 Storage Cluster Controller" to review the settings or reconfigure.

Note

When any status other than those above is displayed, perform the following operations:

If the problem is not solved, record the displayed status and contact Fujitsu Technical Support.

9.4.2.10.2 Session Information of TFO Pairs

The session information of the TFO pair is displayed in the Volume tab of the TFO group details screen. The meaning and action plan of each status are as follows.

Session status of volumes

Status

Meaning and Action Plan

Active

Volume synchronization is operating normally. No action is required.

Error Suspend

Volume synchronization is suspended due to an error. Refer to "9.4.1 Installation" and "9.4.2 Operation" to review the settings or reconfigure, or take action according to the procedure that matches the applicable case described in "9.5 Maintenance".

Suspend

Volume synchronization is suspended. The Standby side storage may be down. Check the state of the Standby side storage and perform the following actions.

  • When the Standby side storage is recoverable

    After recovering the storage, perform the following operations.

    1. To eliminate the abnormal state of the TFO pair session, perform the procedure in "9.5.8 Releasing TFO Pair" to release the TFO pair.

    2. Perform the procedure in "9.5.9 Recovering TFO Pair" to recover the TFO pair.

  • When a replacement of the Standby side storage is required

    Perform the procedure in "9.5.1 ETERNUS Disk Storage System Fault" to recover the Standby side storage.

Halt

Volume synchronization is in an abnormal state. Refer to "Halt Factor" in "9.4.2.10.1 TFO Group Information" to take action.

Session phase of volumes

Status

Meaning and Action Plan

Copying

A volume is being synchronized from the Primary Storage to the Secondary Storage. Wait until the synchronization process is completed.

Equivalent

  • When the session status of the volume is "Active"

    The synchronization process of the volume is completed and the equivalency maintenance state is continued. No action is required.

  • When the session status of the volume is not "Active"

    The integrity of the data may be inconsistent. Refer to "Meaning and Action Plan" for the displayed status and perform the corrective action.

PreviousNext
Copyright 2013-2024 Fujitsu Limited