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. About IBM DS4000 array
  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 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

About IBM DS4000 array

Feedback

Was this page helpful?
Previous

IBM 4000 software requirements

Next

Configuring NetBackup to access the IBM DS4000 array

Feedback

Was this page helpful?