cancel
Showing results for 
Search instead for 
Did you mean: 

NetBackup appliance could not auto detect newly added datastore need to do manual recan

Vickie
Level 6

NetBackup Version : 7.6.0.4

Master Server is Linux VM.

Media server : NetBackup Appliance 5230, 

Appliance Version is 2.6.0.4.

cisco MDS 9148

 

3 REPLIES 3

sdo
Moderator
Moderator
Partner    VIP    Certified

1) Do these appliance CLIsh commands definitely locate all of the WWPNs that you expect to see:

Manage -> FibreChannel -> Reset
Manage -> FibreChannel -> Scan Manage -> FibreChannel -> Show

...warning:  the "Reset" above may abort any inflight backups/duplications/restores - so do the "Reset" at a quiet time.

2) How many LUNs do you have presented from each storage array WWPN Target back to the Appliance WWPN Initiators?

3) How many LUNs presented in total, from all WWPN targets, to the appliance?  More than 99?  I can remember an old bug that confused the Appliance CLIsh if more that 99 LUNs were presented.

sdo
Moderator
Moderator
Partner    VIP    Certified

4) After doing the HBA "reset" and "scan" via the CLIsh, then... if you can drop down to the elevated root prompt, you may be able to also try these safe to run list commands, to try to debug if the expected LUNs really are missing:

lsscsi
lsscsi -d -g -v
lsblk

...assuming that these commands are available in your version of SUSE based v2.6.0.4 Appliance.  Sorry, but I only have a RHEL based v3.0 Appliance to test the above commands on.

Thanks for your reply,

Yes the number of LUNs are >99. And when we trying to do the manual rescan from CLISH it causing NOS alert on MDS and SCSI reset alerts on the VM end. and dose not seems to be fine to use many times a LUN got added.

The value of presented LUN to the Appliance is difference then the value comes via these listed commands.

lsscsi
lsscsi -d -g -v