den 2018-04-06 07:56, skrev Kjell Rilbe
kjell.rilbe@... [firebird-support]:

> den 2018-04-05 09:13, skrev hvlad@...
> [firebird-support]:
> >
> > ---In firebird-support@yahoogroups.com, <kjell.rilbe@...> 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 file touched?
> > >
> > > I'm not sure if it's actually modified, but the timestamp is
> > certainly updated.
> >
> >   Firebird itself doesn't update file timestamp directly.
> > But filesystem often does it in lazy\background mode (for performance
> > reason).
> >
> >   You may know for sure using ProcessMonitor tool, if you wish
>
> Oh, Sorry Vlad, I didn't see your reply at first. My message thread view
> was apparentl corrupt in my e-mail client. Fixed that now.
>
> Sounds like a reasonable explanation. I've inserted a five minute delay
> between lock and copy, but last night's run failed anyway. Guess I'll
> have to investigate a bit more. Thanks for the suggestion with procmon.
>

Process Monitor reveals that the locked database file receives a new
timestamp on the first write by firebird.exe process after the NBACKUP
-L, exepting writes that occur immediately after the lock.

I will try to insert some dummy isql command into the script to see if I
can force this to happen before the copy starts.

Kjell