Expounding on Jon’s ideas: how about, after all the backups are done and finished for the day. Then, I run another job amdump <config> —no-taper <dumphost> <all-its-DLEs>
This would leave them sitting on the holding disk, waiting for tonight’s backup job. In fact, I’ll do that right now, manually. Tonight, I’ll see if they happen to flush to tape first. They might not, since I’ve got “pick biggest file” as my taperalgo . But it’s an interesting experiment. Deb Baddorf Fermilab On Dec 17, 2014, at 3:20 AM, Chris Ritson <chris.rit...@newcastle.ac.uk> wrote: > > > At one point I thought it might help disaster recovery if Amanda's own > status information was last on the tape so I used a starttime in one specific > dump-type, picking a time which, at least 90% of the time was after the > overnight run normally finished. I guess if something had to be first you > could use a starttime in everything else (presuming that the Amanda run > starts at a fixed time of course). > >> -----Original Message----- >> From: owner-amanda-us...@amanda.org [mailto:owner-amanda- >> us...@amanda.org] On Behalf Of Debra S Baddorf >> Sent: 16 December 2014 18:09 >> To: amanda-users Users >> Cc: Debra S Baddorf >> Subject: Re: How to priorize DLEs? >> >> I've often wondered (and then dropped the idea) - is it possible force a >> particular DLE X to be first on the tape? >> For instance, it seems useful to have the backup machine's own backup to >> always be first, >> in case of catastrophe. My impression was that it was NOT possible.
