Administration Guide › Set Up Replication › Multiwrite Replication with DISP Recovery (Multiwrite-DISP) › Transaction Log and Data Recovery › Peer DSAs Recovery

Peer DSAs Recovery

If there is redundancy in the directory configuration, it is possible to recover DSAs from their peers. If a DSA terminates abnormally, and there is a transaction file, the DSA may simply be restarted. If it had multiwrite operations queued, these will be lost. Therefore, the configuration of these DSAs should:

• Enable multiwrite-DISP
• Enable the transaction file

If a DSA terminates normally or abnormally, it may simply be restarted. The transaction file allows the DSA to make the datastore consistent and multiwrite-DISP ensures that the DSA is synchronized with its peers.

Note: For more information, see How Recovery Works in Multiwrite-DISP.

You need to perform disaster recovery if any of the following occurs:

• There is no transaction file
• There was a power outage or an operating system failure
• There was a disk failure
• The DSA has been down for a long time (or it is a new DSA)