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
Hello.
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-06-26
Day 2
/usr/bin/rsync -aH --link-dest /home/backuper/.BACKUP/009/2018-06-26
ro
Hello.
I need the correct UID and GID to be written to the log file when backing up,
rather than being installed on the files in the copy.
When using the fake-super option, symlinks are stored as files,
consequently, an inexperienced user will not be able to turn this file into a
symlin
