Symantec NetBackup Media Manager status code 46 to status code 50

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

Media Manager status code 46
Message: unexpected data from robotic software daemon
Explanation: Message communications (handshaking) between a process and a
robotic software daemon or process failed.
¦ Verify that the correct version of software is running on all servers.
¦ 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 and examine the logs.
¦ Ensure that no embedded whitespaces exist in the fields that do not allow
embedded whitespace.
¦ Check the system log on the robot control host for errors that the robotic
software logged.

Media Manager status code 47
Message: no entries changed
Explanation: Arequested operation was completed, but no changes to the volume
configuration or Media Manager configuration file were made. The administrator
may have terminated an operation instead of continuing with proposed changes.
Or the configuration file may already include the configuration entry that was to
be added.
¦ No action is needed if the administrator aborted the change operation.
¦ 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.

Media Manager status code 48
Message: no entries deleted
Explanation: A delete volume(s) operation completed. No changes were made to
the volume configuration.
¦ No action is needed, unless the volumes that were requested to be deleted were
not in fact deleted.
¦ 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.

Media Manager status code 49
Message: no entries inserted
Explanation: An insert volume(s) operation completed. No volumes were added
to the volume configuration.
¦ No action is needed unless the volumes that were requested to be inserted
were not inserted.
¦ 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.

Media Manager status code 50
Message: invalid change-entry request
Explanation: An invalid request to change volume information was sent to vmd
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.
¦ Check the usage statement for expected usage and compare with the parameters
being sent to start the new process.

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 Media Manager status code 41 to status code 45

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

Media Manager status code 41
Message: invalid media ID for naming mode
Explanation: Arequest to add multiple volumes with a first media ID and a media
ID style failed. It fails because the media ID specified was not compatible with the
media ID naming style provided.
Recommended Action: Provide a first media ID that fits the selected style. For
example, the media ID style is two characters and four digits. Then the least
significant four characters in the first media ID must be digits in the range 0 to
9. Alternatively, select a media ID style that fits the specified first media ID.

Media Manager status code 42
Message: cannot connect to robotic software daemon
Explanation: A connection to a robotic software daemon or process cannot be
established. This error can occur when a process tries to connect to the robotic
process that is not running. It can also occur if the network or server is heavily
loaded and has slow response time.
¦ 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 robotic process: look at the robot type and at the robot host on
the robotic request or the robot host field of the volume being operated on.
¦ Verify that the robotic process to use for robotic control is available
See “Media and device management components” in the Troubleshooting
Guide.
If necessary, start the robotic process.
¦ Ensure that only one configured robot control host exists for each TL8, TLD,
and TLH robot. Also ensure that all volumes in the volume configuration have
a robot host that matches the configured robot control host.
¦ Change the volumes or reconfigure the robot in the device configuration as
needed.
¦ Check the system log on the robot control host to see if the robotic process
processes requests when connections to it are attempted.

Media Manager status code 43
Message: failed sending to robotic software daemon
Explanation: An attempt to write data to a robotic software daemon or process
socket failed.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Identify the robotic process: look at the robot type and at the robot host on
the robotic request or the robot host field of the volume being operated on.
Verify that the robotic process to use for robotic control is available and that
it handles requests.
¦ Identify the robot control host by checking the device configuration. Only one
configured robot control host should exist for each TL8, TLD, and TLH robot.
All volumes in the volume configuration should have a robot host that matches
the configured robot control host.
¦ Check the system log on the robot control host to see if the robotic process
processes requests when communications with it are attempted.

Media Manager status code 44
Message: failed receiving from robotic software daemon
Explanation: An attempt to read data from a robotic software daemon or process
socket failed.
¦ 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 targeted robotic process: look at the robot type and at the robot
host on the robotic request or the robot host field of the volume being operated
on. Verify that the robotic process to use for robotic control is available and
that it handles requests.
See “Media and device management components” in the Troubleshooting Guide.
¦ Identify the robot control host by checking the device configuration. Only one
configured robot control host should exist for each TL8, TLD, and TLH robot.
All volumes in the volume configuration should have a robot host that matches
the configured robot control host.
¦ Check the system log on the robot control host to see if the robotic process
handles requests when communications with it are attempted.
See “Resolving network communication problems with UNIX clients” in the
Troubleshooting Guide.
See “Resolving network communication problems with PC clients” in the
Troubleshooting Guide.

