Symantec NetBackup Media Manager status code 131 to status code 135

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

Media Manager status code 131
Message: requested drive is not registered for host
Explanation: A request was made to reserve a shared drive with theEMMserver.
The requesting host did not register the drive, although that host had registered
other drives.
This abnormal condition can occur in the following situation: two different hosts
with the same name registered different drive lists with the EMM server and one
of those hosts requested a drive reservation. (The same host name occurs when
SSO_HOST_NAME entries in the vm.conf file override the local host name.)
Recommended Action: Use unique (non-duplicate) strings for host names and
SSO_HOST_NAME configuration file entries.

Media Manager status code 132
Message: requested drive is not currently registered
Explanation: A request was made to reserve or release a shared drive with the
EMM server. The requesting host or any other host has not registered the drive.
Recommended Action: This condition is abnormal. It can occur in the following
situation: the EMM server was stopped and restarted. This situation is
automatically handled, because the requesting host re-registers its drives with
the EMM server when this error is encountered.

Media Manager status code 133
Message: requested drive is not reserved by host
Explanation: A request was made to release a shared drive with the EMM server.
The requesting host did not reserve the drive, although it was reserved for another
host.
This condition is abnormal. It can occur if a network problem or a suspended
process exists. The following are possible scenarios:
¦ Host A reserves a shared drive.
¦ Host A becomes unavailable for some time, unable to communicate with other
hosts.
¦ Host B determines that the host having the reservation (Host A) is no longer
available. Host B then makes a request to the EMM/DA denoting Host A as
unavailable.
¦ Some other host (such as Host A or Host C) reserves the drive.
¦ The host that originally owned the drive reservation tries to release the drive.
Recommended Action: Correct the network or the process problem that led to
the communications problem. Ensure that unique non-duplicate strings are used
for host names and for SSO_HOST_NAME configuration file entries.

Media Manager status code 134
Message: requested drive is not currently reserved
Explanation: A request was made to the EMM/DA to release a shared drive, but
none of the hosts reserved the drive.
This condition is abnormal. It can occur if there a network problem or a suspended
process exists. The following are possible scenarios:
¦ Host A reserves a shared drive.
¦ Host A becomes unavailable for some time, unable to communicate with other
hosts.
¦ Host B determines that the host having the reservation (Host A) is no longer
available. Host B then makes a request to the EMM/DA denoting Host A as
unavailable.
¦ The host that originally owned the drive reservation tries to release the drive.
Recommended Action: Correct the network or the process problem that led to
the communications problem. Ensure that unique non-duplicate strings are used
for host names and for SSO_HOST_NAME configuration file entries.

Media Manager status code 135
Message: requested host is not currently registered
Explanation: A request was made to the EMM/DA to reserve or release a shared
drive or designate a host as unavailable. The host (that reserved or released the
drive or that was designated as unavailable) was not registered with the EMM/DA.
This condition is abnormal and can occur in the following situations.
¦ The EMM server was stopped and restarted. This situation is automatically
handled, because the requesting host re-registers its drives with the EMM
server when this error is encountered.
¦ A host was unregistered with the EMM server, and another host declared the
host to be unavailable.
Recommended Action: If the host was declared unavailable, determine whether
it should be available. Correct the underlying network problems or restart ltid
(the device daemon on UNIX and Linux or NetBackup Device Manager service on
Windows).

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 *