vCenter 5.1 and Storage vMotion RDM

Here is my setup our SAN Admin is trying to move all LUN to our new SAN "XIV". The problem I am having trouble wrapping my head around it the following.

-The SAN are new replicating
-Storage vMotion on a RDM only moving the pointer VMDK
-how can I move the data from the old to new storage?
-After new Lun is created how would I connect it to the new VM? Would the new Disk have a new signature and cause a problem with Windows

Please help because I am running out of ideas here and the VM's with RDM's are running Microsoft SQL and others running Exchange 2010.
LVL 21
compdigit44Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you are replicating LUNs between SANs, and the new replicated LUN is a clone of the old LUN. (exactly).

Detach the old LUN (RDM), and re-connect to the new LUN.

if the LUN is a CLONE, it will have the same signature, which will be stored in the OS registry. (confirmed by, it will just become the drive letter again!).

however, if it is not a CLONE, when you complete a re-scan, you'll get NTFS disk, which you need to assign a drive letter.
compdigit44Author Commented:
Thank you Hancock..

Here is the problem my SAN Admin informed me the SAN's are NOT replicating which leaving me puzzled as how to get the LUN  / data to the new SAN and attach the new LUN to the VM?
compdigit44Author Commented:
Could I convert the RDM to a VMDK then convert the VMDK to a RDM on the new SAN..

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=3443266

This seems very risky to me probably would required a large amount of downtime?

How have you done this in the past "oh great one..."
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Q. do you need RDMs ?

and for what reason ?
compdigit44Author Commented:
yes I need RDM because all VM's are running in a MS cluster. Also after a LONG discussion and much eye rolling from my SAN admin I believe I convenience him to enable replication for my volume only. IF he does set this up and updates the zones there should be nothing I need to do I on the VMware side correct?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Ah, Clustering!!!! Now be careful here, and it would be wise to check what your SAN replication does.... because NTFS signature serials are critical to MS Clustering!

We have seen some LUN change the signature!
compdigit44Author Commented:
Thank you for the tip.... Today I did a test with our SAN Admin. He replicate one volume that was attacted as an RDM to a VM. I then powered it down, he rezoned it, I removed and readded it and worked perfectly...

Learned something new... I am a bit neverous about the cluster since the new cloned LUN for the RDM did have a new LUN and how this will impact Windows Clusters
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Test, Test and Test Again.
compdigit44Author Commented:
I have your guidance to thank as always...

One final question. When a LUN number changes will it automatically case a disk resignature in an OS like Windows 2008?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
LUN change, WWNN change, IQN change, path changes, policy changes can trigger a disk to go OFFLINE, and then Windows re-sigs it! (and does not often ask, if you want to re-sig it, unlike a VMFS datastore).

Windows does not really automatically re-sig a disk, often caused by a human Admin that does not appreciate what is happening, when a disk states OFFLINE.

It's at the point of "messing around in Disk Management, the signature gets changed", this is not normally an issue, unless sigs are in the registry, and you have Clusters!

here are some articles worth bookmarking fr a later date, if you ever need them

http://blogs.technet.com/b/markrussinovich/archive/2011/11/08/3463572.aspx

http://jeffwouters.nl/index.php/2011/06/disk-offline-with-error-the-disk-is-offline-because-of-a-policy-set-by-an-administrator/

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Author Commented:
Excellent advice as always!!!
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Thanks...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.