Subject | Re: Some enhancements to NBackup to allow backups more often |
---|---|
Author | m_theologos |
Post date | 2006-09-15T17:42:55Z |
--- In Firebird-Architect@yahoogroups.com, "Leyne, Sean" <Sean@...>
wrote:
(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). See the Microsoft's
Robocopy documentation. 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.
In a few simplistic words, we talking here about the advantages of
connection polling, isn't it?
HTH,
m. Th.
wrote:
>It will reduce the system load on loading/unloadig a program
>
> > Can you add at the NBackup some flags in order to leave the NBackup
> > permanently open and logged on in the FDB(s)?
>
>
> > What do you say?
>
> Please explain what problem you think these changes will resolve.
>
>
> Sean
>
(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). See the Microsoft's
Robocopy documentation. 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.
In a few simplistic words, we talking here about the advantages of
connection polling, isn't it?
HTH,
m. Th.