On 7/28/2009 3:59 PM, Daniel De Marco wrote: > Hi, > > I'm trying to use bacula to keep two independent sets of backups for > some particular machines. I have two storage daemons setup (one of them > offsite) so I can't use Migration or Copy Jobs. > > My first try has been to setup a second set of jobs to do the backups to > the offsite location. > For example for client dummy I have the first job named "BK-dummy" and > a second one named "BK-dummy-offsite". The two job definitions use > different Storage and different Pools. > My understanding is that, since the Job names are different, bacula > would consider them independent, but what happens is that bacula seems > to consider both jobs as related in some way. For example if I start an > incremental backup for BK-dummy-offsite, bacula uses the last backup for > BK-dummy as reference point if that's the latest job for the client. > Is there a way to prevent this? One possibility would be to have two > different Client definitions, but there must be a better solution... > > I'm pretty sure Bacula considers the file set the backup unit of relevance here. Use two identical but differently-named FileSet definitions in the two jobs, and you should get what you want.
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users