Bacula-users

Re: [Bacula-users] tape and disk backup

2008-08-19 05:17:49
Subject: Re: [Bacula-users] tape and disk backup
From: Ronald Buder <rbuder AT proficom-ag DOT de>
To: Nils Blanck-Wehde <nils.blanck-wehde AT backofficeservice DOT biz>
Date: Tue, 19 Aug 2008 11:17:19 +0200 (CEST)
>Hi,

Hi
 
>I know that this question comes up every once in a while, I recently
>lost track of the "status quo".
>Is it possible to write a specific backup-job to different storage
>devices?
>I remember a discussion about "meta-devices" that could consist of
>different "real" storage devices. Is something like this planned or
>maybe even already possible?
>I think a lot of people use a backup strategie that includes something
>like this:
>Weekly full backup to tape
>Weekly full backup to harddisk
>Daily incremental backup to harddisk
>
>Depending on the amount of data being backed up and the underlying
>network infrastructure it can be a problem to do two full backups
>sequentially.
>
>It would be great to be able to do 1x full + 6x inc backups to disk and
>then move them over to tape for off-site storage and recycle the
>harddisk volumes.
>And / or it would be great to have bacula write the files it just got
>from some fd to disk AND to tape so that the data wouldn't need to be
>transported over the network twice. Plus you would have to IDENTICAL
>backups on tape and on disk and not just two similar backups.
>
>Such features are sometimes called "disk-to-disk-to-tape" or "backup
>consolidation".
>
>If things like this aren't neither possible nor planned I don't want to
>start the diskussion again. I just wondered what the status quo was...
>
>Best regards, Nils
>

We're using migration jobs to accomplish the scenario. We have most of
our backups run to a disk storage and migrate every 3 hours to our tape
library. Only a few very large jobs run onto the tape library directly.
Right now we migrate according to disk usage. We have the high water
mark set to 400GB, which amounts to a little less than 40% of the disk
storage. Our low watermark is set to 200GB, however Bacula migrates
pretty much everything right away (which isn't exactly the thing it
should do but we're not too worried about that fact). As far as our
understanding goes migrating is pretty much a copy process from pool A
to pool B and a database update. Too bad, the job logs are lost during
migration, it's pretty nifty to have a look at them in Bweb for
instance, but once a job is migrated, the logs are gone.

Ronald


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users