This post is more than 5 years old
4 Posts
0
1608
symrdf failover leaves snap-xxx prefix in ESXi5.1 datastore name
Hi all
we are facing issue while testing our DR procedure. In one part, procedure consist of executing symrdf -failover on device group.
after that, we are left with snap-xxx-DSNAME like datastore names rather than just DSNAME.
even after symrdf -failback we are still left with that snap-xxx prefix on each datastore name.
R1 and R2 devices are preprovisioned to hosts before executing symrdf -failover. so we only do "datastore rescan" on hosts in failover site.
devices are thin devices on VMAX-10k, enginuity level 5875.
hosts are running ESXi 5.1.0, subver 1065491
RDF mode is sync and during DR they are in "failed over" state
we were testing SRM and SRA on this vSphere server but all was uninstalled as per documentation.
tnx in advance!
Plnky
4 Posts
0
October 17th, 2013 03:00
ok, the issue was resolved. most helpful was "ages old" blog post explaining EnableResignature and DisallowSnapshotLUN
EnableResignature and/or DisallowSnapshotLUN - Yellow Bricks
after setting both options to value of 0, I can execute "symrdf failover" operations without snap-xxx prefix and datastore is visible across all ESXi hosts after single datastore rescan.
as described, I am not using SRM. both SRM and SRA were uninstalled prior playing around manually with symcli commands. that also means that Paul's reply doesn't apply. and btw it is inventory - solutions and apps - storage appliances etc etc... and then right click on site to get to advanced options.
Plnky
4 Posts
0
October 16th, 2013 03:00
ok, probably stumbled on resignature issue left from SRA installation on eshi hosts:
VMware KB: vSphere handling of LUNs detected as snapshot LUNs
VMware KB: Setting LVM.enableResignature =1 remains set after a SRM Test Failover
will test and follow up shortly...
arjunsingh1
32 Posts
0
October 16th, 2013 03:00
Hi Pinky,
Are you currently using SRM to do the Recovery or doing it manually ?
I see that you have mentioned SRM and SRA have been uninstalled.
If you are using SRM and SRA then you'd need to follow the step mentioned by Paul in the previous post.
If not using SRM and SRA, then take look at the following KB to understand how vSphere handles Snapshot LUNS :
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011387
rawstorage
419 Posts
0
October 16th, 2013 03:00
Right click on the site, and go to Advanced Settings.
Put a check in the box that says storageProvider.fixRecoveredDatastoreNames.
This should fix it for you.
FYi... This is assuming SRM 5.x
codyhosterman
286 Posts
0
October 28th, 2013 11:00
We go to into this in our VMAX/VMware techbook too:
http://www.emc.com/collateral/hardware/solution-overview/h2529-vmware-esx-svr-w-symmetrix-wp-ldv.pdf