Symantec NetBackup status code 606 to status code 610

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

NetBackup status code: 606
Message: no robot on which the media can be read
Explanation: bpsynth returns this error when it cannot find a robot on which to
read a particular media ID that contains backup images to be synthesized. The
media ID is included in the message that bpsynth logs. This error should not occur.
Recommended Action: Contact customer support and provide appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 607
Message: no images were found to synthesize
Explanation: The database query to obtain the images to synthesize for the given
policy did not return any images.
Recommended Action: Ensure that a synthetic full backup has one full image
(real or synthetic) and one or more subsequent incremental images (differential
or cumulative) to synthesize. For a cumulative synthetic backup, there must be
two or more incremental (differential or cumulative) images to synthesize. Adjust
your schedules so the appropriate backup jobs complete successfully before the
synthetic job is run. The scheduler does not retry a synthetic backup job that fails
with this error code.

NetBackup status code: 608
Message: storage unit query failed
Explanation: The database query to obtain all storage units failed.
Recommended Action: Verify that the bpdbm process is running and that no
errors were logged to the NetBackup error log. Restart the bpdbm process (on UNIX
and Linux), or the NetBackup Database Manager Service (on Windows) and retry
the synthetic backup job. If the problem persists, contact customer support and
send the appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 609
Message: reader failed
Explanation: The bptm or the bpdm reader process was terminated with an error.
Recommended Action: Refer to the NetBackup error log for the errors that the
bpsynth and bptm or bpdm reader logged. The error message should contain the
actual error that the bptm or the bpdm reader reports. Refer to the NetBackup
Troubleshooting Guide for information on the error that the bptm or the bpdm
reader reports. The media may not be present or is defective or the drive that was
used for reading the media is defective. If the problem persists, contact customer
support and send appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 610
Message: end point terminated with an error
Explanation: An error indication was received on the connection to the bptm or
the bpdm process.
Recommended Action: Review the errors in the NetBackup error log that the
following processes logged: bpsynth and bptm or bpdm. Refer to the debug logs for
these processes for more information. The connection may have broken due to
the following: an error condition that the bptm or the bpdm process detects or
network problems between the master and the media server. Check the network
connectivity between the master and the media server. Retry the job and if the
problem persists, contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.

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.

 

Symantec NetBackup status code 602 to status code 605

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

NetBackup status code: 602
Message: cannot set non blocking mode on the listen socket
Explanation: The bpsynth process is unable to set the non-blocking socket option
on the listen socket.
RecommendedAction: Check the OS error that was reported in the error message,
which was logged in the NetBackup error log. The error helps to diagnose the
problem. Ensure that the bpsynth binary matches the installed NetBackup version.
If the condition persists, contact customer support and send appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 603
Message: cannot register handler for accepting new connections
Explanation: The bpsynth process cannot register the listen socket with the ACE
reactor.
Recommended Action: Ensure that the bpsynth binary matches the installed
NetBackup version. Retry the synthetic backup job. If the problem persists, contact
customer support and send appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 604
Message: no target storage unit specified for the new job
Explanation: A mismatch occurred between storage units that are known to
NetBackup and the specified target storage unit.
Recommended Action: Retry the synthetic backup job. If the problem persists,
contact customer support and provide appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 605
Message: received error notification for the job
Explanation: This error code is no longer used.
Recommended Action: Submit a problem report along with appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” 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.

 

Symantec NetBackup status code 526 to status code 601

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

NetBackup status code: 526
Message: bpjava authentication service connection failed
Explanation: Cannot connect to the bpjava authentication service via NetBackup
PBX at port 1556 (default).
Recommended Action: Do the following, as appropriate:
¦ Check that the PBX service or daemon has been started on the server and that
NetBackup services are running.
¦ If the target server is running a release of NetBackup earlier than 7.0.1, the
Java GUI attempts a further connection via the VNETD port 13724. No action
is required.
¦ Check if the Java GUI properties (java/nbj.conf) have been set up to connect
to a PBX port other than 1556.

NetBackup status code: 527
Message: bpjava user service connection if connection to pbx on port 1556 fails
Explanation: Unable to connect to the bpjava user service using NetBackup PBX
at port 1556 (default).
Recommended Action: Do the following, as appropriate:
¦ Check that the PBX service or daemon has been started on the server and that
NetBackup services are running.
¦ If the target server is running a release of NetBackup earlier than 7.0.1, the
Java GUI attempts a further connection via the VNETD port 13724. No action
is required.
¦ Check if the Java GUI properties (java/nbj.conf) have been modified to
attempt a PBX port other than 1556.

