> >...
> >gbak: restoring index FK_MINPRIJS
> >gbak: finishing, closing, and going home
>
> Do you get a complete log preceding this, though? If so, these

messages

> mean the restore was successful.

Yep, DB looks ok, but where does the errormessages comes from after
the "going home" message ?

As an extra test I did the restore using GBAK directly in a terminal
window, and there it all seems to be ok as well.


Nevertheless I'm a bit worried as to what the cause is for the
reported error, and wether this will also occur when my software
accesses the DB :-(

Further checking firebird.log I See :

luelx1.nbvuga.lan (Client) Tue Dec 21 09:27:14 2004
/opt/firebird/bin/fbguard: bin/fbserver terminated abnormally
(-1)


luelx1.nbvuga.lan (Client) Tue Dec 21 09:27:14 2004
/opt/firebird/bin/fbguard: guardian starting bin/fbserver



luelx1.nbvuga.lan (Client) Tue Dec 21 11:43:36 2004
/opt/firebird/bin/fbguard: bin/fbserver terminated abnormally
(-1)


luelx1.nbvuga.lan (Client) Tue Dec 21 11:43:36 2004
/opt/firebird/bin/fbguard: guardian starting bin/fbserver


So this happens every time when I restored the DB using IBExpert.
I don't see this behaviour when using GBAK directly within the
terminal window.

>
> >IBE: Unsuccessful execution caused by a system error that precludes
> >successful execution of subsequent statements.
> >Unable to complete network request to host "192.168.0.144".
> >Error reading data from the connection.
> >
> >IBE: Restore completed. Current time: 9:31:30. Elapsed time:

00:02:28

> >

> *Never* use -replace_database - it should be bulldozed off a cliff.

Ok, I'll keep that in mind :)

> It looks to me as if IBE is trying to connect remotely but has lost

the

> connection. Try "disconnecting" (even though you know it's

disconnected)

> and then reconnecting. Do you try to connect to the restored

database

> yourself, e.g locally with isql?

I'm not connected to a DB at the moment I start the Restore from
within IBE. (So disconnect is greyed out)

Connecting to the newly created DB after the restore is not a
problem, but FB has restarted after the restore ! Obviously I can't
have this behaviour in a production env. Since this would mean all my
client apps would loose connection. when a DB (even another one than
the one those apps use) gets restored.
And as said, I've seen this "restarting" thing also as a result of a
normal sql action, but wasn't sure at that moment that it wasn't just
my bug or a faulty UDF. Therefore I started trying to simulate it
using FB-tools only. (by executing scripts and restoring db)

Dirk Naudts.