At 11:20 AM 30/04/2006, you wrote:

>Adam wrote:
>
> >>>Worse still, and although I can not understand how it is possible,
> >>>there have been reports about the source database being corrupted
> >
> > Would this be a corrupt 'destination' database?
> >
>yes, sorry, I didn't read your post carefully. As far as I
>know, copying won't corrupt the source database. There have
>been cases where that was suggested, but I don't know of
>any that have been carefully analyzed.

I don't know of any analysis that's been done recently and I believe
that, with Firebird, it would now not be possible to corrupt a
database in this fashion if it was Superserver running on Windows -
because of the exclusive write lock.

However, file image backup utilities on Windows that lock blocks of
disk were shown in the past (IB 5.6 and IB 6.0) to cause corruption
to active databases, presumably by locking blocks that impinged on
page-blocks that the DB server was actively interested in. WinZip
and the MSBackup in NT 4.0 were two that I knew of that could do
this; and another auto-backup utility that used to ship with the
"Mountain-something" tape drives (sorry, can't recall the exact
brand-name). I've seen this (1+1=2) with my own eyes, so I continue
to recommend NOT doing it until convinced otherwise.

(I don't know whether it is possible for applications on non-Windows
platforms to undermine filesystem-level resource protection in this
way, so I'd still go with "better safe than sorry" regarding rsync's
potential to corrupt an active database.)

./heLen

>Regards,
>
>
>Ann
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Visit http://firebird.sourceforge.net and click the Resources item
>on the main (top) menu. Try Knowledgebase and FAQ links !
>
>Also search the knowledgebases at http://www.ibphoenix.com
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Yahoo! Groups Links
>
>
>
>