Video Screencast Help
Search Video Help Close Back
to help

tpautoconf serial number mismatch

Created: 10 May 2012 | 4 comments
Shekhar D's picture
Shekhar D Certified
0 0 Votes
Login to vote

In netbackup what are the steps need to follow the if tpautoconf o/p mismatch and how those are communicated in OS side like windows,Sun<Linux,AIX,HP

Contineously we are facing issue of mismatch the drives and drives goes down.Please suggest.

Sometimes intermmitent issue comming on media server 6.5/7.

THanks.

Discussion Filed Under:
, ,

Comments 4 Comments • Jump to latest comment

revaroo's picture
revaroo Symantec Employee
tpautoconf serial number mismatch - Comment:10 May 2012 : Link

I normally just remove all the drives and re-add them using:

nbemmcmd -deletealldevices -machinename <mediaserver> -machinetype media

especially if you do not have too many drives, then just re-add them after.

 

 

0
Login to vote
  • Actions
Marianne van den Berg's picture
Marianne van den Berg Trusted Advisor Partner Accredited Certified
tpautoconf serial number mismatch - Comment:10 May 2012 : Link

When you are sharing tape drives, try to keep them on the same NBU version.

Device mapping mismatch will cause drives to be unable to unload and then DOWN'ed.

If you have VERBOSE entry in vm.conf on media servers, you will probably see errors in syslog/messages/Event Viewer such as:

TLD(0) drive ## (device ##) is being DOWNED, status: Unable to SCSI unload drive.
or
Incorrect media found in drive index #, expected AAAAAA, found BBBBBB, FREEZING AAAAAA
etc...
 
If media server OS allows, try to ensure that Persistent Binding is done between OS and HBA. This will ensure that tape drives keep the same OS device names when system is rebooted.

 

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

0
Login to vote
  • Actions
wr's picture
wr
tpautoconf serial number mismatch - Comment:10 May 2012 : Link

Use -report_disc, -replace_drive, and -replace_robot to reconfigure the

devices in the EMM database to reflect a serial number change that a configured

device replacement caused. After hardware replacement, the correction process

requires that at least one system is available through the operating system. You

may need to re-map, rediscover, and reboot the system.

 

 

will restore -- where there is a Will there is a way

0
Login to vote
  • Actions
Omar Villa's picture
Omar Villa
tpautoconf serial number mismatch - Comment:10 May 2012 : Link

Unfortunally this happens all the time, mainly when you replace a drive the way we do it is either with the tpautoconf -replace_drive option that will update all the drive in a SSO environment or one by one with the tpconfig -update option, there is no way to alert on this or detected on time, something you can script is the output of the 3 EMM tables related with the drive configuration: configDB (tpconfig), autoconf (tpautoconf) and globDB (vmglob) the output of this 3 needs to match you can write a script to catch any missmatch at Seria Number, Drive Name or Path level.

Omar Villa

Netbackup Expert

Winners do not win the race, just love to run.

 

0
Login to vote
  • Actions