On 02/06/14 23:30, Phil Stracchino wrote:
> On 06/02/14 09:16, Steven Haigh wrote:
>> On 02/06/14 23:01, Kern Sibbald wrote:
>>>
>>> Hello,
>>>
>>> Your comments are quite valid. However a better approach to
>>> solving the problem is when people like you (especially English
>>> speakers) find the solutions, you modify the documentation to
>>> include the correct words for someone not familiar with the
>>> software to understand it, and then send that in as a
>>> contribution, then everyone (including me) benefits from your
>>> work :-)
>
>> At this stage, I'm still not sure I have things set up correctly
>> myself. I'm not quite clear with all knobs and buttons in Bacula.
>> TSM is all coming from a file based - not job based. This means
>> that things like retention are handled per file - not per job.
>
>> I'm not exactly clear what will happen with a file that is still a
>> system that is backed up and the retention time expires. Is that
>> file backed up again on the next incremental? Does it not get
>> backed up at all again?
>
> If there is no existing non-expired backup of a file, it should get
> backed up on the next backup, whatever level.
>
>> My current config does a Full backup once - then a nightly
>> incremental. I'm not exactly sure that this will do what I want -
>> but I can't find anything that says either way...
>
> It works, but I don't recommend it. I suggest interspersing periodic
> Differentials among the Incrementals to "reset the baseline" for the
> incrementals and reduce the number of Incrementals you need to keep
> around (and restore from).
>
>> Some of my backups are multi-Gb and are over a slow (5Mbit) link -
>> as such, incrementals are good - and full backups take hours. I'm
>> not convinced that Bacula handles this case well however - but I am
>> yet unable to prove one way or another.
>
> Have you considered virtual full backups? After you run a
> Differential, you could create a virtual full backup (though I think
> "synthetic full backup" might actually be a better term) from the
> Differential and the last Full. This would allow you to always have a
> recent Full backup on hand without tying up the slow connection for
> many hours while a new Full backup runs.
I can't say I have. I did read parts of the documentation on this - but
I didn't quite understand how it was actually doing what it says.... The
amount that actually changes per backup is usually fairly small. I have
2 x 20Gb File volumes on the local HDD - and that will probably handle
100+ incrementals before me having to figure out what to do with them...
Is there a newbie guide to the different levels of backup? I can go read
this and then come back with any further questions / clarifications etc...
--
Steven Haigh
Email: netwiz AT crc.id DOT au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
