|
Size: 1176
Comment:
|
Size: 2562
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| Berkeley DB provides guarantees about atomicity and durability by first writing changes to a series of log files. A transactions is not marked as committed until it has been flushed to stable storage. This allows recovery from a crash without loss of data. | |
| Line 9: | Line 8: |
| In the event of a crash or hardware failure, the log files will be examined. All committed transactions will be written out to the BTree files (in $DB_HOME/data) and any uncommitted transactions will be aborted. | ---- /!\ '''Edit conflict - other version:''' ---- EMEN2 uses Berkeley DB as the underlying database technology. To provide guarantees about transaction atomicity and durability, Berkeley DB writes changes first to a log file on stable storage before a transaction is marked as committed. Database files are not updated until this step is complete. In the event of a crash or hardware failure, the database files can be checked against the log files to correct any errors or missing data. |
| Line 11: | Line 11: |
| The log files are stored in $DB_HOME/log as log.XX, where XX is a sequential integer starting from 1. With default settings, the files are 8 MB each. As one log file is finished, the next log file in the sequence is created and used as the active log file. | The log files are stored in $DB_HOME/log as log.XX, where XX is a sequential integer starting from 1. With default settings, the files are 8 MB each. As one log file is finished, the next log file in the sequence is created and used as the active log file. ---- /!\ '''Edit conflict - your version:''' ---- EMEN2 uses Berkeley DB as the underlying database technology. To provide guarantees about transaction atomicity and durability, Berkeley DB writes changes to a log file on stable storage before a transaction is marked as committed. Database files are not updated until this step is complete. In the event of a crash or hardware failure, the database files can be checked against the log files to correct any errors or missing data. The log files are stored in $DB_HOME/log as log.XX, where XX is a sequential integer starting from 1. With default settings, the files are 8 MB each. As one log file is finished, the next log file in the sequence is created and used as the active log file. ---- /!\ '''End of edit conflict''' ---- |
| Line 15: | Line 22: |
| .. more to come .. | |
| Line 17: | Line 23: |
| ---- /!\ '''Edit conflict - other version:''' ---- The EMEN2 backup utility will archive finished logs when run with the "--archive" flag. Finished log files will be moved to the location specified by the "ARCHIVE" configuration setting. {{{ backup.py --archive }}} ---- /!\ '''Edit conflict - your version:''' ---- The EMEN2 backup utility will archive finished logs when run with the "--archive" flag. Finished log files will be moved to the location specified by the "ARCHIVE" configuration setting. {{{ backup.py --archive }}} ---- /!\ '''End of edit conflict''' ---- |
EMEN2 Maintenance and Backups
EMEN2 supports three types of backups: Log Archive, Cold Backup, and Hot Backup.
Log Archive
![/!\](/emanwiki/moin_static197/modern/img/alert.png "/!\"){kind=small}
Edit conflict - other version:
EMEN2 uses Berkeley DB as the underlying database technology. To provide guarantees about transaction atomicity and durability, Berkeley DB writes changes first to a log file on stable storage before a transaction is marked as committed. Database files are not updated until this step is complete. In the event of a crash or hardware failure, the database files can be checked against the log files to correct any errors or missing data.
The log files are stored in $DB_HOME/log as log.XX, where XX is a sequential integer starting from 1. With default settings, the files are 8 MB each. As one log file is finished, the next log file in the sequence is created and used as the active log file.
Edit conflict - your version:
EMEN2 uses Berkeley DB as the underlying database technology. To provide guarantees about transaction atomicity and durability, Berkeley DB writes changes to a log file on stable storage before a transaction is marked as committed. Database files are not updated until this step is complete. In the event of a crash or hardware failure, the database files can be checked against the log files to correct any errors or missing data.
The log files are stored in $DB_HOME/log as log.XX, where XX is a sequential integer starting from 1. With default settings, the files are 8 MB each. As one log file is finished, the next log file in the sequence is created and used as the active log file.
End of edit conflict
Log files that are not being used by any open transaction may be archived after a "Checkpoint" is made. This frees up disk space in the DB_HOME environment, and lets the administrator move the logs to long term archival storage.
Edit conflict - other version:
The EMEN2 backup utility will archive finished logs when run with the "--archive" flag. Finished log files will be moved to the location specified by the "ARCHIVE" configuration setting.
backup.py --archive
Edit conflict - your version:
The EMEN2 backup utility will archive finished logs when run with the "--archive" flag. Finished log files will be moved to the location specified by the "ARCHIVE" configuration setting.
backup.py --archive
End of edit conflict
Cold Backup