If your serious about it, you could always script your way out of it. Set the file and job retention to the higher of the two desired values, then conjure up an sql statment that select the jobs that you want to have the lower retention periods and purge the records desired in a script.
You could use the scripting language you feel most comfortable. Then run the script in cron or run after job. Here is an example of a sql statement SELECT Job.JobId FROM job JOIN JobMedia ON JobMedia.JobId=Job.JobId JOIN Media ON JobMedia.MediaId=Media.MediaId WHERE media.volumename IN ($medialist) ORDER BY Job.EndTime Limit 1 ;" ; But you could have it select jobs of a certain jobname or client that are older than a certain age then purge files from those jobs. It only takes a bit to set up. Dirk On Wed, 2009-06-24 at 21:29 -0400, teksupptom wrote: > Trying to work around the file/job retention question above, is it possible > to set up multiple Client resources for a single client machine, without > running multiple file daemons on the client? > > The way I read the manual, the name given to the client file daemon is what > needs to be used for the client resource in the Director config. Is that > true, or am I reading it incorrectly? > > Thanks for any help, > Tom > > +---------------------------------------------------------------------- > |This was sent by tomisom.s...@gmail.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +---------------------------------------------------------------------- > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
