Yes I forgot we also added code into our database access applications. This code ensures the applications stop and don't start while backup is in progress.
We use EVENTS for this. I have in the past also put forward a database level suggestion by enhancements to "gbak" The suggestion is: 1. gbak run with two new options to "-xbackup op.fbk" "-xrestore op2.fdb" 2. this option backups up to op.fbk. 3. Also server keeps a separate file for new changes to database during process. 4. server then restores op2.fdb and at the end attaches all new changes to op2.fdb. 5. shuts down live database and replaces it. I think it can be done. Kind Regards, Robert. --- In firebird-support@yahoogroups.com, Alan McDonald <alan@...> wrote: > > Not fool proof at all really. DB needs to be off line from the second the > backup starts until the restored file is renamed. > You need a better way > Alan > On 01/06/2013 4:22 PM, "sir_wally_lewis" <rgilland1966@...> wrote: > > > current practice is. > > > > - backup database > > - restore to new name. > > - rename old database ( can't be done by firebird ) > > - rename new name to production name. ( can't be done by firebird ) > > > > any step fails process is failed. > > > > This allows for 100 percent fool proof backup restore. > > > > > > > > > > > > ------------------------------------ > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > Visit http://www.firebirdsql.org and click the Resources item > > on the main (top) menu. Try Knowledgebase and FAQ links ! > > > > Also search the knowledgebases at http://www.ibphoenix.com > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Yahoo! Groups Links > > > > > > > > > > > [Non-text portions of this message have been removed] >
