How does ElevateDB ensure data consistency over a hot backup? Other DBMSs take a snapshot, which of course does not include uncommitted transactions, then backs up the snapshot at leisure.

Given that, I'm happy.

Failing that, it has been suggested I use PUBLISH TABLE and SAVE UPDATES to keep an up to date copy of changes. So the sequence would be:

a: Cold, i.e. no activity, backup
b: PUBLISH TABLE
c: SAVE UPDATES
**Crash**
d: Restore from [a]
e: LOAD UPDATES

And get everything back up to the most recent saved updates, including generated fields and updated seeds.

So questions are: does backup take a snapshot?
Does PUBLISH TABLE omit uncompleted transactions? or, does SAVE UPDATES work hot, in the sense that it takes a snapshot or omits uncommitted transactions and prevents commits until the save is complete?

Does LOAD UPDATES load the saved versions of generated fields and update seeds for identity elements?
Gregory Swain

On 10/18/2022 3:15 PM, Gregory T Swain wrote:
> How does ElevateDB ensure data consistency over a hot backup? Other DBMSs take a snapshot, which of course does not include uncommitted transactions, then backs up the snapshot at leisure.
>
> Given that, I'm happy.

As long as you use EDB built-in backup data is consistent - there is a
read lock on the database while backup runs (size of DB determines
length of the read lock but it is fast)

See more here
https://www.elevatesoft.com/manual?action=viewtopic&id=edb2&product=rsdelphiwin32&version=11&topic=Backing_Up_Restoring_Databases

Raul