On Tue, Dec 16, 2014 at 06:08:47PM +0000, Debra S Baddorf wrote: > 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. > > Then again, for “fitting the most onto the tape” you want to put the > biggest thing onto the tape first, > so I’ve stopped asking the above question. But it might be useful to know. >
In what state, or timing, do you want the server's backup created. Not taped, but created. If it can be before the backup run, break it into a separate amdump that does not flush to tape. Then the regular amdump, sans server, that flushes the holding disk immediately. If you want the server backup after the other amdumps, do the reverse the above two amdumps and let the server dump sit on the holding disk til the next day's taping. If you have tons of holding disk, let both amdumps collect there. I suspect, but can't confirm, that amflush will flush in the of its "host" arguments. So after the dumps you could run an amflush listing the server first. Jon > Deb Baddorf > Fermilab > > On Dec 16, 2014, at 8:17 AM, Stefan G. Weichinger <[email protected]> wrote: > > > Am 16.12.2014 um 14:42 schrieb Dennis Benndorf: > >> Hi Stefan, > >> > >> did you consider using > >> dumporder "TTTTT..." > >> in order start with those DLEs which take the longest time? > > > > I *never* really understood that parameter! > > If that does the trick ... sure, we will try :-) > > > > Thanks, Stefan > >>> End of included message <<< -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
