Hi Anton,
Thanks for your reply.
I have done a little investigation based on your response.
We run about fifty/fifty Windows 2003 / Windows 2008, mostly 64 bit, in both versions.
And mostly patched up to date, but not with extra hotfixes.
Out of 21 servers, which failed to do a successfull backup, 3 was on Windows 2008, and the rest on Windows 2003.
Then I checked the SCSI driver on the Windows 2003 servers, and there we are using the symmpi.sys driver 😞
Do you know what happens if I change the driver, do I lose access to the disc?
Of all the hotfixes you mention we only have these:
WindowsServer2003-KB931300-x86-ENU.exe
WindowsServer2003-KB932755-x86-ENU.exe
WindowsServer2003-KB937382-x86-ENU.exe
WindowsServer2003.WindowsXP-KB931300-x64-ENU.exe
WindowsServer2003.WindowsXP-KB932755-x64-ENU.exe
WindowsServer2003.WindowsXP-KB937382-x64-ENU.exe
So there are also some posibillities there...
I have used the last days to surf most of NetApp and varius blogs to find help with this problem...but most are based on marketing material, (I think)
One thing I also found is this one:
http://www.veeammeup.com/2008/08/vss-and-vmware-esx-what-your-vmware.html
So maybe we have to use SMVI for most of the servers, and another solution for the more transaction critical servers.
-yes, I am aware of Snap Manager for SQL and Sharepoint, which we also have, but not yet has had that great succes with, this problem we have asked our vendor to help solve. It mainly goes with the RDM disks in either virtual mode or physical mode, and problems with Vmwares vmotion
I will digg deeper into your information, do some reboots, and come back with the results.
Have you heard anything about what new will be in SMVI version 2.0, and when it will be released?
Best regards,
Jan