Symantec NetBackup status code 34 to status code 39
Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.
Below are some of the NetBackup status error codes from Status Code 34 to Status Code 39 which may be received while using the Symantec NetBackup tool.
NetBackup status code: 34
Message: failed waiting for child process
Explanation: A NetBackup process encountered a failure while it waited for a
child process to complete.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information,
create a debug log for the process that you think may have returned this status
code. Then, retry the operation and check the resulting debug log.
NetBackup status code: 35
Message: cannot make required directory
Explanation: Could not create a required directory.
Possible causes are the following:
A process does not have permission to create the directory
The path to the directory is not valid
An IO error occurs
No space is available on the device that contains the directory
Recommended Action: Do the following, as appropriate:
Check the NetBackup All Log Entries report to determine which directory was
not created and why it was not created. In particular, check for a full disk
Check the permissions on the parent directory. Verify that NetBackup services
are started with a Logonas account that has permission to create the directory.
For detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.
NetBackup status code: 36
Message: failed trying to allocate memory
Explanation: Allocation of system memory failed. This error occurs when an
insufficient system memory is available. This cause of this error may be that the
system is overloaded with too many processes and it does not enough physical
and virtual memory.
RecommendedAction: Free up memory by terminating any unneeded processes
that consume a lot of memory. Add more swap space or physical memory.
NetBackup status code: 37
Message: operation requested by an invalid server
Explanation: An invalid media server or Windows NetBackup Remote
Administration Console made a request to the NetBackup request daemon (bprd)
or NetBackup database manager daemon (bpdbm). On Windows, these daemons
are the NetBackup Request 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 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 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 to access configuration settings” in the
If a server or Windows NetBackup Remote Administration Console has more than
one host name (for example, it has multiple network interfaces), 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.
NetBackup status code: 38
Message: could not get group information
Explanation: Could not get the group entry that describes a UNIX or Linux user
Recommended Action: Check the NetBackup Problems report for clues on why
the error occurred. For detailed troubleshooting information, create a debug log
directory for the process that returned this status code. Then retry the operation
and check the resulting debug log.
NetBackup status code: 39
Message: client name mismatch
Explanation: The client used a name in a request to the NetBackup server that
did not match the configured name in the policy on the server.
Recommended Action: Change one of the following so the two match: the
NetBackup client name setting on the client (see the applicable NetBackup users
guide) or the one in the policy configuration on the server.
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.