HP 3PAR Recovery Manager Software - Manual (Page 149)

HP 3PAR 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( HpRmCli Exch report -h < host name > -output <Output file path name and
location>
) to HP Customer Support.
e sa
Problem:
After installing HP 3PAR Recovery Manager, it is unable to manage the Exchange cluster from
Exchange management. It returns a COM class factory error.
OR
After installing HP 3PAR Recovery Manager, an MSCluster-related COM class factory error is
returned.
Suggestion:
If the previous version of HP 3PAR 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, then to get the writer into a “stable” state with no last error restart
the Microsoft Exchange Replication service. To restart the service, use one of the following methods
.
•
Restart the Microsoft Exchange Replication service from the passive node.
•
Restart the service using the Net command at command prompt. Run the following commands:
Net stop MSExchangeRepl
Net start MSExchangeRepl
If restarting the Microsoft Exchange Replication service does not resolve the issue, then restart the
Microsoft Exchange Information Store service. To restart this service, use one of the following
methods:
•
Restart the Microsoft Exchange Information Store service from services.msc.
•
Restart the service using the Net command at command prompt. Run the following commands:
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
Troubleshooting 149