> I have an application that run on 12/5 environment using firebird 2.5.1
> I read MUCH about avoid firebird problems/corruptions by backup/restore the
> Firebird database eventually. The best approach appears to be every day - in
> my case at night when there's no one connected to database.
>
> The problem is that I cannot force my clients to do not power off the server
> during night! Then: There are a form/way/sql that I can run and check if I
> "REALLY" need to do a backup/restore?

Run gstat -h regularly to see if the transaction counter gaps are
increasing steadily, which is an indication for poor client transaction
management.

Regular backup/restore cycles to cure something shouldn't be the case,
if especially client transaction management is ok. There are other stuff
like running scheduled sweeps from time to time or re-calculating index
statistics.


--
With regards,
Thomas Steinmaurer

* Firebird Foundation Committee Member
http://www.firebirdsql.org/en/firebird-foundation/

* Upscene Productions - Database Tools for Developers
http://www.upscene.com/

* My Blog
http://blog.upscene.com/thomas/index.php