Ok... This statement scares me...

>> 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.

>>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.



So, what you are in effect saying is that my backups might be totally
useless because I might not be able to restore them even though the
backup worked correctly...

So, say I had a hard drive failure (which we recently had), just because
I had a successful backup doesn't mean I am going to have a successful
restore? That makes my legs go wobbly (and makes me want to rethink
using IB/Firebird!). Please tell me it isn't true!

If it is, we are going to have to have to have a policy of restoring
every backup to make sure all is well... And then do some serious
thinking!

Regards
Colin


-----Original Message-----
From: Daniel Rail [mailto:daniel@...]
Sent: Thursday, 24 July 2003 3:05 a.m.
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Re: Database compress/purge


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)



To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################