Symantec NetBackup Robotic status code 226 to status code 230

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 226 to status code 230 which may be received while using the Symantec NetBackup tool.

Robotic status code 226
Message: Requested slot contains the wrong tape
Explanation: The media in the requested slot is different from the media that is
expected in that slot. The volume configuration is not consistent with the physical
contents of the robotic library that is associated with the slot associated with the
requested volume.
Recommended Action: The volume configuration or media placement in the
robotic library needs to be adjusted using one of the media management interfaces.
Determine whether the barcode changed or the media changed since the last time
the EMM database was reconciled for the affected slot. If only the barcode has
changed but not the media, issue an update barcode request for each affected
volume. If the media has been changed, use a media management interface to run
robot inventory update, which updates theEMMdatabase with the media location.

Robotic status code 228
Message: Requested slot does not exist in robot
Explanation: The slot that is associated with a request is not valid for the 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.
¦ Issue a robot inventory Contents report to determine the valid slot range for
the robot. Check the volume configuration to ensure that only valid slots are
referenced in volume records, paying particular attention to the starting and
ending slot numbers. Update the volume configuration as needed, or request
only valid slot ranges for robotic operations.

Robotic status code 229
Message: Requested operation is not supported by the robot
Explanation: A robotic operation was sent to a robotic component that did not
support that operation. Or the options that were requested for the operation were
not supported. There may be an incompatibility between components or versions
of the product.
¦ 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 binaries and user interfaces are at a compatible
version level.

Robotic status code 230
Message: System error occurred during robot operation
Explanation: A robotic operation encountered a system error. This status code
is used for generic system call failures within robotic daemons/processes.
¦ Check for other error messages in the command or interface output to indicate
which system call failed. 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 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: display the Control
Panel, double-click System, and on the Performance tab, set Virtual Memory
to a higher value.
¦ Verify that all product binaries are properly installed.
¦ Verify that no unexpected Media Manager processes are running by executing
vmps. Some processes should remain running, but some processes that do not
go away could indicate a problem, such as a hung system call.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Robotic status code 221 to status code 225

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 221 to status code 225 which may be received while using the Symantec NetBackup tool.

Robotic status code 221
Message: Media access port already contains media
Explanation: A robotic eject media operation returned a status indicating that
the media access port contains one or more cartridges. The operator or
administrator may not have removed media from the media access port as part
of the latest (or a previous) eject operation.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Media Manager status codes” on page 337.
¦ Coordinate inject/eject operations between all operators and administrators.
Ensure that the media access port is empty of media before an eject operation.

Robotic status code 222
Message: Robotic arm has no addressable holder
Explanation: A holder is gone from an element of the robot and cannot be used.
¦ 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.
¦ Investigate the state of the physical hardware and correct the holder status
for storage, drive, and transport elements as needed. Then, resubmit the
request.

Robotic status code 223
Message: Robot busy, cannot perform operation
Explanation: The robot is busy performing another operation, using resources
that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing current
external-based requests (including robot inventory and inject/eject media) before
starting new requests. Check vendor or operating system administrative interfaces
and logs to see if robotic resources are busy.

Robotic status code 224
Message: Control daemon connect or protocol error
Explanation: A protocol error occurred between robotic and other components.
¦ 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.
¦ Investigate the system log messages that are related to the specific error
leading to the media mount failure. Verify that all Media Manager binaries are
at a compatible version level.
¦ Verify that robotic interfaces to vendor and operating system software have
compatible versions.

Robotic status code 225
Message: Robot hardware or communication error
Explanation: Ahardware or communications error occurred between robotic and
other components.
¦ 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.
¦ Investigate the system log messages that are related to the error leading to
the media mount failure.
¦ Verify that all Media Manager binaries are at a compatible version level. Verify
that robotic interfaces to vendor and operating system hardware and software
have compatible versions.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Robotic status code 216 to status code 220

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 216 to status code 220 which may be received while using the Symantec NetBackup tool.

Robotic status code 216
Message: Door is open on cabinet
Explanation: The robotic library door was open.
RecommendedAction: Close the door of the robotic library and reissue the robotic
request. See if the door latch mechanism works by comparing what happens with
robot test utility commands when the door is open versus closed.

Robotic status code 217
Message: Requested slot already has cartridge
Explanation: The requested slot was already held or was associated with a
cartridge.
RecommendedAction: Ensure that the inject/eject request does not target a slot
that already contains media. Check for media in drives to ensure that the media’s
home slot location is not targeted for use with media to be injected.

