Symantec NetBackup status code 506 to status code 510

SQLServerF1

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

NetBackup status code: 506
Message: Cannot connect to the NB-Java user service on host on port port_number.
If successfully logged in before, retry your last operation. Check the log file for
more details.
Explanation: After the NetBackup-Java authentication service validates the user
name, a NetBackup-Java user service is used for all other service requests from
the NetBackup-Java interface. Communication was tried between the
NetBackup-Java interface and the user service on host (host) on the port number
that was specified in the error message. More information about various port
configuration options is available.
See NetBackup Administrator’s Guide, Volume I.
The NetBackupAdministrationConsole log file should contain more detail about
this error.
¦ On UNIX and Linux: the port configuration options are specified in the
/usr/openv/netbackup/bp.conf file or through Administration Console Host
Properties.
¦ On Windows: from the NetBackup Administration Console, select Host
Properties. Select Properties on the Actions menu. The Port Ranges tab
contains the port options.
Recommended Action: Do the following, as appropriate:
¦ Restart the NetBackup-Java interface and log in again.
¦ If the problem persists, enable detailed debug logging.
¦ Restart the NetBackup-Java interface and examine the logs.

NetBackup status code: 507
Message: Socket connection to the NB-Java user service has been broken. Retry
your last operation. Check the log file for more details.
Explanation: The connection was broken to the NetBackup Java application server
that is running on the NetBackup host (where you are logged in). The NetBackup
Administration Console log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
¦ Retry the last operation.
¦ If the problem persists, restart the NetBackup-Java interface and try again.
¦ If the problem still persists, enable detailed debug logging.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Restart the NetBackup-Java interface and examine the logs.
Note: You may have network or system problems unrelated to NetBackup.

NetBackup status code: 508
Message: Can not write file.
Explanation: This cause of this error is one of the following:
¦ The NetBackup-Java user service tries to write to a file that does not have write
permissions. The solution is to enable write privileges.
¦ The NetBackup-Java user service tries to write to a temporary file whose unique
name cannot be constructed. This condition is unlikely, but can result from
an exhaustion of system resources (from the filling of the name space).
Recommended Action: Retrieve the specific details from the user service log
files.
Enable detailed debug logging as explained in the following topic:
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

NetBackup status code: 509
Message: Can not execute program.
Explanation: The NetBackup-Java authentication or user service reported an
error that relates to the creation (or demise) of a child job process. The
NetBackup-Java service programs create separate jobs to accomplish specific
tasks, as follows. The NetBackup-Java authentication service creates the
NetBackup-Java user service. When it is created and connected to, the
NetBackup-Java user service creates all other child processes on behalf of requests
from the NetBackup-Java interface.
The cause of status code 509 can be found in the appropriate log file, either for
bpjava-msvc, bpjava-susvc, or bpjava-usvc.
The cause can be categorized as one of the following:
¦ A job (started by either the NetBackup-Java authentication service or user
service) no longer exists and did not report its result status.
¦ The NetBackup-Java service cannot monitor a job (started by either the
NetBackup-Java authentication service or user service). The reason it cannot
monitor is probably due to a lack of system resources (insufficient memory).
¦ The maximum number of non-transient activity monitor jobs (>100) have
already been started.
Recommended Action: Do the following, as appropriate:
¦ If the problem persists, restart the NetBackup-Java interface and try again.
¦ If the problem still persists, enable detailed debug logging as explained in the
following topic:
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Restart the NetBackup-Java interface and examine the logs.
The error is probably the result of a system resource issue. When detailed debug
logging is enabled, you can retrieve the details from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 510
Message: File already exists: file_name
Explanation: The NetBackup-Java user service try to create a file that already
exists.
RecommendedAction: Remove the file, which can be identified in the user service
log files.
See “Troubleshooting error messages in the NetBackup Administration Console
for UNIX” in the Troubleshooting Guide.

Hope this was helpful.

Thanks,
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 *