Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Storage Interconnection Rules
This section describes how to plan a HyperMetro storage layout.
Both HyperMetro storage systems must comply with the following principles.
Storage Devices
For OceanStor Dorado 6.0.0, the local and remote storage systems must use the same product model.
Storage Pools
- The storage pools where the HyperMetro LUNs reside must use the same storage media and configurations (such as RAID policies).
LUNs
- The local and remote LUNs in a HyperMetro pair must have the same capacity.
- The LUNs in a HyperMetro pair must be mapped to all hosts.
- The LUNs used by a database or VM must be added to the same consistency group. The snapshots of LUNs used by the same application must be protected by a consistency group.
- If either of the two storage systems has taken over a heterogeneous storage system, eDevLUNs that are taken over in online mode and have the Third-party or Basic masquerading properties can be used to create HyperMetro pairs. Before creating HyperMetro pairs, use SmartMigration to migrate data to the local storage system. After data migration is complete, cancel the migration relationship and use the eDevLUNs as internal LUNs. The remote LUN of the HyperMetro pair is an internal LUN whose masquerading property is No Masquerading.