So, here's my scenario: ESX 3.5 Enterprise (build 64607), vCenter 2.5. I am migrating my virtual machines to a new SAN as the old one is no longer sufficient. All of my machines are done being moved but one. The one machine left has 4 physical RDMs setup that house 250+ SQL Server database files (.mdf, .ldf, etc.). I am unable to use storage vMotion to move the virtual machine. I am just using the simple menus built into the vSphere client (right-click the vm and choose Migrate Storage). See the following screenshots:
The only thing I can conclude is that the physical RDMs are a limitation. However, I am finding conflicting information on this. Several blog posts out there indicate that physical RDMs cannot be migrated, but virtual RDMs can. But the following VMware KB article indicates ESX 3.5/VC 2.5 svmotion works find with physical RDMs (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005241). I have seen suggestions to convert the RDMs to virtual, but I believe this will cause more problems than solutions. First, to do this you must remove the RDM from the vm and recreate the disk. I know this preserves the data, but SQL Server is extremely picky when it comes to losing communications with an mdf. Also, as I understand it, when using storage vmotion on a virtual RDM, the process actually converts the disk to a vmdk file. I do not want this converted, I want to maintain it as an RDM.
So, my questions are 1) is this possible with my setup and 2) can anyone point me in the right direction to accomplish this?
Thanks.