Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

serial number mismatch after drive replacement

Created: 11 Feb 2013 • Updated: 09 Apr 2013 | 24 comments
This issue has been solved. See solution.

Hi all,

 

I´ve tried the solutions found in other post of the forum but didn´t get solved.

Our servers ran Solaris 10 and Netbackup7.

After a drive replacement I did:

   DOWN DRIVE

   tpautoconf -report_disc

   tpautoconf - replace_drive ... path ... (with the info reported in the previous command)

   UP DRIVE

   restart services

(same procedure than during previous drive changes without failures), but our platform still references the old serial number:

tpconfig -d:

16  Drive_LTO8        hcart  TLD(1)  DRIVE=5
      MISSING_PATH:/dev/rmt/16cbn:1068041083MISSING_PATH:/dev/rmt/16cb UP
 

user@master $ tpautoconf -report_disc
user@master $

Under Devices\Drives in NB console, clicking on the drive affected I can see the folowing:

Drive_LTO8   nameserver  /dev/rmt/16cbn                                                New serial

Drive_LTO8   nameserver MISSING_PATH:/dev/rmt/16cbn:old_serial    Old serial

 

How can I update the configuration with the correct serial number?

thanks in advance.

Comments 24 CommentsJump to latest comment

mph999's picture

Did you delete the old drive from the NBU config ?

Personally, I would just delete the drive(s) and readd the new one with the wizard.

If solaris, you may need to rebuild the sg driver to get the new drive visible in the scan command output.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
NBdmecha's picture

It will be my next step, just need to re-check as I never had to do that before.thanks for the suggestion.

Anyway, whenever I run the wizard without deleting the drive NB detects the paths (wrong and right serial numbers) and one displays MISSING PATH.

After deleting the drive in the console and re-adding it, Can I rename it with the same name ?

Do i need to rebuild the sg drive?I hope no as I see the paths with the right serial number.

A goal without a plan is just a wish.

mph999's picture

If scan shows all the devices, no need to rebuild sg.

Best to delete the old/ missing_path device before reconfiguring.

You can give the new drive the same name, providing you have deleted the old one.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
NBdmecha's picture

When I try to delete the MISSING PATH  from Devices\Drives it isn´t deleted and trying to DOWN it from Device Monitor appears a message like:

"Volume does not exist in database"

A goal without a plan is just a wish.

mph999's picture

When you say delete the missing path, do you mean you tried to delete the drive ?

Thanks,

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
NBdmecha's picture

I meant that I tried to delete one of the paths of the drive, instead of the drive. As I can see the right ones and the wrong, I tried to remove just the wrong to avoid reconfiguring the whole drive.

A goal without a plan is just a wish.

NBdmecha's picture

I deleted the drive from the console, it asked me to restart media manager daemons which I accepted.

 

After that right paths dissappear but MISSING ones are still present...

A goal without a plan is just a wish.

mph999's picture

Hmm, odd - if you don't have many drives/ robots across loads of servers, I'd be tempted to just run nbemmcmd -deletealldevices -allrecords

This will splat ALL robots/ drives in the envronment (across all media servers).

Then  just reconfigure ...

Failing that,  what does tpconfig -d show and tpautoconf -report_disc

(The full output of each)  I know you posted above, but it may have changed.

M

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
NBdmecha's picture

There are 20 drives and 35 media servers so I´d rather prefer to avoid "nbemmcmd -deletealldevices -allrecords"

 

tpconfig -d (master)

16  Drive_LTO8        hcart  TLD(1)  DRIVE=5
      MISSING_PATH:/dev/rmt/16cbn:1068041083MISSING_PATH:/dev/rmt/16cb UP
 

 tpautoconf -report_disc (master)

 

======================= Missing Device (Drive) =======================
 Drive Name = Drive_LTO8
 Drive Path =
 Inquiry = "IBM     ULTRIUM-TD5     BBNH"
 Serial Number = 1068041083
 TLD(1) definition Drive = 5
 Hosts configured for this device:
  Host = netbackup
======================= New Device (Drive) =======================
 Inquiry = "IBM     ULTRIUM-TD5     BBNH"
 Serial Number = 1068049613
 Drive Path = /dev/rmt/32cbn
 Found as TLD(1), Drive = 5
 Found as TLD(1), Drive = 5
======================= New Device (Drive) =======================
 Inquiry = "IBM     ULTRIUM-TD5     BBNH"
 Serial Number = 1068049613
 Drive Path = /dev/rmt/16cbn
 Found as TLD(1), Drive = 5
 Found as TLD(1), Drive = 5
 

 

Tried to run again tpautoconf -replace_drive and it says:

 

tpautoconf -replace_drive  Drive_LTO8 -path /dev/rmt/32cbn
Found a matching device in global DB, Drive_CC_LTO8 on host netbackup

 

but it keeps the same discrepancies:

tpautoconf -report_disc

======================= Missing Device (Drive) =======================
Drive Name = Drive_LTO8
Drive Path =
Inquiry = "IBM ULTRIUM-TD5 BBNH"
Serial Number = 1068041083
TLD(1) definition Drive = 5
Hosts configured for this device:
Host = netbackup
======================= New Device (Drive) =======================
Inquiry = "IBM ULTRIUM-TD5 BBNH"
Serial Number = 1068049613
Drive Path = /dev/rmt/32cbn
Found as TLD(1), Drive = 5
Found as TLD(1), Drive = 5
======================= New Device (Drive) =======================
Inquiry = "IBM ULTRIUM-TD5 BBNH"
Serial Number = 1068049613
Drive Path = /dev/rmt/16cbn
Found as TLD(1), Drive = 5
Found as TLD(1), Drive = 5

