RTI Persistence Service Crashes in the middle of transaction

Hi

I have written an application which use RTI Persistence Service for saving data in disk. Everything looks fine except when I cut off power from my PC. The next time RTI Persistence Service cannot start and it says that its database is malformed. I have read about this problem in documentations and found this:

Sets the journal mode. This tag can take these values:
DELETE: Deletes the rollback journal at the conclusion of each transaction.
TRUNCATE: Commits transactions by truncating the rollback journal to zero-length instead of deleting it.
PERSIST: Prevents the rollback journal from being deleted at the end of each transaction. Instead, the header of the journal is overwritten with zeros.
MEMORY: Stores the rollback journal in volatile RAM. This saves disk I/O, but at the expense of database safety and integrity.
WAL: Uses a write-ahead log instead of a rollback journal to implement transactions.
OFF: Disables the rollback journal completely. If the persistence service crashes in the middle of a transaction when the OFF journaling mode is set, then the files containing the samples will very likely be corrupted.
Default: DELETE

Can Someone expain more about journal mode and let me know what should I do to prevent this problem? Do I need to create a backup from database and rollback it in case of this problem? Do we have an automatic option for enabling this feature?

Thanks in advance for your helps.

Bonjefir