Hi, happy borgbackup user here. This is probably off-topic for most but as many users probably are evaluating send/receive versus other backup solutions, I'll keep linux-btrfs in the loop. On 28/08/2016 20:10, Oliver Freyermuth wrote: >> Try borgbackup, I'm using it very successfully. It is very fast, >> supports very impressive deduplication and compression, retention >> policies, and remote backups - and it is available as a single binary >> version so you can more easily use it for disaster recovery. One >> downside: while it seems to restore nocow attributes, it seems to do it >> in a silly way (it first creates the file, then sets the attributes, >> which of course won't work for nocow). I have not checked that >> extensively, only had to restore once yet. > Wow - this looks like the holy grail I've been waiting for, not sure how > I have missed that up to now. > Especially the deduplication across several backupped systems on the backup target > is interesting, I originally planned to do that using duperemove on the backup target > to dedupe across the readonly snapshots. Note that only one backup can happen at a given time on a single repository. You'll probably have to both schedule the backups to avoid collisions and use "--lock-wait" with a large enough parameter to avoid backup failures. There's another twist : borgbackup maintains a local index of the repositories' content, when it detects that it is out of sync (if several systems use the same repository it will) it has to update its index from remote. I'm not sure how heavy this update can be (it seems it uses some form of delta). I have a ~user/.cache/borg of ~2GB for a user with ~9TB of data to backup in ~8M files but I don't share repositories so I'm not affected by this). Best regards, Lionel -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
