NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Installation
- Policy configuration
- Selecting the snapshot method
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- NAS snapshot configuration
- Dynamic data streaming for D-NAS workloads
- Setting up a NAS-Data-Protection policy
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- About storage lifecycle policies for snapshots
- Configuration of software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- OS-specific configuration tasks
- About IBM DS6000 and DS8000 arrays
- Configuring NetBackup to access the IBM DS6000 or DS8000 array
- About IBM DS4000 array
- About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
- Hitachi array software requirements
- About HP-XP arrays
- About array troubleshooting
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- Snapshot management
- Troubleshooting
- Logging directories for UNIX platforms
- Logging folders for Windows platforms
- FlashBackup and status code 13
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
Verifying NetBackup client access, zoning, and LUN masking
You can use the nbfirescan command to verify the following: that NetBackup clients have access to the array devices, and that the arrays are properly zoned and LUNs are unmasked. Note that nbfirescan only displays LUNs that have been unmasked and mapped to the host.
To verify NetBackup client access, zoning, and LUN masking
- Enter the following on the client:
/usr/openv/netbackup/bin/nbfirescan
This command queries the host's SCSI bus for all the SCSI (or Fibre) attached devices that are visible.
Example output from an AIX host, for Hitachi and IBM arrays, followed by a description:
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun] ------------------------------------------------------------------------- /dev/hdisk8 HITACHI OPEN-V-CM 10266 241 [00,00,144640,00] /dev/hdisk9 HITACHI OPEN-V 10266 840 [00,00,144640,01] /dev/hdisk45 IBM 1814 FAStT IBM.1814-600A0B800042212 2000000004804132760:0A:0B:80:00:42:33:6E:00:00:16:EF:48:DC:3C:1F [00,00 ,327936,01] /dev/hdisk46 IBM 1814 FAStT IBM.1814-600A0B800042212 2000000004804132760:0A:0B:80:00:42:33:6E:00:00:16:F7:48:DC:57:F3 [00,00 ,327936,02] /dev/hdisk43 IBM 1814 FAStT IBM.1814-600A0B800042212 2000000004804132760:0A:0B:80:00:42:33:6E:00:00:14:A4:48:AA:52:87 [00,00 ,327936,03] /dev/rdsk/c2t6d11s6 HITACHI DF600F 6484 48 [00,00,00,00] /dev/rdsk/c2t6d10s6 HITACHI DF600F 6484 46 [00,00,00,00] /dev/rdsk/c2t10d3s6 HITACHI OPEN-V -SUN 45027 18 [00,00,00,00] /dev/rdsk/c2t10d0s6 HITACHI OPEN-V-CM 45027 0 [00,00,00,00]
Note the following descriptions:
DevicePath
Represents the actual access point for the device as it exists on the client host.
EnclosureId
Unique for each physical disk array.
DeviceId
Unique for a physical disk or virtual disk in an enclosure. The EnclosureId/DeviceId pair constitutes a host-independent designation of a particular physical or virtual disk within a disk array.
Ctl,Bus,Tgt,LUN
Controller, bus, target, and LUN numbers are the elements that designate a particular physical or virtual disk from the perspective of the client host computer.
More Information