Well, bad _technically_, or bad _evil_?

<G>

It does have the sole advantage you can pull a portion of your tree, and
some people have had Data.fs problems (not me thankfully). But in general
I'd guess backing up Data.fs to be the best way. How does it copy with
non-atomicity of disk writes?

Regards,
Phil

+----------------------------------+
| Phil Mayers, Network Support     |
| Centre for Computing Services    |
| Imperial College                 |
+----------------------------------+  

-----Original Message-----
From: Chris Withers [mailto:[EMAIL PROTECTED]]
Sent: 19 January 2001 17:02
To: Andreas Tille
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Zope] Re: How to backup Zope data base?


Andreas Tille wrote:
> 
> On Fri, 19 Jan 2001, Stephane Bortzmeyer wrote:
> 
> > On Thursday 18 January 2001, at 13 h 52, the keyboard of "Mayers, Philip
J"
> > <[EMAIL PROTECTED]> wrote:
> >
> > > This certainly isn't *efficient*, but it works:
> This is great because absolutely the thing I was looking for ...
> Thanks for the zexp part Philip!

That's actually a really bad way to back up Zope :-S

Copying data.fs is much more reliable and _much_ less strenuous on your
server,
especially if it's a big Data.fs

cheers,

Chris

_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to