| Subject | Re: [firebird-support] Consistency Check When Backing Up |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-12-10T02:08:30Z |
At 12:38 PM 10/12/2008, you wrote:
If you have "The Firebird Book", refer to Appendix IV for a pretty exhaustive run-down.
Otherwise, use the steps described here:
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr
Don't overlook the IBSurgeon tools, either. They do a well-organised and thorough page-by-page analysis of the state of data. The analysis module is still free, I think. I'll let you do your own googling for this. ;-)
./heLen
>Thanks, Helen.Hmmm, I didn't mean to imply that the validation/repair utilities could do stuff to analyse RAM state or HDD state!! They won't pop up and say "Corrupt memory" or "corrupt disk". However, because they reach everything in the database, they are going to react in some fashion if any data is damaged. Also, the repair tools won't repair anything that is physically damaged...
>
>Can you elaborate how to determine whether it is a Disk or RAM error using GBAK & GFIX?
>
>I have a couple back-up copies...
If you have "The Firebird Book", refer to Appendix IV for a pretty exhaustive run-down.
Otherwise, use the steps described here:
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr
Don't overlook the IBSurgeon tools, either. They do a well-organised and thorough page-by-page analysis of the state of data. The analysis module is still free, I think. I'll let you do your own googling for this. ;-)
./heLen