Proposal: publish log
Document Actions
Submitted by
jccooper.
on 2007-05-29 09:34.
One way we might improve intra-day recovery would be keeping an independent log of published content.
Consider a scenario where each publish event records the id, new version, text, and metadata of the module in a log somewhere distinct from the rest of the system. This log may be purged after a successful full backup.Our current backup scheme allows us to recover to the last backup, but published content since then is under threat to be lost. We might improve reliability (and ease recovery from certain types of failures) with a system like that described above.
Thoughts? I'll note for one that my proposal doesn't address loss in workspaces, though perhaps we could do that as well.
Re: Proposal: publish log
