HP StorageWorks SAN Virtualization Services Platform 3.0 release notes (5697-0404, April 2010)

Setting the cluster bit for Serviceguard in Linux or HP-UX
If virtual disks are presented through Data Path Modules with Linux or HP-UX, do not set the cluster
bit, as this will force the DPMs to abort pending writes after a period of time.
Capacity limits with thin provisioned volumes
When you run out of free space in a storage pool, a write to a thin provisioned virtual disk will create
an error to the I/O, but information about that error may not convey the idea that thin volume space
has run out because the SCSI standards have not taken this into account yet. You should receive a
message or alert from the VSM indicating that space for a thin volume has run out, because the VSM
understands thin volumes. This can be prevented by properly setting and actively monitoring your
pool protection thresholds, adding capacity, or adding thin provisioning licenses.
VSM issues
Threshold limit message only sent once
When a threshold limit is reached, a single event log message is generated, instead of a message
being sent every five minutes.
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.
SAN Virtualization Services Platform 3.0 release notes 13