NetBackup status code: 600
Message: an exception condition occurred
Explanation: The synthetic backup job encountered an exception condition.
Recommended Action: Contact customer support and send appropriate debug
logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 601
Message: unable to open listen socket
Explanation: The bpsynth process cannot open a socket to listen for incoming
connections from the bptm or the bpdm processes that were started for the
following: for reading backup images or for writing the synthetic image on the
media servers.
RecommendedAction: Check the OS error that was reported in the error message,
which bpsynth logged in the NetBackup error log. This error helps to diagnose
the problem. Ensure that the bpsynth binary matches the installed NetBackup
version. Retry the synthetic backup job. If the problem persists, contact customer
support and provide the appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” 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.

 

Symantec NetBackup status code 521 to status code 525

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

NetBackup status code: 521
Message: NB-Java Configuration file (file_name) does not exist.
Explanation: The configuration file for the NetBackup-Java interface was not
found.
RecommendedAction: Make sure that the configuration file the NetBackup-Java
interface exists and is properly formatted.

NetBackup status code: 522
Message: NB-Java Configuration file (file_name) is not readable due to the
following error: (message).
Explanation: The specified NetBackup-Java configuration file exists but is not
readable.
Recommended Action: Correct the file as specified in the message.

NetBackup status code: 523
Message: NB-Java application server protocol error.
Explanation: In some instances, this message concludes with
Check the log file for more details.
The NetBackup-Java interface received an incorrectly formatted protocol sequence
from its application server.
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.
Note: The error is probably the result of a system resource issue. When detailed
debug logging ID is enabled, the details can be retrieved from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 525
Message: Cannot connect to the NB-Java authentication service via VNETD on
(host) on port (vnetd_configured_port_number). Check the log file for more details.
Explanation: The NB-Java authentication service authenticates the user name
that is provided in the logon dialog box. Communication between the NetBackup
Administration Console and the authentication service is tried to host host on the
configured VNETD port number that error message specifies. The NetBackup
Administration Console log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
¦ On UNIX and Linux: Compare theVNETDentry in the /etc/services file with
the VNETD_PORT entry in /usr/openv/java/nbj.conf
On Windows: Compare the VNETD entry with the VNETD_PORT entry in the
install_path\java\setconf.bat file.
These entries must match.
¦ Ensure that no other application uses the port that is configured for VNETD.

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.

 

Symantec NetBackup status code 516 to status code 520

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

NetBackup status code: 516
Message: Could not recognize or initialize the requested locale –
(locale_NB-Java_was_started_in).
Explanation: This status concerns the UNIX or Linux locale configuration (or
Windows regional settings) defined on the host that was specified in the NB-Java
logon dialog box. At logon, the locale configuration is passed to the NB-Java
authentication service. Status 516 is generated if the locale is not recognized or
if the locale of the user service cannot be initialized.
The rules in the following files determine how a valid locale is recognized:
/usr/openv/msg/.conf on UNIX and Linux and install_path\msg\lc.conf on
Windows. When the locale is validated, initialization of the locale in the user
service’s environment is tried (by means of setlocale).
Recommended Action: On the specified host in the NB-Java logon dialog box,
check the configuration file to ensure that a mapping is available for the indicated
locale.
For information on locale configuration and mapping, refer to the NetBackup
Administrator’s Guide, Volume II.
If there is a mapping, try to set the mapped locale on the host that was specified
in the NB-Java logon dialog box. This system may not be configured properly.

NetBackup status code: 517
Message: Can not connect to the NB-Java user service via VNETD on host on port
configured_port_number. If successfully logged in beforehand, retry your last
operation. Check the log file for more details.
Explanation: After the NB-Java authentication service validates the user name
on the logon dialog box for access, all Administration console service requests
use an NB-Java user service. Communication between the Administration console
and user service is tried to host (host) on the specified port number in the error
message by using VNETD. (The NB-Java configuration option
NBJAVA_CONNECT_OPTION is set to 1.) The NetBackup Administration Console
log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
¦ On UNIX and Linux: Compare theVNETDentry in the /etc/services file with
the VNETD_PORT entry in /usr/openv/java/nbj.conf
On Windows: Compare the VNETD entry with the VNETD_PORT entry in the
install_path\java\setconf.bat file.
These entries must match.
¦ Ensure that no other application uses the port that is configured for VNETD.

NetBackup status code: 518
Message: No ports available in range (port_number) through (port_number) per
the NBJAVA_CLIENT_PORT_WINDOW configuration option.
Explanation: All the ports in the specified range are in use. Too many users
(concurrent) of the NetBackup-Java interface or too few configured ports can
cause this error.
Recommended Action: Do the following, as appropriate:
¦ Restart the NetBackup-Java interface and try again.
¦ If the problem persists, increase the range of ports by changing the
NBJAVA_CLIENT_PORT_WINDOW option in the /usr/openv/java/nbj.conf
file (UNIX and Linux) or the install_path\java\setconf.bat file (Windows).

