On Fri, Nov 20, 2009 at 1:36 PM, Tres Seaver <tsea...@palladion.com> wrote:
>>>> with Zope
>>>> 2.12 and later now running on Python 2.6, we should just tell people
>>>> "Sorry, you can't do backups"?
>> No, we should tell them they should use a mostly untested tool to do backups
>> that doesn't work with blobs. That should inspire confidence.
> We can use rsync to back up blobs safely / losslessly without restarting
> the ZEO server: we can't do that with filestorages.
Depending on backup schedules, I would not rely on the rsync backed
up blobs and repozo backups remaining consistent. Packing complicates
this quite a bit.
>> Does Zope 2.12 use Blobs?
> If configured, sure.
I would not trust repozo + blob backups.
>>> I just checked in a stupid test to ensure that repozo can be imported.
>>> - --- src/ZODB/scripts/tests.py (revision 105913)
>>> +++ src/ZODB/scripts/tests.py (working copy)
>>> @@ -26,6 +26,11 @@
>>> +class RepozoTests(unittest.TestCase):
>>> + def test_importability(self):
>>> + from ZODB.scripts import repozo
>> I appreciate your dedication to quality.
>> That test passes under ZODB 3.9.3 with Python 2.6.
> It emits the same DeprecationWarning (the "bug" Withers fixed). I did
> have to munge the 'test_suite' dinosaur as well.
Fair enough. Given that this provokes the symptom that was fixed.
I can live with this.
I also would fear to rely on repozo in it's current state, but I don't have to.
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org