HP StorageWorks SAN Virtualization Services Platform 3.0.4 Release Notes (5697-0763, November 2010)

Manual failover of loaded system with VSM GUI causes a non-expected system state
A manual VSM failover from the VSM GUI with 512 asynchronous mirror data movers causes a
non-expected system state (NESS). The scenario is as follows:
1. VSM1 is active.
2. A failover is initiated from VSM1 to VSM2.
3. VSM2 becomes active, but experiences a NESS after a period of time and reboots.
4. VSM1 becomes active again and VSM2 becomes passive after it boots up.
5. After VSM2 reboots, the system works as expected.
Actively stopping and starting the SVSP Monitor does not cause this issue; only a manual VSM failover
from the VSM GUI, and appears related to a larger systems. Use either of the following two
workarounds to fail over VSMs with a loaded system:
• Stop VSM1 (the active VSM) from the SVSP Monitor to enable the other VSM to become active,
then restart the SVSP Monitor on VSM1 so it becomes passive.
• Reboot the active VSM.
VSM GUI unable to remove all host presentations in one operation
If the host has one or more VDG snapshot presentations, you are unable to remove all the virtual disk
presentations to the host (by right-clicking the Host entity and selecting Manage > Manage Virtual
Disk Presentations > Remove Presentations). The list will be empty. You must first remove the host
presentation from all VDG snapshots and then go to the Host entity to remove the presentations.
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 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 a thin virtual disk, instead of 64 on a regular (or thick) virtual disk.
The initial PiT of a thin virtual disk is counted against the limit of 64 PiTs.
SAN Virtualization Services Platform 3.0.4 Release Notes 15