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.

 

Symantec NetBackup Device management status code 63 to status code 70

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

Device management status code 63
Message: Request terminated because mount requests are disabled
Explanation: A mount request was canceled because it cannot be satisfied.
Recommended Action:
Examinecommandoutput, debug logs, and system logs for a more detailed message
on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
The detailed reason for the canceled request should be available in the system
log, command output, or from a device monitor interface. Correct the problem
and resubmit the request if needed.

Device management status code 64
Message: Cannot assign a robotically controlled device
Explanation: An attempt was made to manually assign a specific device to satisfy
a mount request, and the chosen device was configured in a robotic library.
RecommendedAction: Assign the request to a standalone drive, or allow requests
for mounts in robotic drives to be automatically assigned.

Device management status code 65
Message: Invalid volume pool specified
Explanation: On a mount request, the media pool specified was not valid.
Recommended Action: Resubmit the request, specifying a volume pool name
that is no more than 20 ASCII characters in length.

Device management status code 66
Message: Request terminated because of volume pool mismatch
Explanation: The volume pool that is specified on the tpreq command did not
match the volume pool in the Media Manager configuration for the media ID.
RecommendedAction: Use a media management interface to obtain the volume
pool name of the media that is to be mounted. Then resubmit the mount request,
specifying the correct pool name.

Device management status code 69
Message: Request terminated because media is unmountable
Explanation: A mount request has been canceled because the media being
requested is not mountable. The same media has been found to be unmountable
in at least two different drives.
¦ Check integrity of the drive, drive path, and media.
¦ Verify that the media is not a misconfigured cleaning tape.

Device management status code 70
Message: Request terminated because media is write protected
Explanation: A mount request has been canceled because the media being
requested for write access is not write-enabled.
Recommended Action: Check the physical media cartridge to see whether
write-protection has been enabled. If write access to the media is desired, disable
write protection for the media.
If read-only access is desired, leave the write-protection enabled. Then make the
necessary administrative requests in the requesting application (such as
suspending the media) to ensure that the media is requested only for read access.
If the media was requested through the command line interface, see the tpreq
man page or command description for specifying the media access mode. The
tpreq command is described in the following manuals:
See the NetBackup Administrator’s Guide, Volume II.
See the NetBackup Commands Reference Guide.

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 59 to status code 62

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

Device management status code 59
Message: No cleaning tape is defined in the device’s robot or 0 cleanings remain.
Explanation: An attempt was made to automatically clean a drive, but no usable
cleaning media is available. Or the number of cleanings that remains for the
cleaning tape is zero.
¦ Ensure that cleaning media was added to the robotic library for each drive
type capable of being cleaned with a separate cleaning cartridge.
¦ Ensure that a positive number of cleanings is available for the cleaning media
in the EMM database for the robotic library. Replace the cleaning tape or
increase the number of cleanings for the cleaning media before the count
reaches zero.
¦ 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 60
Message: Robot daemon and/or robotic hardware is not available
Explanation: A robot was not configured or was operationally unavailable.
Specifically, an attempt may have been made to automatically clean a robotic
drive, but the robot is not defined or is unavailable. Alternatively, on an attempt
to initialize the shared drive lists, a drive was found to be configured as robotic,
without the required robot configured.
Recommended Action: Display the device configuration and ensure that the
drive and robotic configuration information are consistent. Check the operational
status of the robot and robotic software by checking the system log files. If more
detail on robot operational status is needed, increase the level of verbosity by
adding the VERBOSE option in the vm.conf file. Then restart ltid (the device
daemon /NetBackup Device Manager service).

Device management status code 61
Message: No media found in device or robot slot, please verify
Explanation: On a request to mount media, no media was found in the targeted
location before a designated time period had elapsed.
RecommendedAction: Resubmit the request, and mount the media in the targeted
drive before the designated time period has elapsed. Check the device configuration
to ensure the following: that the correct drive name has been configured and that
ltid, the device daemon, was restarted after the last device configuration change
was made.

Device management status code 62
Message: Drive not available in library for mount request
Explanation: A mount request has been canceled because no drive is available.
All compatible drives may be DOWN, or oversubscribed due to other active mount
requests.
Recommended Action: Investigate device availability and scheduling/drive
utilization of applications requesting drive resources. Under some conditions,
mount requests are canceled so that they can be reissued at a later time when
compatible drive resources are available.

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 52 to status code 58

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

