I apologize if I was ambiguous, it was unintentional. I use the schedule to run a single job for each client, all starting at 10 PM, with a limit of 10 concurrent jobs.
So, about 20 jobs are initiated, and 10 run while the rest wait. When one of the running jobs terminates, a waiting job starts running. A similar set of jobs run several hours later, but with a different destination (storage device) and at a different priority. When the last of the first set of 20 jobs completes, the next set begins to run as described in the third paragraph above. Thanks for the question. On Wed, 2007-03-07 at 10:44 -0500, Dan Langille wrote: > On 7 Mar 2007 at 8:36, Don MacArthur wrote: > > > Nick, > > > > I use a similar approach with one significant difference and a few small > > ones. > > > > I have have periodic (daily and weekly) pools and write (in parallel > > jobs for all the clients) all the backups to one volume to save disk > > space and reduce the management complexity. This media goes off site. > > You say "in parallel jobs for all the clients". Please elaborate. > What do you mean? > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
