HP 3PAR Recovery Manager Software User Manual
Page 146
Make sure that the communication port for HP 3PAR Recovery Manager is set to be the same on
all HP 3PAR Recovery Manager installed systems. You need to restart the HP 3PAR Recovery
Manager for Exchange Agent service on every system followed by the port change command.
If the firewall or security monitoring software is installed, verify that the communication port and
remote registry service ports (139 and 445) are allowed for access.
Problem:
HP 3PAR Recovery Manager cannot locate the Exchange Server.
Suggestion:
•
HP 3PAR Recovery Manager uses the Active Directory structure to locate Exchange server
information within the same domain or, if you have registered multiple Active Directory domains,
within the registered domains. HP 3PAR Recovery Manager cannot access the Exchange
information if you have only configured local domains and the information is not in the same
domain, or if you have set up multiple Active Directory domains but the information is in an
unregistered domain.
•
If HP 3PAR Recovery Manager cannot locate the exchange server within the same domain or
a local domain, then check if the system time in production server and backup servers are in
synchronization with Active Directory or NTP (Network Time Protocol) server. Ensure that the
network link between all nodes is working properly.
Problem:
HP 3PAR Recovery Manager cannot detect the mailbox database/storage group.
Suggestion:
The HP 3PAR Recovery Manager user has to have Exchange Administrator privilege to access
Exchange Active Directory objects.
Problem:
Virtual copy creation always fails on the mailbox database/storage group.
Suggestion:
There are a few things to check on your system.
1.
Make sure both that the data and log files of mailbox database/storage group are installed
on an HP 3PAR volume.
2.
Make sure that HP 3PAR volume is formatted as Basic Disk type.
3.
Make sure that snapshot space is allocated for your HP 3PAR volumes.
4.
Make sure that system configuration conforms to the HP 3PAR support matrix.
Problem:
The HP 3PAR Recovery Manager interface takes a long time to start or to bring up the server
registration dialog.
Suggestion:
When HP 3PAR Recovery Manager is started for the first time, or when you click on the server
registration, HP 3PAR Recovery Manager will try to scan the entire network for available Exchange
servers. Exchange object query might cause this latency.
Problem:
HP 3PAR Recovery Manager always fails to issue a command from the user interface and command
line right after the installation.
Suggestion:
If the software is installed through a remote desktop session, the newly added environment variables
will not become effective until you log off the session. If the software is installed directly from the
system console, these variables should be available immediately.
Problem:
Symantec NetBackup takes a substantial amount of time to start a backup process. However, HP
3PAR Recovery Manager claims that the backup has failed.
Suggestion:
146
Troubleshooting