P2V Question

[ixoni]

We currently have a physical file server setup like this:

WIndows 2008R2

iSCSI storage on a EMC VNXe of 4.5 TB. Dual bound NICS.

Dual bound LAN NICS.

The local server drive for the SAN storage consists of 3 spanned volumes.

I need to virtualize this box but I am uncertain of the best procedure. How will VMWare Converter handle this configuration?

I need to keep the storage as iscsi because I do not have enough space on the SAN to create a 4.5 TB vmware storage space.

Would this be as simple as disconnecting the iscsi connection to the SAN and running converter and then reconnectin the SAN?

OR, should I not use converter and build a new vm?

Thanks

[Sreec]

Hi,

   Please follow KB to ensure we are following all best practices>http://kb.vmware.com/kb/1004588

[ixoni]

Thank you, I have read the best practices but they do not specifically answer my questions around handling iscsi.

[Sreec]

Hi ,

      I have a question here >The local server drive for the SAN storage consists of 3 spanned volumes.Can you please explain the same?

[unsichtbare]

Does the physical file server use the Microsoft iSCSI initiator?

[Mouhamad]

At the last stage of conversion (use converter 5.0) you will get an option to select/de-select the volumes which you don't want to convert.

Don't select the 4.5 TB, just un-check it and complete the migration. After, present a new disk to that VM and robocopy the content of the 4.5 TB.

[ixoni]

Yes, to get around the 2 TB limit on windows volumes, three dynamic disks are created and spanned together to appear as one drive. 

[ixoni]

Yes it does use the Microsoft initiator.

[ixoni]

Mouhamad, this would require that I create a new 4.5 TB  drive, and then robo copy the data to it, correct? The problem here is that I do not have enough space on the SAN to create a new 4.5 TB data store. . I was hoping I could use that same iscsi data store.

[unsichtbare]

To clarify, how is the SAN LUN configured?

Are there 2, 2TB volumes on the SAN which have been spanned?

In principal, all you need to use the VMware Converter for is the OS (Windows, C:\)

Better yet, build a fresh windows, configure the iSCSI Initiator and connect your volumes as they are now. SHould be quick because the actual share stays right where it is on the SAN!

Also, use GPT to make disks larger than 2 TB on a sincle LUN.

[ixoni]

The SAN has a 5 TB generic iscsi data store. It is presented with 3 - 1.6  TB LUNS, which are the 3 spanned dynamic disks on the file server. See attached image.

So, as your last statement said, I should be able to creat a new VM (or use converter but not replicate the SAN drive), create a GPT disk, and configure the iscsi initiator and be good to go?

[ixoni]

It  has also been suggestted to me to use RDM to connect the SAN storage to ESXi and then in the VM add RDM storage. Does this make more sense in your opinion?

[unsichtbare]

If the san volume is not currently formatted with GPT, then you are stuck with the current spanned (MBR) disks,.

Using w2k8, be sure to open cmd as administrator and type the following commands, just to be sure:

c:\diskpart

automount disable

automount scrub

exit

This will prevent Windows from doing something unmentionable with the LUNs as soon as you connect the SAN with the iSCSI initiator.

In windows (w2k8) run: diskmgmt.msc (to open the logical disk manager in its own console)

Recreate your spanned disk!