Media Manager status code 45
Message: failed changing terminal characteristics
Explanation: When an attempt was made to change the mode for terminal input
between cooked and raw, a system call failed.
Recommended Action: Examine the user interface output for the system error
that is associated with the failed system call. Then troubleshoot according to
operating system vendor recommendations.

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 Media Manager status code 36 to status code 40

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

Media Manager status code 36
Message: barcode not unique in database
Explanation: A specified bar code in an added or a changed volume entry in the
EMM database duplicated a volume bar code already in the database. All volumes
in the EMM database must have a unique bar code.
¦ 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.
¦ Query or sort volume records by bar code to identify the volume entry with
the duplicate bar code.

Media Manager status code 37
Message: robotic volume position is already in use
Explanation: A robotic coordinate in an added or a changed volume entry in the
EMMdatabase duplicated a volume robotic coordinate in the database. (The robotic
coordinate includes the slot number or the slot number and platter side.) All
volumes in the EMM database must have unique robotic coordinates.
¦ 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.
¦ Query or sort volume records by slot number to identify the volume entry with
the duplicate robotic coordinate.
¦ Change (update or move volume) or delete the existing volume entry if it does
not reflect the following: the correct robotic coordinate corresponding to the
volume’s storage position in the robotic library. If a volume is currently in a
drive, the EMM database should still reflect the volume’s home slot.

Media Manager status code 39
Message: network protocol error
Explanation: An attempt to read data from a socket failed.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the protocol error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the server being connected to is operational.

Media Manager status code 40
Message: unexpected data received
Explanation: Message communications (handshaking) was not correct.
¦ Verify that the correct version of software is running on all servers.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the protocol error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the operation and examine the logs.
¦ Ensure that no embedded whitespaces exist in the fields that do not allow
embedded whitespace.

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 Media Manager status code 32 to status code 35

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

Media Manager status code 32
Message: database write record operation failed
Explanation: nbpushdata encountered an error while writing an EMM database
record.
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 34
Message: media ID not unique in database
Explanation: A volume entry being added to or changed in the EMM database
had a media ID specified. The specified ID was a duplicate of the media ID for
another volume already in the EMM database. All volumes in the EMM database
must have a unique media ID.
¦ 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.
¦ When you add volumes to theEMMdatabase, specify a media ID that is unique.
¦ If you run vmphyinv, there may be two or more media in the tape library with
the same media ID.

Media Manager status code 35
Message: volume does not exist in database
Explanation: A requested operation encountered a case where a volume query
did not return a volume entry that matched the search criteria.
¦ 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 configured properly on theEMMserver that matches
the EMM server configured for the robot or set of stand-alone drives. Use
tpconfig -d to list the configured EMM server.
¦ Do the following so the volume query can find a matching volume: update the
volume or the device configurations, specify the correct EMM server, modify
volume properties, or adjust search criteria.
¦ If you run vmphyinv, none of the media satisfy the search criterion. As such,
vmphyinv cannot inventory the tape library.

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 Media Manager status code 26 to status code 28

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

Media Manager status code 26
Message: database open operation failed
Explanation: A database file cannot be opened.
Recommended Action:
Check for the existence and permissions of the following files in the
/usr/openv/var/global directory (UNIX and Linux) or
install_path\NetBackup\var\global folder (Windows):
¦ external_robotics.txt
¦ external_densities.txt
¦ external_drivetypes.txt
¦ external_mediatypes.txt

Media Manager status code 27
Message: database read record operation failed
Explanation: nbpushdata encountered a read error while reading anEMMdatabase
record.
¦ 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.
¦ The EMM database may be corrupted. Restore an older EMM database from a
saved version or from catalog backups.

