Invalid Virtual Machines "VM1" is no longer protected in SRM

[vmk2014]

Hello,

   I was going through protected group of our SRM environment and i found the error

Invalid: Virtual machines"VM1" is no longer protected.Cannot protect virtual machines'VM1' becuase its config file "[SRM_XG_VMAX_5442_LUN_2EXD_Management]\VM1\VM1.vmx is located on a non-replicated datastore or non-protected data store.

I am new to SRM. Any help to troubleshoot this error will be appreciated. I have attached the screen shot.

Thanks

vmk2014

[vNEX]

Hello,

this error means that all of the VMs marked as "Invalid" and its files are located on non-replicated datastore which can happen for example in these cases:

- VM disks and config files was migrated (with Storage vMotion) to non-replicated (outside of SRM "owned" datastores) datastore by storage DRS or manualy by administrator

- Replication between your sites (or some of the array pairs) is broken

In addition all VM files that VM actively using must:

- belong to same datastore group

- must be associated wit the same array pair

In the Array Manager check status of your array pairs if they are replicated you will see blue arrow in the replication direction. (or consult rep. status with your storage admin)

Also check if the VMs files are located on replicated datastores.

Please post SRM logs they should be located here:

\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\

or through vSphere client SRM plug-in from Site summary tab export system logs and attach this bundle to your answer.

Message was edited by: vNEX

[vmk2014]

Thanks for help.Please find the screenshot for logs

anks

Thanks

vmk2014

[Daniel_Georgiev]

Probably you have a SAN issue, that LUN is not replicate. Look at SAN administration console that the LUN is replicated and is in OK state.

Did you manage to run TEST, FAILOVER, FAILBACK? On which operation VMs became in invalid state?

-Daniel G.

[vNEX]

can you please post print screens from Array Manager about replicated devices and its state ...

If its possible paste info about PG -> edit affected Protection Groups... and look at "Datastore Group" info.

As Daniel already ask what precedes this issue ... any SAN maintenance, failover test ...?

Thanks

[vmk2014]

Thanks for help.I checked with Storage admin but i am not much aware about storage end.

Storage Admin :-

Its the replication link.I keep up on the RDF groups.They suspend when the write pending limit is exceeded. It is exceeded because the replication link is 100% + utilized.

The replication link is over 100% because everyone decided doing an initial sync of NetApp .... AND  ...  DataDomain all at the same time, was a good idea.The DataDomain is almost caught up. Once that thing is synchronized, things should go back to normal.

103, 104, 203   have LUNs with extreme change rates. They are replicating SQL database transaction logs.Over asynchronous SRDF across an OC-12 with 3 other arrays doing full initial syncs.No one asked if that was a good idea, (I think).We found out when we started looking into it.At this point, all we can do is wait it out.

Let me know your thoughts on this.

Thanks

vmk2014

[vNEX]

All you have to do is wait for full sync...

Ping back with results.