--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:
...

> >
> > I can setup automatic backups, which are launched automatically by
> > the server process. But I don't want to stop my server during the
> > backup preventing the client apps from accessing the data (one

backup

> > may last one or several hours, with very large databases).
>
> pardon me but this logic seems a little screwy.. why stop the

server during

> backup? - in fact if you did stop teh server, the backup would

fail. I don't

> understand you here.

I want my server process (not firebird) to run so that when backing
up database A, the users can still access database B (one server
process may use all the databases at the same time, but only one per
connected client).

>
> >
> > I don't want to launch an automatic backup if another one is

running

> > (each automatic backup using a different service handle) even for

a

> > another database. (because it may slow down hard drive

performance).

>
> if you have scheduled your nackups you are in control of the

timing - still

> don't understand you here.

"I" don't schedule backups, my users will. If one sets a one hour
long backup at 8:00PM and another backup (same database or not) at
8:30PM I want the second one to wait for the first to finish. I
cannot control the backup settings, because I can't know how long
they will last.

>
> >
> > I also want to prevent a user from launching a manual

backup/restore

> > on a database which is currently being backed up automatically.
>
> this contradicts your outline above.
>
> >
> > I have used the "isc_service_query" to wait for the end of the
> > backup/restore, but I can't find any way to know if other
> > backup/restore services are currently running.
> >
> > I think I will not use any other kind of service. I can switch to

FB

> > 2.0 if needed but not right now.
> >
> > Thanks for your help.
> > Bénédicte
>
> if your admin client is only ever used by one client and it is the

only

> vehicle for requesting backup, then how do you ever get moren than

one

> simultaneous request... and even if you did get it there is no

problem doing

> 2 backups simutaneously. Restore is far more CPU hungary than

backup.

> Alan

The backup process causes problems with disk access (not necessarilly
CPU). Restore too, but I hope the restore function will never be
called ;-) Nevertheless, when restoring, everybody knows there has
been a problem, while backing up must remain transparent for all
final users.

Bénédicte