Day: January 5, 2015

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

Media Manager status code 96Message: oprd returned abnormal statusExplanation: A request that oprd services (the operator request daemon or
process) returned an abnormal status.
¦ On Windows, do the following when you auto-configure devices or initiate the
NetBackup Device Manager service from a graphical or a command line
interface: ensure that the service is not disabled in the system services
configuration.
¦ 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.
¦ In general, any device management-related errors that occur on a particular
host accompany operator request daemon or process and remote device
management errors. Check for errors in the following: the debug and the system
or the application logs on the host where oprd was started or where it is
running. The host is often a targeted device host or scan host.
The kinds of failed requests that oprd services can include the following:
¦ Down, up, or reset drives
¦ Change drive comments
¦ Deny or resubmit mount requests
¦ Assign drives
¦ Start or stop ltid
¦ Obtain ltid status
¦ Display drive status
¦ Manage pending actions
¦ Set NDMP attributes
¦ Configure devices
¦ Clean drives
¦ Obtain host version and device configuration information
¦ Scan shared drives

Media Manager status code 97Message: rule does not exist in rule databaseExplanation: A request was made to change or delete a bar code rule, but the bar
code rule with the specified bar code tag cannot be found.
¦ 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.
¦ List the configured bar code rules in the EMM database. Adjust the bar code
tag that is specified on the change or the delete request or on the targeted
host. Then the bar code rule is found when the request is retried.

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

Media Manager status code 92Message: cannot delete assigned volumeExplanation: A delete request was made to a volume, and the volume is currently
assigned.
¦ 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.
¦ Assigned volumes cannot be deleted. If no worthwhile data is on the volume,
unassign the media by using the appropriate application interface (which is
bpexpdate for NetBackup). Then retry the delete volume request.

Media Manager status code 93Message: volume is already assignedExplanation: Arequest was made to assign a volume, and the volume was already
assigned.
¦ 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.
¦ Do not try to manually assign any volumes that are already assigned, because
it is not valid except for one condition: you can assign volumes for NetBackup
catalog backups if the volume is already assigned for NetBackup catalog
backups. Always use barcodes that are unique in the six least significant
characters, across all media in all robots. Or use media ID generation rules to
ensure that unique media IDs are generated in a robot inventory update.

Media Manager status code 94Message: volume is not in specified poolExplanation: A request was made to assign a volume from a specified volume
pool. The volume was in a different volume pool.
¦ 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.
¦ When you assign volumes manually, specify the volume pool that is associated
with the volume. Always use barcodes that are unique in the six least significant
characters, across all media in all robots. Or use media ID generation rules to
ensure that unique media IDs are generated in a robot inventory update.

Media Manager status code 95Message: media ID is not the specified media typeExplanation: A request was made to assign or add a volume of a specified media
type. The volume or physically similar volumes have a different media type.
¦ 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.
¦ When you use robot inventory update to make changes to the volume
configuration, do the following: ensure that all volumes of the same physical
cartridge type (for example, 3590J in TLH robots) map to a single media type
such as HCART. This check ensures that all media in the robotic library can
be mounted on drives with a compatible drive type.
¦ When you assign volumes manually, specify the media type that is associated
with the volume. Always use bar codes that are unique with respect to the six
least significant characters, across all media in all robots. Or use media ID
generation rules to ensure that unique media IDs are generated when you use
robot inventory update.

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

Media Manager status code 86Message: failed opening tmp output fileExplanation: The vm.conf file or temporary working file cannot be opened.Recommended Action: On UNIX and Linux, check for the existence and
permissions of the /usr/openv/volmgr/misc directory, /tmp directory, and
/usr/openv/volmgr/vm.conf file. On Windows: check for the existence and the
security properties of the install_path\Volmgr\vm.conf file.

