> > > > It uses the same algorithm as a restore. The way it works now is it > > takes the most recent Full for the Job. > > > > Does Full == VirtualFull in this context? > > I always want my VirtualFull backups to use my 'Disk' pool as a source. > 'Disk' contains actual Full and Incremental backups. 'Tape' contains my > VirtualFull backups (because it is the Next Pool in 'Disk'). > > I (wrongly, obviously) assumed that because 'Tape' didn't have a next > pool setting in it, it wouldn't be considered as a source for a > VirtualFull. >
Kern, Do you think that it is valid for a VirtualFull backup to use a prior VirtualFull backup as a source? I think that there is a bug where this is the case, and I don't know that it's valid anyway. I would like to make a change so that when looking for 'source' jobs for a VirtualFull, only jobs in a Pool that has a Next Pool the same as the current job pool should be considered. So to put it in the context of my previous example: 1. Full Backup (Pool = Disk, Next Pool = Tape) 2. Incremental Backup (Pool = Disk, Next Pool = Tape) 3. Incremental Backup (Pool = Disk, Next Pool = Tape) 4. VirtualFull Backup (Pool = Tape - because job pool = Disk and Disk Next Pool = Tape) 5. Incremental Backup (Pool = Disk, Next Pool = Tape) 6. VirtualFull Backup (***) For (6), only Jobs with media in the Disk pool are to be considered James ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
