请问HN：你们是如何跟踪备份内容的？
我的团队最近丢失了一些生产数据——这并不是因为备份失败，而是因为一些关键内容根本没有被追踪。
- 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?