dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability [2020/11/14 17:59] nick [4.2.2.4 Recoverability] |
dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability [2021/07/30 12:43] (current) murphy [About] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 4.2.2.4 Recoverability ====== | + | ====== 4.3.2.4 Recoverability ====== |
| [[dido:public:ra:1.4_req:2_nonfunc:14_reliability | Return to Reliability ]] | [[dido:public:ra:1.4_req:2_nonfunc:14_reliability | Return to Reliability ]] | ||
| Line 5: | Line 5: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability | Return to the Top]] | [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability | Return to the Top]] | ||
| - | [[[[dido:public:ra:xapend:xapend.a_glossary:r:recoverability]] is the ability of a system to be rebuilt in the event of a system failure do to human or natural disasters or catastrophic failures in hardware or software. After the system is recovered it is able to resume with full functionality with minimum interruption. For example in [[dido:public:ra:xapend:xapend.a_glossary:d:dbms|DataBase Management System's (DBMS)]], a Checkpoint is a place in time where the database transactions, operations, and [[dido:public:ra:xapend:xapend.a_glossary:d:datalog|logging]] are paused long enough to be completed and recorded into the database files. These files are then archived (i.e., copied, backed up) away from the current database files. After the Checkpoints operation is complete, the DBMS can resume with new transactions, operations and logging. Although the concepts of a Checkpoints are usually thought of in conjunction with DBMSs, it is also possible to have Checkpoints applied to [[dido:public:ra:xapend:xapend.a_glossary:o:os | Operating Systems (OSs)]] as well. [[dido:public:ra:xapend:xapend.a_glossary:v:vm | Virtual Machines (VMs)]] and containers (i.e., [[dido:public:ra:xapend:xapend.a_glossary:d:docker]]) can be thought of as a checkpoint made against the OS files, logs, etc. at a particular point in time. Every time the VM or [[dido:public:ra:xapend:xapend.a_glossary:c:container|Container]] are reloaded, they start from a set known point (a Checkpoint). | + | [[[[dido:public:ra:xapend:xapend.a_glossary:r:recoverability]] is the ability of a system to be rebuilt in the event of a system failure do to human or natural disasters or catastrophic failures in hardware or software. After the system is recovered it is able to resume with full functionality with minimum interruption. For example in [[dido:public:ra:xapend:xapend.a_glossary:d:dbms|DataBase Management System's (DBMS)]], a Checkpoint is a place in time where the database transactions, operations, and [[dido:public:ra:xapend:xapend.a_glossary:d:datalog|logging]] are paused long enough to be completed and recorded into the database files. These files are then archived (i.e., copied, backed up) away from the current database files. After the Checkpoints operation is complete, the DBMS can resume with new transactions, operations and logging. Although the concepts of Checkpoints are usually thought of in conjunction with DBMSs, it is also possible to have Checkpoints applied to [[dido:public:ra:xapend:xapend.a_glossary:o:os | Operating Systems (OSs)]] as well. [[dido:public:ra:xapend:xapend.a_glossary:v:vm | Virtual Machines (VMs)]] and [[dido:public:ra:xapend:xapend.a_glossary:c:container|containers]] (i.e., [[dido:public:ra:xapend:xapend.a_glossary:d:docker]]) can be thought of as a checkpoint made against the OS files, logs, etc. at a particular point in time. Every time the VM or [[dido:public:ra:xapend:xapend.a_glossary:c:container|Container]] are reloaded, they start from a set known point (a Checkpoint). |
| - | ===== DDS Specifics ===== | + | ===== DIDO Specifics ===== |
| [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability | Return to the Top]] | [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:12_recoverability | Return to the Top]] | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary:d:data_distribution_service_dds]] can log all the messages sent over a [[dido:public:ra:xapend:xapend.a_glossary:t:topic]]. The logs can then be replayed back in order to restore or recreate a particular scenario in the future This is invaluable for testing and training not just for the DDS infrastructure but also the components that use the DDS, and the people that use the system such as [[dido:public:ra:xapend:xapend.a_glossary:c:c2]] consoles, medical devices scenarios, etc. | ||
| - | |||
| - | * **Note:** There are several excellent examples provided in section [[ddsf:private:cookbook:03_user]]. | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.4_req/2_nonfunc/14_reliability/12_recoverability.1605394741.txt.gz · Last modified: 2020/11/14 17:59 by nick
