HP StorageWorks SAN Virtualization Services Platform 3.0.2 Release Notes (5697-0347, May 2010)

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.
Issue when exceeding 180 async mirror tasks
When the number of asynchronous mirror data mover tasks on a single VSM server exceeds 180, a
situation may arise under specific conditions where the existing asynchronous mirror PiTs do not
progress and new PiTs are not created. A workaround is:
1. Stop and start the VSM service on the passive server using the VSM Monitor.
2. From the active VSM server, failover to the passive server.
MSA capacity can be reported in base 2 or base 10
The VSM reports capacity in base 2 (for example, 1 TB = 1024 GB). The MSA can report capacity
in base 10 (1 TB = 1000 GB) or can be configured to report in base 2. The MSA setting can be
changed from the management GUI or from the CLI:
From the management GUI:
1. Log in to the MSA using the management IP address in the browser window.
2. Click on the storage controller in the config view on the left side of the screen.
3. Select the Configuration pull-down menu on the right side of the screen.
4. Select Users > Modify User.
SAN Virtualization Services Platform 3.0.2 Release Notes 15