HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses - Manual (Page 99)

5. Select the COM Security tab.
6. Under Access Permissions, click Edit Default.
7. Add a Cluster Service account and select Local Access and Remote Access.
8. Reboot the machine.
9. Perform these steps on the second node.
Problem:
You attempt to perform a media restore using the Recovery Manager CLI -ts command and the
attempt fails.
Suggestion:
If the restore log contains the error message: “client <client> peer name <peer name> is
invalid for restore request,” the restore client is different from the backup client. Configure Symantec
NetBackup to perform a redirected media restore as follows:
1.
Create an altnames directory on the NetBackup master server in the directory containing the
backup policy for other clients:
Install_path\NetBackup\db\
2. Place an empty file named No.Restrictions in the altnames directory:
Install_path\NetBackup\db\altnames\No.Restrictions
Do not add a suffix to the files in the altnames directory.
3. Ensure that the NetBackup client name on the requesting client matches the name of the client
for which the backup was created. (The peer name of the requesting client need not match
the NetBackup client name.)
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:
Error in communication between Production Server and Backup Server and the
vcdbasqlRMSQLAgent_1.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 Microsoft SQL Server uses port 9932. This port might
be used by other 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 Recovery Manager in the registry and restart HP 3PAR
Recovery manager for SQL service from services.msc.
NOTE: The port used should be the same on both, backup server and production servers.
•
Find out the application using the default port and stop that application.
To find out the application using the default port:
◦ Open the command prompt
◦ Run netstat -ano | find "<port number>"
Example:
c:\>netstat -ano | find "9965"
UDP 10.10.5.32: 9932 *:* 1252
Troubleshooting 99