The HSQL documentation has the following to say about the "NOT BLOCKING" option on backups:

Hot backup is performed if NOT BLOCKING is specified. In this mode, the database can be used during backup. This mode should only be used with very large databases. A hot backup set is less compact and takes longer to restore and use than a normal backup set produced with the BLOCKING option.

Our databases can be quite large, so we're definitely interested in not blocking the application during backup. Based on this description, it sounds like it should be "safe" to use NOT BLOCKING. My main concern is that it would backup "partial" transactions if changes were being made during backup.

Since there is no mention of data integrity issues, can I assume it's safe to use NOT BLOCKING if I'm not concerned about backup size or restore time?


Yes, you can assume it is safe to use NOT BLOCKING as a valid means of backing up your HSQLDB.

I don't believe the backup would contain "partial" transactions, more likely all versions encountered during the backup operations, hence the larger backup size and more complicated restore process.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.