Error: Cannot protect virtual machine because its config file is located on a non-replicated datastore
search cancel

Error: Cannot protect virtual machine because its config file is located on a non-replicated datastore

book

Article ID: 411318

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware Live Recovery

Issue/Introduction

  • Reprotect operation on SRM using array based replication fails with the following error messages.

"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." 
"Cannot protect virtual machine 'VM_NAME' because its config file "[Datastore_Name] VM_NAME/VM_NAME.vmx' is located on a non-replicated or non-protected datastore."

 

  • From the logs of VLR (SRM) '/var/log/vmware/srm/vmware-dr.log', shows the VM's cannot register or power on because the recovered datastore is currently unprotected and not replicating via the storage array..

    ####-##-##T16:17:52.457+05:30 verbose vmware-dr[01459] [SRM@6876 sub=Storage] Received updates on replication settings from remote site: (vmodl.query.PropertyCollector.Change) [
    -->    (vmodl.query.PropertyCollector.Change) {
    -->       name = "localReplicationSettings.deviceGroupSettings["#########"]",
    -->       op = "remove",
    -->       val = <unset>
    -->    }
    --> ]
    ####-##-##T16:17:52.457+05:30 verbose vmware-dr[01459] [SRM@6876 sub=Storage] Noticed removal of replication settings for '#########'

    ####-##-##T16:47:50.399+05:30 warning vmware-dr[16959] [SRM@6876 sub=StorageProvider opID=#######] Recovered datastore 'datastore-5152' in group 'vm-protection-group-#####' is not replicated
    ####-##-##T16:47:50.399+05:30 warning vmware-dr[16959] [SRM@6876 sub=StorageProvider opID=#######] Recovered datastore 'datastore-5153' in group 'vm-protection-group-#####' is not replicated
    ####-##-##T16:47:50.578+05:30 error vmware-dr[16968] [SRM@6876 sub=StorageProvider opID=#######-####-####-####-############-reprotect:16e3:62f3:0a7c:78f8] Config file '[########] [Datastore_Name] VM_NAME/VM_NAME.vmx' of virtual machine 'VM_Name' is located on a non-replicated datastore 'datastore-5153'

Environment

VMware Live Site Recovery 9.0.x

Cause

The replication configuration for the underlying datastore was inaccessible because the recovered datastore was detected as a snapshot. This placed the datastore in a read-only state, effectively blocking all I/O operations.

  • The ESXi host logs /var/log/vmkernel.log, shows the datastore is mounted as a snapshot in read-only mode, blocking I/O,

    "2026-06-11T01:11:49.866Z Wa (180) vmkwarning: cpu22 : 2099346 opID=2f1698d3) WARNING: ScsiDeviceIO: 5172: Can't write cmd xfe using read-only handle to device naa.################################:1 worldID 2099331, (handle->flags & PSA_STOR_HANDLE_READONLY) =2,
    2026-06-11T01:11:49.866Z Wa (180) vmkwarning: cpu22 : 2099346 opID=2f1698d3) WARNING: vmkCmd->iswriteCdb=0, scsicmd->modifiesMedia=1
    2026-06-11T01:11:49.866Z Wa (180) vmkwarning: cpu22 : 2099346 opID=2f1698d3) WARNING: ScsiVmas: 3546: Failed to issue command on device "naa.################################": Read only"

    "2026-06-11T01:48:08.103Z In(182) vmkernel: cpu31:2099365 opID=f201de7e) LVM: 12069: Device naa.################################:1 detected to be a snapshot:"

Resolution

  1. Engage the Storage vendor to change the datastore status to Read/Write directly on the Storage array.

  2. From vCenter UI, Rescan storage on cluster (Right-click on the Cluster > Storage > Rescan Storage)
    Note : If the datastore is unavailable after rescan, reboot the ESXi host.

  3. Re-run the re-protect operation again.

If the issue remains unresolved after completing these steps, please open a support case using Contact Support.

 

Additional Information

Powered by Wolken Software