Media Manager status code 87Message: failed redirecting tmp output fileExplanation: The system call dup2(3C) failed during an attempt to direct interface
output from a temporary file to the process’s standard output.Recommended Action: Investigate the operating system functionality that is
related to resource limits on the number of open files. Ensure that extraneous
signals do not interrupt processes.

Media Manager status code 88Message: failed initiating child processExplanation: Acommand cannot be ran. This error can occur due to the following:
the command permissions do not allow it to be ran or system resources such as
memory and swap space are insufficient.
¦ 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.
¦ Check the permissions on the vmcheckxxx, vmupdate, and oprd binaries, and
(on Windows only) the rdevmi installed binary.

Media Manager status code 89Message: another daemon already existsExplanation: vmd (the NetBackup Volume Manager daemon on UNIX and Linux
or NetBackup Volume Manager service on Windows) tries to initialize and found
that it was already running, according to the daemon or the service lock file.Recommended Action: Check to see if vmd is already running. Do not try to start
another vmd daemon or service until you first shut down the daemon or the service
that is running. Stop the vmd that is running with vmctrldbm -t. On Windows,
use the system Services interface. If the daemon or the service unexpectedly
terminated, remove the lock file. The lock file is
/usr/openv/volmgr/misc/vmd.lock (UNIX and Linux) or
install_path\Volmgr\misc\vmd.lock (Windows). Then restart vmd.

Media Manager status code 90Message: invalid volume poolExplanation: A request was made to add volumes, change the volume pool for a
volume, add a bar code rule, or change a bar code rule. However, the volume pool
name or number that is associated with the requested change is in conflict with
the requirements for volume pools.
These requirements are as follows:
¦ Volumes in scratch pools cannot be assigned until they are first moved to
another pool.
¦ Volume pool numbers cannot be negative.
¦ Volume pool names must consist of from 1 to 20 printable ASCII characters
with no embedded whitespace.
¦ The None volume pool is the only valid pool for the bar code rule entries that
specify cleaning a media type.
¦ 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.
¦ Ensure that the specified volume pool does not violate the requirements noted.
Use the vmpool command to display the pool information. Use the vmrule
command to display the bar code rule information. Add or change volume
pools and bar code rules as needed to rectify inconsistencies in cases where
the databases are inconsistent or corrupted.

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

Media Manager status code 81Message: robot type and volume group mismatchExplanation: A request was made to add volumes or change volume residences
in the volume configuration. The robot type and volume group that is associated
with the volume configuration changes are in conflict with the requirements for
volume groups. All volumes in a volume group are required to have the same
residence, which includes having the same robot type.Arequested operation may
have tried to associate the special No Volume Group name “—” with a robotic
residence.
¦ 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.
¦ Ensure that the specified robot residence and volume group are compatible
with other volumes in the volume configuration that are in the specified volume
group. Do not move volumes in the special No Volume Group name to a robotic
residence without moving them to a new or auto-generated volume group.
Choose a different volume group on the request, or let the volume group be
automatically selected. Volume group selection depends on the specific
interface being used.

Media Manager status code 82Message: robot host and volume group mismatchExplanation: A request was made to add volumes or change volume residences
in the volume configuration. The robot host and volume group that is associated
with the volume configuration changes are in conflict with the requirements for
volume groups. All volumes in a volume group are required to have the same
residence. This residence includes having the same robot host, where robot host
equivalence is defined as having the same case-sensitive robot host string.
¦ 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.
¦ Ensure that the specified robot residence and volume group are compatible
with other volumes in the volume configuration that are in the specified volume
group. Do not try to add volumes for a robot host by using a different form of
the robot host name. For example, acme is not the same as acme.symantec.com.
Use the same host name that is used for other volumes in the volume group.
If the robot host needs to be changed for volumes in a volume group, do the
following: use a single move volume group request (available only in certain
media management interfaces) to move the volume group to stand-alone
residence. Then move the volume group back to the robotic residence. Specify
the robot control host that you want to be associated with the new volume
group.

