Subject | Re: [Firebird-Architect] Re: (Near to) 0 down time? (with ease I hope...) |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-02-06T05:56:14Z |
On 3 Feb 2006 at 16:32, m_theologos wrote:
preserve DB's integrity on crash. If the crash has happened after
data pages are written but before the TIP is written - boom! you've
lost some changes.
Ideally, a server crash cannot break database (or shadow), but the
reality is a bit differ. There are reports that database become
broken after power failure. Especially if Forced Writes were off.
also can be broken (though unlikely). As Alex said, such things
didn't happen to his customers' databases so far.
--
SY, Dimitry Sibiryakov.
>Do you mean that the shadow is in an inconsistent state when the DBThis one. Pages are written to DB (and shadow) in the order that
>is:
>
>1. open?
>2. Writting on it?
preserve DB's integrity on crash. If the crash has happened after
data pages are written but before the TIP is written - boom! you've
lost some changes.
Ideally, a server crash cannot break database (or shadow), but the
reality is a bit differ. There are reports that database become
broken after power failure. Especially if Forced Writes were off.
>How? IOW, you mean that if the shadow goes broken then the main DB canI mean that if the main DB is destroyed by server breakage, shadow
>go away also?
also can be broken (though unlikely). As Alex said, such things
didn't happen to his customers' databases so far.
--
SY, Dimitry Sibiryakov.