3.7 Explain the importance of backups and restores.
📘CompTIA Server+ (SK0-005)
1. File-Level Backup
A file-level backup (also called file-based backup) focuses on individual files and folders.
What it backs up
- Documents (e.g., Word, PDF, Excel files)
- User data (e.g., Desktop, Downloads, shared folders)
- Application files (e.g., configuration files, logs)
Key characteristics
- You select specific files or directories to back up.
- It is commonly used for:
- User data protection
- Application-level recovery
- It is flexible and easy to restore.
- It does not include system configuration or OS components.
Example in IT environment
- Backing up a shared network folder where users store project files.
- Restoring a deleted configuration file from a server directory.
- Recovering a corrupted database export file stored on disk.
Advantages
- Fast backup and restore (only selected data).
- Requires less storage compared to full system backups.
- Easy to manage and schedule.
Limitations
- Does not protect the operating system.
- Cannot restore a full system after a major failure.
- Manual selection may risk missing important files.
2. System-State Backup
A system-state backup captures critical system components that are required for the operating system to function properly.
What it backs up
- Operating system registry
- Boot files
- System files
- Active Directory (on domain controllers)
- COM+ class registration database
- System services and configuration settings
Key characteristics
- Focuses on the system configuration, not user data.
- Used to recover the system to a working state after failure.
- Important for restoring servers, especially domain controllers.
Example in IT environment
- Restoring a server after a corrupted Windows update breaks system functionality.
- Recovering Active Directory after accidental deletion or corruption.
- Fixing registry issues that prevent the server from booting.
Advantages
- Enables recovery of a non-booting system.
- Essential for restoring server roles and services.
- Works together with file-level backups for complete recovery.
Limitations
- Does not include user files or application data.
- Requires more technical knowledge to restore.
- Not as flexible as file-level backups for individual file recovery.
3. Key Differences (Important for Exam)
| Feature | File-Level Backup | System-State Backup |
|---|---|---|
| Scope | Individual files and folders | Operating system and system configuration |
| Includes OS | No | Yes |
| Includes user data | Yes | No |
| Includes Active Directory | No | Yes (on domain controllers) |
| Recovery type | File recovery | System recovery |
| Use case | Recover lost or deleted files | Recover system after failure |
4. When to Use Each Backup Type
Use File-Level Backup when:
- You need to protect user data or shared files.
- You want to recover deleted or corrupted files.
- You are performing routine data protection.
Use System-State Backup when:
- You need to recover a failed operating system.
- You are working with a domain controller.
- You need to restore system settings, registry, or boot configuration.
5. Exam Tips
- File-level backup = data protection
- System-state backup = system recovery
- System-state backups are critical for domain controllers because they include Active Directory.
- Both backup types are often used together in real environments for complete protection.
- Remember: system-state backup alone cannot restore user files.
6. Simple Concept to Remember
- File-level backup protects “what users create”
- System-state backup protects “how the system runs”
