问题原文
原帖链接 · Greg · CC BY-SA 3.0
How can zfs pools be continuously/incrementally backed up offsite?
I recognise the send/receive over ssh is one method however that involves having to manage snapshots manually.
There are some tools I have found however most are no longer supported.
The one tool which looks promising is https://github.com/jimsalterjrs/sanoid however I am worried that non-widely known tool may do more harm then good in that it may corrupt/delete data.
How are continuous/incremental zfs backups performed?
社区高分解答
原帖链接 · user121391 · CC BY-SA 3.0
You have two different ways you can do that:
- The traditional, filesystem-agnostic way that is/was used for the last decades, with tools like
rsyncorBacula. There you have tested and (hopefully) stable, large software that can be customized for huge deployments and can be used even if you switch away from ZFS - One of the tools that leverage ZFS
send/recv. This can either be your own solution, a script or extended script from the various ones on Github et al., or more feature-rich tools like Sanoid or ZnapZend (send/recv with mbuffer support and retention plans). In this case you will most likely not find any big, "enterprisey" (in the negative sense) solutions, but tools that do just the single task and can be combined with other tools to cater to your specific setup.
In general, I would only trust a tool whose source code is available, and I would keep it as simple as possible. If using send/recv, you don't have to manage much, you just have to delete snapshot n-1 on the local side when transmission and establishment of snapshot n on the remote side was successful.
You can split your transport any way you like, it can even be async (snapshots do not have to be received immediately), if you just keep the iron rule that you can only send a diff between the local current/new and local previous snapshot, and that the local previous snapshot is the most recent one on the remote side (until the backup finishes and everything is reset).
Now that I think of it, you could probably encode that in a state machine and then be sure that no unforeseen cases can slip through.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
