Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- How capacity licensing works
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- DELETE About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About Tape I/O commands on UNIX
Verifying your Shared Storage Option configuration
In a Shared Storage Option configuration, a shared drive must have the same logical name (drive name) on all of the NetBackup media servers. If the drive resides in a robotic library, it also must use the same drive number in the library. This section describes some tools you can use to verify your configuration.
How you verify that your configuration is set up correctly depends on your devices and how you configured Shared Storage Option, as follows:
If you have serialized devices, Veritas recommends that you use the Device Configuration Wizard. The wizard verifies your configuration.
If you have non-serialized devices, see the Veritas support site for tech note TECH31764, "Verifying a Shared Storage Option (SSO) Configuration with Non-Serialized Devices. It describes how to verify your configuration.
If you have serialized devices but you did not use the Device Configuration Wizard, use the following procedure to verify your configuration.
The verification procedures use the following NetBackup commands:
On Windows:
install_path\VERITAS\Volmgr\bin\scan install_path\VERITAS\Volmgr\bin\tpconfig
On UNIX/Linux:
usr/openv/volmgr/bin/scan usr/openv/volmgr/bin/tpconfig
In the following example the ADIC robotic library has six drives, but only drives 5 and 6 are configured on this particular host.
Perform the verification on all of the NetBackup servers in your configuration. Ensure that each shared drive has the same logical drive name and same drive number ID on each media server that shares the drive.
To verify a manually-configured Shared Storage Option configuration
- Execute tpconfig -d or tpconfig -dl. For NDMP devices, use tpautoconf -probe -ndmp_host_name host_list.
The output from tpconfig shows the logical names NetBackup assigns to tape drives. The following example shows drive number 5 is named QUANTUM.DLT7000.000 and drive number 6 is named QUANTUM.DLT7000.001:
Id DriveName Type Residence Drive Path Status *************************************************************** 0 QUANTUM.DLT7000.000 dlt TLD(0) DRIVE=5 /dev/st/nh3c0t5l0 UP 1 QUANTUM.DLT.7000.001 dlt TLD(0) DRIVE=6 /dev/st/nh3c0t1l0 UP Currently defined robotics are: TLD(0) robotic path = /dev/sg/h3c0t0l0 EMM server = norway
- Execute the scan command. The scan output shows the robot and the drive properties.
The following is example output:
************************************************************* ********************** SDT_TAPE ************************** ********************** SDT_CHANGER ************************** ************************************************************* Device Name : "/dev/sg/h3c0t0l0" Passthru Name: "/dev/sg/h3c0t0l0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "ADIC Scalar 100 3.10" Vendor ID : "ADIC " Product ID : "Scalar 100 " Product Rev: "3.10" Serial Number: "ADIC009K0340314" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_CHANGER NetBackup Robot Type: 6 Removable : Yes Device Supports: SCSI-2 Number of Drives : 6 Number of Slots : 50 Number of Media Access Ports: 10 Drive 1 Serial Number : "PXB03S0979" Drive 2 Serial Number : "PXB03S0913" Drive 3 Serial Number : "CXA04S2051" Drive 4 Serial Number : "PXA31S1787" Drive 5 Serial Number : "PXA37S3261" Drive 6 Serial Number : "PXA50S2276" Flags : 0x0 Reason: 0x0 ------------------------------------------------------------ Device Name : "/dev/st/nh3c0t5l0" Passthru Name: "/dev/sg/h3c0t5l0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "QUANTUM DLT7000 2561" Vendor ID : "QUANTUM " Product ID : "DLT7000 " Product Rev: "2561" Serial Number: "PXA37S3261" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_TAPE NetBackup Drive Type: 9 Removable : Yes Device Supports: SCSI-2 Flags : 0x4 Reason: 0x0 ------------------------------------------------------------ Device Name : "/dev/st/nh3c0t1l0" Passthru Name: "/dev/sg/h3c0t1l0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "QUANTUM DLT7000 296B" Vendor ID : "QUANTUM " Product ID : "DLT7000 " Product Rev: "296B" Serial Number: "PXA50S2276" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_TAPE NetBackup Drive Type: 9 Removable : Yes Device Supports: SCSI-2 Flags : 0x4 Reason: 0x0
For each tape drive in the tpconfig output, do the following:
Use the device file name from the tpconfig output to locate the tape drive in the scan output.
Step 1 shows device file pathnames
/dev/st/nh3c0t5l0
and/dev/st/nh3c0t1l0
.Determine the serial number of the drive in the scan output. "Tape" in the device type field identifies a tape drive.
Step 2 shows example scan output shows the following:
The drive
/dev/st/nh3c0t5l0
serial number is PXA37S3261.The drive
/dev/st/nh3c0t1l0
serial number is PXA50S2276.Verify that the serial number for the drive matches the serial number in the output from the robot section of scan. "Changer" in the device type field identifies a robot.
In the previous examples, the serial numbers match.