Open topic with navigation
The remote commit and region commit with journaling protocols coordinate messages to the journal with transaction commits. If an SM process terminates unexpectedly, journaling messages are used to ensure that the archive is in a consistent state when it rejoins the database.
Replication files that are required for journaling are stored in a specified journal directory; if not specified, the default directory is
journal in the archive directory.
Note: You can also configure safe commit to run without journaling. Journaling is a separate option.
Caution: For performance and latency purposes, it is best to have the journal and the archive on different disks. A further improvement would entail using different disk controllers. However, if neither the journal nor the archive is available, (or one of them is corrupt), an SM may not start properly and will likely fail.
For data durability:journaling should be enabled.
For redundancy purposes:at least two SMs should be used.
See the Database Options page for details about these and other database options.
Note: You can configure these options with the Automation Console, NuoDB Manager, the REST API Reference, or in the