Robotic status code 218
Message: Cannot move from media access port to slot
Explanation: A robotic inject media operation returned a status indicating that
an inject failure occurred.
¦ See whether the robotic library has a media access port (use the robot test
utility to validate). Investigate whether the administrator or operator has
canceled the inject 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.

Robotic status code 219
Message: Cannot move from slot to media access port
Explanation: A robotic eject media operation returned a status indicating that
an eject failure occurred.
¦ See whether the robotic library has a media access port (use the robot test
utility to validate). Investigate whether the administrator or operator has
canceled the eject 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.

Robotic status code 220
Message: Media access port does not contain media
Explanation: A robotic inject media operation returned a status indicating that
the media access port does not contain any cartridges/media. The operator or
administrator may not have placed media into the media access port for inject.
¦ 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.
¦ Coordinate inject/eject operations between all operators and administrators.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Robotic status code 211 to status code 215

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 211 to status code 215 which may be received while using the Symantec NetBackup tool.

Robotic status code 211
Message: Process killed by signal
Explanation: An unexpected signal or event canceled the robotic 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.
¦ Check vendor or operating system administrative interfaces and logs to see if
robotic commands are being canceled.

Robotic status code 212
Message: Process killed by parent
Explanation: A robotic operation was canceled because of one of the following:
it did not return a status before a designated time period elapsed, or
communications or hardware errors led to the need to reinitialize the device.
¦ Stop any robot test utilities, since they have the lock on the robotic device
when they are active, and can block other requests.
¦ Check to see whether the robotic device still functions.
¦ Check whether excessive hardware or communication problems have delayed
the completion of a robotic command.
¦ Use a robot test utility to send commands to the device to see whether it is
responsive. Execute vmps to verify that no unexpected Media Manager processes
are running. Some processes should remain running, but some processes that
do not go away can indicate a problem, such as a hung system call.

Robotic status code 213
Message: Drive does not exist in robot
Explanation: A targeted drive was not found in the robotic library. The drive
configuration may be incorrect.
¦ 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 list of drives using a method that involves a robotic library query,
such as a query available from the robot test utility. Compare the list of drives
against the device configuration. Ensure that ltid was stopped and restarted
after changes were last made to the device configuration. ltid is the Media
Manager device daemon on UNIX and Linux or the NetBackup Device Manager
service on Windows.

Robotic status code 214
Message: Robot number does not exist
Explanation: A targeted robotic library was not found in the active device
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.
¦ Ensure that ltid was stopped and restarted after changes were last made to
the device configuration. (ltid is the Media Manager device daemon on UNIX
and Linux or the NetBackup Device Manager service on Windows.) On
commands to robotic libraries, specify only robotic libraries that are actively
part of the device configuration.

Robotic status code 215
Message: Requested tape in other or non-configured drive
Explanation: The targeted media was found in a drive differing from the targeted
drive.
Requested media can be temporarily unavailable, which is normal. Also, media
can remain unavailable until administrator or operator action is taken.
¦ If the media is needed immediately, examine command output (if available),
debug logs, and system logs for messages relating to the targeted media.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Check for conflicts between multiple applications using media in the robotic
library. Check integrity of the drive and drive paths, so that media is not
routinely left in other drives.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Robotic status code 206 to status code 210

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 206 to status code 210 which may be received while using the Symantec NetBackup tool.

Robotic status code 206
Message: Robotic dismount failure
Explanation: The robot could not dismount media.
¦ 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.
¦ Investigate the system log messages that are related to the specific error
leading to the media dismount failure.

Robotic status code 207
Message: Invalid command code
Explanation: A robotic operation was requested with improper options, when it
was not supported, or a robotic operation encountered an incompatible device
interface. There may be an incompatibility between components or versions of
the product.
¦ 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 binaries and user interfaces are at a compatible
version level.

Robotic status code 208
Message: Requested slot is empty
Explanation: No media was found in a specified slot. The volume configuration
may not be consistent with the physical contents of the robotic library that is
associated with the volume.
Recommended Action: Install or realign the container/holder for the media if it
is misplaced or misaligned. Place media right-side-up in the slot if the media is
upside-down. Check to see if the requested slot is reserved to the robotic library
for internal use. Physically correct issues within the robotic library, or use a media
management interface to correct the volume configuration.

