--- In Firebird-Architect@yahoogroups.com, Dmitry Yemanov
<dimitr@...> wrote:

>
> m_theologos wrote:
> >
> > What do you say?
>
> How is it going to know changes made by other processes (in the

classic

> mode)?
>
>
> Dmitry
>

Sorry Dimitry, I don't understand very well. AFAIK, NBackup will log
on _ON_THE_DATABASE_ as another user (thus, in the classic mode will
create another process) will issue an ALTER DATABASE BEGIN BACKUP,
do his job in HIS transaction, after this issue an ALTER DATABASE
END BACKUP and exit closing the process. This is the way in which
works today. Where is the problem if, instead exiting will wait some
time and/or some ammount of changes and do the entire procedure
again? I don't see what's the problem with the other processes?
Aren't FB ACID compilant? Or I'm missing something?

Another very important thing, regarding to the Sean's message, this
will be a very important advantage IMHO rather than creating/closing
server processes only to do an incremental backup (which is the case
in classic mode) which will be a very important speed gain.