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

B.8 Troubleshooting
3PAR Recovery Manager 4.1.0 For Microsoft Exchange 2010 User’s Guide
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, 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. 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. Once it is validated, to truncate logs,
create a snapshot using the -truncate and -nc switches. Now, try a regular virtual copy
creation. If the virtual copy creation with -nc is also taking a longer time, send an RMReport
to 3PAR Customer Support.
Problem:
After installing RME 3.0.2, it is unable to manage Exchange cluster from Exchange
management. It returns a COM class factory error.
OR
After installing RME 3.0.2, an MSCluster related COM class factory error is returned.
Suggestion:
If RME 3.0.0.* 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 “Microsoft Exchange Replication service” from passive node.
OR
Net stop MSExchangeRepl
Net start MSExchangeRepl