NetBackup status code: 519
Message: Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value:
(option_value).
Explanation: The value for the NB-Java configuration option
NBJAVA_CLIENT_PORT_WINDOW is invalid.
Recommended Action: Correct the value in file /usr/openv/java/nbj.conf
(UNIX and Linux) or install_path\java\setconf.bat file (Windows).
NetBackup status code: 520
Message: Invalid value for NB-Java configuration option (option_name):
(option_value).
Explanation: The specified NetBackup-Java configuration option has an invalid
value.
Recommended Action: Correct the value in file /usr/openv/java/nbj.conf
(UNIX and Linux) or install_path\java\setconf.bat file (Windows).

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.

 

Symantec NetBackup status code 511 to status code 514

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

NetBackup status code: 511
Message: NB-Java application server interface error.
Explanation: In some instances, this message concludes with
Check the log file for more details.
This generic error for all non-socket IO/connection-broken related errors (status
code 507) can occur when data is processed from the NetBackup-Java
authentication or user services. The Java exception provides some additional
detail about the error.
This error usually results from system or network problems.
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, the details can be retrieved from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 512
Message: Internal error – a bad status packet was returned by NB-Java application
server that did not contain an exit status code.
Explanation: The NetBackup-Java authentication or user service returned a data
packet that indicated an error, but no status code or error message was contained
within it.
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, the details can be retrieved from the bpjava-msvc,
bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 513
Message: bpjava-msvc: the client is not compatible with this server version
(server_version).
Explanation: The NetBackup-Java application server (on the remote host you log
in to) is not the same version as the NetBackup-Java interface on your local host.
The two are therefore incompatible.
Recommended Action: Do the following, as appropriate:
¦ Log in to a different NetBackup remote host.
¦ Upgrade the NetBackup software on either of the following: the computer that
is specified in the logon dialog box or the local host where you started the
NetBackup Java interface.

NetBackup status code: 514
Message: NB-Java: bpjava-msvc is not compatible with this application version
(application_version). You may try logon to a different NetBackup host or exit the
application. The remote NetBackup host has to be configured with the same version
of NetBackup as the host you started the application on.
Explanation: In some instances, this message concludes with
Check the log file for more details.
The NetBackup-Java application server (on the remote host you log in to) is not
the same version as the NetBackup-Java interface on your local host. The two are
therefore incompatible.
Recommended Action: Do the following, as appropriate:
¦ Log in to a different NetBackup remote host.
¦ Upgrade the NetBackup software on either of the following: the specified
computer in the logon dialog box or the local host where you started the
NetBackup Java interface.

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.

 

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.

 

Symantec NetBackup status code 501 to status code 505

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

NetBackup status code: 501
Message: You are not authorized to use this application.
Explanation: The user is not authorized to use one of the NetBackup Java
Administration utilities on the host that is specified in the login dialog box.
Recommended Action: Check the auth.conf file on the host that is specified in
the NetBackup-Java login dialog box for the proper authorization. If the auth.conf
file does not exist, it must be created with the proper entry for this user name.
More details on the auth.conf file are available.
See NetBackup Administrator’s Guide, Volume I.

NetBackup status code: 502
Message: No authorization entry exists in the auth.conf file for user name
username. None of the NB-Java applications are available to you.
Explanation: The user name is not authorized to use any NetBackup-Java
applications on the host that is specified in the logon dialog box.
Recommended Action: Check the auth.conf file on the computer (host name)
specified in the NetBackup-Java logon dialog box for the proper authorization. If
the file does not exist, create it with the proper entry for this user name. More
details on the auth.conf file are available.
See NetBackup Administrator’s Guide, Volume I.

NetBackup status code: 503
Message: Invalid username.
Explanation: For UNIX and Linux host logon, the NetBackup Java application
server on the host where the logon is requested does not recognize the user name.
For Windows host logon, the NetBackup-Java authentication service on the host
where the logon is requested does not have sufficient privileges to grant the
request.
Recommended Action: Do the following, as appropriate:
¦ For UNIX and Linux hosts: the user name must be a valid user name in the
passwd file on the host that is specified in the logon dialog box.
¦ For Windows hosts: refer to the LogonUser function in the section titled
Client/Server Access Control Functions of the Windows Platform Software
Developer’s Kit to determine the required privileges.

