Convert a physical windows file server to a VM on VNX5500

dynamox wrote: RDM could be at that size before 5.5

True, but only in physical compatibility mode.

RDM could be at that size before 5.5

Hi, they might be thinking of presenting the LUN and then creating an RDM.

At that size, only supported on vmfs5 and esxi 5.5.

i don't see any issues with that, swing LUNs between systems many times in the past.

You'd be surprised how resilient they can be, and like dynamox I've done many and most have been totally trouble free.

If you have the resources and would feel more comfortable, you could build/p2v a vm in parallel, synch changes and then swing access across.

It should work fine, especially if it's a standalone server.

- Disconnect LUN from the physical server.

- P2V the server

- Reconnect LUN to VM

- Post-check

I've done many of these types of P2Vs over time, even with an additional step to storage VMotion the machine afterwards and turn the RDM into a VMDK. Unfortunately your LUN is 4TB so that's going to have to stay an RDM...

Alternatively the approach your colleagues propose would also work (the data would be accessible) but things like shares would have to be recreated (since you're connecting it to a new VM with possibly a different network name).

"I thought you cannot just rip disk out of a server and install it into a new one and have all the data intact. I think there are going to be a lot of issues with the drive being recognized by the new host."

In general there is no problem with this for non-system volumes (meaning not the OS drive itself) assuming OS compatibility, and actually this is a use case for RDMs from VMware.  If you have the need or desire to move between physical and virtual servers (like reproducing a problem with a VM on physical), preserving the data, RDMs fit this mold because RDMs are not formatted when they are pulled into the system.  There is just a mapping or pointer file that references the LUN.

In your case I would recommend setting up a simple test server and run through the process entirely.  Physical windows server, present 50GB LUN from VNX, create a folder and some files, and a few shares.  By going through the process in this manner you will:

1. Be comfortable that attaching as an RDM in this manner doesn't mess with your data
2. Be comfortable with your process as it relates to re-establishing the file shares

Emphasis on #2...you wouldn't want to go through this process only to lose all of the shares...depending on exactly how many you have, anyway.

Also don't forget that you can leverage snapshots as well for some peace of mind, assuming you have the proper licensing.  This gives you a point in time copy that you can take instantly and revert to quickly if things go sideways.

Do you know if they will support it, in case it fails?

nope, you will not find anything official like that. It's up to you, test test test

What component of your migration do you want EMC to support ?  If you have OS issue EMC "might" give it its best effort, after that you will need to work with your OS/Hypervisor vendor.

Thank you all for the input, very much appreciated, it is very valuable. By any chance is there an EMC document that outlines anything of this nature: remapping a LUN from a physical windows to server to a VM as an RDM?

Yep I think Dynamox is right.  if you want tech-support help or confirmation I would think you'd pursue that with VMware.  The array itself doesn't really know or care that the LUN is being presented to a physical host, or is being used as an RDM.  VMware should be able to assist on the RDM "conversion", the P2V process, and any questions there because it is not particularly relevant what storage platform is being used.

It's understandable to have some reservations about the process, after all, you're responsible for the data.

Do lots of testing and practice the process. Repeat it until you're confident.

Have contingencies ready: Backups, lanman share exports etc.

Good luck !