beautypg.com

HP 3PAR Application Software Suite for Microsoft Exchange User Manual

Page 124

background image

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 switch. 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 switches. 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:
If the previous version of Recovery Manager is uninstalled, the msclus.dll is unregistered and
results in the COM class factory error. To resolve this, run:

- regsvr32 C:\Windows\system32\msclus.dll

Problem:
How to recover the Exchange writer status from last error “Non-retryable” to “No error”.
Suggestion:
If the Exchange writer status shows the last error as “Non-retryable” on a CCR active or passive
node or an LCR passive copy, try one of the following methods to get the writer into a “stable”
state with no last error.
Restart the Microsoft Exchange Replication service from the passive node.
OR

Net stop MSExchangeRepl

Net start MSExchangeRepl

If restarting the Microsoft Exchange Replication service does not solve the problem, try one of the
following methods:
Restart the Microsoft Exchange Information Store service.
OR

Net stop MSExchangeIS

Net start MSExchangeIS

Problem:
How to recover the System Writer status from last error “Non-retryable” to “No error”.
Suggestion:
Restart the Cryptographic Services service.
OR

Net stop CryptSvc

Net start CryptSvc

Problem:
The Remote Copy status for volume group does not permit synchronization.
Suggestion:
The involved Remote Copy group has virtual volumes that are not in the synced state. Wait until
all virtual volumes in the group display in synced state and then retry the operation.
Problem:
An LDP COM error message like the following appears:

124

Troubleshooting