HP StorageWorks SAN Virtualization Services Platform 2.1.1 release notes (5697-0066, July 2009)

disk as a back-end logical unit in step 3. The reason is that the disk may contain some SVSP signatures
left over from step 1, which may be recognized in step 3.
ForceActive external utility issues
The following two issues have been identified after installation of the ForceActive external utility:
• The AutoRecover key is deleted from the Windows registry. After installation of the VSM software,
the AutoRecover key must be re-created manually.
• If the utility is running and the VSM server enters an unknown state, stop the VSM GUI, stop the
ForceActive utility, restart the VSM, and then run the utility again.
Limitations on changing the chassis name of a DPM
• Before replacing a DPM or changing the chassis name of a DPM, first remove the preferred path
of the hosts that were set using the DPM to be replaced.
• Before a name change, remove all host permissions from the SAN API virtual disk. Otherwise the
new DPM will not be automatically inserted into the DPM group and you will need to manually
add the DPM to the group and redistribute the virtual disks between the two DPMs.
Incorrect DPM group information in VSM GUI
The DPM group name and the DPM group ID fields in the VSM GUI display the same information.
Deletion of last DPM in a DPM group
Do not delete the last DPM in a DPM group (even though it is enabled for recovery purposes). To
recover from this situation, the following procedures should be followed:
• For non-synchronized mirror objects: Use Remove Host Permissions and then reassign the permis-
sions to hosts that are visible to the presented DPMs.
• For synchronized mirror objects:
1. Delete the host/UDH from the setup.
2. Verify that the host is visible through the presented DPMs.
3. Re-create the UDH.
4. Reassign the synchronous mirror group permission to the host through the presented DPMs.
Deletion of absent DPM that exposes virtual disks to hosts
You should not delete an absent DPM that exposes virtual disks to hosts if it is the only DPM in the
DPM group. The correct way to delete the DPM is to move this DPM to a group with DPMs and then
replace it.
If you cannot move the DPM to a DPM group, and you still want to replace it, then follow these steps:
1. Delete the absent DPM.
2. Remove all host permissions from the virtual disks, PiTs, and virtual disk groups that remain without
the DPM.
3. Connect another DPM.
4. Reassign host permissions to the virtual disks, PiTs, and virtual disk groups.
HP StorageWorks SAN Virtualization Services Platform 2.1.1 release notes 11