Symantec NetBackup Device management status code 76 to status code 80

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. These status codes appear in exit status and command output for the ltid,
tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs
that call those commands, such as media and device management user interfaces
and the vmoprcmd command also presented these codes.

Below are some of the NetBackup Device management status code 76 to status code 80 which may be received while using the Symantec NetBackup tool.

Device management status code 76
Message: Robot/LTI protocol error
Explanation: Communication between ltid and the robotic daemons caused a
protocol error.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that ltid, bptm, and the robotic daemons are at a compatible NetBackup
level.

Device management status code 77
Message: VxSS access denied
Explanation: A user tried to run tpclean without adequate permissions.
¦ Verify that the user is logged on with permissions adequate for this operation.
¦ Verify that the VxSS settings are correct, under Host Properties in the
NetBackup Administration Console.
See the NetBackup Security and Encryption Guide.

Device management status code 78
Message: Unable to connect to the EMM server
Explanation: An attempt to retrieve or update information in EMM failed.
¦ Verify that the correct EMM server name is listed in the NetBackup
configuration.
¦ Verify that the media server that is encountering this error is listed in the
NetBackup configuration on the EMM server.
¦ Verify that EMM is running on the EMM server.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device management status code 79
Message: Can not retrieve Job ID from Job Manager
Explanation: The tpreq, tpclean, or tpunmount command encountered an error
while trying to get a job ID from the NetBackup Job Manager.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the NetBackup Job Manager is running on the master server.

Device management status code 80
Message: Job Manager returned error: see activity monitor
Explanation: The tpunmountcommandencountered an error while communicating
with the NetBackup Job Manager. The details of this issue may be found in the
Activity Monitor entry for this job.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the NetBackup Job Manager is running on the master server.
¦ Verify that the arguments provided to the tpunmount command are correct.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device management status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device configuration status code 91 to status code 96

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 91 to status code 96 which may be received while using the Symantec NetBackup tool.

Device configuration status code 91
Message: The drive serial number already exists in the device database.
Explanation: An attempt was made to add a drive with a duplicate serial number.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the added drive has a unique serial number.

Device configuration status code 92
Message: VxSS access denied
Explanation: A user attempts an operation without adequate permissions
¦ Verify that the user has the correct permissions to perform this operation.
¦ Verify that the authentication and authorization security settings are correct,
under Host Properties in the NetBackup Administration Console.
See the NetBackup Security and Encryption Guide for information on how to
use the Symantec Product Authentication and Authorization Service.

Device configuration status code 93
Message: Database Server is down
Explanation: Arequest was made to theEMMServer, but the underlying database
server does not respond.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ This error can occur if a cold catalog backup is in progress. Retry the request
after this operation has completed.

Device configuration status code 95
Message: The requested operation is not valid for the specified Disk Type
Explanation: The storage device you configured is not a disk storage device.
Recommended Action: Select an appropriate storage device.

Device configuration status code 96
Message: The specified Disk Array Host is not configured in NetBackup
Explanation: You must first add this disk array host to the NetBackup host
configuration before this operation can be performed. To view hosts, see nbemmcmd
-listhosts in the NetBackup Commands Reference Guide.
¦ If you try to update an existing host’s credentials, this host no longer exists
in NetBackup. It must be added again by using the tpconfig or the nbemmcmd
command.
¦ The name you entered for the disk array host does not match any of the
computer aliases in the NetBackup computer configuration. Use the nbemmcmd
command to add the fully qualified array host name (or the name entered) to
the computer alias list for your disk array.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Media Manager status code 188 to status code 190

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, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 188 to status code 190 which may be received while using the Symantec NetBackup tool.

