Hi Ian
Hmmmmm well my first thought was incorrect storage unit for the policies -
but you mention other clients appear to be ok - I do wonder if its worth
re-creating the storage units again.
In terms of the client machines that appear to hang in Activity Monitor -
has anything changed on the client side? (ie: any updates or config
changes).
Might be worth checking the BPCD and BPBKAR logs if enabled. It potentially
could be a client side problem - lack of resources or disk space if you have
an open file agent enabled.
Restarting of the Netbackup Services (if not done so already) may help!
Also, within the policies (if you have not done so), rather than use hosts,
could the clients be entered as their IP address - So, if the client is
known as COMPUTER1 in the policy, remove it and add its IP of 192.11.11.1 as
an example (or whatever its IP is).
Stop and restart the client service again
Hope this is of some help.
Simon Weaver
Technical Support
Windows Domain Administrator
EADS Astrium
Tel: 02392-708598
Email: Simon.Weaver AT Astrium.eads DOT net
-----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
|
