Berkeley DB Reference Guide: Log file only clients
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++

### Berkeley DB Reference Guide: Berkeley DB Replication |

# Log file only clients

Applications wanting to use replication to support recovery after catastrophic failure of the master may want to configure a site as a logs-file-only replica. Such clients cannot respond to read (or write) queries but still receive a complete copy the log files, so that in the event of master failure, catastrophic recovery can be run.

Log file only clients are configured like other client sites, except they should specify the DB_REP_LOGSONLY flag to the DB_ENV->rep_start function and should specify a priority of 0 to the DB_ENV->rep_elect function.

To recover using a log-file-only replica, recovery must be run on the log files accumulated by the replica. If the log files are entirely self-contained, that is, they start with log file number 1, then a log replica can simply run catastrophic recovery. Obviously, if there are a large number of log files in this case, recovery may take a long time. If the log files are not self-contained, an archival copy of the databases must first be restored onto the replica before running catastrophic recovery.

More specifically, the log files accumulating on the log-file-only replica can take the place of the log files described in catastrophic recovery section of the Recovery procedures Berkeley DB Reference Guide.

In all other ways, a log-file-only site behaves as other replication clients do. It should have a thread or process receiving messages and passing them to DB_ENV->rep_process_message and must respond to all returns described for that interface.

Copyright Sleepycat Software