SAN drives getting down in netbackup
Hi Team,
We have Netbackup 8.1 on master. Currently the tape drives are getting down on one SAN media server and which is a shared drive. Need your help to resolve.
How we can identify if the drives are misconfigured and how to solve them back.
/usr/openv/volmgr/bin/vmoprcmd -d -devconfig -l -h ctooptmwdb1un2 -autoconfig -t
TPAC60 IBM 03592E08 47A9 0000078DCAB0 -1 -1 -1 -1 /dev/nst5 - -
TPAC60 IBM 03592E08 47A9 0000078DCAFE -1 -1 -1 -1 /dev/nst2 - -
TPAC60 IBM 03592E08 47A9 0000078DCAB8 -1 -1 -1 -1 /dev/nst7 - -
TPAC60 IBM 03592E08 47A9 0000078DCAF3 -1 -1 -1 -1 /dev/nst6 - -
TPAC60 IBM 03592E08 47A9 0000078DCB3C -1 -1 -1 -1 /dev/nst4 - -
TPAC60 IBM 03592E08 47A9 0000078DCB0C -1 -1 -1 -1 /dev/nst3 - -
TPAC60 IBM 03592E08 47A9 0000078DCB0A -1 -1 -1 -1 /dev/nst1 - -
TPAC60 IBM 03592E08 47A9 0000078DCAF5 -1 -1 -1 -1 /dev/nst0 - -
# /usr/openv/volmgr/bin/vmoprcmd -d ds -h ctooptmwdb1un2 -devconfig
TPC_DEV65 DRIVE OH1SF2C1R3 16 8 0 33 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst6 0000078DCAF3 - 32907 2 -1 -1 -1 -1 0 3720 0 0 - 0 i0000:40/0000:40:02.2/0000:47:00.0/host7/rport-7:0-4/target7:0:2/7:0:2:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 4 0 0
TPC_DEV65 DRIVE OH1SF2C1R4 16 8 0 34 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst5 0000078DCB0C - 128 1 -1 -1 -1 -1 0 2798 0 0 NEEDS~CLEANING 1 i0000:40/0000:40:02.2/0000:47:00.0/host7/rport-7:0-3/target7:0:1/7:0:1:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 5 0 0
TPC_DEV65 DRIVE OH1SF2C1R2 16 8 0 32 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst4 0000078DCAB0 - 128 1 -1 -1 -1 -1 0 1259 0 0 - 0 i0000:40/0000:40:02.2/0000:47:00.0/host7/rport-7:0-2/target7:0:0/7:0:0:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 6 0 0
TPC_DEV65 DRIVE OH1SF2C3R3 16 8 0 41 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst3 0000078DCAF5 - 128 1 -1 -1 -1 -1 0 3595 0 0 - 0 i0000:00/0000:00:03.0/0000:04:00.0/host5/rport-5:0-5/target5:0:3/5:0:3:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 11 0 0
TPC_DEV65 DRIVE OH1SF2C3R1 16 8 0 39 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst2 0000078DCB0A - 128 1 -1 -1 -1 -1 0 3504 0 0 - 0 i0000:00/0000:00:03.0/0000:04:00.0/host5/rport-5:0-4/target5:0:2/5:0:2:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 12 0 0
TPC_DEV65 DRIVE OH1SF2C3R4 16 8 0 42 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst1 0000078DCB3C - 128 1 -1 -1 -1 -1 0 2257 0 0 NEEDS~CLEANING 1 i0000:00/0000:00:03.0/0000:04:00.0/host5/rport-5:0-3/target5:0:1/5:0:1:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 13 0 0
TPC_DEV65 DRIVE OH1SF2C3R2 16 8 0 40 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst0 0000078DCAFE - 128 1 -1 -1 -1 -1 0 2255 0 0 NEEDS~CLEANING 1 i0000:00/0000:00:03.0/0000:04:00.0/host5/rport-5:0-2/target5:0:0/5:0:0:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 14 0 0
TPC_DEV65 DRIVE OH1SF2C1R1 16 8 0 46 - -1 -1 -1 -1 ctooptmwdb1un2 /dev/nst7 0000078DCAB8 - 32907 2 -1 -1 -1 -1 0 3565 0 0 - 0 i0000:40/0000:40:02.2/0000:47:00.0/host7/rport-7:0-5/target7:0:3/7:0:3:0 - IBM~~~~~03592E08~~~~~~~~47A9 - 15 0 0
TPC_DEV65 ROBOT ROBOT0 8 0 ctooptmwdb1un2 - - -1 -1 -1 -1 0000078AA6080402 crebm1300 crebm1300 IBM~~~~~03584L22~~~~~~~~1411 0 1 0
Without knowing what the rest of your environment looks like and how your drive names were selected/configured, probably safest to manually edit drive properties for each incorrect drive and specify correct path.
There are only 6 to edit.
Restart NBU on the media server once completed.