备份 ZODB blob 的正确方法是什么?
我正在使用 plone.app.blob 将大型 ZODB 对象存储在 blobstorage 目录中。 这减少了 Data.fs 的大小压力,但我无法找到任何有关备份此数据的建议。
我已经通过将网络备份工具指向 repozo 备份目录来备份 Data.fs。 我是否应该简单地将该工具指向 blobstorage 目录来备份我的 blob?
如果在复制过程中正在重新打包数据库或添加和删除 blob,该怎么办? blobstorage 目录中是否有必须按特定顺序复制的文件?
I am using plone.app.blob to store large ZODB objects in a blobstorage directory. This reduces size pressure on Data.fs but I have not been able to find any advice on backing up this data.
I am already backing up Data.fs by pointing a network backup tool at a directory of repozo backups. Should I simply point that tool at the blobstorage directory to backup my blobs?
What if the database is being repacked or blobs are being added and deleted while the copy is taking place? Are there files in the blobstorage directory that must be copied over in a certain order?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
只要在这两个操作发生时数据库没有被打包,对 Data.fs 进行 repozo 备份,然后对 blobstorage 目录进行 rsync 应该是安全的。
这是因为,至少在将 blob 与 FileStorage 结合使用时,对 blob 的修改始终会导致创建基于对象 id 和事务 id 命名的新文件。 因此,如果在备份 Data.fs 后写入新的或更新的 blob,则应该不是问题,因为 Data.fs 引用的文件应该仍然存在。 删除 blob 不会导致文件被删除,直到数据库被打包为止,所以这也应该没问题。
以不同的顺序执行备份或在备份期间打包可能会导致备份 Data.fs 引用未包含在备份中的 blob。
It should be safe to do a repozo backup of the Data.fs followed by an rsync of the blobstorage directory, as long as the database doesn't get packed while those two operations are happening.
This is because, at least when using blobs with FileStorage, modifications to a blob always results in the creation of a new file named based on the object id and transaction id. So if new or updated blobs are written after the Data.fs is backed up, it shouldn't be a problem, as the files that are referenced by the Data.fs should still be around. Deletion of a blob doesn't result in the file being removed until the database is packed, so that should be okay too.
Performing a backup in a different order, or with packing during the backup, may result in a backup Data.fs that references blobs that are not included in the backup.
备份“blobstorage”就可以了。 不需要特殊订单或其他任何东西,非常简单。
Plone 中的所有操作都是完全事务性的,因此在事务中间进行备份应该可以正常工作。 这就是您可以对 ZODB 进行实时备份的原因。 在不知道您所在的文件系统的情况下,我猜它应该按预期工作。
Backing up "blobstorage" will do it. No need for a special order or anything else, it's very simple.
All operations in Plone are fully transactional, so hitting the backup in the middle of a transaction should work just fine. This is why you can do live backups of the ZODB. Without knowing what file system you're on, I'd guess that it should work as intended.
我有一个脚本,可以使用硬链接复制一个月的 blob(因此您可以将 blob 的历史记录作为 Data.fs ):
backup.sh
neteja.py
I have an script that copies for a month the blobs using hard links ( so you have and historial of the blobs as the Data.fs ):
backup.sh
neteja.py
您的 FileStorage 备份策略很好。 然而,对在多个文件中存储数据的任何数据库进行备份绝非易事,因为您的复制必须在不写入各个文件的情况下进行。 对于文件存储来说,盲目的愚蠢副本就可以了,因为它只是一个文件。 (使用 repozo 甚至更好。)
在这种情况下(将 BlobStorage 与 FileStorage 结合使用)我必须指出常规备份建议:
Your backup strategy for the FileStorage is fine. However, making a backup of any database that stores data in multiple files never is easy as your copy has to happen with no writes to the various files. For the FileStorage a blind stupid copy is fine as it's just a single file. (Using repozo is even better.)
In this case (with BlobStorage combined with FileStorage) I have to point to the regular backup advice: