Veritas NetBackup™ Troubleshooting Guide
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Robotic tests on Windows
If the robot has been configured (that is, added to NBDB), start the robotic test utility by using the robtest command. This action saves time, since robotic and drive device paths are passed to the test utility automatically.
To use the robtest command, do the following (in the order presented):
Execute the following command:
The test utility menu appears.
Select a robot and press Enter.
The test starts.
install_path\Volmgr\bin\acstest -r ACSLS_HOST
install_path\Volmgr\bin\tl4test -r roboticpath
install_path\Volmgr\bin\tl8test -r roboticpath
install_path\Volmgr\bin\tldtest -r roboticpath
install_path\Volmgr\bin\tlhtest -r robotic_library_name
install_path\Volmgr\bin\tlmtest -r DAS_Hostname
More information on ACS, TLH, and TLM robotic control is available.
See the NetBackup Device Configuration Guide.
In the previous list of commands, roboticpath is the full path to the device file for the robotic control (SCSI). You can review the section for your platform to find the appropriate value for roboticpath.
An optional parameter specifies the device file path for the drives so that this utility can unload the drives using the SCSI interface.
install_path <-p port -b bus -t target -l lan | -r roboticpath>
where: roboticpath is the changer name (e.g., Changer0).