Michael Havard wrote: > > We're missing 16 days worth of content. > > Python 2.3.5, Zope 2.8.4, Plone 2.1.2, and a host of other products. ZEO > configuration. Persistent disk caching is on. > > Yesterday everything was fine. All the content was there and accessible. >
I recall reading about a case that involved quietly running out of free space on the volume used for FileStorage. Something like … the most recent content was in RAM — and the running ZEO cluster seemed to work fine with that (no adverse effect on the end user, at the time) — but that content was not committed to disk (and so, was probably unrecoverable following a restart of the OS). > … Thinking maybe someone restored from an older backup I went out to our > daily backups and pulled the previous days data.fs backup. A restore > didn't work. It still shows the outdated content. > I recently had a similar experience. In Plone, using the backup script associated with collective.recipe.backup I: 1. restored to a less recent point in time (point A), without the desired effect 2. restored to a more recent point in time (point B), but did not find the content that had been created/modified between points A and B. More specifically: I found old versions of content, without the recent modifications. AFAIR the failed restoration occurred in the midst of <http://n2.nabble.com/-tp4291640p4291640.html> using ZODB 3.8.5 (greater than the version normally associated with Plone 3.3.3) with Zope 2.10.7 (less than the version normally associated with Plone 3.3.3). -- View this message in context: http://old.nabble.com/Missing-Content-tp4174116p27382995.html Sent from the Zope - ZODB-Dev mailing list archive at Nabble.com. _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
