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.

 

Symantec NetBackup Device management status code 41 to status code 44

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

Device management status code 41
Message: Unknown drive name
Explanation: A request was made for a specified drive, but no such drive can be
found in the active configuration. This status can occur in the following situations:
if the device files are corrupt or missing, if they cannot be opened or read, or if
there are no devices configured.
¦ 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.) Display the
device configuration (use tpconfig -d or other means) to see the list of valid
drives. Specify the drive name or index as appropriate for the interface being
used.
¦ Check integrity of the EMM database. Display the device configuration to do
the following:
¦ Determine if the database is corrupt.
¦ Restore a saved copy of the database file from catalog backups, or remove
the devices and recreate the device configuration.

Device management status code 42
Message: Incorrect tpreq access mode
Explanation: On a tape mount request, the specified access mode was invalid. On
Windows hosts, a user without Administrator privileges made a request for
NetBackup Device Manager services.
Recommended Action: When you use tpreq, specify an access mode argument
of r for read, w for write, or use the default (read) access mode. When you make
any requests that require NetBackup Device Manager services on Windows, do
so under an account with Administrator privileges.

Device management status code 44
Message: You do not have permission to create the file
Explanation: On a tape mount request, the file name that is associated with the
request cannot be created due to directory permissions or folder permissions.
Recommended Action: Check for existence of a file at the file path specified. If
a file is found, delete the file if it is not needed or submit the request again and
use a different file path. If no file exists at that location, check the directory
permissions or the folder permissions for the following: read and write access for
the user or the application process that issued the mount request.

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

SQLServerF1

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

Device management status code 36
Message: Request terminated by tpunmount call from another process
Explanation: Arequest was made to change the limit for the following: the number
of times that a volume can be mounted with write access for one or more volumes
in the volume configuration. The value specified was not within the acceptable
range. The maximum number of mounts value may also be invalid in the number
of mounts and cleanings field of a bar code rule.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Specify a maximum-mounts value within the range of 0 to 2,147,483,647.

Device management status code 37
Message: Drive being assigned is either not NDMP or on the wrong NDMP client
Explanation: A mount request was canceled because the request was targeted to
a drive configured as attached to an NDMP client. The request was manually
assigned to a drive other than the requested drive. The assigned drive is either
not NDMP or it is an NDMP drive configured to a different client.
Recommended Action: Display the device configuration to determine which
drives are configured as being attached to specificNDMPclients. Ensure that ltid
was stopped and restarted after the last configuration changes were made. Reissue
the request and assign it to a drive that is attached to the requested NDMP client.

Device management status code 38
Message: Character device name for drive is not a character device
Explanation: On a tape mount request, the configured tape drive’s
no-rewind-on-close device file was neither a character-special device nor of a
known type such as NDMP. (NDMP does not need to be a character special file.)
¦ To avoid configuring invalid device paths and device names, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures paths and device names for tape drives.
¦ Always use no-rewind tape device files or recognized drive name syntax (such
as for NDMP) for tape drives. Make sure that the specified device paths exist
as character-special files. Check for detailed errors from the command or the
user interface output.
See the NetBackup Device Configuration Guide.

Device management status code 39
Message: Parameter is invalid
Explanation: The tpclean command was called with invalid arguments, or an
internal function encountered a missing reference to data it requires.
¦ If a cleaning operation was requested, check the tpclean usage statement and
compare with the parameters that were specified.
¦ Check the installed software components and verify that they are all at a
compatible release version.

Device management status code 40
Message: File name already exists
Explanation: On a tape mount request, the file name that is associated with the
request already exists or is already associated with another mount request.
Recommended Action: Submit the request again with a different file name.
Specify a file name that does not correspond to an existing file. Or specify a file
name that is not in use for another mount request that may be in progress.

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

SQLServerF1

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

