Stefan,

On Tue, Nov 30, 2004 at 12:46:17AM +0100, Stefan G. Weichinger wrote:
> Hi, Brian,
> 
> on Montag, 29. November 2004 at 17:51 you wrote to amanda-users:
> 
> BC> I've broken the raid into DLEs based on the top level directory
> BC> structure of the (single large) partition. The raid is .886 PBytes.
> 
> uuuuhh ;-) Sounds tasty.
> 
> BC> Since I don't really have a spool area
> 
> you mean "holding disk" in AMANDA-terms?

Yes, "holding disk". In more generic terms a "spooling" area for the dump/tar'd,
possibly compressed files before they are DD'd to tape. Or, and this happens
periodically, there is some subtletly to the term "spooling" that I've missed
or forgetten ? (Which isn't to say the conversation wouldn't be smoother if I'd
used to proper jargon in context)

> BC> (none officially assigned anyway) the DLE's that saw an EOT from
> BC> the SDLT failed, they don't currently span tapes (no patches in
> BC> place) and don't retry. Direct to tape doesn't retry, does it ?
> 
> BC> Is there a way to force "next tape" prior to running the larger DLEs ?
> 
> I think we could need a bit more details on this.
> Based on my assumptions I think you don't have the proper value for
> "runtapes" set in your amanda.conf.

runtapes is set to 7 - and we in fact consumed multiple tapes during the run.

DLE entries...(extract) There are 14 DLEs in all, 12 of the later type.

samar   /      comp-root
samar   /usr1  comp-user
samar   /usr5/amanda {
        user-tar
        }

samar   /usr5/liw {
        user-tar
        }

samar   /usr5/hxgao {
        user-tar
        }

Since there was no holding area and we where running direct to tape it seems
that we where ok for any DLE that was both started and completed to a single
output tape volume.

However a DLE that "didn't fit" on the remaining tape didn't restart the TAR
when the next tape volume was loaded in the drive nor was it completed in the
holding area for a retry of the DD.

At least that is what it looks like to me, a not very clearly noted failure.

I'll forward the report to you.

Unfortunately the raid array is occupied by large data sets (the users are
analyzing RNA structures) and there is no knowing in advance how much data
an individual will have nor how much of it has been changed between runs.

                                                        thank you,

                                                        Brian

 
> We would need to know how big your DLEs are as well as what config you
> run to be more specific.
> 
> "taperalgo" helps you to get things in order on tapes (and maybe
> avoiding and optimizing "smaller DLEs before big ones").
> 
> -- 
> best regards,
> Stefan
> 
> Stefan G. Weichinger
> mailto:monitor AT oops.co DOT at
> 
> 
> 
> 
---
   Brian R Cuttler                 brian.cuttler AT wadsworth DOT org
   Computer Systems Support        (v) 518 486-1697
   Wadsworth Center                (f) 518 473-6384
   NYS Department of Health        Help Desk 518 473-0773