Subject | endless backup |
---|---|
Author | Ferda Brabenec |
Post date | 2005-02-24T09:16:39Z |
Hello,
I have got few quite basic questions about usage of gbak backup utility.
gbak is version LI-V1.5.1.4500 Firebird 1.5
1)
Is it safe (regarding to database being backed up) to interrupt
gbak by signalling? Is SIGINT fine?
If I do this, fbserver thread that worked for gbak seems to continue
in its work. Is there a way to stop this thread safely at runtime?
If no, is it safe to restart the database server in such a state?
In case of safe restart, will I get rid of this post-mortem activity permanently?
2)
Has database filename extension ".gdb" any specific influence on gbak?
Could gbak behave differently if the extension was ".fdb" or whatever else?
3)
Is it safe to run 2 instances of gbak on the same database?
Perhaps when I find out that backup with garbage collecting
will take hours, can I safely run another "gbak -g ..." ?
TIA, Ferda
I have got few quite basic questions about usage of gbak backup utility.
gbak is version LI-V1.5.1.4500 Firebird 1.5
1)
Is it safe (regarding to database being backed up) to interrupt
gbak by signalling? Is SIGINT fine?
If I do this, fbserver thread that worked for gbak seems to continue
in its work. Is there a way to stop this thread safely at runtime?
If no, is it safe to restart the database server in such a state?
In case of safe restart, will I get rid of this post-mortem activity permanently?
2)
Has database filename extension ".gdb" any specific influence on gbak?
Could gbak behave differently if the extension was ".fdb" or whatever else?
3)
Is it safe to run 2 instances of gbak on the same database?
Perhaps when I find out that backup with garbage collecting
will take hours, can I safely run another "gbak -g ..." ?
TIA, Ferda