No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback:
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 Device Used by a Protected Object

Storage Device Used by a Protected Object

This section describes the storage restrictions and limitations of a protected object.

You must comply with version restrictions and limitations when using a storage device for a protected object supported by eReplication. Read descriptions in eReplication before implementing DR for a protected object.
Table 1-20  Restrictions and limitations on a storage device used by the protected object

Object

Restriction

Compatibility

Only support the DR protection solutions based on the Huawei storage value-added features. The storage devices must meet the compatibility requirements. For details, see the OceanStor BCManager 6.5.0 eReplication Compatibility List.
NOTE:

Dorado storage systems only support active-passive DR solutions based on asynchronous replication (SAN) DR and local protection solutions based on snapshot (SAN) DR.

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.
  • The solution based on mirroring (VIS) and asynchronous replication (SAN) must meet the following requirements:
    • The LUNs used by the VIS volume must be created the remote replication, and added into a consistency group.
    • The storage plan for the protected VMs of using VIS volumes for part and using storage LUNs for part is not supported.
    • Configuring remote replication relationships for LUNs associated with both VIS volumes and mirrored disks that are used for protected applications is not supported. Only one of the LUNs can be configured with asynchronous remote replications.
    • All the disks where the applications reside must source from VIS volumes. The VIS volumes must meet the following requirements:
      • When creating logical disk groups, set data retention of the logical disks to Yes.
      • Data retention of a Data Change Object (DCO) disk must be set to No.
      • The VIS volumes and logical disks are in one-to-one relationship. A complete logical disk must be used to create VIS volumes. Volume expansion is not supported.
      • VIS volumes used by applications must be configured with mirroring relationships.

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.
  • The established remote replication or consistency must meet the following requirements: synchronous and asynchronous cascading replication, synchronous and asynchronous parallel replication, asynchronous and asynchronous cascading replication, and asynchronous and asynchronous parallel replication.

    In the DR Star network scenario, DR Star must meet the following requirements: DR Star cascading replication (synchronous + asynchronous), DR Star parallel (synchronous + asynchronous), and 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 eReplication server.

  • Only the Geo-Redundant Solution provides by T series V200R002 and later versions, 18000 series, and V3 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 asynchronous replication (SAN) must meet the following requirements:
    • The HyperMetro consistency group cannot contain unprotected LUNs whose remote replication relationships are created.
    • The remote replication relationships must be configured in the same consistency group.

      If the protected object is an Oracle database, and multiple archive logs are configured for the database, at least one group of archive logs must use storage resources that are configured with a remote replication relationship or a consistency group. In addition, the consistency group must be a different one from that of data files, control files, and online log files.

    • 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.

      If the protected object is an Oracle database and archive logs are configured in the database, archive logs, data files, control files, and online log files must be configured in two different DR Stars.

  • 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.
    • The remote replication relationships must be configured in the same consistency group.
    • 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 geo-redundant DR solution based on HyperMetro (VIS) and asynchronous replication (SAN), all the disks where applications reside must source from VIS volumes. The VIS volumes must meet the following requirements:
    • When creating logical disk groups, set data retention of the logical disks to Yes.
    • Data retention of a DCO disk must be set to No.
    • The VIS volumes and logical disks are in one-to-one relationship. A complete logical disk must be used to create VIS volumes. Volume expansion is not supported.
    • VIS volumes used by applications must be configured with mirroring relationships.
    • Configuring remote replication relationships for LUNs associated with both VIS volumes and mirrored disks that are used for protected applications is not supported. Only one of the LUNs can be configured with asynchronous remote replications.
  • In the DR Star network scenario, only the storage with DR Star is supported (V3 series V500R007C20 and later versions, Dorado series V300R002C00 and later versions).

HyperMetro DC solution

  • The DR data center solution (HyperMetro Mode) based on HyperMetro (SAN) and snapshot (SAN) must meet the following requirements:

    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 data center solution (HyperMetro Mode) based on HyperMetro (VIS), all the disks where the applications reside must source from VIS volumes. The VIS volumes must meet the following requirements:
    • When creating logical disk groups, set data retention of the logical disks to Yes.
    • Data retention of a DCO disk must be set to No.
    • The VIS volumes and logical disks are in one-to-one relationship. A complete logical disk must be used to create VIS volumes. Volume expansion is not supported.
    • VIS volumes used by VMs must be configured with mirroring relationships.
  • The mapping relationship between the host and storage device can be established by initiator mapping. Port mapping is not supported.
  • The active-active DC solution based on NAS must meet the following requirements:
    • The local vStore and the remote vStore must be paired as a HyperMetro vStore pair the HyperMetro pairs of file systems are all working properly.
    • All file systems in the local vStore must be paired with file systems in the remote vStore in one-to-one mode.

Local HA solution

  • In the HA solution based on mirroring (VIS), all the disks where the applications reside must source from VIS volumes. The VIS volumes must meet the following requirements:
    • When creating logical disk groups, set data retention of the logical disks to Yes.
    • Data retention of a DCO disk must be set to No.
    • The VIS volumes and logical disks are in one-to-one relationship. A complete logical disk must be used to create VIS volumes. Volume expansion is not supported.
    • VIS volumes used by applications must be configured with mirroring relationships.
  • The mapping relationship between the host and storage device can be established by initiator mapping. Port mapping is not supported.

Local protection solution

  • In the disaster recovery data center solution based on VIS snapshots, configure sufficient cache and data DCO disks on a VIS storage device to ensure sufficient space for storage of duplicates.
  • In the disaster recovery data center solution based on clone SAN, ensure that the controllers and capacities of the created and protected primary LUNs are consistent and no secondary LUNs of data protection tasks have been created.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 18579

Downloads: 76

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next