Symantec NetBackup Device management status code 36 to status code 40
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.
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.