HP 3PAR Recovery Manager Software User Manual
Page 150
Problem:
The Remote Copy status for volume group
Suggestion:
The involved Remote Copy group has virtual volumes that are not in the synchronized state. Wait
until all virtual volumes in the group display synchronized state and then retry the operation.
Problem:
An LDP COM error message like the following appears:
RME5220: ERROR: COM: Failed to bind to LDAP path
Groups,CN=Westwood,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=westwood2000>: 0xc1032221.
Suggestion:
You may not have permissions for the specified mailbox database/storage group or the mailbox
database/storage group is absent.
Problem:
When using Symantec NetBackup, you see this message: 0x1: ERROR: Cannot connect
to [NBU server name]; socket error
.
Suggestion:
Check whether you are using a different version of the NBU master server and the NBU client. If
so, upgrade the NBU client to the same version as the NBU master server.
Problem:
While installing HP 3PAR Recovery Manager Software for Exchange, the setup.exe prompts to
uninstall HP 3PAR CLI though it is a supported version as per the Single Point of Connectivity
Knowledge for HP Storage Products (SPOCK) document. The installer does not provide an option
to install HP 3PAR Recovery Manager Software for Exchange.
Suggestion:
If you want to install only HP 3PAR Recovery Manager Software for Exchange without its required
components, then run RME_2k8_x64.msi directly from the folder \HP3PAR\
RecoveryManagerExchange
. Ensure that you have the supported configuration as per the Single
Point of Connectivity Knowledge for HP Storage Products (SPOCK) document.
Problem:
In Exchange 2010 DAG setup, after passive node restore (with activating the passive copy), the
“Exchange Management Console” doesnot refresh the mailbox status correctly.
Suggestion:
First, refresh the Exchange Management Console window to refresh the mailbox status correctly.
If it does not show the correct status, restart Exchange Management Console
Problem:
Error in communication between Production Server and Backup Server and the RMService.log
shows the following exception - System.Net.Sockets.SocketException: Only one usage of each
socket address (protocol/network address/port) is normally permitted
Suggestion:
By default, HP 3PAR Recovery Manager for Exchange uses port 9933. This default port might be
used by another application leading to a communication issue between backup server and
production servers.
If you continuously notice this issue, follow either of the following steps:
•
Change the default port used by HP 3PAR Recovery Manager for Exchange in the registry
and restart HP 3PAR Recovery manager for Exchange service from services.msc.
150
Troubleshooting