Media Manager status code 188
Message: VxSS Access Denied
Explanation: The user identity that is used to attempt an operation does not have
the permissions needed to perform the action.
¦ If you use the default groups, make certain that the user attempts to perform
an operation appropriate for that group. For example, a member of
NBU_Operators is unable to modify policy information, a permission reserved
for administrator roles.
¦ Ensure that the system has sufficient swap space and the following directories
are not full:
¦ /home/username
¦ /user/openv/netbackup/logs
¦ /tmp
¦ If you use your own defined groups and permissions, first determine the object
with which the operation is associated. Then add the permissions relative to
the action. For example, a user is required to up and down drives but does not
currently have permission to do so. Verify that the user belongs to the correct
authorization group.
If necessary, verify that the group has Up and Down permissions on the Drive
object within the Group Permission tab. If necessary, you can increase the
verbosity level of NetBackup to locate what object and what permissions are
required for the failing request. The pertinent lines in the debug logs look
similar to the following:
17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.
Name: JMIZZLE
Expiry: Sep 24 21:45:32 2003 GMT
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
AuthType: 1
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:
Function: VssAzAuthorize. Object
NBU_RES_Drives
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:
Function: VssAzAuthorize. Permissions Up
17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:
Function: VssAzAuthorize. 20 Permission denied.
In the example, the user JMIZZLE attempts to perform an operation that
requires the Up permission on the Drives object. To diagnose the problem,
examine the group(s) to which the user belongs to ensure that the appropriate
group includes the Up permission. (Up is a member of the Operate permission
set for Drives.)

Media Manager status code 189
Message: failed to initialize a connection to the Enterprise Media Manager
Explanation: A request to initialize a connection with the EMM server failed or
was already initialized.
¦ Verify that pbx_exchange and nbemm are running.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.

Media Manager status code 190
Message: the request sent to the Device Allocator has failed
Explanation: A request to reserve or release a drive with the DA (EMM server)
failed.
¦ Verify that pbx_exchange and nbemm are running.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.
¦ For a DA reserve drive request, verify that another host had not already
reserved the drive.
¦ For a DA release drive request, verify the following: that the drive is DA
reserved by the host requesting the DA release and has not already been
released.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Media Manager status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 117 to status code 120

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

NetBackup status code: 117
Message: VxSS access denied
Explanation: The user identity that was used to attempt an operation does not
have the permissions that are needed to perform the action.
Recommended Action: Do the following, as appropriate:
¦ If you use the default groups, make certain that the user attempts to perform
an operation appropriate for that group. For example, a member of
NBU_Operators is unable to modify policy information, which is a permission
reserved for administrator roles.
¦ Ensure that the system has sufficient swap space and the following directories
are not full:
¦ /home/username
¦ /user/openv/netbackup/logs
¦ /tmp

NetBackup status code: 118
Message: VxSS authorization failed
Explanation: NetBackup was unable to complete the authorization check against
the authorization service.
Recommended Action: Do the following, as appropriate:
¦ Ensure that the Symantec Product Authorization Service or daemon is running.
Refer to the NetBackup Security and Encryption Guide for more information
on authentication and authorization daemons.
¦ Ensure that you are in communication with the correct master server. Within
the bp.conf files on the local server, verify that the entry
AUTHORIZATION_SERVICES specifies the proper host name (fully qualified) of
the authorization service. For example, AUTHORIZATION_SERVICE = machine2.mycompany.com 0 specifies that the server contacts machine2 to
perform authorization checks. Also ensure that this entry matches that of the
master server.
¦ Ensure that the system has sufficient swap space and the following directories
are not full:
¦ /home/userName
¦ /user/openv/netbackup/logs
¦ /tmp

NetBackup status code: 120
Message: cannot find configuration database record for requested NB database
backup
Explanation: The program that backs up the NetBackup internal catalogs did not
find the attributes that indicate which media IDs to use or paths to back up. This
error should not occur under normal circumstances.
Recommended Action: Do the following, as appropriate:
¦ Check the NetBackup Problems report for additional information about the
error.
¦ For detailed troubleshooting information, create admin and bpdbm debug log
directories and retry the operation. Check the resulting debug logs.
¦ Contact customer support and send the appropriate problem and debug log
sections that detail the error.

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.