Veritas-bu

[Veritas-bu] Jobs failing with error 50

2006-03-13 09:30:32
Subject: [Veritas-bu] Jobs failing with error 50
From: CJManders AT lbl DOT gov (Christopher Jay Manders)
Date: Mon, 13 Mar 2006 06:30:32 -0800
You will also want to look at the logs to isolate where the 
communication breakdown is.

Enable verbose logging with this in your /usr/openv/netbackup/bp.conf 
file, on both master and media servers:
VERBOSE = 5

Then, create some log directories on the master and media server. All 
under /usr/openv/netbackup/logs:
On the master:
bptm
bpbrm
bpsched

On the media server:
bpbrm
bptm

You might want to look at the client-side as well. With a bpbkar and 
bpcd log dir. Does the new nedia server get a forwards and reverse DNS 
mapping somewhere? What does 'bpclntcmd -hn mediaserver.you.com return?

If you have the logging going, then what are the last 20 lines of each 
of these. That might tell a bit more of a story.

You may also want to have it re-queue on error using the bp.conf directive:
QUEUE_ON_ERROR (requires all nbu daemons to be bounced to take effect)

And, if that does not get us there, then you will want to do a bpps -a, 
and kill the ltid process and spark up a new one with the '-v' flag.
You will note that all of the VM stuff is then -v. Create the vmd and 
ltid log dirs to get the logs. On the media server.

I usually (on Solaris) use truss -p on the PID of the vmd while running 
a backup to see what it gets back. Can also be very entertaining...and 
enlightening.


Hope that helps.

Cheers!

--Chris

>
>-----Original Message-----
>From: Ian.Fehring AT nab.com DOT au [mailto:Ian.Fehring AT nab.com DOT au] 
>Sent: 12 March 2006 05:45
>To: Veritas-bu AT mailman.eng.auburn DOT edu
>Subject: [Veritas-bu] Jobs failing with error 50
>
>
>
>
>Hi all,
>
>I am currently have some major issues with my NetBackup 5.1MP3A environment
>(running on Solaris systems) where ALL my jobs fail with an error 50 after
>random amounts of time. This includes both Active, and Queued jobs.
>
>Symantec has told me they think it is a network related issue between my
>master server and my media server, and to put all the IP addresses of my
>media servers in the /etc/hosts file (which I have done), but the jobs still
>fail. Things may work OK for a few hours, and some of my jobs complete, but
>then all of a sudden, all jobs fail with an error 50.
>
>Anyone have any thoughts on this, or seen it before.
>
>
>One a related issue (I think), we are also getting jobs Queued for 1 hour
>and then failing with 219 errors, even though other jobs may be going to the
>same storage unit successfully. The 1 Hour timeout is due to a bpsched
>parameter somewhere, but why do the jobs sit in the Queued state and then
>after this timeout, fail with a 219 error?
>
>Any help on any of this would be very appreciated. This has been going on
>for over a week now, and we do not seem to be getting very far
>                                                                            
> Ian Fehring                                                                
> Lead Technical Specialist, Storage Management                              
> National Australia Bank                                                    
>                                                                            
> Level 1, 122 Lewis Rd                                                      
> Tel: +61 (0) 3 9886 2367  |  Fax: +61 (0) 3 9886 2700  |  Mob: +61 (0)417  
> 520 953                                                                    
> Email: Ian.Fehring AT nab.com DOT au                                          
>     
>                                                                            
>
>
>
>
>National Australia Bank Limited - ACN 004 044 937
>This email may contain confidential information. If you are not the intended
>recipient, please immediately notify us at postmaster AT nab.com DOT au or by
>replying to the sender, and then destroy all copies of this email. Except
>where this email indicates otherwise, views expressed in this email are
>those of the sender and not of National Australia Bank Limited. Advice in
>this email does not take account of your objectives, financial situation, or
>needs. It is important for you to consider these matters and, if the e-mail
>refers to a product(s), you should read the relevant Product Disclosure
>Statement(s)/other disclosure document(s) before making any decisions. If
>you do not want email marketing from us in future, forward this email with
>"unsubscribe" in the subject line to Unsubscribe AT nab.com DOT au in order to 
>stop
>marketing emails from this sender. National Australia Bank Limited does not
>represent that this email is free of errors, viruses or interference
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>This email is for the intended addressee only.
>If you have received it in error then you must not use, retain, disseminate or 
>otherwise deal with it.
>Please notify the sender by return email.
>The views of the author may not necessarily constitute the views of EADS 
>Astrium Limited.
>Nothing in this email shall bind EADS Astrium Limited in any contract or 
>obligation.
>
>EADS Astrium Limited, Registered in England and Wales No. 2449259
>Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, 
>England
>_______________________________________________
>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>