Symantec NetBackup Media Manager status code 21 to status code 25


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

Media Manager status code 21
Message: cannot obtain daemon lockfile
Explanation: vmd (NetBackup Volume Manager daemon on UNIX and Linux;
NetBackup Volume Manager service on Windows) or operator request daemon or
service cannot obtain an internal software lock.
Recommended Action: Check for the existence and permissions of the lock file
itself and the lock file directory: /usr/openv/volmgr/misc/vmd.lock (UNIX and
Linux) or install_path\Volmgr\misc\vmd.lock (Windows). Create the directory
or folder and adjust the permissions as needed so that vmd can obtain the lock:
/usr/openv/volmgr/misc/vmd.lock (UNIX and Linux) or
install_path\Volmgr\misc\vmd.lock (Windows).

Media Manager status code 22
Message: pool type change is not allowed for <CatalogBackup> pool
Explanation: An attempt was made to remove the catalog backup attribute of the
default CatalogBackup pool.
Recommended Action: Verify that the appropriate pool name was used in this

Media Manager status code 23
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.

Media Manager status code 25
Message: failed making the database directory
Explanation: nbpushdata cannot create a working directory during upgrade.
RecommendedAction: Determine why the directory /usr/openv/tmp (UNIX and
Linux) or install_path\tmp (Windows) cannot be created. Check to see what
account nbpushdata was run under. Compare it against the security properties
of the database folder.

Hope this was helpful.

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 *