NetBackup status code: 504
Message: Incorrect password.
Explanation: For logon to a UNIX or Linux host, the user name is recognized on
the host where the logon is requested, but the supplied password is incorrect.
For logon to a Windows host, the attempt to log in the user failed. The failure can
be due to an unrecognized user in the specified domain.
Recommended Action: Do the following, as appropriate:
¦ Enter the correct password.
¦ On Windows hosts: The exact error can be found in the bpjava-msvc log file.
For more details, refer to the LogonUser function in the section Client/Server
Access Control Functions of the Windows Platform Software Developer’s Kit.

NetBackup status code: 505
Message: Can not connect to the NB-Java authentication service on host on the
configured port – (port_number). Check the log file for more details.
Explanation: The initial connection from the NetBackup-Java interface to its
authentication service on (host) was on the configured_port_number that was
mentioned in the error message. Either the port is in use by another application
or the NetBackup-Java interface and its application server are not configured with
the same port. The default port is 13722. The NetBackupAdministrationConsole
log file should contain more detail about this error.
Recommended Action: Do the following, as appropriate:
¦ On UNIX and Linux, compare the bpjava-msvc entry in the /etc/services
file with the BPJAVA_PORT entry in the /usr/openv/java/nbj.conf file
On Windows, compare the bpjava-msvc entry in the
%systemroot%\system32\drivers\etc\services file with the
install_path\java\setconf.bat file (Windows). The entries must match.
¦ Ensure that no other application uses the port that is configured for the
NetBackup-Java interface.

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.

 

Symantec NetBackup status code 406 to status code 409

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

NetBackup status code: 406
Message: The computer specified is not a member of the server group specified
Explanation: A server that is not a member of the server group that owns the
media performed an operation on a media.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified media is correct.
¦ Verify the media ownership
¦ Verify that the server where the operation is performed is a member of the
owning server group. If not, try the operation from a server that is a member
of the server group.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which use unified logging.

NetBackup status code: 407
Message: Member’s NetBackup version not compatible with Server Group
Explanation: The attempt to add or update a server group failed. One of the server
group member’s NetBackup version is not valid for the specified server group
type.
Recommended Action: Do the following, as appropriate:
¦ Ensure that each member server has NetBackup 6.5 or later.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

NetBackup status code: 408
Message: Server Group is in use
Explanation: The attempt to delete a server group that failed because the server
group owns one or more media.
Recommended Action: Do the following, as appropriate:
¦ Ensure that the server group is not the owner of any media by running
bpmedialist -owner group_name from the master server.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

NetBackup status code: 409
Message: Member already exists in server group
Explanation: The attempt to add or update a server group failed because one of
the server group members is the same as the one being added.
Recommended Action: Do the following, as appropriate:
¦ Ensure that the server group member that you add does not already exist in
the group.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

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.

 

Symantec NetBackup status code 351 to status code 405

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

NetBackup status code: 351
Message: all configured vault steps failed
Explanation: This error occurs when multiple Vault steps are configured for a
session and all of them fail.
RecommendedAction: For duplication and catalog backup steps, use the Activity
Monitor to check the status of the respective jobs that Vault started. For Eject
step status, check the Detailed Status tab of the Job Details dialog box for the
Vault job.

NetBackup status code: 400
Message: Server Group Type is Invalid
Explanation: The creation of a server group fails because the server group type
is invalid.
Recommended Action: Do the following, as appropriate:
¦ Select a valid server group type: MediaSharing, Symantec OpsCenter, or
AltServerRestore.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 401
Message: Server Group Already Exists
Explanation: The attempt to create a server group failed. The server group already
exists.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified server group name is not in use.
¦ Create the server group by specifying a name that is not currently in use.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 402
Message: Server Group Already Exists with a different type
Explanation: The attempt to create a server group failed. The server group name
is already in use by a server group with a different group type.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified server group name is not in use.
¦ Try to create the server group by specifying a name that is not currently in
use.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 403
Message: Server Group Active State is not valid
Explanation: The attempt to create a server group failed. The server group state
was invalid.
Recommended Action: Do the following, as appropriate:
¦ Valid server group states are: ACTIVE and INACTIVE
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 404
Message: Server Group does not exist
Explanation: An operation was tried by using a server group that does not exist.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified media is correct.
¦ Verify the media ownership.
¦ Verify that the server group exists.
¦ Verify that the server where the operation is performed is a member of the
owning server group. If not, try the operation from a server that is a member
of the server group.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

NetBackup status code: 405
Message: Member’s server type not compatible with Server Group
Explanation: The attempt to add or update a server group failed. A member’s
server type was not valid for the specified server group type.
Recommended Action: Do the following, as appropriate:
¦ The Media Sharing server group can contain the following types of servers:
Master, Media, NDMP, and cluster.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

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.