Hi all,


I am testing the backup and restore functions for interbase.
I created a backup using gbak.
And I restored the backup with the IB Expert / Services / Restore
function.
I had no error messages whatsoever neither for the backup nor for the
restore.
But I can't add new records over the software using the database. In
the database i can still add records to the table but the ID_generators
dont work anymore.
I recompiled the generators - no effect.
I validated the database - no errors
The database is online and in read/write mode.


Any suggestions what the problem might be ?


Thanks for your help.

Thanks Whitebat

Ok i found my problem. Triggers, views and procedures are not included in the backup.

my backup statement looks like this:

gbak -b -v -e -t -user sysdba -password masterkey  -y c:\integreattransport%date:~-4%%date:~4,2%%date:~7,2%.log dbnhtsa.gdb c:\dbnhtsatransport%date:~-4%%date:~4,2%%date:~7,2%.gbk

it makes no difference if i do a compact/full backup, transportable or non transportable backup they are never included.

Any suggestions?

Thanks Whitebat

OK, so what happens when you manually run a backup using IBConsole's UI rather than using gbak ?

The exact same happens. :(.

Thanks Whitebat

Hm, tricky. Needless to say that this shouldn't happen - the one time I saw it was when someone used a FireBird UI tool to restore an InterBase database

What about going the whole hog, shutting down the database and transferring it onto a 'clean' IB install and trying a backup/restore cycle ?

...and yes this is definitely a 'quick-fix-try-it-and-see' approach for which I make no apology , if this fails then the next thing to do is go through the process step-by-step in a more logical manner than how I have done thus far

ujb

That might be the problem then. The manufacturer of the software using the Interbase Database is using the firebird tools.

But we fixed it differently. We have a task that shuts down the database copies the file and opens the database again. That works good so far.
:)

Thanks Whitebat

Jolly good show. I guess one other thing you could do to avoid similar issues in the future is to make sure that the complete backup/restore cycle is logged and appropriate notification set up (say via email using something like blat), i.e. a batch file that carries out the required tasks and sends a notification to the DBA if any of them fails.

For what its worth here is what my batch file does:

1) Shutdown the database
2) Do an IB backup of the database into the 'backup' folder
3) Do an IB backup of the InterBase security admin database into the 'backup' folder
4) Restart the database
5) Do an IB restore of the backed up database from step 2) into the 'backup' folder
6) Do an IB restore of the backed up InterBase security admin database from step 3) into the 'backup' folder
7) Shut down the InterBase Guardian service
8) Delete temporary sort files (if any exist)
9) Start up the InterBase Guardian service

Then you are in a position to OS backup the output of step 2 or 5 (depending upon how fast you need to recover the last backup) secure in the knowledge that a restore will work 100%.

good luck