Hi

> Correct, but that information is actually stored as a "version number" in the header of each data page. When page data changes

the "version number" is changed.

> The nbackup database structure only stores the "version number" for the backup level.

From a quick search, I suspect that will be the "pag_scn" 4 byte value.
That would mean that I could relatively easily write my own sync code that could also read all those values and decide which page
would need to be transferred while the file is locked.

The advantage above nbackup would simply be that I could control the way the information is merged and stored on the server better
and that I could use that information to update different clients at different times (with no common base).
The disadvantage would be that I would need to keep close control of these files as nbackup could not come to help to prevent
incorrect ordering while merging...

> NBackup physically reads each page header to determine if the page "version" has changed since the last backup.

Does NBackup do any other magic than that?


Regards,
Steffen




[Non-text portions of this message have been removed]