Preventing Data Loss Pt.1 – CompTIA Security+ Lesson 14

Sooner or later, your equipment will fail, an thus result in a loss of data. Implementing fault tolerance is a good way of preventing data loss.

In this post I will give you a quick overview on preventing data loss through fault tolerance.

What does that even mean? It means we’re gonna take a look at Backups and RAID systems.

If you’re following this weekly series, you are probaly familiar with the importance of backups from posts like this and this.


A backup is the periodic archiving of data. The data can be restored from the archive, if there is a server failure.

Different types of backups give you a range of options to which to choose from. Either one has pros and cons, and which one you use depends on the requirements.

Type Description Pros Cons
Full Archives ALL changes made to the data
  • saves all the data
  • requires you only
    to restore one
  • time consuming
  • resource intensive
  • negative impact
    on server per-
Differential All changes since the last FULL BACKUP are archived
  • less resource intensive
  • just one step more
    to restore data
    (Restore full
    backup+ differential
  • backups get larger
    each time
  • will  still have an
    impact on server
    (but not as much
    as a full backup)
Incremental All changes since the last backup of ANY TYPE are archived
  • least resource intensive
  • small backups
  • does not take much time
  • every incremential
    backup must be restored
    in order of archiving
  • more complex to restore

A good way to keep backups is to make a full backup each day when no ones working. Like 2 AM.

Then you can continue to make more backups throughout the day. But which type you use is up to you, the requirements and the equipment that you use.

The only effective way to test your backup strategy is to restore the backup data to a test machine.

Stay tuned for next weeks Pt.2 : Raid systems.