Administration Guide › Set Up Replication › Multiwrite Replication with DISP Recovery (Multiwrite-DISP) › Transaction Log and Data Recovery
Transaction Log and Data Recovery
CA Directory keeps a transaction log of the updates it makes to a datastore. You should configure the transaction log based on your requirements for safety versus performance:
- Disable transaction logging—Provides the highest performance, but if the DSA exits abnormally, or there is a power failure, you will have to perform disaster recovery to restore the datastore from a backup.
- Enable logging without flushing—Provides a performance that almost parallels that of a disabled log. If the DSA exits abnormally, you can simply restart it and recovery is not required. However, if there is a power outage, recovery is necessary.
- Enabled logging with flushing—The safest setting as the DSA can be restarted after an abnormal termination or power failure and recovery is not required. However, there will be around 100 updates per second, instead of around 10,000 per second if flushing was disabled.
Note: Just setting the transaction log to flush to disk may not be enough for safety. This is because many operating systems, depending on configuration and disk systems, may report that the data has been written to disk some time before the transfer actually takes place. Refer to your OS documentation for more information about write behind settings.
