On Friday 11 October 2002 03:56, Toralf Lund wrote: >> > the person managing the tapes (not me) to know which one to >> > bring. I thought about using labels of the form <week no>.<run >> > no> or simple sequencing, but I decided that would be more >> > confusing.
In which case have amanda do a printout of whats on each tape, with will I believe also contain the date, and keep that printout with that tape until such time as that tape is over-written. The paper copy effectively becomeing your "label". >> Your confusion level may vary from mine and from the person >> managing the tapes. >> I would certainly be confused when amanda needs a tape labeled >> Monday on Wednesday. > >Well, I may be wrong, but I'm assuming that would be the case only > if an exceptional event that would have to be addressed anyway, > occured. > >> Trust the collective experience of the list, they will get out >> of your planned sequence. > >I still find it hard to convince myself that a simple sequencing > number, like most people suggest, would be better. > >> > Forgot to mention this earlier: I'm not using incrementals at >> > all. >> >> Tapes >> >> > from the same week will contain full backups of different >> > directories, >> >> and >> >> > a given file is backed up (only) once a week. >> >> When you figure out how to get amanda to do this please let the >> list know. >> It is very atypical amanda usage. > >Is it really? I'm merely using "skip-incr", and the total amount > backed up is a little smaller than the space on runspercycle > tapes. I don't see but one problem with that, and it comes in terms of the maximum filesize vs the size of one tape. Because amanda cannot, and likely never will for dependability reasons, span a single disklist entry across 2 or more tapes, instead restarting the failed dump on the next tape when EOT is encountered, it makes sense to have the disklist entry's broken up into pieces smaller than a tape. This translates to less wasted tape when amanda has to move on to the next tape in the current invocation. >It seems to me that: >1. Under these conditions, Amanda won't try to do a 2nd full dump > of any of the data, even though the config allows it to do that > (?) Also, if it does, I don't really care. >2. Trying to run incremental dumps would be meanlingless as there > is hardly any room for the data, although some of it might fit in > at the "holes" left when there is more room on a tape, but not > enough to allow a full dump of a dirlist entry to be written. >- Toralf Two questions come to mind, the answers to which may lead us to a better suggestion box filler here. 1. How big are the largest of these files expressed as a percentage of a tapes capacity? 2. Do their names regularly change? And a subquestion might be asked, how compressable are these files? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.17% setiathome rank, not too shabby for a WV hillbilly
