Known issues

This section details the known issues in version 4.5.0 of the IBM® System Storage® Support for Microsoft Volume Shadow Copy Service and Virtual Disk Service.

Ticket ID	Description
VPSD-258619	When using the IBM VSS Hardware Provider in a Windows Hyper-V Live Migration environment, FlashCopy® fails on any guest operating system where the cluster owner and Hyper-V host are not on the same node.
VPSD-258648	Supports only NTFS volume.
VPSD-258649	When you create a Shadow Copy for dynamic disk on Microsoft Windows Server 2003, the Shadow Copy must be "transportable" type.
VPSD-258650	Import operation for GPT + Dynamic disk is not supported on Microsoft Windows Server 2003.
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.
VPSD-258652	Drops support of DS6000, SAN Volume Controller 4.3.1 and earlier, and DS8000 CIM agent version 5.3 and earlier
VPSD-258653	Supports only embedded CIM Agent.
VPSD-258654	For DS8000® restore operation, space efficient volume or backgroundCopy of zero is not supported.
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 pool.
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 pool. The snapshot IDs of earlier FlashCopy volumes stay in host until the next snapshot/restore is run. Alternatively, ibmvcfg.exe cleanupDependentMaps can be used to clean up the snapshot IDs of earlier FlashCopy volumes manually.
VPSD-258657	Before using 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.
VPSD-258658	IBM Virtual Disk Service provider is not automatically registered after installation. To manually register IBM Virtual Disk Service provider, issue the regsvr32 ibmvds.dll command under the directory of the IBM Volume Shadow Copy Service provider.

Known defects

Ticket ID	Description
VPSD-245364	Microsoft DPM creates the FlashCopy for the shared source volume. In case SEV and copy rate are zero, the cascading FlashCopy is created unexpectedly. The deletion of cascading FlashCopy(s) causes target volumes to error. Work around: Set the background copy rate above zero when you use the space efficient volume in Microsoft DPM.
VPSD-250031	Cascading FlashCopy(s) are mapped to the wrong host after deleting shadows when backgroupCopy is zero. Work around: Create cascading transportable FlashCopy(s) with backgroundCopy rate 0. Import one FlashCopy and delete it. The FlashCopy volume will be mapped to both free the pool and reserved pool. It is recommended to import all the FlashCopy(s) before you delete one of them to avoid this issue. Or, after you delete the FlashCopy, map the deleted FlashCopy volume to the right pool manually.

Ticket ID

Description

VPSD-245364

Microsoft DPM creates the FlashCopy for the shared source volume. In case SEV and copy rate are zero, the cascading FlashCopy is created unexpectedly. The deletion of cascading FlashCopy(s) causes target volumes to error.

Work around:

Set the background copy rate above zero when you use the space efficient volume in Microsoft DPM.

VPSD-250031

Cascading FlashCopy(s) are mapped to the wrong host after deleting shadows when backgroupCopy is zero.

Work around:

Create cascading transportable FlashCopy(s) with backgroundCopy rate 0. Import one FlashCopy and delete it. The FlashCopy volume will be mapped to both free the pool and reserved pool. It is recommended to import all the FlashCopy(s) before you delete one of them to avoid this issue. Or, after you delete the FlashCopy, map the deleted FlashCopy volume to the right pool manually.