I was hoping the docs were clear :).
"Filled" means a backup contains a complete representation of the backup.
No other backups have to be merged to view/browse/restore. Any backup can
be filled. The most recent backup is always filled.
Non-filled backups are represented only as deltas (changes) from the next
more recent backup. So to view/browse/restore a non-filled backup,
BackupPC has to start with the nearest future filled backup, and work
backwards merging every delta until you get to the backup of interest.
The reason you want some backups periodically filled is that
viewing/browsing/restoring an old back would otherwise be very slow. In
your example with FullPeriod = 120 and you keep 120+ incrementals, you will
have to merge 119 backups to view/browse/restore the backup from 119 days
ago.
By default (with $Conf{FillCycle}) set to zero, every full backup is
filled, and every incremental backup is not filled. When $Conf{FillCycle}
is non-zero, some of the incrementals will be filled. In your case, if you
set $Conf{FillCycle} to 10, then every 10th backup will be filled, and
you'll only need to merge at most 9 deltas to view/browse/restore any older
backup.
Note that a filled backup does use more inodes than a delta (~3 per
directory), but otherwise doesn't use much more storage, so the cost is
relatively small in terms of storage.
Craig
On Sun, Nov 5, 2017 at 7:55 PM, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:
> What's the difference between a filled backup and a full one?
>
> Currently I have set FullPeriod to 120 as we would like to only do
> incrementals, but what's the fillcycle?
> Doc's are unclear about this, at least for non native English readers
>
>
>
>
>
> Il 6 nov 2017 2:38 AM, "Craig Barratt via BackupPC-users" <
> backuppc-users@lists.sourceforge.net> ha scritto:
>
> Removing --checksum will make an rsync full behave just like an
> incremental.
>
> An equivalent, and clearer, way to do that is to only do incrementals.
> BackupPC 4.x allows you to do that. That can be accomplished by setting
> $Conf{FullPeriod} to a large value. You should also set $Conf{FillCycle}
> to, eg, 7, so that every 7th backup is stored filled (doesn't affect the
> client transfer).
>
> I agree with Les that a reasonable compromise is to set $Conf{FullPeriod}
> to, eg, 28 or 56 so you do actually get a full backup every 4 or 8 weeks.
>
> Craig
>
> On Fri, Oct 27, 2017 at 9:42 AM, Les Mikesell <lesmikes...@gmail.com>
> wrote:
>
>> On Fri, Oct 27, 2017 at 10:11 AM, Gandalf Corvotempesta
>> <gandalf.corvotempe...@gmail.com> wrote:
>> > I'm using ZFS, so checksumming is done by ZFS itself, is not an issue
>> for me
>> > to skip any data corruption check, as zfs does this automatically
>> >
>> > What I would like is to keep load as low as possible on clients and
>> > checksumming every file is slowing down everything
>>
>> I don't currently have a system running so I can't give very specific
>> advice, but if I were doing it I'd probably try to fix the schedule to
>> do fulls every 4 or 8 weeks and make them happen on weekends if that
>> is down time on the clients, skewing them so different large clients
>> get the full on different weekends and ones that complete overnight on
>> weekdays. Alternatively, if the target data is neatly subdivided
>> into top level directories, I might try to split runs to a single
>> large host giving it multiple names, each with different shares, using
>> ClientNameAlias to point it to the same target to make it possible to
>> split the fulls into different days so each completes in the available
>> time.
>>
>> --
>> Les Mikesell
>> lesmikes...@gmail.com
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> BackupPC-users mailing list
>> BackupPC-users@lists.sourceforge.net
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki: http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