Media Manager status code 83Message: device management errorExplanation: One of the device management errors occurs during the execution
of vmphyinv.Recommended Action:
Examinecommandoutput, 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.

Media Manager status code 84Message: this machine is not the database hostExplanation: A request was made to initiate vmd on a host other than the local
host. vmd is the NetBackup Volume Manager daemon (UNIX and Linux) or
NetBackup Volume Manager service (Windows).
vmdport numbers other than the default or use of unsupported options can affect
the referenced host and port in the interfaces that start vmd.
¦ Initiate vmd on the local host only, by logging on to the host where vmd needs
to run Start vmd on that host. On UNIX and Linux, run
/usr/openv/volmgr/bin/vmd [-v].OnWindows, start the NetBackup Volume
Manager service in Services of the system Control Panel.
¦ If more information is needed to explain the problem, 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.
¦ Make sure port numbers are consistent.

Media Manager status code 85Message: volume daemon fork failedExplanation: A Media Manager daemon or service cannot create a child process
due to an error from the system. This error probably is intermittent, based on the
availability of resources on the system.
¦ Restart the service at a later time and investigate the system problems that
limit the number of processes.
¦ 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.

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

Media Manager status code 76Message: cannot get host nameExplanation: The system call gethostname(3C) failed during an attempt to obtain
the name of the local host.
¦ 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.
¦ Obtain the specific system call failure from the debug log, and investigate the
operating system functionality that is related to the failure. Run the hostname
system command to see if the command operates correctly.

Media Manager status code 78Message: barcode does not exist in databaseExplanation: A query volume by bar code request did not return a volume entry
having the specified bar code, or bar code and media type.
¦ Examine the daemon and reqlib debug logs for a more detailed message on the
error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Ensure that volumes are properly configured in the EMM database. Use
tpconfig -d to list the configured EMM server. Select the current server (the
one being administered) to be the same as the host, which is the correct EMM
server. Do the following so that the volume query can find a matching volume:
update the volume or the device configurations, modify volume properties, or
adjust search criteria as needed. For media in their correct slot locations, run
the Rescan or the update bar code request so the following occurs: the bar code
field in the volume configuration matches the actual bar code as interpreted
by the robotic library bar code reader.

Media Manager status code 79Message: specified robot is unknown to vmdExplanation: A request was made to query volumes by residence. No volumes
were found in the targeted volume configuration that matched the provided robot
number, robot type, and robot host.
¦ 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.
¦ Ensure that volumes are properly configured in the EMM database. Use
tpconfig -d to list the configured EMM server. Select the current server (the
one being administered) to be the same as the host which is the correct EMM
server. Perform the following so the volume residence query can find a
matching volume: update the volume or the device configurations, modify
volume properties, or adjust search criteria as needed.

Media Manager status code 80Message: cannot update database due to existing errors
vmphyinv is unable to update the EMM database because of the existing errors.
The errors can be as follows:
¦ A Media Manager volume record belongs to a different robot with the same
media ID as the media ID that the tape header read.
¦ The media type or media GUID or the volume pool of an assigned volume
record needs to be changed.
¦ A bar code conflict is detected and vmphyinv needs to change the bar code of
the existing volume record.Recommended Action: vmphyinv, in such a scenario, generates a list of errors.
Examine the output. You must resolve all these errors before you run the utility
again.

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

Media Manager status code 71Message: failed sending to vmdExplanation: Anattempt to write data to avmdsocket failed.vmdis the NetBackup
Volume Manager daemon (UNIX and Linux) or NetBackup Volume Manager service
(Windows).
¦ Examine command output (if available) and the daemon and reqlib debug logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Identify the system where vmd is running. The system usually is termed the
Media Manager host or EMM server and defaults to the local system in some
user interfaces (such as vmadm). Possible causes for the error are high network
load, missing operating system patches or service packs, or unexpected vmd
process failure.

