Subject | Re: [Firebird-Architect] (Near to) 0 down time? (with ease I hope...) |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-02-03T04:59:53Z |
On 2 Feb 2006 at 11:08, m_theologos wrote:
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.
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).
--
SY, Dimitry Sibiryakov.
>I think that is very easy to make a small change in order to acheive aI don't think so. Because you can't control network buffers
>very high availability. Now we can do only:
>
>Create shadow <...> C:\MyShadow.sh
>
>Perhaps you can do
>
>Create shadow <...> \\<Server>\<Share>\MyShadow.sh
>
>IMHO, this is rather simple to achieve and then we have a sort of RAID
>between computers which can be very "usefull" when a server fails.
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.
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).
--
SY, Dimitry Sibiryakov.