Symantec NetBackup Device configuration 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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 41 to status code 44 which may be received while using the Symantec NetBackup tool.

Device configuration status code 41
Message: Cannot change terminal mode
Explanation: When an attempt was made to change the mode for terminal input
between cooked and raw, a system call failed.
Recommended Action: Examine the user interface output for the system error
that is associated with the failed system call. Then troubleshoot according to
operating system vendor recommendations.

Device configuration status code 42
Message: Cannot create miscellaneous working repository
Explanation: On a device configuration request, the miscellaneous working
directory or folder is not present and cannot be created.
RecommendedAction: Find out why /usr/openv/volmgr/misc (UNIX and Linux)
or install_path\volmgr\misc (Windows) cannot be created. On Windows,
determine which accounts the NetBackup Volume Manager service and device
configuration interfaces are running under. Compare them with the security
properties of the database folder. On UNIX and Linux, determine whether users
or device configuration interface callers are running under a user and group with
permissions to create the miscellaneous directory.

Device configuration status code 44
Message: Cannot discover devices. See the Troubleshooting Guide for details.
Explanation: Device discovery cannot obtain or verify its lock file or had a problem
with the EMM server.
¦ Examine the daemon debug log and command or interface output for a more
detailed message on the system error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the operation and examine the logs. One of the following may have
occurred:
¦ Lock file problems: The device discovery process sets a lockfile in the
/usr/openv/volmgr/misc (UNIX and Linux) or install_path\Volmgr\misc
(Windows) directory named tpac.lock. It sets the lockfile to ensure that
only one instance of discovery runs on a particular host. It then checks the
lockfile before it updates the configuration.
¦ Cannot obtain lockfile.
The lockfile may be held by another discovery process. In this case the
following error is displayed:
another tpautoconf is already running
Use standard OS process tools (ps on UNIX and Linux or Task Manager
on Windows) to determine if another tpautoconf process is running.
If not, delete the lockfile and re-run device discovery. If another
tpautoconf process is running, wait for it to complete before retrying.
¦ Failed the lockfile check.
In the case of long device-discovery cycles, the interface may timeout
or the user may cancel the process. Part of the timeout or cancellation
is to remove the lockfile. This action tells the device discovery process
that it should not continue making modifications to the device
configuration. If action occurs, run the discovery process again.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration 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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 36 to status code 40 which may be received while using the Symantec NetBackup tool.

Device configuration status code 36
Message: <NONE>
Explanation: On a request to make a device configuration change, an error
occurred. A detailed message appears in the command or the utility interface
output.
¦ Examine the daemon debug log and command or interface output for a more
detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the device configuration request and examine the logs.

Device configuration status code 37
Message: Residence is not licensed for shared drive support
Explanation: On a request to add or update a drive in the device configuration,
the drive was specified as shared. No support for shared drives exists for that
drive type or for the type of robot that is associated with the drive.
RecommendedAction: Check the Technical SupportWebsite and product release
documentation for supported device configurations.

Device configuration status code 38
Message: Current version does not support remote device host
Explanation: On a request to change the EMM server, the specified host is not
the local host. The current software is not licensed to allow remote hosts.
Recommended Action: Check product documentation for supported device
configurations. Obtain an additional software license that allows remote hosts to
be configured, or specify only local host names on the configuration request.

Device configuration status code 39
Message: Adding this drive would exceed the maximum allowed
Explanation: On a request to add a drive to the device configuration, the licensed
limit for the maximum number of drives was reached on the targeted host.
Recommended Action: Check product documentation for supported device
configurations. Obtain an additional software license that allows more drives to
be configured. Or limit the configuration to the number of drives that the current
licensing allows.

Device configuration status code 40
Message: Adding this device would exceed the maximum allowed
Explanation: On a request to add a robot to the device configuration, the licensed
limit for the maximum number of robots was reached on the targeted host.
Recommended Action: Check product documentation for supported device
configurations. Obtain an additional software license that allows more robots to
be configured. Or limit the configuration to the number of robots that the current
licensing allows.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration status code 31 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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 31 to status code 35 which may be received while using the Symantec NetBackup tool.

