HP 3PAR Application Software Suite for Microsoft Exchange Licenses User Manual
Page 91
Make sure the communication port for Recovery Manager is set to be the same on all Recovery
Manager installed systems. You need to restart the 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:
Recovery Manager cannot locate the Exchange Server.
Suggestion:
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. 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.
Problem:
Recovery Manager cannot detect the mailbox database.
Suggestion:
The 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.
Suggestion:
There are a few things to check on your system.
1.
Make sure both the data and log files of your mailbox database are installed on an HP 3PAR
volume.
2.
Make sure your HP 3PAR volume is formatted as Basic Disk type.
3.
Make sure you have allocated snapshot space for your HP 3PAR volumes.
4.
Make sure your system configuration conforms to the HP 3PAR support matrix.
Problem:
The Recovery Manager interface takes a long time to start or to bring up the server registration
dialog.
Suggestion:
When Recovery Manager is started for the first time, or when you click on the server registration,
Recovery Manager will try to scan the entire network for available Exchange servers. Exchange
object query might cause this latency.
Problem:
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,
Recovery Manager claims that the backup has failed.
Suggestion:
Timeout for backup initialization detection can be modified to accommodate the timing issue.
Please refer to the RMExch config command for more information.
Problem:
NetBackup takes a substantial amount of time to complete a backup process.
Troubleshooting
91