Quantcast
Channel: VMware Communities : Discussion List - Site Recovery Manager
Viewing all articles
Browse latest Browse all 3691

After failing over and Failing back LUN has been renamed and also left on DR side as inactive

$
0
0

Hi All

 

We have a primary and DR site, bith sites have 5 ESXi 5.0 hosts and a separate Vcentre. We are running SRM 5.0

 

Storage is EMC VNX 5500, we are replicating asynchronously  with snap mirror.

 

We done a full SRM testing using a test LUN / Protection group at the weekend as we are planning a full DR test shortly, we chose the full test but slected the planned option (we did not want to do the isolated test where it does a snapshot and ring fences it)

.

Everything went fine, we failed the VM's over to our DR site, tested then after 20 minutes we re-protected and failed them back to our primary site.

 

2 Questions I have are

 

A, it took 8 minutes to fail them over but 25 minutes to fail them back, seemed to spend a fair amount of time on stage “Preparing the protected VM’s for migration” , what's actually happening under the hood at this stage?

 

B. After everything has been completed I looked a Vcentre and I see that the test LUN which was originally called TESTSRMLUN01 (original I know) however it is now called "snap-433ad3a8-TESTSRMLUN01", also on our DR side there is a LUN of the same name but status inactive, why has it renamed the Datastore and also why would the datastore still be showing on our DR side Vcentre, I would have thought as part of the reprotect and failback we did the LUN would have been de presented to DR side

 

Thanks

 

Nick

 



Viewing all articles
Browse latest Browse all 3691

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>