Forum Discussion
Thanks Marrianne
My search results (based on your suggestion) were more related to Windows Server 2003 and the older versions of the Microsoft iSCSI initiator software.
My Exchange 2010 servers are 2008 R2, running version 6.1 build 7600 of the iSCSI initiator software. There is no update beyond that I can find.
According to technet VSS should work with iSCSI:
"From the guest operating system, you can connect directly to iSCSI LUNs on a storage array. Direct connectivity using iSCSI offers the following advantages over other iSCSI LUN options:
- You can transparently operate SAN management applications.
- Supports guest clustering.
- You can connect to iSCSI LUNs without shutting down and restarting the guest operating system.
- You can manage LUNs in the guest operating system in the same way that LUNs are managed in the physical environment.
- Support for VSS hardware snapshots in the guest operating system."
Also, I am not seeing any errors in the Windows event logs. I would assume if the issue was with Windows and VSS, there would be errors associated with each attempt.
As well, I am running SMVI backups of this Exchange VM without issue. The default action is to take a quiesced snapshot which should also be calling the VSS writer. These backups run fine (and at a different time), so I'm really not finding any evidence that the issue resides within Microsoft VSS and compatibility with iSCSI attached storage.
That said I'm perfectly willing to accept that fact that is the issue, if someone could provide me with data specific to my situation that proves the case.
Related Content
- 2 years ago
- 11 years ago