On Friday 08 February 2008 10:11:04 am Dave Howorth wrote: > Red Mop wrote: > > On Friday 08 February 2008 09:34:28 am Jarkko Ypäjä wrote: > > In your case, I would make a single cron entry for dirvish-expire at, > > say, 8pm , then at 9pm or so, run 'dirvish --vault (vaultname) for each > > vault. I would avoid trying to run more than one vault at a time on any > > given backup client to prevent disk thrashing and to minimize resource > > usage. > > In general, you don't want to use separate cron jobs for dirvish-expire > and dirvish / dirvish-runall. You almost always want to guarantee that > the two do not run at the same time and the easiest way to do that is to > run them sequentially in a single cron job. > > You *can* have multiple separate scripts for different vaults, but do > all the tasks associated with each vault in a single script. >
I assume so that expire doesn't nuke a backup-in-progress. In that case, a script for server1 with 3 vaults dirvish-expire --vault server1-vault1 dirvish-expire --vault server1-vault2 dirvish-expire --vault server1-vault3 dirvish --vault server1-vault1 dirvish --vault server1-vault2 dirvish --vault server1-vault3 You can always get fancy with loops and variables. Can you do a multi-threaded bash script, perhaps via backgrounding tasks? _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
