> I think you are right. Volumes on HDD 1 will be in one pool and
> volumes on HDD 2 in another. For each client, there will be a full
> backup in both pools created by manually running level=full jobs. The
> schedules will automatically run daily backups, odd weeks storing into
> volumes in one p
I don't think that will do what you want. The reason for 4 pools is to
keep the incrementals on drive 1 relative to the fulls on drive 1, and
the incrementals on drive 2 relative to the fulls on drive 2. If you
have only 2 pools, then the incrementals will be relative to the last
full b
> I'm doing a similar backup but with 3 disks :
> - 2 disks (A and B) connected as RAID.
> - a third disk.
> When I want to change a disk, I replace B with C and I rebuild the
> RAID. :) I'm using mdadm on Linux
Now this is really briliant idea! Thanks for sharing it. Currently I
don't have an
You could probably do this with 4 pools. Each drive would contain
volumes in two pools, one for full backups and one for incremental
backups. For each client there would be two jobs, one backing up to
drive 1 using pools "full1" and "incremental1" and another backing up to
drive 2 using
Hi John,
> After that I would adjust my scheduling to run the full backups on
> Friday night so that after a change Full backups will be made.
That's exactly what I want to avoid. I would like to:
Do a full backup twice (once per HDD) per year and daily increment
otherwise.
In the sam
Hi All,
I would like to configure the Bacula in following way
use 2 external hard disks connected over the USB
change these 2 HDDs once per week (let's say on friday afternoon)
every day doing a backup - incremental (of several servers)
once per year do a full backup
if o
