Ask HN：你们如何追踪备份了哪些内容？
1 分•作者: atomicnature•9 个月前
我的团队最近丢失了一些生产数据——不是因为备份失败，而是因为一些关键的东西根本没有被追踪。
Postgres 数据库转储 -> 已备份
GitLab 仓库 -> 已备份
Ghost 配置文件 -> 已备份
Listmonk 数据库 -> 未备份
虽然有快照，但它们很大，而且无法明确说明是否包含了所有重要的内容。此外，管理它们、制定策略等等也带来了额外的开销——这感觉有点过头了。备份整个操作系统、临时文件等等，我不太喜欢这种方式。
临时脚本给人一种安全感——但实际上很容易遗漏东西（我们之前就有一堆用于这类任务的脚本/定时任务）。
难点不在于运行备份——而在于可见性：了解需要备份什么、实际涵盖了什么以及它在哪里。
你们的组织是如何处理这个问题的？在实际操作中，追踪备份最难的部分是什么？
查看原文
My team recently lost some production data - not because backups failed, but because some critical things weren’t tracked at all.<p>Postgres dumps -> backed up<p>GitLab repos -> backed up<p>Ghost configs -> backed up<p>Listmonk database -> NOT backed up<p>Snapshots exist, but they’re heavy and don’t make it clear whether everything important is included. Also, there's the overhead of managing them, policies, etc - which just feels like overkill. Backing up the entire OS and temp files and so on doesn't sit well with me.<p>Ad-hoc scripts give an illusion of safety -- but practically it’s easy to miss something (we had a bunch of scripts/cron for this stuff).<p>The hard part isn’t running backups -- it’s visibility: knowing what needs backup, what’s actually covered, and where it lives.<p>How do you handle this in your organization? What’s the hardest part of tracking backups in practice?