Subject | Re: [firebird-support] Re: Timestamp of Database File |
---|---|
Author | Kjell Rilbe |
Post date | 2012-02-29T21:29:32Z |
Den 2012-02-29 22:22 skrev Doug Chamberlin s�h�r:
copied using Nbackup or a regular file copy tool. Or backup software.
After backup completion, the changes are merged back and the delta file
is deleted.
I did have some issue with it 1-2 years ago, with a rather large DB.
Some problem with transaction commit during nbackup locked state. I
never had time to investigate if it was really caused by nbackup, but it
only happened in that state...
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64
[Non-text portions of this message have been removed]
>Yes. Using Nbackup the main DB file is a snapshot that can be safely
> On 2/29/12 3:47 PM, Leyne, Sean wrote:
> > The NBackup functionality allows a database file to be quiesced (with
> > changes written to a delta file) to allow for OS level backups to be
> > performed (thru Lock and Unlock options).
> But doesn't that just move the potential conflict to the delta file,
> leaving you with the same issue but in a different place? I don't see
> that it really improves things all that much.
>
> Well, on further thought I suppose the original database file could then
> be thought of as internally consistent as of the time NBackup was
> started. Is that what you were getting at?
>
>
copied using Nbackup or a regular file copy tool. Or backup software.
After backup completion, the changes are merged back and the delta file
is deleted.
I did have some issue with it 1-2 years ago, with a rather large DB.
Some problem with transaction commit during nbackup locked state. I
never had time to investigate if it was really caused by nbackup, but it
only happened in that state...
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64
[Non-text portions of this message have been removed]