Glynd wrote:
> Thanks for this as it is exactly what I want to do too (except the annual
> full BUP)
>
> I am a little confused about setting up the jobs. If there are 2 jobs per
> client, how do they write tothe pools full1, incr1, full2 and incr2? I have
> all mine set to level = incremental and when there is a new volume, Bacula
> automatically upgrades it to a full but to the same (default) pool.
>
> Would you explain a little more for me, please?
>   

The reason for two jobs per client is to use different pools and 
schedules on odd weeks than on even weeks.

In the below, notice that USB drive 1 is to be somehow mounted at 
/mnt/usbdrive1 and drive 2 at /mnt/usbdrive2. Also note that the drives 
contain a directory named 'backups' where the Bacula volume files will 
be created. This is to prevent Bacula from writing to the root partition 
should the needed USB drive not be mounted. You can mount the drives 
manually, with autofs, or with Bacula's built-in removable media 
mounting mechanisms.

# bacula-sd.conf
Device {
  Name = usb-drive-1
  RandomAccess = yes
  DeviceType = File
  MediaType = File1
  ArchiveDevice = /mnt/usbdrive1/backups
  LabelMedia = yes
}
Device {
  Name = usb-drive-2
  RandomAccess = yes
  DeviceType = File
  MediaType = File2
  ArchiveDevice = /mnt/usbdrive2/backups
  LabelMedia = yes
}

# bacula-dir.conf
Storage {
  Name = HDD1
  Address = sd.domain.name
  Device = usb-drive-1
  MediaType = File1
}
Storage {
  Name = HDD2
  Address = sd.domain.name
  Device = usb-drive-2
  MediaType = File2
}
Pool {
  Name = odd-week-pool
  Storage = HDD1
  PoolType = Backup
  Recycle = yes
  VolumeRetention = 373 days       # allow extra time for next full 
backup to be made
  VolumeUseDuration = 7 days
  LabelFormat = "hdd1-"
}
Pool {
  Name = even-week-pool
  Storage = HDD2
  PoolType = Backup
  Recycle = yes
  VolumeRetention = 373 days       # allow extra time for next full 
backup to be made
  VolumeUseDuration = 7 days
  LabelFormat = "hdd2-"
}
Schedule {
  Name = odd-week-schedule
  Run = Level=Full on jan 1st sun at 00:02
  Run = Level=Incremental  w01 at 00:01
  Run = Level=Incremental  w03 at 00:01
  Run = Level=Incremental  w05 at 00:01
  ...
  Run = Level=Incremental  w53 at 00:01
}
Schedule {
  Name = even-week-schedule
  Run = Level=Full on jan 1st sun at 00:02
  Run = Level=Incremental  w00 at 00:01
  Run = Level=Incremental  w02 at 00:01
  Run = Level=Incremental  w04 at 00:01
  ...
  Run = Level=Incremental  w52 at 00:01
}
Job {
  Name = client1-odd
  Client = client1
  Pool = odd-week-pool
  Schedule = odd-week-schedule
 ...
}
Job {
  Name = client1-even
  Client = client1
  Pool = even-week-pool
  Schedule = even-week-schedule
  ...
}


> What do I do with the catalog? Does this remain as it is, i.e. just one
> catalog for all the jobs and all the pools, do I use one of the new ones
> (full1, etc), or do I keep the default pool?
>
>   

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users