Veritas-bu

[Veritas-bu] Re: Strange Netbackup/Library Behavior

2007-08-08 13:06:45
Subject: [Veritas-bu] Re: Strange Netbackup/Library Behavior
From: dbwallis <netbackup-forum AT backupcentral DOT com>
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Date: Wed, 08 Aug 2007 09:41:34 -0700

Marianne Van Den Berg wrote:
> Sounds like a mapping mismatch. 
> 
> You need to verify that the robot drive positions is mapped to the
> correct O/S device name in NetBackup.
> 
> When a backup starts and a tape is mounted, NetBackup waits for the tape
> mount to be confirmed. If the tape mount is not confirmed on the correct
> O/S device name, but in stead it finds a tape that fits the criteria on
> another drive, it will proceed with the backup.
> 
> At the end of the backup, a 'rewind & offline' is sent to the O/S device
> name. If the mapping is wrong, you will understand that the dismount
> cannot take place.
> 
> If you have a VERBOSE entry in your vm.conf, you will find the evidence
> in syslog (Unix) or Event Viewer App (Windows). 
> 
> It might look like this (extract from Solaris messages file):
> 
> Aug 15 04:54:47 BFe450 tldcd[21016]: [ID 183166 daemon.error] TLD(0) key
> = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENT 
> Aug 15 04:54:47 BFe450 tldcd[21016]: [ID 841094 daemon.error] TLD(0)
> Move_medium error: CHECK CONDITION 
> 


Those messages match what I'm seeing in the server's syslog:


> 
> Aug  8 11:17:21 venga tldcd[8812]: [ID 183166 daemon.error] TLD(0) key = 0x5, 
> as
> c = 0x3a, ascq = 0x0, MEDIUM NOT PRESENT
> Aug  8 11:17:21 venga tldcd[8812]: [ID 719803 daemon.error] TLD(0) 
> Move_medium e
> rror
> Aug  8 11:17:21 venga tldcd[4213]: [ID 683182 daemon.error] Cannot find 
> request
> in decode_response, pid = 8812
> 
> 


However, as far as I can tell, the device mappings are correct on the master 
and media servers.

Marianne Van Den Berg wrote:
> 
> 
> 
> Also check bptm log for dismount errors.
> 
> You should be able to obtain drive serial #'s from the display panel on
> the robot (Drive0 on the robot will be position 1 in NBU).
> Run 'tpautoconf -t' to see how the serial #'s are mapped to O/S device
> names.
> Check if NBU config is correct by comparing the above with 'tpconfig -l'
> output. (commands in volmgr/bin)
> 
> Also see TechNote http://seer.support.veritas.com/docs/259090.htm
> 
> Regards
> 
> Marianne
> 


The bptm log doesn't show any indication of dismount errors (unless I don't 
know what to look for). tpautoconf and tpconfig both match a manual mapping of 
drive number to device file.

The tech note refers to a problem opening the drives, which doesn't appear to 
be a problem here... when this happens, the tapes are ejected from the drive.

+----------------------------------------------------------------------
|This was sent by wallis AT aps.anl DOT gov via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>