I've actually found what the issue is.
I contact VERITAS support and it seems it's because NBU 6 (it may also
happen for older versions) apparently assumes that open file backups is
desirable unless otherwise specified. To resolve, I had to add the host
to Client Attributes of the Master and then explicitly uncheck the open
file backups box.
This is contrary to how we thought it worked.....
This worries me a bit; if open file backups are generally done by
default (unless otherwise specified) how do you control the
location/size, etc. of the cache file? Could this lead to backup jobs
not completing (156 errors) if there is not enough space for the cache
file, out of the box?
Cheers,
Tim
________________________________
From: WEAVER, Simon [mailto:simon.weaver at astrium.eads.net]
Sent: Monday, 26 June 2006 3:58 PM
To: Wilkinson, Tim; veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] NBU6 with NBU 5.1 NT4 client mounts but never
startsbacking up
Tim
First thing I can think of is the TRACKER.exe is that running in the
TASKBAR (near the clock)?
Any AV running at the same time perhaps? Turning that off can help?
Also, what if you backup single drives?
I hate tracker.exe :-)
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: Simon.Weaver at Astrium-eads.net
<mailto:Simon.Weaver at Astrium-eads.net>
-----Original Message-----
From: Wilkinson, Tim [mailto:Tim.Wilkinson at dsto.defence.gov.au]
Sent: 26 June 2006 02:37
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] NBU6 with NBU 5.1 NT4 client mounts but
never startsbacking up
Hi,
We have NBU6 Master/Media servers and few NT4 clients (w NBU 5.1
MP5).
We're having issues where the ALL_LOCAL_DRIVES directive starts
to run; it mounts a tape but never progresses from there. Strangely,
there is Exchange 5.5 on one of these boxes that backs up fine, but for
some reason it is having issues actually writing the A_L_D.
Does anyone know what might be causing this behaviour? It
doesn't actually exit with any errors until it is stopped by admin (at
least it didn't stop itself after 2 days or so). It doesn't seem to be
the tape drive other file system jobs run fine.
Cheers,
---------------------------------------------------------------------
Tim Wilkinson
I.T. Support Officer
Science Corporate Information Systems
Defence Science & Technology Organisation
Department of Defence
Tel: (02) 96921484
Fax: (02) 96921562
Email: tim.wilkinson at dsto.defence.gov.au
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060626/fd7e1e35/attachment-0001.html
|