Never backup/copy the database file directly. Make the backup from the
database with Firebird (gbak, Services API) and then backup/copy the
created database backup file.

If you want to upgrade to 2.1.x please read the Release Notes and
Migration & Installation guide, because metadata need an upgrade.

Version 2.1.3 not released yet.
You can use a snapshot build, but this just compiled from source tree
and not tested like a release build.
http://www.firebirdsql.org/download/snapshot_builds/win

Gabor

Gustavo írta:

> Gabor:
>
> Thank you for your answer.
>
> I discover that they installed Nova Backup in the server and it was not executing in the times where the corruption events occurred and it really didn´t execute during the day while users where using the database. But I found there was something wrong with it because when I ran it, it "hanged". So yesterday I reset the server and now it doesn´t hang. Perhaps this was the reason. I don´t know yet.
>
> If the problem persist, I will check the hardware.
>
> Anyway I will upgrade FireBid to version 2.1.2.
>
> I read the links you sent me and in the second one http://tracker.firebirdsql.org/browse/CORE-1961 it says it is fixed in version 2.1.3 but... Is there any 2.1.3 FireBird version? In FireBirdSQL page, the last 2.1.x version is 2.1.2!