Re: Fresh snapshot

Hi,

there is indeed no way out of the box to do this.

The simplest way to realize this would be to create a new backup repository each week, it would then always have one snapshot and 6 deltas. Keeping the 4 youngest repositories, you would have reached your goal.

Hope this helps,
Eric

On 13 October 2021 23:03:31 UTC, billy noah <[email protected]> wrote:
>Hello,
>
>The older snapshots in my backup scheme take very long to restore as they
>are database dumps over 15GB and stored on a rotational drive (which is
>more cost effective as a backup volume).  I noticed that this is partially
>due to the fact the rdiff-backup needs to apply each increment as a patch,
>stepping backwards until the desired state is achieved.
>
>Is there a simple way around this?  I wouldn't mind taking up the space
>needed for a full snapshot if there is some argument that can accomplish
>this, but I'm trying to avoid the need to build some complex snapshot
>directory rotation in to my script logic.  Currently I'm simply doing:
>
>mysqldump --single-transaction --lock-tables=false my_database >
>/mnt/mirror/daily/dump/my_database.sql
>rdiff-backup  --no-eas --no-acls --no-file-statistics
>/mnt/mirror/daily/dump/ /mnt/mirror/daily/diff/
>rm /mnt/mirror/daily/dump/*sql
>rdiff-backup --force --remove-older-than 10D /mnt/mirror/daily/diff/
>>/dev/null 2>&1
>
>We'd like to keep up to 30 days of increments here but the time needed to
>restore something that old would be a bit absurd.  I'm thinking something
>like 4 full backups with 6 increments each.
>
>I hope this makes sense.  Thanks!