VMware Site Recovery Manager error while doing reprotect

Products

• VMware Live Recovery

Issue/Introduction

• After successfully running a protection group, cannot re-protect to the original Source Site.
  
  Re-protect fails with error:
  
  "Cannot protect virtual machine 'VM_NAME' because its config file '[Datastored] VM_NAME/VM_NAME.vmx' is located on a non-replicated or non-protected datastore.
  
  

• vmware-dr.log errors:

2026-01-01T00:01:01.000-00:00 verbose vmware-dr[######] [SRM@#### sub=StorageProvider opID=reprotect:###a] ReprotectVmSelectLocators: group 'vm-protect
ion-group-##:', VM 'VM_NAME'

2026-01-01T00:01:01.000-00:00 warning vmware-dr[######] [SRM@#### sub=StorageProvider opID=reprotect:###a] Datastore 'datastore-' is no longer replicated

2026-01-01T00:01:01.000-00:00 error vmware-dr[######] [SRM@#### sub=StorageProvider opID=reprotect:] Config file '[Datastored] VM_NAME/VM_NAME.vmx' of virtual machine 'vm-:VM_NAME' is located on a non-replicated datastore 'datastore-'

• Discover Devices no longer shows the Datastore mapping
  
  
• Netapp Ontap Version 10.5

Environment

Live Recovery 9.x

Cause

ONTAP Tools for VMware vSphere (OTV) did not clean up a failover device entry in a OTV database.  As such, the device state is not properly reported when running a discover devices operation as part of the Reprotect.

Resolution

• Contact Netapp Support to Upgrade ONTAP Tools for VMware vSphere (OTV) 10.5 patch 1 and upgrade the Netapp SRA.
  
  
• Repeat workflow to re-protect.

Additional Information

Heartbeat datastores get unmounted during a VMware Site Recovery Manager failover operation resulting in a HA error.