Hello,

On 1/19/2006 12:08 PM, Ralf Gross wrote:
Hi,

I want to backup 2 of our server to tape (AIT-2, 50GB native, 65-70GB
compressed, TLS-4210 12 slot autochanger). bacula 1.36.3 (debian sarge,
maybe I'll build bacula 1.38.4 from source...) is running and I'm already
able to backup to tape.

First, upgrade to 1.38.whatever-is-current.

Using volumes from more than one pool in one autochanger is not supported with 1.36, and you will probably run into problems sooner or later.

Both machines are also backed up to disk by an other backup tool, but I
want to have a backup on tape, just to be safe...

What I want:

Server 1:
 * ~55GB data
 * full backup each Sunday 6am
 * no inc/diff backup
 * 2 tapes/slots for 2 backups/weeks

Server 2:
 * ~190GB data (takes 10 hours and more...)
 * monthly backup at the first Saturday 8pm of the new month, this should
be archived for 2 years
 * regular full backup each Friday at 7pm, incr. backup Moday to Thursday
at 7pm

Because I'm only rarely at the place where the autochanger is located, I
can't change the tapes every week. My goal is to change only the archive
tapes once a month and - if possible - leave/reuse the other tapes.

I'm not quite sure how to setup bacula to achieve this. Should I really
use 2 differnt jobs and differnt pools for the regular/archive backup of
server 2?

One job per each combination of client and fileset. You set the levels in the schedule. See the manual for more information.

I'd create a pool with 2 tapes for server 1, and a pool with 3 tapes for
the archive job. Thus 7 tapes are left for the regular jobs. But the 2
regular full backups already need 6 tapes, thus only 1 tape is left for
the incr. job.

Determining the right strategy is, obviously, up to you. (You wouldn't be the first to discover that your autochanger doesn't fit your needs, though.)

Apart from that, I don't exactly understand why you make a distinction between archive and regular jobs. The simplest solution is to keep the full backups as long as you need them, and have the differential and incremental jobs go to pools that cycle more quickly.

In that case, you could leave the diff/incr volumes in the changer and only remove the full backup volumes.

I'm also very unsure about the right settings for
retention/prune/purge/recycle.

That's something you should look up in the manual, then - I couldn't explain it much differently.

Maybe I'm a just bit to confused at the moment ;)

Maybe... start with a simple experimental setup, with a small fileset, disk based volumes, and run your backups multiple times a day. This would allow you to observer the volume management live.

Arno

Ralf



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


--
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to