Robotic status code 209
Message: Unable to open drive
Explanation: The drive could not be opened. The drive configuration may be
incorrect and the drive may be logically DOWN. Also, the drive may never have
become ready after media was placed in the drive.
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 improperly configured cleaning media or interference with the drive
cleaning operation. Check for bad media that may have led to the drive not
becoming ready after media was placed within it.
¦ To avoid configuring incorrect device paths and device names, which is a
common cause of drive open problems, use the Device Configuration Wizard
(on supported device discovery platforms) so that device paths and device
names can be automatically configured. Investigate the system log messages
that are related to the specific error leading to the open failure.

Robotic status code 210
Message: Unable to SCSI unload drive
Explanation: The drive could not be unloaded. The drive configuration may be
incorrect and the drive may be logically DOWN. Also, the drive may never have
become ready after media was placed in the drive.
¦ 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 improperly configured cleaning media or interference with the drive
cleaning operation. Check for bad media that may prevent unloading the drive.
To avoid configuring incorrect device paths and device names, which is a
commoncause of drive unload problems, use the Device Configuration Wizard
(on supported device discovery platforms) so that device paths and device
names can be automatically configured. Investigate the system log messages
that are related to the specific error leading to the unload failure.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Robotic status code 203 to status code 205

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 203 to status code 205 which may be received while using the Symantec NetBackup tool.

Robotic status code 203
Message: Timeout waiting for robotic command
Explanation: A robotic operation timed out: it did not return with a status before
a designated time period elapsed.
¦ Stop any robot test utilities, since they have the lock on the robotic device
when they are active, and can block other requests.
¦ Check whether excessive hardware retries have delayed the completion of a
robotic command.
¦ Check to see whether the robotic device still functions. Use a robot test utility
to send commands to the device to see whether it is responsive. Execute vmps
to verify that no unexpected Media Manager processes are running. Some
processes should remain running, but some processes that do not go away can
indicate a more serious problem, such as a hung system call.

Robotic status code 204
Message: Unable to initialize robot
Explanation: The robot could not be initialized. This generic status is used for
many conditions.
¦ 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.
¦ Investigate the system log messages that are related to the specific error
leading to the robot initialization failure.

Robotic status code 205
Message: Robotic mount failure
Explanation: The robot could not mount media.
¦ 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.
¦ Investigate the system log messages that are related to the specific error
leading to the media mount failure.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Robotic status code 200 to status code 202

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. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 200 to status code 202 which may be received while using the Symantec NetBackup tool.

Robotic status code 200
Message: STATUS_SUCCESS
Explanation: A robotic operation was successfully completed.
Recommended Action: None.

Robotic status code 201
Message: Unable to open robotic path
The robotic library device could not be opened. The specific case could be one of
the following:
¦ The robot device, path, or library name in the device configuration may not
be valid.
¦ The configured robotic device may not exist.
¦ The robotic device may be incorrect, such as a UNIX and Linux device file that
is not of a character special file format.
¦ The robotic daemon/process lock file could not be opened or a lock obtained.
¦ The open operation on the device or through the API interface (such as NDMP)
failed.
¦ Stop any robot test utilities that may be running, since they have the lock on
the robotic device when they are active.
¦ Check the configuration of the robot against the recommended configuration
as indicated in the documentation for robot configuration.
¦ Check the health of the robotic device by using a robot test utility, then close
the test utility when finished.
¦ Check for the existence and permissions of the lock file itself and the lock file
directory, which is /usr/openv/volmgr/misc/vmd.lock (UNIX and Linux) or
install_path\Volmgr\misc\vmd.lock (Windows). Create the directory/folder
and adjust the permissions as needed so that the robotic daemon/process can
use the lock file. Stop and restart ltid (the device daemon on UNIX and Linux
or the NetBackup Device Manager service on Windows).

Robotic status code 202
Message: Unable to sense robotic device
An element of the robotic library device could not be sensed. The cause could be
any of the following:
¦ The SCSI commands mode sense, mode select, or read element status (of slot,
drive, transport, i/e element) may have failed.
¦ A network API-controlled library inventory request may have failed.
¦ The robotic daemon/process could not initialize a robotic database file.
¦ Check the configuration of the robot against the recommended configuration
as indicated in the documentation for robot configuration.
¦ Check the health of the robotic device by using a robot test utility, then close
the test utility when finished.
¦ Check for the existence and permissions of the temporary robotic database
and the temporary database directory/folder, which is
/usr/openv/volmgr/misc/robotic_db (UNIX and Linux) or
install_path\Volmgr\misc\robotic_db (Windows). Create the
directory/folder and adjust the permissions as needed so that the robotic
daemon/process can create it or use it. Stop and restart ltid (the device daemon
on UNIX and Linux or the NetBackup Device Manager service on Windows).

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device management status code 81 to status code 84

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. These status codes appear in exit status and command output for the ltid,
tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs
that call those commands, such as media and device management user interfaces
and the vmoprcmd command also presented these codes.

