> It will reduce the system load on loading/unloadig a program
> (NBackup), creating/destroing a process (CPU, memory (de)allocating)
> aso. and also the FB server load (it cuts down the time and the
> resources (de)allocated on logging on/off).

It would be my opinion that this overhead is minimal.

> Also, most probably, both NBackup and FB has
> internal data structures which must be allocated in order to do the
> backup which, in case of a permanent watch are only to be maintained.

All of the NBackup data is stored in the local database in a new RDB$
table, but this data is read at the start of the backup and then updated
at the end of the backup. When NBackup is running or not running, no
structures are specifically maintained by the engine.


Finally, what you propose would seem to be a function which maintains a
database mirror. If that is the case, then there are better ways to
approach this.


Sean