Device configuration status code 31
Message: Robot number does not exist
Explanation: On a request to add or update a drive or robot in the device
configuration, the following occurred: the robot number and robot type specified
were not associated with any configured robots on the targeted device host.
Recommended Action: Check the device configuration on the targeted device
host and identify the configured robots. Every drive that is configured as a robotic
drive must already have its robot configured on that device host. Shared robotic
libraries having robotic control on a remote host must have a logical robotic entry
that refers to the remote host having robotic control. Add the robot to the device
configuration first. Then add the drive. Define it to be in the robot. If the robot
was already configured, specify the correct robot number and robot type on the
drive or the robot configuration request.

Device configuration status code 33
Message: Robot type must be controlled locally
Explanation: On a request to add or update a robot in the device configuration,
a remote control host was specified for a library type which does not support it.
¦ Check that you configured the correct robot type.
¦ Configure the device with local control by using its local device path.

Device configuration status code 34
Message: Drive name is already in use by another drive
Explanation: On a request to add or update a drive in the device configuration,
the requested drive path was in use on the targeted device host.
¦ To avoid configuring any paths that are already in use, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures the drive paths.
¦ Before you make configuration changes, check the existing drive configuration
through a device configuration interface. Or run tpconfig -d to determine
the drive paths that are already in use on the targeted device host. Then specify
a drive path that is not already in use.

Device configuration status code 35
Message: Drive name does not exist
Explanation: On a request to update or delete a drive in the device configuration,
the following occurred: no drives having the specified drive name were found on
the targeted device host.
Recommended Action: Check the device configuration on the targeted device
host and identify the configured drives. When you make drive configuration
changes or deletions, specify the drive name as it is configured. Take care to use
the proper case.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration status code 27 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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 27 to status code 30 which may be received while using the Symantec NetBackup tool.

Device configuration status code 27
Message: Invalid drive type for the robot
Explanation: On a request to configure a drive to be in a robot, the drive type was
not valid for the selected robot type.
RecommendedAction: Check the Robot Attributes tables in the following manual
to determine valid media types for a given robot type:
See the NetBackup Device Configuration Guide.
Drive types directly correspond to the listed media types. Configure supported
devices so that invalid combinations of drive types and robot types are not
required.

Device configuration status code 28
Message: Invalid robot drive number for the robot type
Explanation: On a request to configure a drive to be in a robot, the robot drive
number was not valid for the selected robot type.
Recommended Action: The robot drive number (for ACS robots, the set of ACS
drive identifiers) is limited to the ranges that are based on the robot type. These
limits are based on a supported device list. An invalid robot drive number means
that the drive number was not within the acceptable range. Make sure that the
robot hardware is supported and that the required patches are installed to support
the robotic library. If the robot type is TLH or TLM, do not specify a robot drive
number because the drives are addressed with a vendor drive name.

Device configuration status code 29
Message: Drive index is in use by another drive
Explanation: On a request to add a drive to the device configuration, the requested
drive index was in use on the targeted device host.
¦ To avoid configuring a drive index that is already in use, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures the drive index.
¦ If you use a device configuration interface that allows the drive index to be
specified, use tpconfig -d to determine the drive indexes already in use on
the targeted device host. Then specify a drive index that is not in use.

Device configuration status code 30
Message: Robot number is in use by another robot
Explanation: On a request to add or update a robotic drive in the device
configuration, the following occurred: the robot number and robot type specified
were associated with an existing robot of a different robot type.
Recommended Action: Check the device configuration on the targeted device
host and identify the configured robots.Onthe drive configuration request, specify
both the robot number and robot type that relate to the robot that contains the
drive.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration 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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 21 to status code 25 which may be received while using the Symantec NetBackup tool.

Device configuration status code 21
Message: Robot number is already in use
Explanation: On a request to add a robot to the device configuration, the robot
number was found to be already in use for a different robot.
Recommended Action: Check the device configuration on all device hosts for
configured robots, and specify a robot number that is not already in use. Use the
following command to display all devices in the EMM database:
tpconfig -emm_dev_list

