Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 8938

NetBackup scan; two drives same serial?

$
0
0
I need a solution

Hi all,

I have a wiered phenomenon on a NBU 7.5.0.3. media server.

i have connected 20 drives via FC to this host.

Two rives are missing, because they are faulty and have to be changed, those are turned off, so it should not show up at the host at all.

When I do a rescan in windows device manager, everything is fine, there a 18 drives.

When I now do a scan with netbackup!

 

PS C:\Program Files\Veritas\Volmgr\bin> ./scan | select-string "Device I" | sort
 
Device Identifier: "IBM     ULTRIUM-TD5     F002547001"
Device Identifier: "IBM     ULTRIUM-TD5     F002547007"
Device Identifier: "IBM     ULTRIUM-TD5     F00254700D"
Device Identifier: "IBM     ULTRIUM-TD5     F002547013"
Device Identifier: "IBM     ULTRIUM-TD5     F002547019"
Device Identifier: "IBM     ULTRIUM-TD5     F002547019"
Device Identifier: "IBM     ULTRIUM-TD5     F00254701F"
Device Identifier: "IBM     ULTRIUM-TD5     F002547025"
Device Identifier: "IBM     ULTRIUM-TD5     F00254702B"
Device Identifier: "IBM     ULTRIUM-TD5     F002547031"
Device Identifier: "IBM     ULTRIUM-TD5     F002547037"
Device Identifier: "IBM     ULTRIUM-TD5     F002566001"
Device Identifier: "IBM     ULTRIUM-TD5     F002566007"
Device Identifier: "IBM     ULTRIUM-TD5     F002566019"
Device Identifier: "IBM     ULTRIUM-TD5     F00256601F"
Device Identifier: "IBM     ULTRIUM-TD5     F002566025"
Device Identifier: "IBM     ULTRIUM-TD5     F00256602B"
Device Identifier: "IBM     ULTRIUM-TD5     F00256602B"
Device Identifier: "IBM     ULTRIUM-TD5     F002566031"
Device Identifier: "IBM     ULTRIUM-TD5     F002566037"

Don't count the, these are 20!

As you can see 2 serial numbers show up twice!

Here are the details from 1 of those candidates:

 

 

Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 2; Bus: 0; Target: 11; LUN: 0
Inquiry    : "IBM     ULTRIUM-TD5     D2A6"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD5     "
Product Rev: "D2A6"
Serial Number: "F002547019"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD5     F002547019"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
 
Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 2; Bus: 0; Target: 4; LUN: 0
Inquiry    : "IBM     ULTRIUM-TD5     D2A6"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD5     "
Product Rev: "D2A6"
Serial Number: "F002547019"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD5     F002547019"
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0

What is this?

Port 2/0/11 is the working one, Port2/0/4 is dead, I can see this directly at the HBA!

Why does Netbackup think that the dead drive has the same serial than another drive in the same library?

During the last night I saw lots of these in the windows appl log:

serial number check failed on Drive002 (device 4, SCSI coordinates {2,0,4,0}, \\.\Tape3), drive serial number is F002547019, database serial number is F00256600D, DOWN'ing it

These are IBM LTO5 drives, driver is installed non-exclusive.

best regards

Volker

 

 


Viewing all articles
Browse latest Browse all 8938

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>