Ralf Auer wrote:
> Hello Frank,
>
> obviously I found an expert... Thanks for your reply.
Eh, I've just read the manual a few times =)
> The reason why I decided to have so many different pools was motivated
> by the (confusing) examples in the manual, so I DID read it, even more
> than twice ;-)
>
> My problem is, that I have to write to both tapes simultaneously for
> timing reason (but spooling to my HD-RAID). That's why I don't have a
> tape changer and introduced the two different pools for 'full' and
> 'incremental'. If it is possible to write in parallel from within only
> one pool, that would make things easier.
Absolutely - just make sure that you've got all of your max concurrency
settings set correctly (there's a chapter in the manual on this), and you can
have multiple jobs of the same priority running at the same time. Note that
it's a really good idea to use spooling in this scenario.
> Same for the 'mo-fri' pools. I thought I would need that complicated
> setup in order to tell bacula to start a new tape every day as the
> example given in the manual shows.
> Thanks to your explanation I know now, that this is not necessary and
> can be achieved by the 'volume use duration' setting. That's perfect and
> answers one of my questions in the last mail completely.
Great!
> But it brings up the retention period question:
> * Assuming I do the 'full' and the 'incremental' backups, the retention
> periods for both would be the same, 3 weeks,right? The 'incrementals'
> can be taped over, after the 'full' has been replaced by a newer 'full'
> and I don't want to keep the 'fulls' longer than the incrementals... Or
> is it 3 weeks-1 day ? To avoid double entries for the first clients?
You could have them set the same, but you don't have to.
Also, just a quick clarification - retention period control how long records
are kept in the database. You want to look at recycling to determine when
Bacula will overwrite an existing volume with new backup data.
As for double entries, that's not a problem at all - the catalog will keep
track of everything for you, and on restore, you can just tell Bacula to use
the most recent backup, and it will just do the right thing.
> * Assuming I had also 'differentials' once a week as you suggested, the
> retention periods would be 3 weeks for 'full', 1 week for 'diffs' and 1
> week for 'incrementals', right ? Therefore, to avoid buying a third tape
> drive I would have to put the 'diffs' into the 'incremental' pool,
> because then retention periods differ. Do I get this right?
That sounds right to me, but you would definitely want to test it out to make
sure - getting all of the retention periods right can be a little tricky.
> And a more practial question:
> * 'Amanda' has this nice feature to send me a mail which tape to put
> into each drive before leaving office ('amcheck' cronjob).
> How does bacula remind me which tapes to put in today ?
I've never dealt with this myself (I just use a library), but I believe that
suggestions on this have come through the mailing list in the past.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