Device management status code 32
Message: Error in getting semaphore
Explanation: ltid made an attempt to obtain a semaphore that was used for
arbitrating access to shared memory. (ltid is the Media Manager device daemon
on UNIX and Linux or the NetBackup Device Manager service on Windows) The
request failed due to a system error. The error probably indicates a lack of system
resources for semaphores, or mismatched 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.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use. Check the installed software components
and verify that they are all at a compatible release version.

Device management status code 33
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.

Device management status code 35
Message: Request terminated because media is unavailable (in DOWN drive,
misplaced, write protected or unmountable)
Explanation: A mount request was canceled because the media being requested
is not available. It may be in a DOWN drive or misplaced, write protected, or
unmountable. Another possible cause of this message is that you are using a
cleaning tape with no cleanings remaining.
Recommended Action: Use robotic inventory or manual means to compare the
contents of media in the robotic library with the volume configuration. Then
update the configuration as needed. Determine the physical location of the media.
Check integrity of the drive, drive path, and media if the media is found in a
logicallyDOWNdrive. Verify that the media is not a misconfigured cleaning tape.
Move the media into the robotic library and update the volume configuration if
the media was not present in the library. Set the cartridge tab to allow write access,
or request the media with read-only access if the write protection was the cause
of the error.
If the problem is a cleaning tape with no cleanings remaining, replace the cleaning
tape.

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 26 to status code 30

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

Device management status code 26
Message: Request terminated because host not validated for volume pool
Explanation: The host where the mount request was initiated is denied access to
the media. It is denied due to defined permissions for the volume pool in which
the media ID is contained.
¦ Query the volume pool information for the requested volume pool on the host
where the mount request was issued by running vmpool -listall -b. Check
the system log to obtain the name of the host where the mount request
originated. This host name is the one returned by the system hostname(1)
command.
¦ Change the volume pool host name security with vmpool or another user
interface that supports volume pool host attributes. Or change the volume
pool that is associated with the volume (if it is not assigned). Or log on to the
host that is allowed to use media in the targeted volume pool. Then, submit
the mount request again.

Device management status code 27
Message: Request terminated because media ID is expired
Explanation: A mount request was canceled because the media was requested
with write access, and the media has expired.
Recommended Action: Request read-only access to the media on the mount
request if a read-only operation is needed. Replace the media or change the
expiration date to a future date that is based on site policy. Use the media
management interface to view and change the expiration date for the media.
Check and correct the system date and time, as needed.

Device management status code 28
Message: Error in MsgGet
Explanation: ltid made an attempt to obtain a message queue identifier that
was used for internal message communications. (ltid is the Media Manager device
daemon onUNIXand Linux or the NetBackup Device Manager service on Windows.)
The request failed due to a system error. The error probably indicates a lack of
system resources for message queues, or mismatched 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.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use. Check the installed software components
and verify that they are all at a compatible release version.

Device management status code 30
Message: Request terminated because media id will exceed maximum mount
count
Explanation: A mount request has been canceled because the media being
requested has reached the maximum mount count associated with the media.
RecommendedAction: Replace the media or change the maximum mount count
to a higher value that is based on site policy. A media management interface can
be used to view and change the maximum mounts allowed for the media. Check
that the number of mounts for the media is set to a reasonable value given the
media’s usage history. Correct it as needed by using vmchange.

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

SQLServerF1

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

Device management status code 21
Message: The drive is not ready or inoperable
Explanation: A drive was selected for a mount request, but the drive is not ready
with loaded media.
Recommended Action: Wait until the drive is ready before you manually assign
a drive to a pending mount request.

Device management status code 22
Message: IPC Error: Daemon may not be running
Explanation: A request to ltid cannot be serviced. (ltid is the Media Manager
device daemon on UNIX and Linux or the NetBackup Device Manager service on
Windows.) ltid is probably not running. If ltid is still running, its process lock
file may have been removed. Also, message queues may not function correctly on
the system.
¦ If ltid is not running, start ltid and try the operation again. On UNIX and
Linux, run /usr/openv/volmgr/bin/ltid, and on Windows, start the
NetBackup Device Manager service.
¦ If ltid is already running, check for the existence and permissions of the lock
file itself and the lock file directory, which are as follows:
/usr/openv/volmgr/misc/.ltipid (UNIX and Linux) or install_path\
Volmgr\misc\.ltipid (Windows). Terminate the ltid process if it is running.
Create the lock directory or folder and adjust the permissions as needed so
that ltid can obtain the lock.
¦ On UNIX and Linux, check the msgget man page and look for suggestions on
how to troubleshoot the system message queues.

