Hi,

At July 23, 2003, 11:24, Scott Taylor wrote:

> At 02:38 07/23/03, you wrote:
>>--- In firebird-support@yahoogroups.com, "Scott Taylor" <scott@d...>
>>wrote:
>> > # and restore it
>> > /opt/interbase/bin/gbak -R -USER SYSDBA -PASSWORD masterkey \
>> > /opt/databases/mydatabase.fbk /opt/databases/mydatabase.fdb
>>
>> Never make it. Only -C into another file and after successfull
>>restore replace database. Some kinds of corruptions can show
>>themselves on restore only and you can finish with unrestorable .gbk
>>and not having original database.

> Pardon me, but I don't understand what you are trying to say.

Not all possible error checks are made during backup. But, they are
all performed on restore, and most of the time, the restore process is
stopped when an error is encountered.

In example:
If you have an error in your database that is not manifesting itself,
in normal operations. When performing the backup, the error might not
be picked up. But, when restoring the database, there's a very big
possibility that the error will be noticed and the restore process is
stopped. So, if you didn't make a copy of your database before
performing the restore, at this point you might have lost your
database, because the backup can't be restored and your database is
only partially restored and might not be usable.

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)