Protecting existing volumes with high availability

Ops Center Administrator User Guide

Version
10.9.x
File Size
6.6 MB
Audience
anonymous
Part Number
MK-99ADM001-17

You can protect existing volumes with high availability.

  • Register Ops Center Protector in Ops Center Administrator.
  • Set up your environment for high availability.
Note:
  • If you want to align the same volume ID between a primary volume with a secondary volume of a high availability pair, the secondary volume ID must belong to the metadevice or the same virtual storage machine as the primary storage system. If you want to use the same virtual storage machine, ensure it has the same resource group.
  • To protect a volume which is also the primary volume in another high availability pair, Ops Center Protector v7.5.2 or later needs to be registered.
  1. Access the Volumes window and select one or more attached volumes. They cannot belong to different VSMs. Click Actions > Protect Volumes and select Protect Volumes with High Availability.

    Attach Settings in Protect Volumes with HA

  2. The Host Mode is set by default to the server operating system. You can make a selection if needed.
    The server OS Type is provided when the server is added to Ops Center Administrator.
  3. The prepopulated Host Mode Option depends on the Host Mode selection. The default Host Mode Option can be changed manually.
    Default values are set only for VMWARE EX and WIN EX host modes. The default for all other host modes is none.
    Ops Center Administrator identifies all host groups containing any of the server WWNs. If all host groups have the same host mode and host mode options, those settings are prepopulated with the same settings in the host groups.
  4. Select Mandate LUN Alignment.
    This option specifies whether to assign the same LUN number to multiple servers for volumes containing primary and secondary HA pairs. If Yes is specified, the same LUN number (LUN number of primary volume) is always assigned to each primary and secondary HA pair volumes among all servers. If No is specified, Ops Center Administrator tries to use the same LUN if it is available. If it is not available, Ops Center Administrator selects available LUNs separately for each primary and secondary volume.
  5. The Auto Create Zone is set to No by default. You can set it to Yes to automatically create zones.
  6. ALUA Enabled is set to Yes. If it is set to No, you must rediscover volume or restart the OS after job completion.
  7. Click Next to select secondary servers, if applicable.
  8. Click Next to choose a secondary storage system and replication group, and quorum disk.

    protect volumes with high availability--protect

  9. In the Protect Volumes window, select a secondary storage system.
  10. Choose whether to use an existing replication group.
  11. Select the Consistency setting. By default, this is set to Yes. Using consistency means that copy processes run on all pairs in the group simultaneously.
  12. Select a replication group from the options in the Replication Group list or enter a new name. Up to 26 alphanumeric characters, and hyphens (-) and underscores (_), are allowed. Spaces are not allowed. If you select an existing replication group, the Storage Pool of Secondary Storage System for S-Vol and Quorum Disk are selected automatically.
    Note: Ops Center Administrator can protect volumes with high availability in existing replication group with following conditions:
    • P-VOL STATUS and S-VOL STATUS of all paired volumes in the replication group is PAIR.
    • Status of the corresponding replication in Ops Center Protector is OK.
    Note: Capacity saving setting applied to the secondary volumes depends on the version of Ops Center Protector.
    • v7.4 or earlier: The capacity saving setting of the secondary volumes will not be enabled.
    • v7.5 or later: The same capacity saving setting as the selected volumes will be applied to the secondary volumes. However, it will not necessarily be applied in any of the following cases:
      • An existing replication group is selected and Match Origin Volumes is set as the capacity saving setting policy in the corresponding Data Flow in Ops Center Protector
        • Ops Center Administrator will only set Match Source Volumes or None but Match Origin Volumes can be set in Ops Center Protector for cascading high availability pairs. Ops Center Administrator does not support that pair configuration.
      • The pool specified in Storage Pool of Secondary Storage System for S-Vol cannot be used to create volumes with capacity saving enabled.
  13. Select the pool to use for S-Vols and select a quorum disk.
  14. Click Next to configure the primary site.
  15. In the Configure Primary Site window, you can view the path of the primary server. If you need to change it, you must edit the LUN path before applying data protection.

    protect volumes with high availability--configure primary site

    Optionally, you can click Switch View to use tables to create paths by selecting Server Ports to attach to Storage Ports.

    For VSP 5000 series storage systems, you can click a port to display a list of ports with their DKC locations, CTL locations, and redundancy levels.
    Port Redundancy Level

  16. Click Next to configure ports in the secondary storage system to the server in the primary site, and to the server is the secondary site, if there is one.
  17. Click Submit to create a job to protect volumes.
  18. You can monitor the job in the Jobs window.
  19. When you protect a volume which is also the primary volume in another high availability pair, suspend the original high availability pair in tools other than Ops Center Administrator. The job is completed after suspending the original high availability pair.
    Note: If the job does not complete successfully, access Ops Center Protector to remove the related resources (Block Host Node, Policy, and Data Flow) with the same name as the selected replication group. When using an existing replication group, remove added P-Vol from Block Host Node.

    To edit a Block Host Node created by Ops Center Administrator in Ops Center Protector, specify LDEV IDs in decimal format per line and not in hex format or range format.