ah ha!
We are backing up the amanda server, a FW, the old database
system behind the FW and this new system. The DBA has been
installing/configuring additional SW and databases and the
non-global zone has grown to over 200 Gig.
We are still using an SDLT 320 as the SL24/LTO4 hasn't been
delivered.
No wonder my backups keep failing. We are simply out of
capacity - I know amanda timeout didn't feel right. I failed
to recheck that the DBA had done and the limits on the
available HW.
Thanks for your time... I now have a definite direction to
move in, one that is outside the scope of amanda. [Too bad,
I know how to cadjole amanda, there is little I can do to
finess more space out of the SDLT.]
thank you,
Brian
On Wed, Nov 18, 2009 at 05:20:36PM -0500, Nathan Stratton Treadway wrote:
> On Wed, Nov 18, 2009 at 16:56:47 -0500, Brian Cuttler wrote:
> >
> > Yes, I saw what you saw in the gtar report - I can only
> > surmize that the error is written in a confusing mannor.
> >
> > /proc is definitely a directory that contains files that
> > are named for process ids that can be found on the system.
>
> Well, I suppose it's possible that for some version or other of GNU tar
> this could just be because of a misleading error message, but my hunch
> would be that someting more tricky is going on. (In other words, I
> don't think tar would output that error message unless it really was
> trying to back up "proc" as a file -- which seems like it would be a bad
> sign.... As long as it was treating "proc" as a directory, you'd expect
> tar to report changes with "file changed as we read it" or "cannot stat:
> no such file or directory" errors on the files found underneath that
> directory, and not as a message realted to the directory itself.)
>
> I take it you did tests like running
> ls -l /export/zones/dorldom1z1/root
> ls -ld /export/zones/dorldom1z1/root/proc
> ls -l /export/zones/dorldom1z1/root/proc
>
> from within the environment that the Amanda client software would run
> while doing this backup?
>
> (I don't know that this necessarily has anything to do with your timeout
> problem; I'm just saying that message seems like a red flag worth
> investigating to make sure it doesn't indicate a deeper problem. Though
> it's certainly possible that it's just an artifact related to Solaris
> zones, which I don't have any experience with myself.)
>
> Nathan
>
>
>
> ----------------------------------------------------------------------------
> Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
> Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
> GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
> Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
---
Brian R Cuttler [email protected]
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
