Reprotect failed with Cannot protect virtual machine because its config file is located on a non-replicated or non-protected datastore.
Article ID: 404973
Updated On:
Products
Issue/Introduction
Symptoms:
Re-protect failed with the error: "Cannot protect virtual machine because its config file is located on a non-replicated or non-protected datastore," even though the datastore is actually replicated.
Similar entries were identified in the vmware-dr.log
Warning vmware-dr "Datastore 'datastore-####' is not replicated"
The message indicates that SRM was still scanning the datastore at the time of the failure.
Environment
Live Site Recovery 9.x
Cause
It is not recommended to set the storagemindsGroupcomputationalinterval values to excessively large numbers such as 10800, as this may lead to unintended behavior or performance issues. In this case, the storagemindsGroupcomputationalinterval value was incorrectly set to 10800 seconds, causing SRM to delay datastore status updates.
Resolution
1) Navigate to Site recover page > Site Pair > Advanced Settings > Storage, and set the storage.minDsGroupComputationInterval value to 0 on both sites. Refer to the document for SRM advanced settings Change Storage Settings
2) Restart the srm-server service from the SRM Management Interface page on both sites. Refer to the document for steps to restart the services Start, Stop, and Restart Site Recovery Manager Appliance Services
3) Re-run the re-protect operation.
Feedback
