000 | a | ||
---|---|---|---|
999 |
_c9738 _d9738 |
||
003 | OSt | ||
005 | 20191017141039.0 | ||
008 | 191017b xxu||||| |||| 00| 0 eng d | ||
040 |
_aAIKTC-KRRC _cAIKTC-KRRC |
||
100 |
_99911 _aRathore, Neeraj |
||
245 |
_aRathore, Neeraj _b:Fault Tolerance Mechanism |
||
250 | _aVol.4(1), Jan-June | ||
260 |
_aTamil Nadu _bi-manager's _c2017 |
||
300 | _a28-34p. | ||
520 | _aCheckpointing is a technique for inserting fault tolerance into computing systems. It basically consists on storing a snapshot of the current application state, and uses it for restarting the execution in case of failure. It is saving the program state, usually to stable storage, so that it may be reconstructed later in time. Checkpointing provides the backbone for rollback recovery (fault-tolerance), playback debugging, process migration, and job swapping. It mainly focuses on fault-tolerance, process migration, and the performance of checkpointing on all computational platforms from uniprocessors to supercomputers. Checkpointing and restart has been one of the most widely used techniques for fault tolerance in large parallel applications. By periodically saving application status to permanent storage (disk or tape), the execution can be restarted from the last checkpoint if system faults occur. It is an effective approach to tolerating both hardware and software faults. For example, a user who is writing a long program at a terminal can save the input buffer occasionally to minimize the rewriting caused by failures that affect the buffer. | ||
650 | 0 |
_94622 _aComputer Engineering |
|
773 | 0 |
_ti-manager's journal on cloud computing (JCC) _dNagercoil i-manager Publication _x 2349-6835 |
|
856 |
_uhttps://www.imanagerpublications.com/article/13756/23 _yClick here |
||
942 |
_2ddc _cAR |