3PAR VSS Provider 1.6.2 for Microsoft Windows Release Notes (320-200229 Rev A, May 2010)

Page 2
320-200229 Rev A 3PAR VSS Provider for Microsoft Windows Release Notes May 2010
5.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 an InServ booted 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 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 do auto-recovery. This might lead to data loss when
used in conjunction with Recovery Manager products. Microsoft has released a patch to fix this
problem. Refer to Microsoft KB 970770 for more information.
• This version of 3PAR VSS Provider for Microsoft Windows does not support a direct upgrade
(install on top) from 1.5.x or earlier version due to a change in registration process.
• 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.
• Snapshot taking longer than 10 seconds will be discarded. This is a Microsoft VSS framework
restriction.
CAUTION: If Recovery Manager products are already installed prior to the installation or
upgrade of VSS Provider, stop the corresponding Recovery Manager services
from the Service Control Panel prior to the operation, and start the service
again after the installation.
Make sure the event viewer is not opened during the installation of VSS
Provider; otherwise the system will prompt you for a reboot after the
installation.
If the previous installation is not in the default location, specify the alternate
location again during a direct upgrade.
The 3PAR VSS Provider service will stay started even after the internal COM
modules are unloaded and released.