#VVol disk mapped with physical disk in Windows 2008 R2.

[PGPulp]

Our situation is :
2 3PAR boxes
1 cluster Windows 2008 R2 used for Hyper-V

We have appx 200 virtual machines.
On the 3PAR box, 4 differents disk sizes are created.
200 vvol are presented on the cluster nodes.

Each VM use 1 3PAR vvol, giving us the high availibility with the CLX feature.

My question is :
We use an algorithm based on the SCSI ID of the disk inside windows (mpclaim) and map this with the serial number (3PAR) of the disk. But that gives sometimes issues as differents disks inside windows are mapped to the same 3PAR serial number.

Isn't it a better way to map a physical disk inside Windows to a 3PAR serial number?
Or isn't there another property of 3PAR VVol that we can export to map with some diskpart or Win32_disk value inside Windows?

Thx for your help
Laurent.

[Richard Siemers]

I'm not very familiar with Hyper-V, just Vmware and IBM VIO.... however, in all situations on all OS's, we used LUN#'s (scsi id) to uniquely identify luns.

We also make sure to label the vvname with the intended lun id. For example:

VV name:
vmware_0_ntserver1
vmware_1_ntserver2
vmware_2_ntserver3

and we will export _1_ as LUN ID 1, and 2 as 2... etc etc etc.