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).
VMware VMs

VMware VMs

This section introduces the DR restrictions for VMware VM protected objects.

You must comply with version restrictions when implementing DR for a protected object. Read description in Table 1-12 before implementing DR for a VMware VM.
Table 1-12  DR restrictions for VMware VMs

Object

Restriction

Compatibility

  • VMware vSphere 5.0, VMware vSphere 5.1, VMware vSphere 5.5, VMware vSphere 6.0, VMware vSphere 6.5, and VMware vSphere 6.7 are supported.

  • In HyperMetro (NAS) scenarios, only OceanStor V3 series V300R006C00 and later versions can be used to create protected groups for NAS file systems.

  • In HyperMetro (NAS) and HyperVault or HyperMetro (NAS) and asynchronous replication (NAS) scenarios, only OceanStor V3 series V300R006C10 and later versions can be used to create protected groups for NAS file systems.

  • In asynchronous replication scenarios, FusionStorage Block V100R006C30SPC100 is supported only when you create a VMware VM protected group.

For details about VMware VM compatibility, see the OceanStor BCManager 6.5.0 eReplication Compatibility List.

DR protection

  • When a Linux operating system is installed for VMware VMs, the name of the host on which VMs are installed cannot contain the . period.
  • Only vSphere vCenter can implement DR for VMs managed by the host.
  • DR can be implemented only for VMs that are created (manually or from templates) or fully cloned.
  • Only when the operating systems of vCenter on the active and standby servers are the same, DR can be performed.
  • VMs can only use VMFS or RDM virtual disks.
    NOTE:
    For some DR solutions, DR cannot be implemented for RDM virtual disks. For details, choose DR Configuration > xx DR Solution > Checking the DR Environment > VMware VMs where xx represents Active-Passive, Geo-Redundant, HA, HyperMetro, and Local Protection.
  • DR cannot be implemented for VM peripheral devices such as USBs, GPUs, HBAs, and CD-ROM drives.
  • DR cannot be implemented for linked clone VMs or vApp VMs.
  • DR cannot be implemented for VMs that use local disks on host machines.
  • DR cannot be implemented for VMs whose operating systems are installed on RDM disks.
  • The Storage I/O Control property cannot be enabled for datastores.
  • The name of a protect VM cannot contain any pound key (#). Otherwise, the VM configuration file cannot be modified during the testing of the recovery plan.

Recovery operations

  • Active-Passive DR Solution
    • The solution based on asynchronous replication (VIS) does not support testing of the recovery plan.
    • The solution based on HyperVault does not support testing of the recovery plan.
    • The solution based on HyperVault does not support configuration of more than one eReplication.
  • Geo-Redundant Solution
    • In the solution based on cascading replication (synchronous and asynchronous) or parallel replication (synchronous and asynchronous), when services are switched over to the remote DR site, reprotection cannot be implemented.
    • In the solution based on cascading replication (asynchronous and asynchronous), when services are switched over to the remote DR site, reprotection cannot be implemented.
    • The solution based on HyperMetro + replication (NAS) does not support testing of the recovery plan and reprotection after fault recovery.
    • The solution based on HyperMetro + replication (NAS) ensures that the NAS file systems on the storage array are working properly.
  • Local Protection

    The solution based on snapshot (NAS) does not support testing of the recovery plan.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 13827

Downloads: 68

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