Below are some of the NetBackup Device management status code 81 to status code 84 which may be received while using the Symantec NetBackup tool.

Device management status code 81
Message: Retry later
Explanation: An attempt was made to use resources controlled by EMM. These
resources were not available.
Recommended Action: Retry the command at a later time.

Device management status code 82
Message: No drive available
Explanation: An attempt to use a drive was made but that drive was not available.
¦ Verify that the drive is not DOWN on the intended media server.
¦ Verify that the media server where the drive is found is ACTIVE.
¦ Retry the command with a different drive.

Device management status code 83
Message: Media does not exist in database
Explanation: The requested media ID was not found in the EMM database.
¦ Verify that the requested media ID was entered correctly.
¦ Retry with a different media ID.

Device management status code 84
Message: No Error on operation, sideband data only
Explanation: This is only an informational message.
Recommended Action: No action is required by the user.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device management status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device management status code 76 to status code 80

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. These status codes appear in exit status and command output for the ltid,
tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs
that call those commands, such as media and device management user interfaces
and the vmoprcmd command also presented these codes.

Below are some of the NetBackup Device management status code 76 to status code 80 which may be received while using the Symantec NetBackup tool.

Device management status code 76
Message: Robot/LTI protocol error
Explanation: Communication between ltid and the robotic daemons caused a
protocol 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.
¦ Verify that ltid, bptm, and the robotic daemons are at a compatible NetBackup
level.

Device management status code 77
Message: VxSS access denied
Explanation: A user tried to run tpclean without adequate permissions.
¦ Verify that the user is logged on with permissions adequate for this operation.
¦ Verify that the VxSS settings are correct, under Host Properties in the
NetBackup Administration Console.
See the NetBackup Security and Encryption Guide.

Device management status code 78
Message: Unable to connect to the EMM server
Explanation: An attempt to retrieve or update information in EMM failed.
¦ Verify that the correct EMM server name is listed in the NetBackup
configuration.
¦ Verify that the media server that is encountering this error is listed in the
NetBackup configuration on the EMM server.
¦ Verify that EMM is running 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.

Device management status code 79
Message: Can not retrieve Job ID from Job Manager
Explanation: The tpreq, tpclean, or tpunmount command encountered an error
while trying to get a job ID from the NetBackup Job Manager.
¦ 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 NetBackup Job Manager is running on the master server.

Device management status code 80
Message: Job Manager returned error: see activity monitor
Explanation: The tpunmountcommandencountered an error while communicating
with the NetBackup Job Manager. The details of this issue may be found in the
Activity Monitor entry for this job.
¦ 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 NetBackup Job Manager is running on the master server.
¦ Verify that the arguments provided to the tpunmount command are correct.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device management status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup Device management status code 71 to status code 75

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. These status codes appear in exit status and command output for the ltid,
tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs
that call those commands, such as media and device management user interfaces
and the vmoprcmd command also presented these codes.

Below are some of the NetBackup Device management status code 71 to status code 75 which may be received while using the Symantec NetBackup tool.

Device management status code 71
Message: Request terminated because media is a cleaning tape
Explanation: A mount request has been canceled because the media that was
found in the drive is a cleaning tape.
Recommended Action: Check to make sure that the Media Manager’s EMM
database is up-to-date. If there are cleaning media in the library, assign appropriate
cleaning media types to them in the Media Manager EMM database.

Device management status code 72
Message: EMM library call failed
Explanation: A request that was made to read/write data to EMM failed.
¦ 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 pbx_exchange is running.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and accepting new connections.

Device management status code 73
Message: Stopping device daemon with tapes assigned
Explanation: An operator requested that ltid shutdown but tapes are still in use.
RecommendedAction: None. This message is advisory and no action is required.

Device management status code 74
Message: Robot operation failed
Explanation: A tape mount via bptm resulted in a failed robotic 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.
¦ Verify that the robotic hardware is functional.

Device management status code 75
Message: LTI system error
Explanation: A system error occurred.
¦ 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.
¦ Atpclean operation was attempted and Windows networking was not properly
configured.
¦ A malloc system call failed when trying to stop ltid.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device management status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 
1 2 3 4 25