Media Manager status code 72Message: failed receiving from vmdExplanation: An attempt to read data from a vmd socket failed. vmd is the
NetBackup Volume Manager daemon (UNIX and Linux) or NetBackup Volume
Manager service (Windows).
¦ Examine command output (if available) and the daemon and reqlib debug logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Identify the system where vmd is running. The system is usually termed the
Media Manager host or EMM server and defaults to the local system in some
user interfaces (such as vmadm). Possible causes for the error are high network
load, missing operating system patches or service packs, or unexpected vmd
process failure. Also, the socket read may have failed because the requested
operation did not complete within a specified time period. The robotic process
and vmd interactions can affect some requests to vmd; check the system log
for errors on the robotic control host.

Media Manager status code 73Message: invalid query typeExplanation: An invalid volume query request was attempted.
¦ 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 all Media Manager and user interface binaries are at a compatible
version level.

Media Manager status code 74Message: invalid number of cleaningsExplanation: Arequest was made to change the number of cleanings that remains
for one or more volumes in the volume configuration.Whenthe request was made,
the specified value was not within the acceptable range. The number of cleanings
value may also be invalid in the number of mounts or cleanings field of a bar code
rule.
¦ 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.
¦ Specify a number of cleanings value within the acceptable range of 0 to
2,147,483,647.

Media Manager status code 75Message: invalid change typeExplanation: An invalid volume change request was attempted.
¦ 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 all Media Manager and user interface binaries are at a compatible
version level.

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

Media Manager status code 67Message: unable to send exit statusExplanation: vmd cannot send the status of a requested operation to the requestor.
(vmd is the NetBackup Volume Manager daemon on UNIX and Linux and the
NetBackup Volume Manager service on Windows.)
¦ Examine the daemon debug log for a more detailed message on the system
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.
¦ Obtain the specific send or write system call failure from the debug log, and
investigate the operating system functionality that is related to the failure.
¦ Use the following steps to check whether the command or the application
interface that sends the request aborts prematurely: enable reqlib debug logs,
retry the operation, check the debug logs, and observe application interface
output.

Media Manager status code 68Message: too many volumes in volume groupExplanation: A request was made to add or change volumes in the volume
configuration but the volume number was at its allowable limit. The limit is based
on the number of volumes that is allowed in a particular type of robot.
¦ 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.
¦ Check to see if volumes are defined in theEMMdatabase. They may be defined
in the EMM database, which is associated with a slot number zero that may
not exist in the robot. Run a robot inventory. Show contents of robot report
and observe the starting slot number. If the starting slot number is one and a
volume is defined in the robot at slot zero, delete the volume entry. Or move
it to stand-alone so that the remaining available media slots can be used.

Media Manager status code 69Message: failed sending request to vmdExplanation: A request cannot be sent to vmd or to oprd, even though the initial
connection to the server process was successful. (vmd is the NetBackup Volume
Manager daemon on UNIX and Linux or NetBackup Volume Manager service on
Windows; oprd is the operator request daemon or process.)
¦ 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.
¦ Check to see whether the vmd or the oprd process continues to run once it
receives the connection from the requestor. Run netstat -a or an equivalent
socket diagnostic utility. Check the following to see if the server process is
hung up: the daemon debug log on the server-side system and the process
status of vmd or oprd.

