STATUS CODE 37: Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server"
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
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.
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: