3PAR® VSS Provider 1.6.1 for Microsoft® Windows® Release Notes

320-200207 Rev A 3PAR VSS Provider for Microsoft Windows Release Notes January 2010
4.0 New Features and Enhancements
• Supports multiple InServ Storage Servers from one single backup host.
• Eliminates the dependency of Microsoft Distributed Transaction Coordinator (MSDTC) service.
• Automatically re-establishes connections to the InServ Storage Server with the InForm CLI if a
network socket is disconnected during the snapshot management process.
5.0 Upgrading
This version of 3PAR VSS Provider for Microsoft Windows supports a direct upgrade (install on top)
from 3PAR VSS Provider 1.6.0 for Microsoft Windows by running the MSI package directly to install.
6.0 Known Issues
• The virtual server environment uses the controller to distribute the hardware resources;
therefore snapshot LUNs may not be surfaced to the Windows OS. This is a known issue for the
virtual server environment.
• Snapshot creation on a booted InServ system drive might fail.
• Windows operating system only supports up to 255 LUNs.
• Any LUN ID greater than 254 will not be visible to the Windows operating system since the
Windows Operating System supports a maximum of 255 LUN IDs.
• Windows 2008 MPIO hangs with VSS operation. Microsoft has released a patch to fix this
problem. Refer to Microsoft KB 957522 for more information.
• If remote desktop is being used to install VSS Provider, you need to re-login to the remote
desktop after the installation has completed.
• Windows 2008 attempts to import snapshots and perform auto-recovery on data during
snapshot creation even though the requestor has explicitly indicated that the snapshot is
transportable, and the hardware cannot perform auto-recovery. This can lead to data loss when
used in conjunction with 3PAR Recovery Manager products. Microsoft has released a patch to fix
this problem. Refer to Microsoft KB 970770 for more information.
• The maximum number of shadow copied volumes in a single shadow copy set is 64. If any
snapshot operation exceeds this limit, the operation fails and the VSS framework requires some
time to perform the cleanup task.
• If a user resets the password on the InServ Storage Server, regardless of whether it is the same
password as the previous one, the user needs to re-run the InServ Storage Server configuration
registration using ProvCfg on the host system.