Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Snapshot Client Administrator's Guide
  3. Configuration of snapshot methods for disk arrays
  4. OS-specific configuration tasks
  5. Verifying NetBackup client access, zoning, and LUN masking
Veritas NetBackup™ Snapshot Client Administrator's Guide

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
    • Windows

      \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]

Note:

The last line of output is wrapped.

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 Enclosure ID/DeviceID pair constitutes a client 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.

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.

More Information

OS-specific configuration tasks

Feedback

Was this page helpful?
Previous

Linux modprobe.conf file

Next

About VSS configuration (Windows)

Feedback

Was this page helpful?