On Wed, Jun 09, 2010 at 12:05:34PM +0400, Alexander Pyhalov wrote:
> Hello.
> I have some questions about Virtual Full backups. As I understood, VF 
> backups should use separate volume pool. We are going to use bacula for 
> making backups of a lot of data (>2 TB, about 10 servers). In this 
> circumstances I'd like to avoid making Full backup. I'd like to make one 
> initial Full backup and after only Incremental and Virtual Full.
> But how can I achieve this? Virtual Full use separate pool and as far as 
> I know we can't use one pool for reading one VF backup and writing other 
> one. So I assume I must make VF and before making next VF backup the old 
> one should be moved to other pool (on separate storage).
> What is the best way to do it? We use file storage. Should I modify my 
> Job to run after job script which moves VF volume to other pool? But how 
> will I recognize that it is VF backup and not incremental backup for the 
> same job?

Hello,
I have been using Virtual Full for a while now. Doing something like the
following seems to work for me (I don't recall having to do anything else
special):

Schedule {
  Name = "Daily"
...
  Run = Level=Incremental mon at 18:50
  Run = Level=Incremental tue at 18:50
...
  Run = Level=VirtualFull sun at 18:50
}

Pool {
  Name = "FullPool"
  Maximum Volume Jobs = 1
...
}

Pool {
  Name = "IncrPool"
...
  Maximum Volume Jobs = 1
  NextPool = "FullPool"
}

Job {
...
  Schedule = "Daily"
  Full Backup Pool = "FullPool"
  Incremental Backup Pool = "IncrPool"
...
}


------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users