4.3 Given a scenario, implement workstation backup and recovery methods.
📘CompTIA A+ Core 2 (220-1202)
When you back up a workstation (computer or server), creating the backup is only half the job. You also need to test those backups to make sure they actually work when you need them. This is called backup testing.
Why Backup Testing is Important
- Backups can fail without you noticing. For example:
- The backup might not have copied all files.
- The backup might be corrupted.
- The backup might be incomplete because the computer was in use.
- If a disaster happens (like accidental deletion, ransomware, or hardware failure), untested backups can be useless.
- Testing ensures that data can be restored successfully, saving time, money, and stress.
Backup Testing Frequency
The frequency of testing backups depends on the importance of the data and the organization’s policy. Here’s what you need to know:
- Daily Backups
- Test at least once a week.
- Example: A company backing up emails every night should check that they can restore a sample email folder weekly.
- Weekly Backups
- Test every month.
- Example: A workstation that backs up project files weekly should test one of the weekly backups to make sure all project files are intact.
- Monthly or Less Frequent Backups
- Test before major restores or quarterly.
- Example: A system backup taken at the end of the month should be tested once every quarter to ensure it works for disaster recovery.
Testing Methods
There are a few common ways to test backups:
- Restore a Sample File
- Pick one or two files from the backup and restore them.
- Check if the files open and work correctly.
- Example: Restore a document from yesterday’s backup to a test folder.
- Full Restore Test
- Restore the entire system or critical files to a test computer or virtual machine.
- Ensures everything works as expected.
- Example: Restore a user’s profile, settings, and documents to a virtual machine to check functionality.
- Verify Backup Logs
- Check backup software logs to make sure backups completed without errors.
- Example: A backup program might show “Backup completed – 100% success.”
Key Points for the Exam
- Backups must be tested regularly – creating a backup is not enough.
- The testing frequency depends on:
- How often data changes.
- How critical the data is.
- Organizational policies or SLAs.
- Common testing practices include sample restores and full restores.
- Backup testing helps prevent surprises during actual disasters.
✅ Memory Tip:
Think of it as “Backup it, Test it, Trust it.” You can’t trust a backup until you test it.
