Symantec NetBackup Media Manager status code 182 to status code 187

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 182 to status code 187 which may be received while using the Symantec NetBackup tool.

Media Manager status code 182
Message: device test state file does not exist
Explanation: The state file does not exist. The reason may be because no tests
have been run yet.
RecommendedAction: If the state file is lost, any previous test runs are also lost.
The recommended action is to start again.

Media Manager status code 185
Message: the robotic library is full and may still have media in its map
Explanation: During a robot inventory update, the user attempted to use the
empty_map option. The MAP contained more media than the library had space
for. In this case, the inventory update was successful, the empty_map part was
only partially successful. Those media still in the MAP are not changed or added
in the EMM database.
Recommended Action: No action is necessary on the user’s part except to be
aware that not all of the media was removed from the MAP and placed into the
library.

Media Manager status code 186
Message: invalid container id
Explanation: ANetBackup Vault container ID was used with an invalid character.
¦ 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.
¦ Retry the operation with a container ID that does not contain invalid characters.

Media Manager status code 187
Message: VxSS authentication failed
Explanation: The parties on either end of a socket connection cannot mutually
authenticate each other.
¦ Ensure that the Symantec Product Authentication Service is installed and
configured.
For complete installation instructions, see the NetBackup Security and
Encryption Guide.
¦ Check that both parties have a valid certificate by examining the listed expiry
date from a bpnbat -WhoAmI. For example:
bpnbat -WhoAmI
Name: JDOG
Domain: MYCOMPANY
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
Expiry Date: Sep 19 12:51:55 2009 GMT
Authentication method: Microsoft Windows
Operation completed successfully.
¦ Shows an expiry date of September 19th, 2009. After 12:51:55 GMT this
credential is no longer valid and a new credential is required.
¦ If you are running from the NetBackup Administration console, close and
reopen the console. The console automatically obtains a credential for the
currently logged in identity, if possible. By default these certificates are valid
for 24 hours. To set a longer default time, consult the following:
See the NetBackup Security and Encryption Guide.
¦ Ensure that the certificates for both sides either use the same broker, are
children of the same root broker, or have trusts established between them.
More information is available on broker hierarchies and how to establish trust
relationships between brokers.
See the NetBackup Security and Encryption Guide.
¦ Ensure that connectivity is possible between the physical systems in question.
If general sockets cannot connect between the machines (such as ping and
telnet), network issues unrelated to NetBackup may be the cause of this
problem.
¦ Ensure that the system has sufficient swap space and the following directories
are not full:
¦ /home/username
¦ /user/openv/netbackup/logs
¦ /tmp

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.

 

Leave a Reply

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