Error: Reprotect operation failing with "config file is located on a non-replicated datastore" in Site Recovery Manager

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

When performing a Reprotect operation in VMware Live Site Recovery (SRM), the task fails with: The operation was only partially completed for the protection group '####' since a protected VM belonging to it was not successful in completing the operation. Cannot protect virtual machine '####' because its config file '[snap-####] ####/####.vmx' is located on a non-replicated or non-protected datastore.

Environment

VMware Live Site Recovery (SRM) 8.x,

VMware Live Site Recovery (SRM) 9.x

Array-Based Replication (ABR)

Cause

This issue occurs when the underlying storage state is out of sync with vCenter and SRM. SRM incorrectly references a temporary snapshot datastore (snap-####) rather than the active, reversed datastore. This often happens if the storage array takes longer than the default 300-second timeout to complete the replication reversal.

From the logs, /opt/vmware/srm/logs/vmware-dr.log. Shows error since it fails to access the config file for the VM protected by the protection group.

warnings = (vmodl.MethodFault) [
-->          (dr.fault.Timedout) {
-->             faultCause = (vmodl.MethodFault) null,
-->             faultMessage = <unset>,
-->             timeout = 300
-->             msg = "Operation timed out: 300 seconds"
-->          }

-->       ],errors = (vmodl.MethodFault) [
-->          (dr.replication.fault.IncompleteOperation) {
-->             faultCause = (vmodl.MethodFault) null,
-->             faultMessage = <unset>,
-->             protectionGroup = 'dr.replication.VmProtectionGroup:########-####-####-####-############:vm-protection-group-#####',
-->             protectionGroupName = "Protection_Group_Name"
-->             msg = "The operation was only partially completed for the protection group 'Protection_Group_Name' since a protected VM belonging to it was not successful in completing the operation."
-->          },

Resolution

1. Force Re-protect:
   
   Initiate the Re-protect task for the Recovery Plan again.
   In the wizard, select the checkbox for Force Cleanup. This instructs SRM to ignore the inaccessible state and update its database to match the current storage state.
2. Increase Storage Timeout:
   
   Navigate to Site Pair > Advanced Settings > Storage.
   Locate the setting storage.commandTimeout,Increase the value from 300 to 600 seconds.

If the problem still persists, contact Broadcom Support for further assistance.