Issue

The error message "Module Monitor-loop Power On Failed" appears in reports when attempting to power on a replicated Virtual Machine (VM) on the destination host after reverting a snapshot during failover. This error may also occur after performing a failback and trying to power on the Virtual Machine.

Cause

1. Insufficient Resources: VM replication involves copying the configuration from the Source VM to the target host. If the destination host has fewer resources, such as a lower number of cores or inadequate memory, compared to the Source VM, this issue may arise.

2. Space Constraints: Another possible cause is the absence of sufficient space in the residing datastore of the Virtual Machine on the destination host.

Solution

1. Check Error Message

Review the vSphere client or web client for the specific error message, as it will indicate the resource causing the VM to fail to power on.

2. Edit VM Settings

a) Manually edit the VM settings, adjusting the number of cores and memory as needed, to match the capabilities of the destination host.

b) Try powering on the Virtual Machine again after making the necessary adjustments. This will enable the use of the replicated Virtual Machine temporarily until the next scheduled replication job.

3. Contact Support

To retain the changes made during the VM failover and perform a failback, get in touch with BDRShield Support for further assistance.

Note: It is essential to ensure that the destination host has sufficient resources and datastore space to accommodate the VM's configuration during failover and failback operations. Failure to do so may result in the recurrence of the "Module MonitorLoop Power On Failed" error.