Netbackup Error 37 Operation Requested By An Invalid Server
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas operation requested by an invalid server 37 restore Customer Success Licensing Programs Licensing Process ABOUT About Corporate
Netbackup Error 37 Restore
Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English netbackup error 37 on client restore Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Restore fails with status 37: operation requested by an invalid server Article:000012587
Peer Name Is Invalid For Restore Request
Publish: Article URL:http://www.veritas.com/docs/000012587 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Exchange Agent or other user-directed restore fails with status 37 before the job goes active. Error Message The Backup, Archive, and Restore (BAR) GUI will display this error: Operation requested by an invalid server - status 37 The bprd debug log shows the processing that occurs to authenticate the restore request. First, a check is made to see if this is a server-directed restore. The requesting source IP is resolved to a hostname (referred to as the peername), but it is not in the SERVER list so this is not a server-directed restore. 15:00:03.713 [13886] <2> bprd: socket fd from accept() is 10 15:00:03.720 [27641] <2> logconnections: BPRD ACCEPT FROM 3.3.3.3.43716 TO 1.1.1.1.13724 15:00:03.729 [27641] <2> connected_peer: Connection from host Node1-bk.domain, 3.3.3.3, on non-reserved port 43716 15:00:03.73
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 37: When viewing policies in a remote NetBackup Admin Console, the following error is seen: The list of policies could not be retrieved, status 37, operation requested by an invalid server. Also, the https://www.veritas.com/support/en_US/article.TECH155673 activity monitor shows: Not connected.... Article:000027826 Publish: Article URL:http://www.veritas.com/docs/000027826 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage https://www.veritas.com/support/en_US/article.000027826 your Subscriptions Problem STATUS CODE 37: When viewing policies in a remote NetBackup Administration Console, the following error is seen: "The list of policies could not be retrieved, status 37, operation requested by an invalid server." Also, the activity monitor shows "Not connected. Check if services are up." Error Message The list of policies could not be retrieved, status: 37. Operation requested by an invalid serverNot connected. Check if services are up. Solution Overview:When viewing policies in a remote NetBackup Administration Console, the following error is seen: "The list of policies could not be retrieved, status 37, operation requested by an invalid server." Also, the activity monitor shows "Not connected. Check if services are up."Troubleshooting:This error can occur because the machine being used as the remote administration console does not have a server entry on the Master Server that allows it to perform server level operations. In some cases, when this server entry on the Master Server is already in place, name resolution issues can still cause this error.Note: The remote administration console machine may be also
or NetBackup database manager daemon (bpdbm). On Windows, these daemons are the NetBackup Request http://systemmanager.ru/nbadmin.en/nbu_37.htm Manager and NetBackup database manager services. Recommended Action: Examine the NetBackup All Log Entries report for the time of this error to determine which system tried to connect to the master server. If the server is a valid media server, verify that the storage unit for the netbackup error media server is defined. Also, verify that the server or Windows NetBackup Remote Administration Console has a server list entry on the master server. If necessary, update the server list. On a UNIX or Linux master server, add a SERVER = media_server_name to the bp.conf file. media_server_name netbackup error 37 is the host name of the media server. On a Windows master server, add the media server to the list on the Servers tab in the Master Server Properties dialog box. See "Using the Host Properties window" in the Troubleshooting Guide. If a server or Windows NetBackup Remote Administration Console has more than one host name (for example, it has multiple network interfaces), do the following: verify that the master server has a server list entry for each of them. If you change the server list on a UNIX or Linux master server, for the changes to take effect do the following: stop and restart the NetBackup Request daemon (bprd) and NetBackup database manager daemon (bpdbm). If you change the server list on a Windows master server, stop, and restart the NetBackup Request Manager and NetBackup database manager services.