Von: "Kevin Korb via rsync"
>> An: rsync@lists.samba.org
>> Betreff: Re: link-dest and batch-file
>>
>> If you are using ZFS then forget --link-dest. Just rsync to the same
>> zfs mount every time and do a zfs snapshot after the rsync finishes.
>> Then de
But don‘t forget —inplace, otherwise snapshots would not be efficient
> Gesendet: Mittwoch, 18. Juli 2018 um 21:53 Uhr
> Von: "Kevin Korb via rsync"
> An: rsync@lists.samba.org
> Betreff: Re: link-dest and batch-file
>
> If you are using ZFS then forget --link-d
If you are using ZFS then forget --link-dest. Just rsync to the same
zfs mount every time and do a zfs snapshot after the rsync finishes.
Then delete old backups with a zfs destroy.
On 07/18/2018 03:42 PM, Дугин Сергей via rsync wrote:
> Hello.
>
> I need that during today's backup, the meta
Hello.
I need that during today's backup, the metadata about the files is
saved in a file, so that tomorrow when creating a backup with the
option "link-dest" instead of this option I would specify a file with
metadata, then rsync will not scan the folder specified in
"link-d
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 "succes
I don't know how the OP manages their backups. I write out a
backupname.current symlink pointing to the new backup once it is
completed. That is what I use as the --link-dest parameter and what I
would restore from. If a backup is aborted in the middle, doesn't
happen at all, or fails the symlin
On Tue, Jun 26, 2018 at 12:02 PM, Дугин Сергей via rsync <
rsync@lists.samba.org> wrote:
> I am launching a cron bash script that does the following:
>
> Day 1
> /usr/bin/rsync -aH --link-dest /home/backuper/.BACKUP/009/2018-06-25
> root@192.168.1.103:/home/ /home/backuper/.BACKUP/009/2018
I don't believe there is anything you can do with the batch options for
this. If you added a --write-batch to each of those you would get 3
batch files that wouldn't be read without a --read-batch. If you also
did a --read-batch that would contain differences between a backup and
the backup befor
