Symantec NetBackup Robotic status code 261 to status code 262

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

Robotic status code 261
Message: EMM error
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.
■ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively processing commands.

Robotic status code 262
Message: Configuration has changed, robot daemons and ltid need restarting
Explanation: A device configuration change has been made that is not reflected
in the robotic daemon’s run-time cache of the data.
■ 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.
■ Restart ltid and the robotics on this system or on the robot control host
system.

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 256 to status code 260

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

Robotic status code 256
Message: Robot busy, multiple eject operation in progress
Explanation: The robot is unavailable because a multiple eject is in progress,
using resources that are needed for the requested operation.
RecommendedAction: Wait until the robot is done performing the multiple eject
operation before starting new requests. Check the vendor or operating system
administrative interfaces and logs to see if robotic resources are busy.

Robotic status code 257
Message: Robot busy, multiple inject operation in progress
Explanation: The robot is unavailable because a multiple inject is in progress,
using resources that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing the multiple
inject operation before starting new requests. check the vendor or operating
system administrative interfaces and logs to see if robotic resources are busy.

Robotic status code 258
Message: Cleaning/unknown media in drive
Explanation: A request to mount a tape failed because cleaning media was found
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.
¦ Retry the operation once the drive cleaning has completed.

Robotic status code 259
Message: Not authorized by VxSS
Explanation: A request was made to the robot daemons by an unauthorized user.
¦ Verify that the user has the necessary permissions to perform this operation.
¦ Verify that the authentication and authorization security settings are correct,
under HostProperties in the NetBackupAdministrationConsole. Information
is available on using the Symantec Product Authentication and Authorization
Service.
See the NetBackup Security and Encryption Guide.

Robotic status code 260
Message: Robot busy, robot diagnostics in progress
Explanation: The requested robot is running a robot diagnostic.
¦ 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 when the robot diagnostic cycle is complete.

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 246 to status code 255

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

Robotic status code 246
Message: Failed to find an available slot to inject to
Explanation: An attempt to inject a volume into a full library failed. This error
should only occur when the library is full. Full means that all storage elements
either contain media or have been assigned media that are currently mounted in
a drive. Note that some libraries that support multiple media types restrict which
type of media can be assigned to each storage element. In this case, this error
might occur even if some of the storage elements in a library were not full. Since
the empty storage elements may not match the media type for the media to inject,
the library is full for this media type.
Recommended Action: Clear the media access port, then re-inventory the robot
by doing a volume configuration update.

Robotic status code 249
Message: Volume is in home slot
Explanation: Volume is currently in its home slot and ready for eject.
Recommended Action: None.

Robotic status code 250
Message: Media access port is available
Explanation: Media access port is available for inject or eject.
Recommended Action: Begin inject or eject operation.

Robotic status code 251
Message: Media access port is unavailable
Explanation: Media access port is not ready for inject or eject.
Recommended Action: Manually remove any media remaining in the robot’s
media access port. If this status persists, check robotic console for errors.

Robotic status code 252
Message: Media access port is in inject mode
Explanation: Media access port is ready to inject and is not available for eject.
Recommended Action: Complete inject operation.

Robotic status code 253
Message: Media access port is in eject mode
Explanation: Media access port is ready to eject and is not available for inject.
Recommended Action: Complete eject operation.

Robotic status code 254
Message: Robot busy, inventory operation in progress
Explanation: The robot is not available because it is performing an inventory,
using resources that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing the inventory
before starting new requests. Check the vendor or operating system administrative
interfaces and logs to see if robotic resources are busy.

Robotic status code 255
Message: Robot busy, inject operation in progress
Explanation: The robot is not available because it is involved in an inject operation,
using resources that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing the inject
operation before starting new requests. check the vendor or operating system
administrative interfaces and logs to see if robotic resources are busy.

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 242 to status code 245

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

Robotic status code 242
Message: Robot media access port does not exist
Explanation: the requested media access port was not valid for use with the
targeted media.
Recommended Action: Use the robot test utility or a vendor administrative
interface to verify the media access port address based on the location of the
media. Choose a media access port that is valid, or let one be automatically selected,
and retry the robotic operation.

Robotic status code 243
Message: Cannot open/create the media access port status file
Explanation: A robotic daemon/process could not create or open a status file in
the database directory/folder.
Recommended Action: Investigate why the robot status file in the directory
/usr/openv/volmgr/database (UNIX and Linux) or folder
install_path\Volmgr\database (Windows) cannot be created or opened. On
Windows, check which account the NetBackup Device Manager service (and thus
the robotic process) is running under. Compare it against the security properties
of the database folder.

Robotic status code 244
Message: The eject command was aborted by the user
Explanation: An administrator or operator canceled an eject media request.
Recommended Action: This error happens when an administrator or operator
cancels an eject request. The request may have been canceled for a number of
reasons: missing or faulty media, to allow the media access port to be used for
other requests, or to perform the operation at a later time. Check with the
administrator or operator for more information.