Device configuration status code 22
Message: Device path is already in use
Explanation: On a request to add or change robot information in the device
configuration, the specified robotic device path is in use for another configured
robot.
¦ To avoid configuring the device paths that are already in use, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures device paths and device names.
¦ Display the device configuration using tpconfig -d or a device configuration
interface to see the robotic information that is already configured. Windows
hosts have multiple ways to configure robots (changer names or port, bus,
target, LUN). Check the operating system configuration or registry for changer
names and their associated SCSI paths. Check for detailed errors from the
command or the user interface output.

Device configuration status code 24
Message: Incomplete robot information
Explanation: Ona request to change the device configuration, some of the required
robot information was not specified.
Recommended Action: Check the command usage and reissue the request with
all required robot information specified.

Device configuration status code 25
Message: Robot drive number in use for this robot
Explanation: On a request to change the device configuration, the specified drive
address in the robot is in use by another drive in the device configuration.
Recommended Action: The drive address in the robot is the following: the robot
drive number for most robot types, the ACS/LSM/PANEL/DRIVE coordinates for
ACS robots, or a vendor drive name for TLH and TLM robots. Two drives cannot
have the same drive address in a robot in a given device configuration. If the drive
addresses need to be adjusted, delete one of the drives or make use of an unused
drive address as a temporary state. For example, a robot has two drives with robot
drive numbers 1 and 2 that need to be swapped. Change one drive to use robot
drive number 3 temporarily. Then change the other drive to use robot drive number
1 or 2 as appropriate. Finally, change the first drive to the open robot drive address
1 or 2.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration status code 16 to status code 19

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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 16 to status code 19 which may be received while using the Symantec NetBackup tool.

Device configuration status code 16
Message: A SCSI inquiry sent to the device has failed
Explanation: On a request to add or update a SCSI robotic library or drive, Media
Manager cannot obtain the device’s serial number and inquiry string. Media
Manager is obtains this information by sending a SCSI Inquiry command to the
device. Failure indicates that NetBackup was not able to communicate with the
device by means of SCSI.
¦ Ensure that the device is physically connected.
¦ Ensure that the operating system is configured to recognize the device and
that the operating system can see the device.
¦ Ensure that no other process uses the device and that the device is not offline.

Device configuration status code 17
Message: This robot type does not support multiple media types
Explanation: An attempt to add or update a robotic drive failed because the drives
in this robotic library are configured with a different drive type. (Some NetBackup
robotic library types do not support multiple media types.)
Refer to the NetBackup Release Notes or to the NetBackup Administrator’s Guide,
Volume II, for more information on which NetBackup robotic library types support
multimedia.
¦ Configure all drives for this robotic library with the same drive type.
¦ If you use NetBackup Server and want a robotic library with multiple media
types, contact Symantec to purchase NetBackup Enterprise Server.

Device configuration status code 18
Message: Invalid robot type
Explanation: On a request to modify the device configuration, the specified robot
type was invalid. Or it did not match the robot type for the robot that is associated
with the specified robot number.
¦ Check the device configuration for configured robots, and specify the correct
robot type applicable for the device configuration information being updated.
¦ 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.

Device configuration status code 19
Message: Invalid device path name
Explanation: On a request to change the device configuration, the specified device
path or device name was not valid.
¦ To avoid configuring invalid device paths and device names, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures device paths and device names.
¦ On Windows hosts, check the operating system configuration or registry for
device names and refer to the tpconfig command in NetBackup online Help.
Information for UNIX and Linux hosts is available
See the NetBackup Device Configuration Guide.
Always use no-rewind device files for drives that are attached to UNIX and
Linux hosts. Check to ensure that the specified device paths exist as
character-special files. Check for detailed errors from the command or the
user interface output.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration status code 11 to status code 15

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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 11 to status code 15 which may be received while using the Symantec NetBackup tool.

Device configuration status code 11
Message: Invalid Usage
Explanation: One of the Media Manager device configurationcommands(tpconfig
or tpautoconf) was executed with improper options. Or an incompatibility exists
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.
¦ Check the tpconfig or the tpautoconf usage statement for expected usage
and compare with the parameters being sent to start the new process.
¦ Verify that all Media Manager binaries are at a compatible version level.

Device configuration status code 13
Message: Failed reading drive or robot config file
Explanation: A request was made to list the device configuration, but an error
was encountered while reading from the EMM database.
¦ Examine the daemon debug log 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 nbemm is running. Display the device configuration to determine
whether or not the database is corrupt. Restore a saved copy of the databases
from catalog backups, or delete them and recreate the device configuration as
needed.

