3 Ways to Achieve Crash Consistency
“Even well-managed data centers suffer from occasional power-loss events,” says Ram Alagappan in a recent article for ACM Queue, which means ensuring crash consistency across data storage systems is crucial.
“A storage system is deemed crash-consistent if it can recover the persistent data it stores to a meaningful state after crashes,” Alagappan says, but achieving this state can be quite challenging.
This article explores three ways (through three research papers) to help: “finding and fixing crash-consistency bugs; developing new abstractions that ease crash consistency; and exploiting new hardware.”
Read more at ACM Queue.
Related content
-
A storage engine for every use case
You can choose from among a number of open source database storage engines for both general and specialized data. - Better Crash Recovery with Journaling in MongoDB
-
A Real-World Look at Scaling to the Amazon Cloud
The Amazon cloud environment adapts easily to custom solutions. We'll show you how one company built their solution in the cloud.
-
Analyzing Kernel Crash Dumps
If the Linux server crashes, not only do you need to restore operations, you also need to analyze the problem. A kernel crash dump at the time of the crash can be a big help.
-
Integrating FreeNAS with Windows Active Directory
FreeNAS offers a powerful array of features and is adaptable to a wide range of network-attached storage solutions. We look at integrating Windows Active Directory, taking snapshots, replicating, and backing up.