Robotic status code 245
Message: Physical drive is not available
Explanation: Arobotic mount operation could not be completed because physical
drive resources are not available for the request. This error may result from an
environment that is based on virtualized resources, such as one involving the
Storagenet 6000 Storage Domain Manager (SN6000).
The SN6000 virtualizes tape drives. Some SN6000 configurations may have more
logical drives than the number of physical drives (or equivalent resources) available
for drive requests. Also, the relationship between the number of logical drives
and physical drives may change as hardware failures occur. NetBackup scheduling,
drive allocation, and drive assignment algorithms can only determine logical drive
availability. NetBackup attempts to fully utilize all configured and available logical
drives. If the number of required logical drives exceeds the physical drives
available, a NetBackup job may be started with insufficient drive resources. Instead
of queueing the job in the scheduler, the job runs and encounters the resource
issue when it makes an ACS tape mount request.
¦ Install the Shared Storage Option (SSO) license for mount requests to requeue
when physical drive resources are not available.
¦ The number of drives that can be in use at any one time is limited. Configure
backup windows so the different storage units that are tied to the same physical
drives are active only at non-overlapping times. Increase the media mount
timeout to avoid job failures when the job cannot get a physical drive due to
the drives all being busy.

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 236 to status code 240

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

Robotic status code 236
Message: Robot has misplaced the media
Explanation: The requested media was known according to the vendor software
managing the robotic library, but the media has been misplaced.
RecommendedAction: Use a robot test utility or a vendor administrative interface
to verify the status of media. Search for the media inside the robotic library.
Update the volume configuration and search for the media if it was not in the
robotic library, as needed, and resubmit the request.

Robotic status code 237
Message: Volume is in use
Explanation: The media was in use.
Recommended Action: Use the robot test utility or a vendor administrative
interface to verify the status of media. Determine what applications may be using
the media. Dismount the media if it is not being used. Wait for the media to become
available, as needed.

Robotic status code 238
Message: Requested drive is in an offline domain
Explanation: The drive that is targeted for a mount request was in a robotic
library domain that is offline.
Recommended Action: Bring back the robotic library domain ( ACS Library
Storage Module ) online. Or postpone use of drives in that domain until the domain
can be brought back online.

Robotic status code 239
Message: Requested volume is in an offline domain
Explanation: The volume that is targeted for a mount request was in a robotic
library domain that is in the offline or offline pending state.
RecommendedAction: Bring back online the robotic library domain (ACS Library
Storage Module). Or postpone use of media in that domain until the domain can
be brought back online.

Robotic status code 240
Message: A memory allocation attempt failed in the robotic daemon
Explanation: An attempt by the robotic control daemon to allocate memory has
failed. This error may indicate serious memory problems on your media server.
RecommendedAction: Stop all NetBackup Media Manager daemons. Consult the
documentation for your operating systemmemorymanagement tools to determine
what remaining process is leaking memory, and stop that process. Restart the
NetBackup Media Manager daemons. Free up memory by terminating unneeded
processes that consume a lot of memory. Add more swap space or physical memory
if necessary.

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 232 to status code 235

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

Robotic status code 232
Message: Volume not found in library
Explanation: The requested media was not found in the robotic library. The media
has been ejected or become inaccessible for some other reason.
¦ 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 obtain the list of media in the robotic
library. See whether inventory filters have been enabled in the Media Manager
configuration file. Inventory filters affect the contents of the media list
returned from the robotic daemon or process. Use a robot test utility or an
operating system/vendor administrative interface to verify the status of media,
as needed. Update the volume configuration and search for the media if it was
not in the robotic library, as needed, and resubmit the request.

Robotic status code 233
Message: Volume is in library, but not in drive domain
Explanation: The media was in the robotic library, in a library domain that is
inaccessible to the drives that are configured in the robot.
RecommendedAction: Issue a robot inventory Contents report to obtain the list
of media in the robotic library. Check the device configuration and ensure that
the drive addresses correspond to the correct domain for the media. Correct the
device configuration as needed and restart ltid (the device daemon on UNIX and
Linux or NetBackup Device Manager service on Windows). Use a robot test utility
or a vendor administrative interface to verify the status of media, as needed.
Update the volume configuration and physically move the media into the robotic
library, as needed, and resubmit the request.

Robotic status code 234
Message: Robot denied access to the resource
Explanation: The media was found in the robotic library, but is denied access
according to an established security policy.
RecommendedAction: Issue a robot inventory Contents report to obtain the list
of media in the robotic library. Use a vendor administrative interface to verify
the status of media, as needed. Delete the media in the volume configuration, or
make the volume accessible through a vendor administrative interface, as
appropriate. Update the volume configuration, as needed, and resubmit the request.

Robotic status code 235
Message: barcode label is unreadable
Explanation: The media was found in the robotic library, but it has an unreadable
barcode label.
Recommended Action: Use the robot test utility or a vendor administrative
interface to verify the status of media. Correct the label or replace the media as
appropriate. Update the volume configuration, as needed, and resubmit the request.

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

 
1 2