Virtual machine is no longer protected. Cannot protect virtual machine because its config file is located on a non-replicated or non-protected datastore.

Products

• VMware vCenter Server

Issue/Introduction

The error "Virtual machine is no longer protected. Cannot protect virtual machine because its config file is located on a non-replicated or non-protected datastore" indicates that the virtual machine's configuration file (.vmx) is on a datastore that isn't replicated or protected by your replication solution (like VMware vSphere Replication or Site Recovery Manager). This prevents the virtual machine from being properly replicated or protected in a recovery scenario.

Environment

vCenter 7.0.x
vCenter 8.0.x
vSphere Replication 8.7.x | 8.8.x | 9.0.x
Site Recovery Manager 8.7.x | 8.8.x
VMware Live Site Recovery 9.0.x

 

Cause

The VM's configuration file ended up on a non-replicated datastore, which is preventing Site Recovery Manager (SRM) from protecting it.

Resolution

Here is how, step by step,  to migrate all files to a single replicated datastore to ensure SRM can properly safeguard it.

Steps to Move All VM Files to One Datastore

Step 1: Verify Current VM Storage Configuration
Before making changes, confirm which files reside on which datastores:

• Open vSphere Client and locate the virtual machine under the VMs and Templates view.
• Right-click the VM and select Edit Settings.
• Expand the disk and storage configuration to check which files reside on Replicated vs. Non-Replicated datastore.

Step 2: Storage vMotion to Consolidate VM Files

Since the VM is in production, using Storage vMotion (advanced migrate) is the safest method to move the files without downtime.

• Ensure your VMware environment has vMotion and Storage vMotion enabled.
• Initiate Migration by opening vSphere Web Client.
• Right-click  on the VM > Select Migrate.
• Select the migration type:  Choose Change Storage Only and click Next. (since we are keeping it on the same ESXi host).
• Choose Datastore:  Select the Replicated datastore as the destination and Click Next.
• Review and Finish:  Click Finish to start the migration process.
• Monitor the task completion via Recent Tasks.

Step 3: Confirm File Locations
Once the migration is complete:

Navigate back to the VM settings and confirm all files (VMX, VMDK, etc.) reside entirely on the replicated datastore.
If everything checks out, proceed to re-protect the VM in SRM.

Step 4: Reprotect the VM in SRM

• Open VMware Site Recovery Manager.
• Locate the VM in the inventory.
• Click on Reprotect to ensure SRM recognizes the updated storage configuration.
• Run a test recovery to confirm no further errors appear.

Additional Notes

• Ensure sufficient free space exists in the replicated datastore before migration.
• If Storage vMotion is unavailable, you may need to shut down the VM and manually migrate its files.
• If this issue recurs, consider adjusting your VM deployment strategy to prevent non-replicated datastore usage.

Once you've completed these steps, your VM should be fully protected again under SRM.