|
⇤ ← Revision 1 as of 2010-03-29 10:14:39
Size: 87
Comment:
|
Size: 1176
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Coming soon | EMEN2 supports three types of backups: Log Archive, Cold Backup, and Hot Backup. |
| Line 5: | Line 5: |
| see: emen2/cmdlineutils/backup.py | == Log Archive == 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. 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. 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. 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. .. more to come .. == Cold Backup == == Hot Backup == |
EMEN2 Maintenance and Backups
EMEN2 supports three types of backups: Log Archive, Cold Backup, and Hot Backup.
Log Archive
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.
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.
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.
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.
.. more to come ..
Cold Backup