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

Gregory,

EDB starts a transaction that lasts while the backup is running and that's how it guaranties consistency.
EDB transactions don't block reads but block all writes to the database, so it's important to ensure they are fast.
Although EDB backups are fast, they should always be done to a local disk for speed and reliability.
My strategy is to backup to a local store, and then a scheduled job copies it to a remote store at night.

--
Fernando Dias
[Team Elevate]