Device management status code 23
Message: Invalid Drive Number
Explanation: A request was made for drive, but no such drive can be found in the
active configuration.
RecommendedAction: Ensure that ltid was stopped and restarted after changes
were last made to the device configuration. (ltid is the Media Manager device
daemon onUNIXand Linux or the NetBackup Device Manager service on Windows.)
Display the device configuration (by using tpconfig -d or other means) to view
the list of valid drives. Specify the drive name or index as appropriate for the
interface being used.

Device management status code 24
Message: Requested drive could not be reserved
Explanation: An attempt was made to reserve a shared drive, but the drive
reservation request failed. This status code is related to the internal
implementation of the SSO feature. It is not related to SCSI Reserve or Release.
RecommendedAction: This condition is expected for any shared drives that are
retried automatically. If problems persist, verify the following: the EMM server
services requests and it does not list drives as reserved to hosts that currently do
not use the drives.

Device management status code 25
Message: File name does not exist
Explanation: A logical tape file or help file cannot be found. The tpunmount
command was probably issued with a logical tape file specified that does not exist
for this user.
RecommendedAction: Check for existence of the logical tape file at the file path
specified. The specified file path must match the exact case-sensitive path that
was used when the tape mount was requested. Submit the request again with the
correct file path. If the condition occurs during operator display of a pending
request error message, check to see if the help files are properly installed at the
following: /usr/openv/volmgr/help/robots/robot_type/help_file name (UNIX
andLinux) or at install_path\Volmgr\Help\Robots\robot_type\help_file_name
(Windows).

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

SQLServerF1

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

Device management status code 16
Message: No mount pending for given mount index
Explanation: Anattempt was made to retrieve information about a pending mount
request, but no such pending mount request was found.
RecommendedAction: Use a device monitor interface or consult application logs
to see whether the request was completed or canceled. Requests to retrieve
information for pending mount requests are valid only when the mount request
is ongoing.

Device management status code 17
Message: Drive does not support pending request density
Explanation: A drive was selected that has a drive type which is not compatible
with the requested density.
¦ Allow the drive selection to be determined automatically.
¦ When you select the drive manually, check the device configuration and the
valid density table (available in the tpreq man page or command description).
Then specify a drive that is compatible with the requested density.

Device management status code 19
Message: Only the administrative user can perform the requested operation
Explanation: Either an attempt was made to stop ltid (the Media Manager device
daemon onUNIXand Linux or the NetBackup Device Manager service on Windows).
Or the tpclean command was called, but the user was not root (UNIX and Linux)
or the administrator (Windows).
RecommendedAction: If appropriate, give the user or the process administrator
privileges on Windows or root privileges on UNIX and Linux and retry the
operation.

Device management status code 20
Message: Cannot stop device daemon with tapes assigned
Explanation: An attempt was made to stop ltid, but media is currently mounted
and assigned. (ltid is the Media Manager device daemon on UNIX and Linux or
the NetBackup Device Manager service on Windows.)
Recommended Action: Halt all jobs referencing media, unmount all media, and
stop all applications from using Media Manager before trying to stop ltid. If
unable to unmount media through the application interface, check for the existence
and permissions of the .ltisymlinks file in the /usr/openv/volmgr/misc
directory or in the install_path\Volmgr\misc folder. Initiate tpunmount
filename for each line in the .ltisymlinks file, where filename specifies the
contents of a line in that file. For example, on UNIX and Linux, the command may
look like the following:
tpunmount /usr/openv/netbackup/db/media/tpreq/A00001

Hope this was helpful.

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

 
1 2 3 4 5 25