We set up a backup server (Windows 2008 r2) for our VMware infrastructure which uses an iSCSI SAN for storage. The backup server has to be connected to the SAN for Veeam to be able to backup virtual machines. The SAN provides 18 targets, all of the same size (1TB).

All initiators (ESX, Windows 2003 r2, Windows 2008 r2) are connecting fine, but the volume manager of Win2k8r2 only shows part of the targets/volumes.

For example: we connect Windows 2008 r2 to all 18 targets, the targets show as "connected" in Microsoft initiator, but volume manager only shows 8 of the targets.

For comparison: the volume manager of Windows 2003 r2 behaves normal and produces one volume for every connected target.

Restarting iSCSI initiator service or rebooting the machine did not help.


Disk management

No MPIO defined

No volumes available for MPIO

  • What kind of SAN? Can you post the iSCSI initiator config (screencaps) and screencaps of the disk management panel in Windows? I assume you tried to rescan disks in disk management? – Jeremy May 7 '12 at 21:50
  • Jeremy, thanks for reading my post. I added some screens hoping to illustrate the situation. If you are looking for something more specific let me know. The SAN is based on open-e DSS V6 (latest release). – ceebee May 9 '12 at 16:15
  • I assume you did a rescan disks and that the remaining 8 volumes aren't coming up? Do you have MPIO enabled (in Windows 2008)? I wonder if MPIO is seeing the volumes as the same even though they are different. – Jeremy May 9 '12 at 17:40
  • I did a rescan everytime I disconnected and reconnected the targets. MPIO is not enabled. Or is there any way to configure MPIO outside of MS Initiator that I am missing here? – ceebee May 9 '12 at 19:15
  • See i.imgur.com/pkgZu.png. Check to see if MPIO is enabled for any of the targets. Is it? – Jeremy May 9 '12 at 19:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.