den 2018-04-06 18:08, skrev hv...@users.sourceforge.net [firebird-support]:
>
> > Thanks! As a workaround, I attempted gfix -write sync, but alas, it
> will
> > work only if no other attachments. We start the copy at midnight, when
> > it's likely there won't be other connections, but can't be gua
> Thanks! As a workaround, I attempted gfix -write sync, but alas, it will
> work only if no other attachments. We start the copy at midnight, when
> it's likely there won't be other connections, but can't be guaranteed.
>
> For now, I've added, between lock and copy, a dummy isql script that
den 2018-04-06 10:53, skrev hv...@users.sourceforge.net [firebird-support]:
>
> > After testing a bit more, I notice that the locked database file has
> its
>
> > timestamp updated when firebird.exe does a "FlushBuffersFile"
> operation,
> > which can occur several minutes after the NBACKUP -L op
> After testing a bit more, I notice that the locked database file has its
> timestamp updated when firebird.exe does a "FlushBuffersFile" operation,
> which can occur several minutes after the NBACKUP -L operation.
>
> Isn't that a bug? Everything should be flushed to file immediately when
>
Den 2018-04-05 09:13, skrev hv...@users.sourceforge.net [firebird-support]:
>
> ---In firebird-support@yahoogroups.com, wrote :
>
> ...
> >
> > It seems like the original database file is touched about a half to one
> > minute after being locked with NBACKUP -L.
> >
> > Why is the locked database
den 2018-04-06 07:56, skrev Kjell Rilbe
kjell.ri...@marknadsinformation.se [firebird-support]:
> den 2018-04-05 09:13, skrev hv...@users.sourceforge.net
> [firebird-support]:
> >
> > ---In firebird-support@yahoogroups.com, wrote :
> >
> > ...
> > >
> > > It seems like the original database file
den 2018-04-05 09:13, skrev hv...@users.sourceforge.net [firebird-support]:
>
> ---In firebird-support@yahoogroups.com, wrote :
>
> ...
> >
> > It seems like the original database file is touched about a half to one
> > minute after being locked with NBACKUP -L.
> >
> > Why is the locked database
