Fault Tolerant Design
SpiderOak was designed and implemented by engineers with a background in fault tolerant systems with a margin of error of 0.0000%.
Consider what might happen if you are working on a document, hit Save, and just as the document is halfway through overwriting the old version, the power fails. You may now have replaced the old copy of the document with a half-written, corrupted document that you cannot open.
Most programs are not created using a fault tolerant design, but your backup software absolutely should be.
The biggest worry with corrupted backups is that you don't notice — until you try to restore. You might go on with a false sense of security knowing all your data is safe. SpiderOak eliminates this concern.
If your hardware, operating system, or electrical power fails, SpiderOak’s design makes it impossible for your backup result to be corrupted.
We accomplish this with a transactional file system layer and application level transactions. SpiderOak works as a fully ACID compliant database, distributed across each computer you use SpiderOak from, and the SpiderOak servers. But basically, what you need to know is this approach is significantly different from the way most applications are engineered.