Media Manager status code 28
Message: database read operation read too few bytes
Explanation: nbpushdata encountered a record that was smaller than expected
while reading an EMM database record.
¦ 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.
¦ The EMM database may be corrupted. Restore an older EMM database from a
saved version or from catalog backups.

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 Media Manager status code 21 to status code 25

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 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
operation.

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.

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 Media Manager status code 16 to status code 20

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

Media Manager status code 16
Message: invalid robot coord1
Explanation: A requested operation encountered a missing or out-of-range robot
slot number. Or a move by volume group residence was attempted when the volume
did not originate from a valid robotic library slot.
¦ 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 slot number (robot coordinate 1) where required and ensure that the
number is within the allowable range for the given robot type.

Media Manager status code 18
Message: cannot allocate requested memory
Explanation: Allocation of system memory failed. This error occurs when
insufficient system memory is available. The system may have too little physical
and virtual memory to handle the current load of processes.
RecommendedAction: Free up memory by terminating any unneeded processes
that consume a lot of memory. Add more swap space or physical memory.

Media Manager status code 19
Message: invalid database host
Explanation: Arequested operation encountered a missing or an invalid database
host. Or a request was sent to a host that is running a version of the product that
does not support the requested operation.
¦ 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 validEMMdatabase host on which the following is running: a version
of nbemm (the NetBackup Enterprise Media Manager) or an operator request
daemon or process that supports the requested operation.

Media Manager status code 20
Message: protocol error
Explanation: Message communications (handshaking) was not correct.
¦ 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 and examine the logs. Ensure that no whitespaces are
embedded in the fields that do not allow embedded whitespace.

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 Media Manager status code 11 to status code 15

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

Media Manager status code 11
Message: invalid description
Explanation: The volume description exceeds 25 ASCII characters in length, or
contains unprintable characters.
RecommendedAction: When you add or change a volume record or bar code rule
record, ensure that the description field contains the following: no more than 25
ASCII characters that can be printed.

Media Manager status code 12
Message: invalid robot type
Explanation: A requested operation encountered a case where a specified robot
type or a volume’s robot type is different. It differs from the type of robot that is
required to perform the operation in the current 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.
¦ Specify a robot type that supports the volume’s media type.
¦ Check the EMM database and ensure that the specified robot type agrees with
the type for all volumes having the specified robot number.
¦ If a robot type is required for the requested operation, ensure that a robot type
has been specified.

Media Manager status code 13
Message: invalid robot number
Explanation: The robot number was not specified or was not within the allowable
range.
¦ Specify a robot number in the range of 0 to 32767.
¦ If you run vmphyinv, the global device database may not be updated, or the
specified robot number may not be configured.

Media Manager status code 14
Message: invalid robot host
A requested operation encountered a case where the following is true of the robot
control host:
¦ It is not specified.
¦ It is not valid for the given robot type.
¦ It is not in an acceptable format.
¦ It exceeds the allowed length of a robot control 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.
¦ If possible, attempt the requested operation again with another user interface
that supports the type of request.

Media Manager status code 15
Message: invalid volgroup
A requested operation encountered a case where the volume group:
¦ Is not specified
¦ Is not in an acceptable format
¦ Exceeds the allowed length of a volume group 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 a volume group where one is required to ensure that it contains the
following:
¦ 25 ASCII characters or less
¦ No white space
¦ No unprintable characters

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 Media Manager status code 06 to status code 10

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

Media Manager status code 6
Message: invalid protocol request
Explanation: An invalid request was sent to a robotic process or operator request
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.
¦ Identify the target components (for example, vmd, nbemm, and robotic processes
on local or remote hosts). Then verify that all media and device management
binaries are at compatible version level.

Media Manager status code 7
Message: daemon terminated
Explanation: The process is inactive or terminates (or has terminated) from the
following: an event or signal or as a direct result of a request from an authorized
user or process.
Recommended Action: If the targeted product component is needed but has
terminated, restart the daemons or services on the targeted host.

