Storage Device Used by a Protected Object

Compatibility

Only support the DR protection solutions based on the Huawei storage value-added features. The storage devices must meet the compatibility requirements.

Active-passive DR solution

• Active-passive, passive-passive, and N:1 share DR protection solutions are supported.
• If data consistency needs to be guaranteed for protected VMs, the used storage device must be configured with the replication relationship of a consistency group.
  • If data of a single VM is stored in a LUN, remote replication relationships must be created for the LUN.
  • If data of a single VM is stored in multiple LUNs, remote replication relationships must be created for all LUNs, and the LUNs must be added in the same consistency group.
• One-to-two synchronous remote replication is not supported.
• The storage device models used at the production site and DR site can be slightly different (for example, the storage device used at the production site is OceanStor 18000 series, and that used at the DR site is OceanStor T series). However, you must ensure that remote replication relationships can be successfully established.
• The mapping relationship between the host and storage device can be established by initiator mapping. Port mapping is not supported.
• If Huawei Distributed Block Storage is used, only one-to-one asynchronous replication DR protection is supported. In addition, the consistency replication relationship must be configured for the storage devices to be used.
• After a fault recovery or planned migration is performed, you need to perform reprotection before adding or removing volume protection.

Geo-redundant DR solution

• If data consistency needs to be guaranteed for protected applications, the storage device used by the applications must be configured with the replication relationship of a consistency group.
  • If data of a single application is stored in a LUN, remote replication relationships must be created for the LUN.
  • If data of a single application is stored in multiple LUNs, remote replication relationships must be created for all LUNs, and the LUNs must be added in the same consistency group.
  • In the DR Star network scenario, all LUNs must be in one DR Star.
• In the DR Star network scenario, DR Star must meet the following requirements: DR Star HyperMetro (SAN) + asynchronous replication (SAN). In addition, one DR Star can be used only in one protected group and cannot be used by other protected groups of the local or remote UltraVR server.
• Only the Geo-Redundant Solution provides by T series V200R002, 18000 series, V3 series, V5 series and Dorado series are supported.
• One-to-two synchronous remote replication is not supported.
• The storage device models used at the production site and DR site can be slightly different (for example, the storage device used at the production site is OceanStor 18000 series, and that used at the DR site is OceanStor T series). However, you must ensure that remote replication relationships can be successfully established.
• The mapping relationship between the host and storage device can be established by initiator mapping. Port mapping is not supported.
• The geo-redundant DR solution based on HyperMetro (SAN) and synchronous replication (SAN) must meet the following requirements:
  • The HyperMetro consistency group cannot contain unprotected LUNs whose remote replication relationships are created.
  • LUNs used by the protected objects in the protected group must be located in the same HyperMetro consistency group. In addition, the HyperMetro consistency group contains only the LUNs used by the protected objects.
  • In the DR Star network scenario, the remote replication consistency group that is created must be in one DR Star.

HyperMetro DC solution

• The mapping relationship between the host and storage device can be established by initiator mapping. Port mapping is not supported.

HA solution

• Supports only Huawei Distributed Block Storage.
• Supports only one-to-one HyperMetro pair DR protection. In addition, the storage must be configured with a consistent replication relationship.
• Disaster recovery is not supported for VMs with IDE disks.