HP 3PAR Application Software Suite for Microsoft Exchange - Manual (Page 145)

If the virtual copy is requested on a passive from active node or vice versa, it will be created on
the desired node. The virtual copy is visible only on the node where it is created. Check the
appropriate node.
Problem:
Recovery Manager shows the virtual copy as available but it is mounted or vice versa.
OR
Recovery Manager shows the virtual copy as available but it still cannot be mounted because the
status indicates that the virtual copy is already mounted.
Suggestion:
This mismatched entry might be due to a previously failed Recovery Manager operation. Check
for mismatched entries using the analyze command.
To resolve mismatched entries, follow these steps:
1.
Remove VLUNs and virtual volumes for the mismatched volume. Run the command:
(For Exchange 2010/ Exchange 2013) HpRmCli Exch analyze -mdb <mailbox_db>
(For Exchange 2007) HpRmCli Exch analyze -s <exchange server> -g <storage
group>
This command shows which virtual volumes and VLUNs might be left over from a previously
failed operation. Remove these VLUNs and virtual volumes manually from the HP 3PAR
StoreServ Storage System.
2. Remove timestamp entries from the repository. Run the command:
(For Exchange 2010/ Exchange 2013) HpRmCli Exch analyze -mdb <mailbox_db>
(For Exchange 2007) HpRmCli Exch analyze -s <exchange server> -g <storage
group>
This shows all the missing virtual volumes from a mailbox database/storage group. These are
the virtual volumes entries that are deleted from HP 3PAR StoreServ Storage System but are
still in the repository. Remove the respective timestamps from repository by deleting the
directory:
(For Exchange 2010/ Exchange 2013)
<installpath>\3PAR\RM\Exchange\Repository_E2010\<exchange
server>\<mailbox_db>\<time stamp>
(For Exchange 2007) <installpath>\3PAR\RM\Exchange\Repository\<exchange
server>\<storage group>\<time stamp>
Problem:
Recovery Manager takes too long to create a virtual copy.
Suggestion:
Once the snapshot is created, it is verified and .log files are truncated. For this, the checkpoint
is fetched and log file names are traversed one by one. This may take a longer due to a large
number of .log files for a mailbox database/storage group. If a virtual copy creation is taking
too long, check the virtual copy creation with the -nc option. This will skip log verification and
log truncation. Then, verify this snapshot using the validate command. After it is validated, to
truncate logs, create a snapshot using the -truncate and -nc options. Finally , try a regular
virtual copy creation. If the virtual copy creation with -nc is also taking a longer time, send an
RMReport to HP Customer Support.
Problem:
After installing Recovery Manager, it is unable to manage the Exchange cluster from Exchange
management. It returns a COM class factory error.
OR
After installing Recovery Manager, an MSCluster-related COM class factory error is returned.
Suggestion:
Troubleshooting 145