HP 3PAR Mangement Plug-In and Recovery Manager 2.5.1 for VMware vSphere Release Notes (QL226-97318)

WorkaroundDescription
the vSphere client resides. Failing to do so might cause
vSphere client to hang.
3. Follow the prompts in the certificate wizard and then click
OK when installation completes.
4. Click OK on the Security Warning dialog.
5. Close and then reopen the vSphere Client.
This needs to be done only once.
This behavior can be ignored because it does not affect the
uninstallation or reinstallation process.
While removing the application, the following event is logged
in the Event viewer:
Application or service '3PAR Management
Plug-in and Recovery Manager for VMware
vSphere Web Service' could not be restarted.
This version supports only English language for virtual
machines and Datastores.
RMVMware.exe Virtual Copy creation fails when virtual
machine or Datastore name is in Japanese.
Perform one of the following workarounds:
• Rename Japanese names to English names.
• Use the UUID method to create snapshots for virtual
machines or Datastores.
Application Consistency is not supported on virtual machines
that are configured using physical compatibility RDM LUNs.
Application consistent Virtual Copy creation fails if the virtual
machine has physical compatibility RDM (Raw Device
Mapping).
If possible, remove physical compatibility RDMs or convert
the VMs to virtual compatibility RDMs.
Remove the expiry value from the base volume or remove the
expiry value from the Virtual Copies using the HP 3PAR OS
CLI.
Virtual Copy volumes display as expirable even though
the Expiry option is not selected. This instance occurs when
the base volume has an expiration set by the HP 3PAR
StoreServ Storage system. By default, all Virtual Copies inherit
expiry values from the parent base volume.
Datastore/Virtual Volume promote must only be used as the
last available option if virtual machine level Virtual Copies
are not available.
When multiple VMs sit on a single Datastore/Virtual Volume,
a Datastore promote will roll back all VMs to a point-in-time.
If a single VM resides on multiple Datastore/Virtual Volumes
Always use VM level application consistent Virtual Copy
whenever possible and restore only the affected virtual disk.
and if only a single volume is promoted, then data
inconsistencies might occur.
If a single VM sits on multiple Datastores/Virtual Volumes,
all Datastores used by the same VM must be promoted.
The reason for the error relates to the UAC (User Access
Control) feature of Microsoft Windows. With UAC enabled,
Microsoft Windows domain users with local administrator
privileges are unable to run the RMV Admin Tool. The
following error is displayed: a domain user with local administrator privileges is treated
Only user with administrative privilege is
permitted to use this utility.
as a regular user unless the access right to a program is
elevated.
There are two ways for a domain user with administrator
privileges to run the program properly:
• Disable the Microsoft Windows UAC feature.
• Choose Run as administrator when you open the Admin
Tool.
This error is caused by the Guest OS when Daylight Savings
Time change is about to occur. Reschedule the operation to
run after the time change occurs.
Scheduling Virtual Copy tasks near Daylight Savings Time
change might fail to create snapshot. The following message
is displayed:
The guest OS has reported an error during
quiescing. The error code was: 4 The error
message was: Quiesce aborted.
Click No and refresh the screen. Wait for a few seconds
before scrolling up and down through the table.
When scrolling up and down through the Virtual Volumes
table in the Virtual Volumes tab, a script error might occur
in the vSphere Client.
Known issues 5