STATUS CODE 37: Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server"

Problem

STATUS CODE 37: Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server"

Error Message

Operation requested by an invalid server

Solution

Overview:  Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server"

Troubleshooting: Review the Activity Monitor or the All Log Entries report for the backup which failed with a Status Code 37 and determine what server name is not considered valid by the master server

Log files:  N/A

Resolution:
Most commonly, a Status Code 37 is the result of not adding a new media server's name to the servers list on the master server.
 
- For UNIX master servers, add the line SERVER = <new_media_server_name> to the bp.conf file on the master server.  Be sure to add this entry after any existing SERVER = lines in the bp.conf file.  
- For Windows servers, add the new media server to the master server's server list by opening the NetBackup Administration Console, and under "Host Properties", selecting Master Server.  On the right hand window pane, double click on the name of the master server and go to the "Servers" section.  Add the new server name to the servers list.  

After adding the server to the servers list on a UNIX master server, stop and restart the NetBackup request daemon (bprd) and NetBackup database manager daemon (bpdbm) for the changes to take effect. If the master server is Windows, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services for the changes to take effect.  

This issue has also been observed when there are problems with name resolution.  Confirm the name of the server generating the Status Code 37 was added to the Domain Name Service (DNS) name tables and/or the local hosts file depending on how the environment resolves names.  

In previous incidents, a Status Code 37 was caused by corrupt lock files within the master server's bprd.d directory (/usr/openv/netbackup/bin on a UNIX master server, and <install_path>\veritas\netbackup\bin on a Windows master server).  

The master server's bpcd log may repeatedly display a message similar to the following:
<16> bpcd valid_server: <servername> is not a server

To clear up the corrupt lock files, use the following steps:
1. Stop all NetBackup daemons/services on the master server
2. While all NetBackup daemons/services on the master server are stopped, rename the bprd.d directory to bprd.d_old
3. Recreate a new, empty bprd.d directory on the master server
4. Start the master server NetBackup daemons/services

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)