TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Disaster Recovery with ZFS and Zrepl

32 点作者 aargh_aargh大约 1 年前

7 条评论

justinclift大约 1 年前
It <i>sounds</i> like the author is using ZFS encryption.<p>If that&#x27;s the case, then doing so with replicated ZFS snapshots is probably not a good idea.<p>That specific scenario (ZFS encryption -&gt; replication of encrypted snapshots) is a known cause of ZFS corruption. :(<p><a href="https:&#x2F;&#x2F;www.phoronix.com&#x2F;news&#x2F;OpenZFS-Encrypt-Corrupt" rel="nofollow">https:&#x2F;&#x2F;www.phoronix.com&#x2F;news&#x2F;OpenZFS-Encrypt-Corrupt</a><p>Unfortunately it doesn&#x27;t seem to be widely known about, though there is a suggestion to make it official:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;openzfs&#x2F;openzfs-docs&#x2F;issues&#x2F;494">https:&#x2F;&#x2F;github.com&#x2F;openzfs&#x2F;openzfs-docs&#x2F;issues&#x2F;494</a>
l2dy大约 1 年前
&gt; I don’t back up my drives, I replicate them.<p>Don&#x27;t take this as a general advice. For important data, it&#x27;s important to have multiple backups and validate their effectiveness routinely.
评论 #40305943 未加载
评论 #40306079 未加载
评论 #40305957 未加载
kkfx大约 1 年前
Well... The issue with encrypted zfs + raw send is that a pool encrypted with a common key for all volume became an individual key per volume, a non-RAW send means your target read your files. If you use a keyfile this is a non-issue. If you type your key, well, you import all the old volumes, create a new pool and send them re-encrypting them with a common key. Very raw but doable at home scale setups.
tie-in大约 1 年前
You don&#x27;t actually need a dedicated ZFS backup program. A simple cron script will handle incremental backups just fine. If anyone is interested, the script we use to backup our multi-TB PostgreSQL database can be found here: <a href="https:&#x2F;&#x2F;lackofimagination.org&#x2F;2022&#x2F;04&#x2F;our-experience-with-postgresql-on-zfs&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lackofimagination.org&#x2F;2022&#x2F;04&#x2F;our-experience-with-po...</a>
justinclift大约 1 年前
For ZFS use it&#x27;s probably a good idea to avoid WD NVMe drives too.<p>There are a <i>large</i> number of people who&#x27;ve reported problems with ZFS (and btrfs) with WD SN770 and a few other WD models:<p>• <a href="https:&#x2F;&#x2F;github.com&#x2F;openzfs&#x2F;zfs&#x2F;discussions&#x2F;14793">https:&#x2F;&#x2F;github.com&#x2F;openzfs&#x2F;zfs&#x2F;discussions&#x2F;14793</a>
chromakode大约 1 年前
Funny story -- when I was working on the xkcd Machine comic, I actually used the ZFS snapshots to rescue data. I accidentally blew away some early physics prototype code and fished it out of &#x2F;.zfs&#x2F;snapshot.
评论 #40306307 未加载
totetsu大约 1 年前
My face palm moment of this year was accidentally restoring a zfs snapshot of my root pool form a week ago, but it was actually a year and a week ago. Didn’t lose any of my data, but suddenly I had some offering to format their version mismatched databases.