Known issues

The known issues that are in version 4.9.0 of the IBM® Storage Support for Microsoft VSS VDS are summarized here.

Ticket ID	Description
VPSD-245364	When Microsoft Data Protection Manager (DPM) creates FlashCopy® for the shared source volume, if the space-efficient volume and copy rate are zero, a cascading FlashCopy is created unexpectedly. Deleting the cascading FlashCopy causes an error to the target volumes. Workaround: Set the background copy rate above zero when you use the space efficient volume in Microsoft DPM.
VPSD-258716	When you open an administrator command prompt in Microsoft Windows Server 2012 or 2012 R2 and create a Volume Shadow Services (VSS) DiskShadow snapshot, you might produce a message similar to the following output: `DISKSHADOW> add volume c: DISKSHADOW> create COM call "lvssObject4->GetRootAndLogicalPrefixPaths" failed.` This type of COM call failure message is harmless, and despite the message, the ShadowCopy backup completes successfully. For more details, refer to the Microsoft Knowledge Base article.
VPSD-258651	Incremental FlashCopy does not support dynamic disks with concatenate volumes either spanned or striped, and does not support multi-target volumes for the same source disk. Note: Currently there is no solution or workaround for this limitation (VPSD-258651).
VPSD-258653	Supports only embedded CIM Agent. Note: Currently there is no solution or workaround for this limitation (VPSD-258653).
VPSD-258655	For the SAN Volume Controller/Storwize V7000 cascading/multi-target FlashCopies with zero copy rate, after restoring one of the FlashCopy mappings, the current and newer FlashCopy relationships are withdrawn. The current target volume and newer FlashCopy volumes are returned to the free storage pool. Note: Currently there is no solution or workaround for this limitation (VPSD-258655).
VPSD-258656	For the SAN Volume Controller/Storwize V7000 cascading/multi-target FlashCopies with zero copy rate, after deleting one of the FlashCopy mappings, the current and earlier FlashCopy relationships are withdrawn. The current target volume and earlier FlashCopy volumes are returned to the free storage pool. The snapshot IDs of earlier FlashCopy volumes stay in the host until the next snapshot/restore is run. Alternatively, ibmvcfg.exe cleanupDependentMaps can be used to manually clean up the snapshot IDs of earlier FlashCopy volumes. Note: Currently there is no solution or workaround for this limitation (VPSD-258656).
VPSD-258657	Before you use the IBM Virtual Disk Service, the prerequisite Java JRE 7.0 application must be installed. For example, ibm-java-jre-70-win-i386.exe or ibm-java-jre-70-win-x86_64.exe. Note: Currently there is no solution or workaround for this limitation (VPSD-258657).
VPSD-258658	Starting from version 4.4.0, IBM VDS provider is not automatically registered after installation. Workaround: To manually register IBM VDS provider, issue the regsvr32 ibmvds.dll command under the directory of the IBM VSS provider.
VPSD-258671	To avoid problems when upgrading from V4.7.0 to V4.7.0.1, uninstall V4.7.0 first. Install V4.7.0.1 with the default configuration and double-click the cfg.reg file, which is generated in the installation path, to restore the configuration. Note: Currently there is no solution or workaround for this limitation (VPSD-258671).