Bug ID
Description
Solution
mislabeled to a fixed name that created the potential
file access violation by two or more backup cleanup
request. This has been corrected. Handled the race
condition on writing into the trace log file when the
backup completes faster and triggers the cleanup
command causing both processes to write into the same
trace log file.
72755
The RME repositories are not updated properly when
Added new logic to handle this scenario. RME will work
last 5 digits of the system serial number is greater than
if last 5 digits of Inserv serial number is greater than
65535.
65535.
Known Issues with Recovery Manager
Item
Description
Workaround
44711
The analyze command displays the wrong information This is expected behavior and that is the reason it is
for out-of-sync virtual volumes if two storage groups have always advisable to have separate volume for each
the same volume.
storage group.
64852
The server time change is not reflected in the RME create If the system time is changed after GUI is launched,
virtual copy schedule wizard.
relaunch the application to refresh the changed system
time in GUI.
65458
RME is unable to detect a disk as an HP 3PAR disk.
The disks presented to the Exchange Servers must be
mapped as raw devices with their compatibility mode
set to physical.
67956
There is no option to skip validation of a virtual copy
If you wish to use virtual copy validation, do not use
when performing one-click backup.
one-click backup. Create the virtual copy first and then
take the backup.
68334
The iSCSI connection for virtual machines fails to mount Ensure that the iSCSI host name in the HP 3PAR Storage
virtual machines.
System is configured as a Fully Qualified Domain Name
(FQDN). For example, if a host's iSCSI qualified name
is
iqn.1991–05.com.microsoft:vm1–exch2010.cw-domain2.comkeep,
the iSCSI host name on the HP 3PAR Storage System
should be vm1–exch2010.cw-domain2.com. The
name is case sensitive.
70439
The Server/Mailbox registration action from the GUI
RME expects that the Exchange configuration is
causes the RME application to exit.
performed properly in the domain. Any error in setup
results in RME exiting..
72094
For DAG setups when nodes are hosted across different The RME GUI may show a "policy limit reached"
systems, the numeric policy is not applied correctly
message. Increase the policy limit to avoid unwanted
during create operations. The RME GUI displays a
messages.
warning message indicating the number of virtual copies
has exceeded the policy limit despite the actual number
of virtual copies being below the policy limit.
72798
Issues with an alternate location during backup and
The mount point should not have blank space in between
restore.
mount point path.
72837
After a week without creating a virtual copy on a DAG Occasionally this issue occurs in a scenario when after
mailbox, attempts to create virtual copies on a passive
a week or so of not creating virtual copy on a DAG
node fail.
mailbox. When trying to create a virtual copy when all
mailbox nodes are healthy on passive nodes, the
operation fails (create on active node succeeds). Move
the active DAG node and attempt the create operation
again on both the active and passive nodes.
72940
RME backups cause system event logs to have many
During restore and creation with validation processes,
errors of the form "device...is not ready for access yet". you may encounter Event ID 15 in the Windows Event
Logs. It is a harmless event log caused by accessing the
4
Known Issues with Recovery Manager

---

...

Dieses Handbuch ist für folgende Modelle:
Software - HP 3PAR StoreServ Application Suite for Microsoft Exchange Media (105.43 kb)