Subject Re: [firebird-support] Re: Corruption in Firebird Classic
Author jason palmer
We found problems with those backups so we make em logout to backup and flash
up a warning message when they log in if no backup has been taken for more than 48 hours.

They just ensure everyone is logged out and click on 'backup' which shells out to
gbak and go home.

----- Original Message ----
From: Adam <s3057043@...>
Sent: Sunday, 3 December, 2006 1:09:24 AM
Subject: [firebird-support] Re: Corruption in Firebird Classic

--- In firebird-support@ yahoogroups. com, jason palmer
<jasonthepolymath@ ...> wrote:
> If it takes a long time to backup, then users will never backup :)

Your kidding right? Firebird supports a hot backup, meaning that
everyone works as normal while the backup runs. It can happen without
user interaction during non peak times.

Expecting end users to backup is a poor design if your data is
important and not easily regenerated.

> jason palmer wrote:
> > no, trust me on this one, large databases are not stable, unless
your using a very
> > expensive database system

Are you referring to Firebird databases specifically? If so there are
a lot of people who would be interested in the specifics, in
particular what you consider 'large', and what instabilities one
should expect.

From what I can gather, this thread is about an issue that is not yet
identified, the only thing these two databases have in common is that
they are large. That does not imply that all large databases are at risk.


Send instant messages to your online friends

[Non-text portions of this message have been removed]