Hey, Martijn!

> > 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?
>
> From what I remember, NBackup doesn't "do" transactions, but creates
> a database-page level backup.

As usual you are absolutely correct!


Sean