Device management status code 52
Message: No robot is defined of this type
Explanation: On internal communications between a robotic daemon or process
and ltid, no robots of the expected type were found actively configured. (ltid is
the Media Manager device daemon on UNIX and Linux or the NetBackup Device
Manager service on Windows.)
RecommendedAction: Display the running robotic processes to see if processes
from a previous configuration are still running. If any are found, terminate them.
Check the installed software components and verify that they are all at a
compatible release version.

Device management status code 53
Message: Request has been queued (Cancel to clear message)
Explanation: A mount request or drive-related operation was queued because
drive resources were in use.
RecommendedAction: Wait until the drive resources become available, or cancel
pending mount requests as needed.

Device management status code 55
Message: Operator denied mount request
Explanation: The operator denied a mount request.
Recommended Action: This error occurs when an administrator or operator
cancels a user or application mount request. The request may have been canceled
for a number of reasons: missing or faulty media or the need to allow other, higher
priority requests to obtain drive resources. Check with the administrator or
operator for more information.

Device management status code 56
Message: Mount canceled, device daemon is terminating
Explanation: Pending mount requests were canceled because the administrator
terminated ltid (the Media Manager device daemon on UNIX and Linux or the
NetBackup Device Manager service on Windows).
RecommendedAction: Wait for ltid to be restarted before you submit the request
again. Check with the administrator as needed to determine daemon or service
availability.

Device management status code 58
Message: The device is not robotic, cannot perform cleaning
Explanation: An attempt was made to automatically clean a drive, but the drive
is not in a robotic library.
Recommended Action: Clean stand-alone drives by inserting a cleaning tape
when needed. For non-shared drives, update the cleaning statistics with tpclean
or another user interface that supports cleaning-related operations.

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 46 to status code 50

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. 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 46 to status code 50 which may be received while using the Symantec NetBackup tool.

Device management status code 46
Message: Tape needs to be write enabled
Explanation: On a tape mount request, the specified access mode was for write
access, but the physical media was write-protected.
RecommendedAction: Change the physical media write-protect setting to allow
write access (unlocked), or submit the request again with read-only access. To
request read-only access using tpreq, specify an access mode argument of r for
read or use the default (read) access mode.

Device management status code 47
Message: Unable to establish scan host for shared drive
Explanation: On a request to change a shared drive’s status, an attempt to
establish a connection to the drive’s scan host failed.
¦ Determine which host serves as the drive’s scan host: use vmoprcmd output or
by checking the Device Monitor in the Administration Console.
¦ Ensure that vmd (the NetBackup Volume Manager daemon on UNIX and Linux
or NetBackup Volume Manager service on Windows) is running on the scan
host. On the scan host, examine debug logs and system logs for any messages
that are related to the 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.
¦ The detailed reason for the canceled request should be available in the daemon
debug logs on the scan host. Correct the problem and submit the request again
if needed.

Device management status code 48
Message: Host is not the scan host for this shared drive
Explanation: On a request to assign, reserve, or scan a drive, the targeted device
host determined that it was not the scan host for the drive. The request was refused
(the caller retries it).
¦ If problems are encountered as a result of the reported error, check for
communication, configuration, and system problems among the associated
hosts. To check, use vmoprcmd output or check the Device Monitor in the
Administration Console.
¦ 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.
¦ Configure scan ability priorities for assigning scan hosts by changing the Media
Manager configuration. Configure so that less network connections need to
be maintained, and greater system load is placed on hosts with more capability
to service the load.

Device management status code 49
Message: Tape file path exceeds 255 character maximum
Explanation: On a tape mount request, the file name that is associated with the
request exceeds 255 characters.
RecommendedAction: Whenyou request a tape mount, ensure that the file name
does not exceed 255 ASCII characters in length. If the mount requests come from
an application, request an application change to use a shorter file name. Or install
the product in a directory or a folder that does not cause the file name limit to be
exceeded.

Device management status code 50
Message: No action pending for given mount index
Explanation: On a request to obtain the pending action for a mount request, no
known pending action was associated with the request.
Recommended Action: Use a device monitor interface to display any requests
that have pending actions. Perform requests (like assign, deny, display, or resubmit)
only on the requests that have pending actions.

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