Device configuration status code 14
Message: Invalid drive index
Explanation: A request was made to add, update, or list a drive configuration
entry, and the specified drive index was not associated with a configured drive.
¦ Display the device configuration to obtain the list of valid drives. Avoid making
device configuration changes from multiple sources simultaneously.
¦ If more information is needed, examine the daemon debug log and command
or interface output for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 15
Message: Invalid robot number
Explanation: On a request to modify the device configuration, the specified robot
number was not within the allowable range, the robot number did not correspond
to a currently configured robot, or the robotic database is corrupted.
¦ Specify a robot number in the range of 0 to 32767.
¦ Ensure that all device configuration changes or deletions are performed on
the devices that are currently part of the device configuration.
¦ Verify that nbemm is running. Restore a saved copy of the robotic database from
catalog backups, or delete it and recreate any needed robotic configuration
information.

Hope this was helpful.

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

 

Symantec NetBackup Device configuration status code 7 to status code 10

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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 7 to status code 10 which may be received while using the Symantec NetBackup tool.

Device configuration status code 7
Message: Invalid SCSI port number for the robot
Explanation: A request was made to add or change the SCSI port number for a
robot, but the SCSI port number provided was not valid.
¦ 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 the correct SCSI port number for the robot. Perform device discovery
by using the Device Configuration Wizard, or check the Windows registry as
needed to obtain the SCSI port number.

Device configuration status code 8
Message: Invalid SCSI bus number for the robot
Explanation: A request was made to add or change the SCSI bus number for a
robot, but the SCSI bus number provided was not valid.
RecommendedAction: Specify the correct SCSI bus number for the robot. Perform
device discovery by using the Device Configuration Wizard, or check the Windows
registry as needed to obtain the SCSI bus number.

Device configuration status code 9
Message: Invalid SCSI target for the robot
Explanation: A request was made to add or change the SCSI target for a robot,
but the SCSI target provided was not valid.
Recommended Action: Specify the correct SCSI target for the robot. Perform
device discovery by using the Device Configuration Wizard, or check the Windows
registry as needed to obtain the SCSI target.

Device configuration status code 10
Message: Invalid SCSI logical unit number for the robot
Explanation: A request was made to add or change the SCSI logical unit number
for a robot, but the SCSI logical unit number was not valid.
RecommendedAction: Specify the correct SCSI logical unit number for the robot.
Perform device discovery by using the Device Configuration Wizard, or check the
Windows registry as needed to obtain the SCSI logical unit number.

Hope this was helpful.

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

 

 

Symantec NetBackup Device configuration status code 0 to status code 3

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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 0 to status code 3 which may be received while using the Symantec NetBackup tool.

Device configuration status code 0
Message: Success
Explanation: A requested operation was successfully completed.
Recommended Action: None.

Device configuration status code 1
Message: Cannot execute command, permission denied
Explanation: A user or process that did not have root privileges (on UNIX and
Linux) or administrator privileges (on Windows) started the process. Or theEMM
server name cannot be set.
¦ If appropriate, give the user or the process administrator privileges (on
Windows) or root privileges (on UNIX and Linux) and reissue the device
configuration request.
¦ Establish a common EMM server name as follows:
¦ Run tpautoconf -get_gdbhost on other hosts.
¦ Set the EMM server name with
tpautoconf -set_gdbhost host_name
where host_name is the host name returned by tpautoconf -get_gdbhost.

Device configuration status code 2
Message: The device_mappings file has invalid license info
The problem concerns one of the following files:
/usr/openv/share/device_mappings.txt (UNIX and Linux) or
install_path\VERITAS\NetBackup\share\device_mappings.txt (Windows).
¦ The file does not exist.
¦ The file is for a different version of NetBackup. You can find what version it
is for by reading the header in the file.
¦ The file has a corrupted licensing digest.
RecommendedAction: Download the latest device mapping file from the following

Device configuration status code 3
Message: Could not get hostname
Explanation: An attempt to look up the host name for this host 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 the host name is resolvable.

Hope this was helpful.

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

 
1 2