Invalid: Virtual machine 'VM' is no longer protected. Cannot protect virtual machine 'VM' because its config file '[Local Non Replicated] VM/VM.vmx' is located on a non-replicated or non-protected datastore.

Products

• VMware Live Recovery

Issue/Introduction

During a Live Recovery test you may see the following error:

Invalid: Virtual machine 'VM' is no longer protected. Cannot protect virtual machine 'VM' because its config file '[Local Non Replicated] VM/VM.vmx' is located on a non-replicated or non-protected datastore.

• The VM's files are split across two different datastores (Named Replicated & Non-Replicated)
• The VM functions normally and is in production.
• You need the best practice to get all the VM's files back onto a single datastore without impacting the operation of the VM.

Environment

VMware Site Recovery Manager 8.x
VMware Live Site Recovery 9.x

Cause

• Virtual Machine files are split across multiple datastores, one of which is unprotected by Site Recovery Manager / VMware Live Site Recovery.  
• The VM's configuration file ended up on a non-replicated datastore, which prevents Site Recovery Manager / VMware Live Site Recovery (SRM) from protecting it.

Resolution

Here is how to migrate all virtual machine files to a single replicated datastore to ensure SRM can properly safeguard it.

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

1. Open vSphere Client and locate VMname under the VMs and Templates view.
2. Right-click the VM and select Edit Settings.
3. 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 (advance migrate) is the safest method to move the files without downtime. To migrate a virtual machine (VM) to a single datastore using advanced migration in VMware vSphere, you can use the Migrate feature and select the Change datastore option. This allows you to move the VM's virtual disk files (VMDKs) to a new datastore while the VM is powered on, without interrupting its operation.

1. Ensure your VMware environment has vMotion and Storage vMotion enabled.
2. Open vSphere Web Client.
3. Right-click VM > Select Migrate.
4. Choose Change Storage Only (since we are keeping it on the same ESXi host).
5. Select the Replicated datastore as the destination.
6. Click Finish to start the migration process.
7. Monitor the task completion via Recent Tasks.
   
   

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

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

Step 4: Reprotect the VM in SRM

1. Open VMware Site Recovery Manager.
2. Locate VM in the inventory.
3. Click on Reprotect to ensure SRM recognizes the updated storage configuration.
4. 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.