In Host Replication Scenarios, the DR VRG Has Alarms that Affect VM Recovery, Resulting in Planned Migration or Fault Recovery Failure

14

1.Log in to DR OceanStor BCManager and choose Monitor > Alarms > Current Alarms. Then view current alarms on OceanStor BCManager.
2.Search for alarms reported by VRGs and related to VMs contained in recovery plans.
3.In the Name area, click the names of alarms. View details about alarms and perform recommended actions to troubleshoot faults. After alarms are cleared, perform planned migration or fault recovery again.

If VRG alarms persist, manually confirm and clear alarms without affecting services. Then perform planned migration or fault recovery again.

Other related questions:
Differences between fault recovery and planned migration of OceanStor ReplicationDirector
If data or applications at a production site need to be recovered from a disaster recovery site, you need to perform planned migration at the disaster recovery site. The latest data changes at the production site will be synchronized to the disaster recovery site. Planned migration is performed only in the disaster recovery management system at the disaster recovery site. If data or applications at the production site become unavailable due to disasters or faults, you need to perform fault recovery. Fault recovery is performed only in the disaster recovery management system at the disaster recovery site. The latest backup data at the disaster recovery site is used to recover data.

Why Cannot Storage Devices Be Discovered on Hosts When I Execute a Recovery Plan to Implement Tests, Planned Migration, or Fault Recovery
1.Check whether the LUNs mapped to the hosts are normal. If no, troubleshoot the LUNs and go to 3. If yes, go to 2. 2.Check whether the service network communication between hosts and storage devices is normal. If no, troubleshoot the service network and go to 3. If yes, contact Huawei technical support engineers. 3.Clear the recovery plan and perform a test again.

OceanStor 9000 disaster recovery (DR) method
OceanStor 9000 provides the InfoReplicator feature to recover data and services upon disasters.

Starting or Shutting Down VMs Fails When You Execute a Recovery Plan for VMware VMs
1.If you want to recover a VM to an ESXi host, log in to vCenter through a vCenter client. Set the location for storing VM swap files on the ESXi host. You are advised to set the location on a dedicated datastore without affecting other VMs. The dedicated datastore must have adequate space. For details, see the VMware documentation. 2.If you want to recover a VM to an ESXi host cluster, ensure that VM swap files and the VM reside under the same directory to prevent the adverse impact on VM vMotion performance. Adjust the space of the datastore where the VM resides to ensure that the VM can correctly create swap files.

Starting VMs Timed Out When You Execute a Recovery Plan for VMware VMs
1.Log in to vCenter through a vCenter client, select the VM that fails to be started, and view the tasks and events concerning the VM. 2.If error pbm.fault.PBMFault.summary is displayed during VM startup, check the ESXi cluster settings, disable the vSphere DRS setting, and execute the recovery plan again. After the recovery plan is completed, you can enable the vSphere DRS setting the ESXi cluster based on actual requirements.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top