Media Manager status code 70Message: cannot connect to vmd [on host host name]Explanation: A process times out while connecting to the following: vmd (the
NetBackup Volume Manager daemon on UNIX and Linux or NetBackup Volume
Manager service on Windows) or to oprd (the operator request daemon or process).
This problem can occur when a connection is attempted and the server process
is not running. It also can occur if the network or server is heavily loaded and has
slow response time.
¦ On the host where vmd is the recipient of the connection, verify that the daemon
or the service is running. (The host is the Media Manager host, the Device
Host, or the EMM server.) If the daemon or the service is not running, start it.
On Windows, vmd is the NetBackup Volume Manager service.
¦ If vmd is already 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.
¦ Verify that the correct host names are defined in the configuration.
¦ Check the services file. On UNIX and Linux, verify that the /etc/services file
(and NIS services if NIS is used) has entries for the vmd service. (Note that the
vmd service always starts oprd.) On Windows, verify that the
%systemroot%\system32\drivers\etc\services file has the correct entry
for vmd. Also verify that the vmd port number in the services file agrees with
the port number configuration. The port number is noted in the man page for
vmd(1M).
¦ Verify that all operating system patches or service packs are installed.
¦ Ensure that the Media Manager configuration is not tuned so that the load on
vmd exceeds its ability to service requests. Look for entries in the vm.conf file
that increase the load. Consider placing the EMM database on a higher
performance server and file system if performance is an issue. To reduce the
number of volumes in the volume configuration, use inventory filtering for
the robot types that support it
¦ Check utilities such as ipcs -a to ensure that shared memory functions
properly. The oprd process may not respond because it cannot attach to shared
memory.

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

Media Manager status code 61Message: robot number and robot host mismatchExplanation: A request is made to add or change volumes in the volume
configuration, or to issue a robot inventory update request. A specified robot host
differs from the robot host for other volumes in the same robot (defined as those
volumes having the same robot number). All volumes in the EMM database that
have a given robot number (for instance, 0) must have the same robot host name.
¦ 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.
¦ Specify the robot host in the device configuration to be the same case-sensitive
host name on all hosts where the robot is configured. Re-issue the request. As
an alternative, use move-by-volume group to move all volumes logically from
a robotic volume group to stand-alone and then back into the robot. Specify
the robot host as the host name that is used in the robot configuration. Then
re-issue the request.

Media Manager status code 62Message: failed redirecting input to pipeExplanation: A system pipe cannot be created.Recommended Action: Check the interface output for the specific system error
and investigate the operating system functionality that is related to the failure.

Media Manager status code 63Message: child process killed by signalExplanation: An unexpected signal terminated a robot inventory update process.
¦ Examine interface output and debug logs for a more detailed message 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.

Media Manager status code 64Message: no child process to wait forExplanation: Amedia management interface attempted to wait for a child process
to complete, but unexpectedly found that no such child process existed.
¦ Examine interface output and debug logs for a more detailed message 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.
¦ Retry the operation (or try to use a different media management interface)
and examine the logs.

Media Manager status code 65Message: volume group does not existExplanation: During a request process, a volume group cannot be found within
the existing volume entries in the EMM database.
¦ Examine interface output and debug logs for a more detailed message 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.
¦ Check for data integrity or consistency problems in theEMMdatabase by using
a media management interface. Delete or move volume entries so that the
volume group issues are corrected.

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

Media Manager status code 56Message: invalid database version headerExplanation: nbpushdata cannot find a recognizable EMM database version in
the EMM database, and cannot initialize with the database currently in place.
¦ 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.
¦ From catalog backups or another source if available, restore an earlier version
of the database file: /usr/openv/volmgr/database/volDB (UNIX and Linux)
or install_path\Volmgr\database\volDB (Windows). Then restart vmd.

Media Manager status code 57Message: error auto-generating volume groupExplanation: A request was made to add or change volumes in the volume
configuration by using automatic generation of the volume group name.Aunique
volume group name cannot be generated because the available combinations were
used up.Recommended Action: Consolidate volumes into volume groups within the
targeted robot number so that a new volume group can be generated automatically.
Or provide a specific volume group name.

