On 2/29/12 3:28 PM, todderamaa wrote:

> But with this latest issue, we needed the database file and not the
> backup. The restore of the backup failed, because we had a stored
> procedure that was selectable that didn't include a 'suspend'
> statement. I think this must be something that was allowed in Firebird
> 2.0 but not with 2.1. To fix this, I had to have the database itself.
> So I could alter the procedure and add the 'suspend' statement. The
> restore of the gbk file resulted in a half restored database with no
> procedures or triggers.

Yeah, that's why the test restore is so important. It's like reading the
backup tape and comparing it to the original. Verifies not only is the
content the same but that the tape, itself, is readable.

Unfortunately this is one of the biggest weaknesses of Firebird. One of
the recurring issues on the support list is backups that will not
restore. Very, very messy.