Media Manager status code 8
Message: invalid media ID
Explanation: Whena process performed a media-related operation, it encountered
an empty or an incorrectly formatted media identifier. Or a media ID that was
passed to it cannot be operated on as requested.
¦ 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 media ID, where requested, is not blank.
¦ Ensure that the specified media IDs contain valid characters only: alphanumeric
characters, the period (.), the plus sign (+), and the underscore (_). A hyphen
(-) is also a valid character when not the first character in the media ID.
¦ If media are specified to be ejected from a library, ensure the following: they
exist in the EMM database and are associated with the correct robot number.
¦ Ensure that the media ID is from 1 to 6 characters in length.
¦ Ensure that a valid media and seed were specified.
¦ If the operation is an inventory request for an ACS robot, use the robtest
utility to verify the following: the ACS interface returns cleaning media IDs
both in the query volume list and in the query cleaning volume list.

Media Manager status code 9
Message: invalid media type
Explanation: A process that performed a media-related operation encountered
an unknown, missing, or incompatible media type specifier.
¦ If you run a robot inventory on a robot of type ACS, TLH, or TLM, ensure the
following: the installed version of NetBackup supports and recognizes the
vendor media type that the robot control software returns.
¦ If using a command line interface directly, verify that a valid media type has
been passed, according to vmadd(1m) command line documentation.
¦ Ensure that an operation valid only for cleaning media has not been requested
on a media ID that does not correspond to cleaning tape.
¦ Ensure that the media type in all bar code rules is a valid media type or the
ordinal zero (0), to represent the default media type.

Media Manager status code 10
Message: invalid barcode
Explanation: Whena process performed a media-related operation, it encountered
an unknown, missing, or incompatible bar code.
¦ 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 bar code, where requested, is not blank.
¦ Ensure that the specified bar codes contain valid characters only: alphanumeric
characters, and the period (.), plus sign (+), and underscore (_). A hyphen (-) is
also a valid character when not the first character in the media ID.
¦ Ensure that the number of characters in the bar code does not exceed the
maximum that is allowed for the robot type.
¦ Ensure that the bar code tag in all bar code rules is a subset of a valid, supported
bar code format.

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 Media Manager status code 01 to status code 05

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

 

Media Manager status code 1
Message: request completed
Explanation: Arequested operation was completed. The operation may have been
one of several related operations for a particular task.
Recommended Action: None.

Media Manager status code 2
Message: system error
Explanation: A system call failed. This status code is used for a generic system
call failure that does not have its own status code.
¦ Check for other error messages in the command or the interface output to
determine which system call failed.
¦ Check the system application log for error and warning messages.
¦ Verify that the system is not running out of virtual memory. If virtual memory
is the problem, shut down unused applications or increase the amount of
virtual memory.
To increase virtual memory on Windows, do the following in the order
presented:
¦ Display the Control Panel.
¦ Double-click System.
¦ On the Performance tab, set Virtual Memory to a higher value.
¦ Verify that all product binaries are properly installed.
¦ Verify that no unexpected media and device management processes are in
operation by running vmps. Some processes are expected to continue running.
Others that continue to run can indicate a more serious problem, such as a
hung system call.

Media Manager status code 3
Message: user id was not superuser
Explanation: A user or process that did not have root privileges (on UNIX and
Linux) or administrator privileges (on Windows) started the process.
RecommendedAction: If appropriate, give the user or the process administrator
privileges (on Windows) or root privileges (on UNIX and Linux) and retry the
operation.

Media Manager status code 4
Message: invalid command usage
Explanation: A media and device management command was run with improper
options, or an incompatibility between components or versions of the product
exists.
¦ 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 usage statement for expected usage and compare with the parameters
being sent to start the new process.
¦ Verify that all media and device management binaries are at a compatible
version level.

Media Manager status code 5
Message: daemon resources are busy
Explanation: A requested operation cannot be processed because resources were
busy.
Recommended Action: Check the status of any resources that the requested
operation uses. On a robotic inventory request, verify that the inventory operation
completes within a reasonable time.

 

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.

 
1 2 3 4 5