HSQLDB employs a REDO log for data recovery. All the changes to the database are reflected in this log. Extensive user tests have demonstrated this mechanism to be effective and fail-safe in most cases. For ADDED security, you can BACK up the database files while the engine is running using the BACKUP DATABASE command.

By default, a FileDescriptor.sync () call is made every 500 milliseconds on the redo log file. If the MACHINE or the Java process is likely to crash often, you can reduce this down to 20 milliseconds for more frequent sync() calls. You can also specify 0 to force a sync () on each commit. This SETTING can be changed with "SET FILES WRITE DELAY MILLIS m" or the equivalent connection property.

With all the rest of the database files, calls to sync () are made at all critical points to ensure the files are consistent both after a shutdown and after a crash.

HSQLDB employs a redo log for data recovery. All the changes to the database are reflected in this log. Extensive user tests have demonstrated this mechanism to be effective and fail-safe in most cases. For added security, you can back up the database files while the engine is running using the BACKUP DATABASE command.

By default, a FileDescriptor.sync () call is made every 500 milliseconds on the redo log file. If the machine or the Java process is likely to crash often, you can reduce this down to 20 milliseconds for more frequent sync() calls. You can also specify 0 to force a sync () on each commit. This setting can be changed with "SET FILES WRITE DELAY MILLIS m" or the equivalent connection property.

With all the rest of the database files, calls to sync () are made at all critical points to ensure the files are consistent both after a shutdown and after a crash.