Ian,
I'm wondering how you have your multiplexing and multi-streaming set up
as well as how you have your storage units defined. The 50 error may be
caused by all the jobs going to the same storage unit at one time.
Start by creating two storage units for each media server use a 0 and a
1 before each Storage Unit Name to make sure you have the spread evenly
in the Storage Unit list allot half of the available tape drives in each
unit. Set Max Fragment size to 2048, and Max multiplexing per drive to
4. In your client policy make sure the Allow multiple data streams is
enabled and in the attributes of the policy the multiplexing is set no
higher then 4. Also check to make sure your drives are all up and make
sure that they stay up. This will help you determine if the problem is
with only one of your media servers or if it the problem is happening on
all your servers. Also if you happen to set all your backups to start
at the same time each night, you may have to increase your timeout in
queue in your bp.conf on the master and media servers. I know a couple
of other things to try if this doesn't work so let me know if you need
some more help.
Thanks,
Judi
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
Ian.Fehring AT nab.com DOT au
Sent: Saturday, March 11, 2006 11:45 PM
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
|
