Hi again, Arno!
>Oh... I don't feel like going over your configuration in detail now,
>sorry ;-)
>
>The basic setup is rather straight-forward, though:
>
>Define the pools you need (like one pool for full backups, one for
>incrementals).
>Determine how long you want to keep the data on the volumes.
>Determine how many backups that represents (like, one weekly backup
>for all clients, kept for six weeks, means you need storage for six
>times the weekly amount of data for these backups). Add some space for
>future growth of the data. A factor between 1.2 and 1.5 might be a
>good start, but that depends on your users and so on.
>Calculate the number of volumes you need, and add one or two volumes -
>just to make sure you really always have a usable volume ready.
>(The above is more or less my approach when I don't know much about
>the kind of data to expect - you can refine that, but most of the
>time, it's easier to use more storage than to fine-tune the setup to
>minimize the storage used to the absolute minimum.)
>Now you can easily setup the volumes you need - just label them, buy
>the tapes and barcode labels, set up the scratch pool - however you
>handle this.
>
>The directives you mentioned are very simple to set up:
>Accept Any Volume - remove this. It's no longer used, was never really
>used, and what it's supposed to do is done by default.
>Volume Retention - set this to the time you want to keep your backups.
>When you use different pools for full, differential, and incremental
>backups it's not a good idea to set a longer retention times for
>incrementals than for full backups :-)
>Use Volume Once - Deprecated by now... also, if you want to recycle
>volumes (which is necessary to keep intervention to a minimum) you
>don't want it anyway.
Thank you! This is all I most desired, if you would be so kind, and
you were. Just an idea of the things to do, from someone who knows Bacula
stuff much better than I.
I'll work on these things. Thank you very much!
>> Really? That probably isn't serious. My original intention was to
>> be able to tell by the filename the age of the file, before it started
>> recycling *some* volumes (filenames). :-)
>
>Well, you know that I prefer to do things differently :-) or rather,
>to let Bacula do that. Of course, if you decide to keep certain jobs,
>now you'd have to query the catalog and find the volumes you need to
>store. Or use migration.
Thank you! I'll check these out! :-)
Barry
--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
Software Engineer, ITT Corporation | (My personal home web page, last
| updated February 17, 2005)
|
[EMAIL PROTECTED] <- personal | Re-Vita Products:
[EMAIL PROTECTED] <- Work ONLY | http://www.re-vita.net/barrybond
| Re-Vita Distributor Information
Home office: 407-382-2815 | http://www.re-vita.net/barrybond-2
Work: 321-494-5627 | Toll free order: 1-888-820-5531
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
