I've been playing around with using Virtual Full backups for off-site
backups, and generally I really like it. But of course I have a problem.

First, a bit of background: We are doing disk to disk backups for daily
backups. I have the full backups spread across the week to even the load
and keep the backup window sized about the same across the week.

Our off-site backups happen once a week and go onto LTO-6 tapes and then
are stored, well, not on-site.  :)  We keep a few months of tapes stored
off-site and then eventually re-use the tapes.

I was doing Copy jobs to make the off-site tapes, but then I had to
schedule full backups close to the Copy job for them to be fairly fresh.
 Also, since you can't recover from a Copy job until the source job has
been purged, testing the off-site backups was a pain.

So I tried Virtual Full and they are just as fast as Copy jobs for me.
(Even faster if I allow the Virtual Full job to spool to disk first.)
And I get the freshest data for the backups.

But the problem is that sometimes, especially during my testing, the
Virtual Full tries to use the last Virtual Full backup as the base.
Which doesn't work since that is on tape and not on disk.

Is there a way to get the Virtual Full job to ignore the backups stored
on tape when it does a new one, and only use the on-disk Full backups as
the base? All of them are in different pools, so I had thought that that
would do it, but it doesn't.

job {
  name = "agena-virtual"
  client = agena
  job defs = "virtual-full"
}

job defs {
  name = "virtual-full"
  type = backup
  level = virtual full
  file set = "standard"
  accurate = yes
  messages = "standard"
  write bootstrap = "/var/db/bareos/%c.bsr"
  pool = "full"
  full backup pool = "full"
  differential backup pool = "differential"
  incremental backup pool = "incremental"
  spool data = yes
  next pool = "offsite"
}

pool {
  name = full
  pool type = Backup
  next pool = offsite
  label format = "full-"
  volume retention = 30 days
  maximum volume bytes = 16 GB
  maximum volumes = 1024
  storage = disk
}

pool {
  name = differential
  pool type = Backup
  label format = "differential-"
  volume retention = 15 days
  maximum volume bytes = 16 GB
  maximum volumes = 1024
  storage = disk
}

pool {
  name = incremental
  pool type = Backup
  label format = "incremental-"
  volume retention = 15 days
  maximum volume bytes = 16 GB
  maximum volumes = 1024
  storage = disk
}

pool {
  # No "Label Format" disables automatic volume labeling
  name = offsite
  pool type = Backup
  storage = lto6-1
  volume retention = 30 days
  volume use duration = 1 day
  purge oldest volume = yes
}
storage {
  name = disk
  address = bareos-sd.meridian-enviro.com
  password = "foo"
  device = disk-0
  device = disk-1
  device = disk-2
  device = disk-3
  device = disk-4
  device = disk-5
  device = disk-6
  device = disk-7
  device = disk-8
  device = disk-9
  maximum concurrent jobs = 10
  media type = file
}

storage {
  name = lto6-1
  address = bareos-sd.meridian-enviro.com
  password = "bar"
  device = lto6-1
  maximum concurrent jobs = 2
  media type = "lto-6"
}



-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to