Symantec NetBackup Robotic error code 14 to error code 17

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 are returned if a robotic daemon/process was started from the command line and an error occurs. For example, if the administrator executes the following:

/usr/openv/volmgr/bin/tl8d

and no robots are configured, the following may be returned:

TL8: No robots are configured

These status codes are also logged to the system log. Usually, robotic daemons/processes are not started from the command line, but are started automatically, as needed, when ltid starts.

Below are some of the NetBackup Robotic error code 14 to error code 17 which may be received while using the Symantec NetBackup tool.

Robot Error status code 14
Message: You must be administrator to execute
Explanation: A robotic process was started under a user account that lacks
Administrator privileges (applies to Windows systems only).
Recommended Action: Allow robotic daemons to be started automatically as
needed by the NetBackup Device Manager service. Ensure that this service starts
from a user account with administrator privilege.

Robot Error status code 16
Message: Devices located in multiple domains
Explanation: A robotic daemon or process encountered an invalid device
configuration. In this configuration, a single logical robot controls drives from
different domains.
Recommended Action: Display the device configuration using tpconfig -d or
a device configuration interface to see the robotic and the drive information that
is already configured. Ensure that the drive addresses do not span physical
domains. Drives can only be configured in the same robot if they can be used with
media from a single domain. The domain must include a single physical library
or multiple libraries that are connected by a cartridge exchange or pass-through
mechanism.

Robot Error status code 17
Message: Robotic daemon not licensed
Explanation: A robotic daemon or process was started without the required,
current product license, or a required database file was missing or corrupt.
¦ Check product documentation for supported device configurations.
¦ Obtain an additional software license that allows robots of the associated robot
type to be configured. Or, limit the configuration to robot types that current
licensing allows. Check for the existence and permissions of the
external_robotics.txt file in the /usr/openv/share directory (UNIX and
Linux) or in the install_path\NetBackup\share folder (Windows).

Hope this was helpful.

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

 

Symantec NetBackup Robotic error code 09 to error code 13

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 are returned if a robotic daemon/process was started from the command line and an error occurs. For example, if the administrator executes the following:

/usr/openv/volmgr/bin/tl8d

and no robots are configured, the following may be returned:

TL8: No robots are configured

These status codes are also logged to the system log. Usually, robotic daemons/processes are not started from the command line, but are started automatically, as needed, when ltid starts.

Below are some of the NetBackup Robotic error code 09 to error code 13 which may be received while using the Symantec NetBackup tool.

Robot Error status code 9
Message: Error in SEMAPHORE operation
Explanation: A process was unable to perform a semaphore operation (such as
lock or unlock) associated with resources maintained by ltid. (ltid is the Media
Manager device daemon on UNIX and Linux or the NetBackup Device Manager
service on Windows.)
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use.

Robot Error status code 10
Message: Fork failure occurred
Explanation: A robotic daemon or process could not create a child process due
to a system error. This error is probably intermittent, based on the availability of
resources on the system (applies to UNIX and Linux servers only).
¦ Restart the device daemon at a later time and investigate system problems
that limit the number of processes.
¦ Examine the system logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Restart the device daemon, then retry the operation and examine the system
log file.

Robot Error status code 11
Message: System error occurred
Explanation: A robotic daemon/process encountered a system error.
Recommended Action: Examine command output, debug logs, and system logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Robot Error status code 12
Message: Usage error in creating child process
Explanation: A robotic daemon/process could not create a child process due to
an incompatibility between robotic software 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.
¦ Verify that all Media Manager binaries are at a compatible version level.

Robot Error status code 13
Message: EMM error
Explanation: The robotic daemon had a problem communicating with EMM.
¦ Make sure nbemm is running and responding to requests.
¦ 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.

Hope this was helpful.

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

 

Symantec NetBackup Robotic error code 05 to error code 08

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 are returned if a robotic daemon/process was started from the command line and an error occurs. For example, if the administrator executes the following:

/usr/openv/volmgr/bin/tl8d

and no robots are configured, the following may be returned:

TL8: No robots are configured

These status codes are also logged to the system log. Usually, robotic daemons/processes are not started from the command line, but are started automatically, as needed, when ltid starts.

Below are some of the NetBackup Robotic error code 05 to error code 08 which may be received while using the Symantec NetBackup tool.

Robot Error status code 5
Message: Error in getting process Id
Explanation: A robotic daemon/process was unable to obtain its own process
identifier due to a system call failure.
Recommended Action: Investigate operating system functionality regarding a
process obtaining its own process identifier.

Robot Error status code 6
Message: No devices are configured on the robot
Explanation: Arobotic daemon/process was started, but no drives are configured
for the robot.
RecommendedAction: Some robotic daemons or processes do not run if no drives
are configured for them to manage. Add or reconfigure one or more drives to be
in the associated robot. Then, stop and restart ltid (the Media Manager device
daemon on UNIX and Linux or NetBackup Device Manager service on Windows).

Robot Error status code 7
Message: No robots are configured
Explanation: A robotic daemon/process was started, but no robots of the
associated robot type are configured.
RecommendedAction: Robotic daemons or processes do not run if no robots are
configured for the associated robot type. Add or reconfigure robots, then stop and
restart ltid (the Media Manager device daemon on UNIX and Linux or NetBackup
Device Manager service on Windows).

Robot Error status code 8
Message: No memory available
Explanation: A robotic daemon/process was unable to allocate memory. This
error occurs when insufficient system memory is available. This error could result
from the system being overloaded with too many processes and from insufficient
physical and virtual memory.
RecommendedAction: Free up memory by terminating unneeded processes. Add
more swap space or physical memory.

Hope this was helpful.

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

 

Symantec NetBackup Robotic error code 01 to error code 04

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 are returned if a robotic daemon/process was started from the command line and an error occurs. For example, if the administrator executes the following:

/usr/openv/volmgr/bin/tl8d

and no robots are configured, the following may be returned:

TL8: No robots are configured

These status codes are also logged to the system log. Usually, robotic daemons/processes are not started from the command line, but are started automatically, as needed, when ltid starts.

Below are some of the NetBackup Robotic error code 01 to error code 04 which may be received while using the Symantec NetBackup tool.

Robot Error status code 1
Message: You must be ROOT to start daemon
Explanation: Auser other than root started a robotic daemon. This status applies
to UNIX and Linux systems only.
Recommended Action: Log on as the root user before starting robotic daemons.
Allow robotic daemons to be started automatically as needed by ltid (the device
daemon).

Robot Error status code 2
Message: LTI Daemon may not be running
Explanation: On an attempt to start a robotic daemon or process, an attempt to
connect to the ltid message queue failed. This error indicates that ltid (the
device daemon or NetBackup Device Manager service) may not be running.
¦ Start ltid so that shared memory can be initialized, allowing the robotic
daemon/process to function.
¦ If problems persist, 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.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use.

Robot Error status code 3
Message: Error in getting shared memory
Explanation: A robotic daemon/process was unable to get a shared memory
identifier associated with a segment of shared memory that ltid maintains. (ltid
is the Media Manager device daemon on UNIX and Linux or the NetBackup Device
Manager service on Windows.)
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use.

Robot Error status code 4
Message: Error in attaching the shared memory
Explanation: A robotic daemon/process was unable to attach a shared memory
segment that ltid maintains. (ltid is the Media Manager device daemon on UNIX
and Linux or the NetBackup Device Manager service on Windows.)
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use.

Hope this was helpful.

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

 

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.

 
1 2 3 25