--- In Firebird-Architect@yahoogroups.com, "Dimitry Sibiryakov"
<SD@...> wrote:

> I don't think so. Because you can't control network buffers
> shadowing to another computer either lead to slowdown (if FB will
> wait till the data is really written to the shadow) or broken shadow
> if the server crashed before sending data from buffers.

Do you mean that the shadow is in an inconsistent state when the DB is:

1. open?
2. Writting on it? (IMHO, on a 1Gb wire writting a change on a server
with "classical" components (>1GB RAM, >2.2 GHz CPU, >=7200RPM (P)ATA
HDD) cannot least too much.

> I think that currently there is only one real way to decrease
> downtime with FB (and IB) - replication. But neither method guarantee
> against data loss. When you use replication and server crashed you'll
> lose data that is not replicated yet. If you use shadowing you may
> lose whole database if the shadow become inconsistent (broken).

How? IOW, you mean that if the shadow goes broken then the main DB can
go away also?

Thx for your opinions,

m. Th.

>
> --
> SY, Dimitry Sibiryakov.
>