Media Manager status code 58Message: daemon cannot obtain socketExplanation: vmd cannot bind to its socket. (vmd is the NetBackup Volume Manager
daemon on UNIX and Linux and the NetBackup Volume Manager service on
Windows.) When vmd attempts to bind to its configured port number, system call
fails. The call fails usually because another process having acquired the port
before the vmd daemon or service started.
¦ Examine the daemon debug log for a more detailed message on the system
error.
¦ If another process has the port, use other system commands to determine the
process. Based on the result, either change the port number in your services
file or map, or terminate the process that has acquired the port.
¦ UNIX and Linux only: Another possible cause for this error is the use of the
kill command to terminate vmd. To stop vmd, the recommended method is to
use the Terminate Media Manager Volume Daemon option on the Special
actions menu in vmadm. (Or use the equivalent command line request,
vmctrldbm -t). The use of the kill command to stop this process can leave
it unable to bind to its assigned port the next time it restarts. When the socket
problem occurs, the daemon debug log contains lines similar to the following:
unable to obtain bound socket, Address already in use (125)

Media Manager status code 59Message: daemon failed accepting connectionExplanation: vmd cannot accept a new connection due to a system call failure.
(vmd is the NetBackup Volume Manager daemon on UNIX and Linux and the
NetBackup Volume Manager service on Windows.)
¦ Examine the daemon debug log for a more detailed message on the system
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.
¦ Obtain the specific system call failure from the debug log, and investigate the
operating system functionality that is related to the failure.

Media Manager status code 60Message: cannot perform operation on this hostExplanation: A requested operation is not functional on a particular host.
¦ 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.
¦ Robot inventory update must be initiated only on the host where the robotic
control and drives are configured.

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

Media Manager status code 51Message: cannot auto-eject this robot typeExplanation: A request to change volume residence with media eject was sent to
vmd, but the volume’s robot type does not support automated media eject. (vmd
is the NetBackup Volume Manager daemon on UNIX and Linux or NetBackup
Volume Manager service on Windows.)
¦ 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.
¦ Ensure that change volume residence requests are not sent to vmd on a system
that runs an older, incompatible software version level. (The change volume
residence requests are requests with eject for the robot type that is involved
with a newer release version level.)

Media Manager status code 52Message: cannot auto-inject this robot typeExplanation: A request to change volume residence with media inject was sent
to vmd, but the volume’s robot type does not support automated media inject. (vmd
is the NetBackup Volume Manager daemon on UNIX and Linux or NetBackup
Volume Manager service on Windows.)
¦ 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.
¦ Ensure that change volume residence requests are not sent to vmd on a system
that runs an older, incompatible software version level. (The change volume
residence requests are requests with inject for the robot type that is involved
with a newer release version level.)

Media Manager status code 53Message: invalid volume move modeExplanation: A robotic-related request was made specifying a media movement
option that not all affected software components supports.
¦ 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.
¦ Ensure that the robotic request is sent to a system that runs a release version
of software that supports the particular request.

Media Manager status code 54Message: robot number and robot type mismatchExplanation: A request was made to add or change volumes in the volume
configuration. The robot number to be associated with a volume is already in use.
It is associated with another volume in a robot with the same number but of
another robot type.
¦ 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.
¦ Ensure that robot numbers are unique for each physical robot in the EMM
database. Delete and re-add a robot. Use a unique robot number if duplicate
robot numbers are in use. Use a media management interface to identify robot
numbers currently in use for all volumes in the volume configuration. If you
use a command line interface, specify the correct robot type for the robot
number that is associated with the request.

Media Manager status code 55Message: robot number and volume group mismatchExplanation: A request was made to add or change volumes in the volume
configuration. The robot number and volume group that is associated with the
volume configuration changes are in conflict with the requirements for volume
groups. All volumes in a volume group are required to have the same residence,
which includes having the same robot 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.
¦ Ensure that the specified robot number and volume group are compatible. If
volumes in the volume group have a given robot number, then volumes with
a different robot number cannot be added to that volume group. Volumes
cannot be moved directly from one robotic volume group to another robotic
volume group. The intermediate steps (some volume entries are changed, some
are not) would cause a conflict with robot numbers. Choose a different volume
group on the request, or let the volume group be selected automatically. Volume
group selection depends on the specific interface being used.