Before importing the HA replication pairs, make sure of the
following:
- Both primary and secondary storage systems of the high availability (HA) pairs are onboarded on Ops Center Administrator.
- The data flow for HA pairs is created with the following conditions in
Ops Center Protector:
- The node for the primary storage is Hitachi Block Host.
- The logical devices for the primary volumes are defined in the
Included Logical Devices of the Hitachi Block Host.
The logical device must be defined with the LDEV_ID. Ops Center Administrator cannot use logical devices defined with Host Group ID.
- Specify Use Block Host selections in the Specify Hitachi Block Storage classification attributes of the policy.
- Configure the following in Secondary Volume Host Groups in the Dataflow:
- Specify Enforce LUN ID Matching.
- Specify host groups in Secondary Volume Host Groups.
- Do not specify Automatically Provisioned Host Group.
Note: If you configure the following in Secondary Volume Host Groups in the Dataflow, legacy remote replication groups are imported:- Specify Automatically Provisioned Host Group.
- Do not specify any host groups in Optionally specify one or more host groups on the destination storage system.
- Replication is marked as Active Full Copy in Ops Center Protector.
- The HA pair must use a Quorum disk.
Note:
- If you add or remove pairs in the replication group, the logical device range will be regenerated and the updated logical device specification will be listed as a list of single logical device specification and the Excluded Logical Devices specification will be retained.
- Do not change the following configuration on Ops Center Protector to change the remote replication group type:
- Enforce LUN ID Matching
- Host groups in Secondary Volume Host Groups
- Automatically Provisioned Host Group
Changing these configurations might create unexpected paths between the hosts and volumes when adding or removing pairs in the replication group.