ambiser
/
btrbk
mirror of https://github.com/digint/btrbk
9
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

btrbk-mail, README.md: suggest using "rsync --inplace" 

When used without --inplace, rsync creates a new copy of the file and
moves it into place when it is complete, having the effect that btrfs
creates a new extent for the WHOLE file. With --inplace however, rsync
writes the updated data directly to the destination file, having the
effect that btrfs creates a new extent only for the differing part of
the file.
pull/100/merge
Axel Burri 2016-08-17 14:49:27 +02:00
parent 84a5c56a83
commit 708444b096
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -299,7 +299,7 @@ First create a btrfs subvolume on the backup server:
In your daily cron script, prior to running btrbk, sync your source to
`myhost_sync`, something like:
rsync -a --delete -e ssh myhost.mydomain.com://data/ /mnt/btr_backup/myhost_sync/
rsync -a --inplace --delete -e ssh myhost.mydomain.com:/data/ /mnt/btr_backup/myhost_sync/
Then run btrbk, with myhost_sync configured *without any targets* as
follows:

2
contrib/cron/btrbk-mail
View File

@ -32,7 +32,7 @@ rsync_src[example_data]=user@example.com:/data/
rsync_dst[example_data]=/mnt/backup/example.com/data/
rsync_log[example_data]=/mnt/backup/example.com/data-${now}.log
rsync_key[example_data]=/mnt/backup/ssh_keys/id_rsa
rsync_opt[example_data]="-az --delete"
rsync_opt[example_data]="-az --inplace --delete"
# Enabled rsync declarations (space separated list)
#rsync_enable="example_data"