Can´t put the drive DOWN previously on netbackup console because "invalid drive number" error.

 

A goal without a plan is just a wish.

Marianne's picture

Use toconfig (without any options) - it is a text-based menu that will allow you to delete the MISSING PATH tape drive (Drive_LTO8). 

Remember to restart ltid after deleting the drive.

Use the wizard to re-add.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NBdmecha's picture

Thanks Marianne, going to try as soon as jobs running finish.

A goal without a plan is just a wish.

NBdmecha's picture

This is how tpconfig displays my config:

 

Id=0   NameOfDrive=Drive_LTO1a
Id=1   NameOfDrive=Drive_LTO2a
Id=2   NameOfDrive=Drive_LTO3a
Id=3   NameOfDrive=Drive_LTO8b
Id=4   NameOfDrive=Drive_LTO4a
Id=5   NameOfDrive=Drive_LTO5a
Id=6   NameOfDrive=Drive_LTO6a
Id=7   NameOfDrive=Drive_LTO7a
Id=8   NameOfDrive=Drive_LTO8a
Id=9   NameOfDrive=Drive_LTO1b
Id=10  NameOfDrive=Drive_LTO2b
Id=11  NameOfDrive=Drive_LTO3b
Id=12  NameOfDrive=Drive_LTO4b
Id=13  NameOfDrive=Drive_LTO5b
Id=14  NameOfDrive=Drive_LTO6b
Id=15  NameOfDrive=Drive_LTO7b
Id=16  NameOfDrive=Drive_LTO8b

so Id=3 (right paths) and Id=16 (wrong paths) have the same name. As operations are done by drive name how can I refer the delete actions only to Id=16 ??

 

I´m thinkig about deleting Drive_LTO8b and see what happens...

A goal without a plan is just a wish.

NBdmecha's picture

Ok I did it. I deleted Drive_LTO8b, and so Id=3 dissapeared but the wrong one is still there:

Id=0 NameOfDrive=Drive_LTO1a
Id=1 NameOfDrive=Drive_LTO2a
Id=2 NameOfDrive=Drive_LTO3a
Id=4 NameOfDrive=Drive_LTO4a
Id=5 NameOfDrive=Drive_LTO5a
Id=6 NameOfDrive=Drive_LTO6a
Id=7 NameOfDrive=Drive_LTO7a
Id=8 NameOfDrive=Drive_LTO8a
Id=9 NameOfDrive=Drive_LTO1b
Id=10 NameOfDrive=Drive_LTO2b
Id=11 NameOfDrive=Drive_LTO3b
Id=12 NameOfDrive=Drive_LTO4b
Id=13 NameOfDrive=Drive_LTO5b
Id=14 NameOfDrive=Drive_LTO6b
Id=15 NameOfDrive=Drive_LTO7b
Id=16 NameOfDrive=Drive_LTO8b

 

EMM Server = netbackup

        1) Add
        2) Delete
        3) Update
        4) List Configuration
        5) Drive Path Configuration
        6) Help
        7) Quit - return to main menu

Enter option:

Enter name of drive to delete: Drive_LTO8b

Drive name Drive_LTO8b does not exist
Press any key to continue

A goal without a plan is just a wish.

NBdmecha's picture

Any help  deleting the wrong drive?

A goal without a plan is just a wish.

Will Restore's picture

restart ltid process and it should go away

Will Restore -- where there is a Will there is a way

NBdmecha's picture

Already tried, also I restarted all NB services but it´s still there.

A goal without a plan is just a wish.

mph999's picture

OK, so if the foolowing has been done, which I believe it has ...

You have deleted the drive from the NBU config that has the missing path.

Even though you have restarted ltid, it is still there.

If this is true ...

Two options.

1.  nbemmcmd -deletealldevices -allrecords

2.  Log call enquire to the possibility of getting an SQL script to detele the drive from the database directly.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
NBdmecha's picture

Thanks for the suggestion mph999.

I was wondering about the second option, I will do it and let you know the solution.

 

A goal without a plan is just a wish.

Mark_Solutions's picture

So as you are at the moment can you run a tpconfig -l and show the output.

maybe a tpconfig -update -drive driveindex -path drivepath could be used to set the one left as being correct path.

Or maybe something has a lock on it - do a nbrbutil -dump in case it has an MDS allocation that needs clearing before you can get rid of it.

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

NBdmecha's picture

I did the tpconfig -update as I always follow the steps on this link:

http://www.symantec.com/business/support/index?page=content&id=TECH34296

Nbrbutil -dump reflects no reservations:

 

Allocation Requests
(AllocationRequestSeq )

Allocations
(AllocationSeq )

MDS allocations in EMM:

A goal without a plan is just a wish.

Mark_Solutions's picture

I take it you have also tried deleting the drive via the admin console (do a View - Refresh All after each attempt to force an EMM re-read)?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

NBdmecha's picture

Sure, also restart services.

A goal without a plan is just a wish.

ankmah's picture

 

Very first do the following command on master servr.

  nbemmcmd -deletealldevice - machinename machinename -machinetype machinetype

Now on media server where u have to replace the drive..

  Check drive is visible at OS or not.. if not then make this visible..

Do scan and see drive visible or not. Must be visible.

 now /usr/openv/volmgr/bin/tpautoconf -a

 

See robots and drive is visible or not by tpconfil -l

 

GO to NBC run the wizard.. 

vmoprcmd -d -h hostname will display new drive..

 

 

 

 

 

 

 

NBdmecha's picture

Still haven´t contact symantec support but the best option will be  the possibility of getting an SQL script to detele the drive from the database directly as mph999 said.

 

Thanks all.

A goal without a plan is just a wish.