0x3230023 VM Configuration Does Not Meet Host Replication Protection Requirements and the VM Is Not Consistently Protected

Description

The configurations of VM (name: {1}) in protected group (name: {2}) do not meet protection requirements and the VM is not under consistency protection.

Attribute

Impact on the System

Some protected objects are not in the protected group and fail to be protected.

Possible Causes

• The placeholder VM for the protected VM is deleted.
• A disk is added to the protected VM, and no resource mapping is created for the datastore where the disk resides.
• A disk is added to the protected VM, and a remote replication is created for the datastore where the disk resides.
• A network adapter is added to the protected VM, and no resource mapping is created for the port group (network) where the network adapter resides.
• After the disk, network adapter, and properties of the protected VM are changed, the changes fail to be synchronized to the placeholder VM.
• VM disks are on different datastores, and the datastores are not associated with the same host.

Procedure

1. On UltraVR, click Protection and select the required protected object. On the page that is displayed, click Protected Object. Check whether the placeholder VM for the protected VM is deleted.
   • IIf yes=>reconfigure the VM in the Virtual Replication Gateway (VRG) and manually refresh FusionCompute or FusionManager. For details, see section Configuring VRG Pairs in the User Guide.If the alarm persists=>Step 2.
   • If no=>Step 2.

2. Check whether a disk is added to the protected VM.
   • If no=>Step 3.
   • If yes=>Check whether a resource mapping is created for the datastore where the disk resides. If no resource mapping is created, create one and manually refresh FusionCompute or FusionManager. If the alarm persists=>Step 3.

3. Check whether a remote replication is created for the datastore where the disk resides.
   • If yes=>unbind the disk and manually refresh FusionCompute or FusionManager. If the alarm persists=>Step 4.
   • If no=>Step 4.

4. Check whether a network adapter is added to the VM. For details, see the documents of the VM.
   • If no=>Step 5.
   • If yes=>check whether a resource mapping is created for the port group (network) where the network adapter resides. If no resource mapping is created, create one and manually refresh FusionCompute or FusionManager. If the alarm persists=>Step 5. If a resource mapping is created=>Step 5.

5. CCheck whether datastores used by the VM are associated with the same host. For details, see the documents of the VM.
   • If no=>associate all datastores used by the VM with the same host and manually refresh FusionCompute or FusionManager. If the alarm persists=>Step 6.
   • If yes=>Step 6.

6. Reconfigure the VM in the VRG and manually refresh FusionCompute or FusionManager. For details, see section Configuring VRG Pairs in the User Guide. If the alarm persists=>Step 7.
7. Contact technical support engineers.

Related Information

None