Timeline for Can rsync work in write-only mode?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2021 at 20:01 | answer | added | Ploszpe | timeline score: 2 | |
| Mar 3, 2018 at 17:22 | vote | accept | Tal | ||
| Mar 3, 2018 at 17:20 | vote | accept | Tal | ||
| Mar 3, 2018 at 17:22 | |||||
| Mar 3, 2018 at 16:49 | comment | added | meuh |
Note, rsync only reads file contents when it has found a mismatch in the size or timestamp etc (depending on your options), and wants to optimise the network copy of the changes. You can stop this with --whole-file and the whole new file will be copied over.
|
|
| Mar 3, 2018 at 10:59 | answer | added | meuh | timeline score: 2 | |
| Mar 3, 2018 at 9:14 | comment | added | Ipor Sircer | use btrfs and transfer only the differences between snapshots. btrfs.wiki.kernel.org/index.php/Manpage/btrfs-send | |
| Mar 3, 2018 at 8:21 | comment | added | davidbaumann | So the clients may not even read their own backup? | |
| Mar 3, 2018 at 7:23 | comment | added | Sparhawk | I doubt it. But why don't you just do it the Linux way, and create a separate user on the backup server for each server-client? Then each server-client only has access to its own backups. | |
| Mar 3, 2018 at 7:04 | history | asked | Tal | CC BY-SA 3.0 |