You have to have a script that places a "successful" file in the root of the completed rsync... And use that to figure out what to do for link-dest at the top of the script... I use something more like daily.0-daily.7 and monthly.0-monthly.3 for the folders and rotate them daily -if- the "successful" file exists. If it does not rotate, then the failed rsync from the day before is reused...
(i.e. I always backup to daily.0 using daily.1 as the link-dest...)
I make a hard-link replica of daily.1 into monthly.0 on the first of each month. That leaves me with 7 days of successful daily backups and 4 months of depth backups.

Larry Irwin

On 06/26/2018 04:36 PM, Dan Stromberg via rsync wrote:

On Tue, Jun 26, 2018 at 12:02 PM, Дугин Сергей via rsync < <>> wrote:

    I am launching a cron bash script that does the following:

    Day 1
    /usr/bin/rsync -aH --link-dest
    root@ /home/backuper/.BACKUP/0000009/2018-06-26

    Day 2
    /usr/bin/rsync -aH --link-dest
    root@ /home/backuper/.BACKUP/0000009/2018-06-27

    Day 3
    /usr/bin/rsync -aH --link-dest
    root@ /home/backuper/.BACKUP/0000009/2018-06-28

    and etc.

This isn't really what you were asking, but with the "dated directories" scheme, what happens if one or your machines crashes during a backup?  Don't you end up storing a lot more data in the next successful backup?

Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
Before posting, read:

Reply via email to