| Subject | SV: [firebird-support] Internal GDS errors that cause corruption and unrecoverable databases |
|---|---|
| Author | Poul Dige |
| Post date | 2013-03-05T08:53:40Z |
Hi Eduardo,
A backup that can't be restored is not very useful. Thus, it makes very much sense to test the backups every now and then.
In our production we use an immediate restore of the database to verify that it actually works. You can do so in one pass by piping the backup output directly as input to the restore function, e.g.
gbak.exe -b -user "SYSDBA" -password "MASTERKEY" database.fdb stdout | gbak.exe -user "SYSDBA" -password " MASTERKEY " -r stdin restored.fdb
After this operation you have a "clean restore" of your database. Then zip the restored.fdb and archive it. It will be of much lower size than the usual .fbk-file and will be much faster to "restore" as you only have to unzip it.
Best regards
Poul
PS! In the restore part you might want to set buffers/page size, but that's your choice.
A backup that can't be restored is not very useful. Thus, it makes very much sense to test the backups every now and then.
In our production we use an immediate restore of the database to verify that it actually works. You can do so in one pass by piping the backup output directly as input to the restore function, e.g.
gbak.exe -b -user "SYSDBA" -password "MASTERKEY" database.fdb stdout | gbak.exe -user "SYSDBA" -password " MASTERKEY " -r stdin restored.fdb
After this operation you have a "clean restore" of your database. Then zip the restored.fdb and archive it. It will be of much lower size than the usual .fbk-file and will be much faster to "restore" as you only have to unzip it.
Best regards
Poul
PS! In the restore part you might want to set buffers/page size, but that's your choice.
> -----Oprindelig meddelelse-----
> Fra: firebird-support@yahoogroups.com [mailto:firebird-
> support@yahoogroups.com] På vegne af Eduardo A
> Sendt: 4. marts 2013 22:07
> Til: firebird-support@yahoogroups.com
> Emne: [firebird-support] Internal GDS errors that cause corruption and
> unrecoverable databases
>
> Need a lot of help. Urgently. Using FB version 1.5.6.
>
> I am having a few databases reporting Internal GDS errors that allow the
> database to be backed up but do not allow it to be restored. Most of them
> have reported I/O errors 10054 at one time or another. Most of these are
> databases of 40 GB or less.
>
> What I need to know is how can I tell (by looking at the Firebird log or doing
> some other operation) that the database is in bad shape and may allow a
> back up and not restore, or may soon result in an internal gds error that
> require some time with GFIX to get it back to service.
>
> I need to be able to create, or buy, an application that either reads the FB log
> or performs some actions that send me notification that a database is in the
> process of being damaged before they are beyond repair.
>
> Thanks for you quick answer.
>
> -Eduardo
>
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item on the main
> (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++
> Yahoo! Groups Links
>
>
>