Symantec NetBackup status code 45 to status code 50


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 45 to Status Code 50 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 45
Message: request attempted on a non reserved port
Explanation: A try was made to access a client from a non-reserved port.
Recommended Action: Verify that the latest software is installed on the client
and server.
On UNIX and Linux NetBackup servers and clients, check the
/usr/openv/netbackup/bin/version file.
On Windows NetBackup servers, check the
install_path\netbackup\version.txt file or the AboutNetBackup item on
the Help menu.
On Microsoft Windows clients, check the About NetBackup item on the Help
On NetWare target clients, check the Version entry in the bp.ini file.
On Macintosh clients, check the version file in the bin folder in the NetBackup
folder in the Preferences folder.

NetBackup status code: 46
Message: server not allowed access
Explanation: The server tries to access a client, but access is blocked.
Possible causes are as follows:
The server is not listed on the client as a valid server.
The client was configured to require encrypted backups, but the encryption
attribute for the backup policy on the server was not selected.
The evaluation license for the NetBackup Encryption product has expired on
the server, but the NetBackup client was configured to require encrypted
backups. As a result, the server tries to make a non-encrypted backup of the
client. Since the client is configured to require encryption, the backup failed.

NetBackup status code: 47
Message: host is unreachable
Explanation: An attempt to connect to another computer failed.
Recommended Action: Do the following, as appropriate:
Verify that the name service (or services) used by the client are configured to
resolve the host names of the NetBackup server correctly.
Verify that the name service (or services) used by the server are configured to
resolve the host name of the NetBackup client correctly.
Try to ping the client from the server and the server from the client.
If you continue to have problems, do the following:
See “Resolving network communication problems” in the Troubleshooting

NetBackup status code: 48
Message: client hostname could not be found
Explanation: The system function gethostbyname() failed to find the client’s
host name.
Recommended Action: Verify that the client name is correct in the following:
The NetBackup policy configuration on the master server.
The General tab in the following dialog boxes: NetBackupClientProperties
and SpecifyNetBackupMachinesandPolicyType (on Microsoft Windows
and NetWare nontarget clients). To display these dialog boxes, start the
Backup, Archive, and Restore interface on the client. For the General tab,
click NetBackup Client Properties on the File menu; click Specify
NetBackup Machines and Policy Type on the File menu.
The bp.conf file on UNIX, Linux, and Macintosh clients.
The bp.ini file on NetWare target clients.
On clients and servers, verify that the name service is set up to resolve the
NetBackup client names correctly.
On UNIX and Linux clients, verify that the client’s host name is in the
/etc/hosts file or the YP hosts file or NIS maps.

NetBackup status code: 49
Message: client did not start
Explanation: The client failed to start up correctly.
Recommended Action: Do the following, as appropriate:
Make sure that software is installed on the client and it is the correct version.
If necessary, reinstall the client software.
Check for full file systems on the client.
Enable detailed debug logging on the client by doing one of the following:
Create bpcd and bpbkar (UNIX, Linux, and Windows only) debug log
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
On Windows clients, increase the debug or log level.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
Retry the operation and examine the resulting logs.
On UNIX or Linux systems, use the UNIX sum command to check for corrupt

NetBackup status code: 50
Message: client process aborted
Explanation: The client backup terminated abnormally. For example, this error
occurs if a NetBackup master or media server is shut down or rebooted when a
backup or restore is in progress.

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *