Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Client Administrator's Guide
Last Published:
2022-05-23
Product(s):
NetBackup & Alta Data Protection (10.0)
- 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 that the NetBackup clients have access to the array devices and that the arrays are properly zoned and LUNs are LUN masked. Note that nbfirescan only displays LUNs that have actually been LUN masked to the host.
To verify NetBackup client access, zoning, and LUN masking
- Enter the following on the client:
UNIX
/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 Linux output (wrapped to fit page):
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun] --------------------------------------------------------------------------------- /dev/sdb DGC RAID 5 APM00050602951 60:06:01:60:83:B0:11:00:4D:C4:8A:1D: 35:EC:DA:11 [01,00,00,00] /dev/sdc DGC RAID 5 APM00050602951 60:06:01:60:83:B0:11:00:4C:C4:8A:1D: 35:EC:DA:11 [01,00,00,01] /dev/sdd DGC RAID 5 APM00050602951 60:06:01:60:83:B0:11:00:4B:C4:8A:1D: 35:EC:DA:11 [01,00,00,02] /dev/sde DGC RAID 5 APM00050602951 60:06:01:60:83:B0:11:00:4A:C4:8A:1D: 35:EC:DA:11 [01,00,00,03] /dev/sdf HP HSV200 5000-1FE1-5007-0020 6005-08B4-0010-5F49-0000-5000-22F8-0000 [01,00,01,01] /dev/sdg HP HSV200 5000-1FE1-5007-0020 6005-08B4-0010-5F49-0000-5000-22FF-0000 [01,00,01,02]
More Information