Veritas NetBackup™ Snapshot Client Administrator's Guide
- Snapshot Client features
- About snapshot basics
- Off-host backup overview
- Off-host backup methods
- About alternate client backup
- Snapshot Client requirements
- Policy configuration
- Selecting the snapshot method
- Configuration parameters for Snapshot Client
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- About configuring VxVM
- About storage lifecycle policies for snapshots
- Network Attached Storage (NAS) snapshot configuration
- Configuration of software-based snapshot methods
- Software-based snapshot methods
- Cache device requirements
- About VxFS_Checkpoint
- About VxVM
- About FlashSnap
- About VVR
- About VSS
- Software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- About the new disk array snapshot methods
- Disk array configuration tasks
- OS-specific configuration tasks
- About VSS configuration (Windows)
- About EMC CLARiiON arrays
- Configuring NetBackup to access the CLARiiON array
- Configuring a NetBackup policy for a CLARiiON array method
- About EMC Symmetrix arrays
- About configuration for EMC_TimeFinder_Mirror
- About configuration for EMC_TimeFinder_Clone
- About HP EVA arrays
- Verifying connectivity from clients to array using SSSU 5.0
- 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
- Troubleshooting issues pertaining to all arrays
- Troubleshooting IBM DS6000 and DS8000 arrays
- Troubleshooting IBM4000 arrays
- Troubleshooting Hitachi arrays
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- About restores from a FlashBackup backup
- Instant Recovery restore features
- About Instant Recovery: block-level restore
- About Instant Recovery: file promotion
- About Instant Recovery: Fast File Resync (Windows clients only)
- About Instant Recovery: point in time rollback
- About configurations for restore
- About restoring from a disk snapshot
- 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
- Appendix C. NetBackup integration with CloudPoint for snapshot managment
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:
\Program Files\Common Files\Veritas Shared\VxFI\4\Bin\nbfirescan.exe
This command queries the host's SCSI bus for all the SCSI (or Fibre) attached devices that are visible.
Note the following regarding CLARiiON:
If there are LUNs in the client's CLARiiON storage group, the LUNs are included in the output.
If there are no LUNs visible but the array is zoned to allow the host to see it, the output includes the entry DGC LUNZ. This entry is a special LUN that the CLARiiON uses for communication between the client and the array. The LUNZ entry is replaced by another disk entry as soon as one is put in the storage group which has been presented to the client.
Example Solaris output, followed by a description:
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun] --------------------------------------------------------------------------------- /dev/rdsk/c3t4d57s2 EMC SYMMETRIX 000187910258 013C [00,00,00,00] /dev/rdsk/c3t6d10s2 HP HSV200 5000-1FE1-5007-0020 6005-08B4-0010-5F49-0000-5000-408F-0000 [00,00,00,00]
The last line of output is wrapped.
Represents the actual access point for the device as it exists on the client host.
Unique for each physical disk array.
Unique for a physical disk or virtual disk in an enclosure. The Enclosure ID/DeviceID pair constitutes a client host-independent designation of a particular physical or virtual disk within a disk array.
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.
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]
Most of the output lines are wrapped.
DGC designates a CLARiiON device.