Products.TIDStorage is a Plone product that provides a way to have consistent backups when running a multi-storage instance (only ZEO is supported at the moment).
Doing backups of individual Data.fs who are part of the same instance (one mounted in another) is a problem when there are transactions involving multiple storages: if there is a crash during transaction commit, there is no way to tell which storage was committed and which was not (there is no TID consistency between databases). There is an even more tricky case. Consider the following:
2 transactions running in parallel:
T1: modifies storage A and B
T2: modifies storage A
Commit order scenario:
T1 starts committing (takes commit lock on A and B)
T2 starts committing (waits for commit lock on A)
T1 commits A (commit lock released on A)
T2 commits A (takes & releases commit lock on A)
[crash]
T1 commits B (commit lock released on B)
Product's homepage
Requirements:
· Python
· Plone CMS
What's New in This Release: [ read full changelog ]
· drop base_url parameter [Romain Courteaud]
· add missing __init_.py files [Romain Courteaud]
Find us on Google+
