HP StorageWorks SAN Virtualization Services Platform 3.0.1 Release Notes (5697 - 0405, May 2010)

Restoring a VSM setup from a backup cannot have PiTs
Restoring a VSM setup from a backup can be safely performed only if there are no PiTs in the system.
If PiTs exist (either created directly or by Business Copy or Continuous Access applications), their
metadata in the setup backup may be invalid and may result in data loss/corruption if restored.
Error 1618 during VSM installation
During a VSM installation, you may receive an error 1618 and the procedure aborts. This is caused
by another installation program trying to perform an install during the VSM installation. Wait for all
other pending installations to finish, and then install VSM.
Limit of 63 PiTs on thin virtual disk
You can only create 63 PiTs on top of a thin virtual disk, instead of 64 on top of a regular (or thick)
virtual disk. The initial PiT of a thin virtual disk is counted against the limit of 64 PiTs.
Front-end hosts not able to work with objects
When a back-end array or LUN in the DPM back-end disappears or is masked out for a long time
and then returns, the front-end hosts are not able to work with the objects (virtual disks, snapshots,
and so on) that use the disappearing device (array or LUN). The workaround is that you need to
execute an HBA disable/enable cycle or reboot the front-end host when the device returns.
Export/import query does not work
The export or import of a query does not work at this time.
Cannot have same first 29 characters in sync mirror task names
You cannot have two synchronous mirror tasks with the first 29 characters of their names being
identical. When this occurs, an Object already exists message appears, and the operation
(adding the second task) fails.
Cannot expand VDG without same DPM as the members
You are unable to expand a virtual disk group (VDG) if the added virtual disks do not have the same
active Data Path Module and the virtual disk group members. In addition, a virtual disk with host
permissions cannot be added to a VDG with asynchronous mirroring. In order to expand a VDG with
asynchronous mirroring (with an “expand VDG” operation), the virtual disk added must not have host
permissions.
VSM does not enforce 512 data movers
VSM does not enforce the limit of 512 data movers in the destination domain. Going above 512
may cause the task to slow down, or other unintended consequences, and is not supported.
SAN Virtualization Services Platform 3.0.1 Release Notes 13