Backup Strategy Basics What is the most appropriate general strategy for scheduling backups in a typical installation to balance data safety and storage/time costs?

Introduction / Context:
A sound backup plan seeks to minimize data loss (recovery point objective) while keeping restore times acceptable (recovery time objective). Pure daily full backups are safe but expensive; pure incremental backups save space but can slow restores. A balanced, widely used approach is to run several incrementals between periodic full (image) backups.

Given Data / Assumptions:

• Typical mixed-use environment (files, documents, small databases).
• Desire to reduce backup windows and storage consumption.
• Need for quick restoration of current state within practical time.

Concept / Approach:
Combine full backups with a chain of incremental backups. The full backup captures the entire data set (a clean base). Incrementals capture only changes since the previous backup, reducing duration and storage. Periodically refreshing with another full backup shortens the chain used during restores, making recovery faster and more reliable.

Step-by-Step Solution:
Select a cadence: for example, weekly full + daily incremental.Full (image) backup establishes a baseline snapshot.Run incrementals on intervening days to capture changes.Repeat the cycle so that restores require at most one full plus a limited set of incrementals.

Verification / Alternative check:
Test restores periodically. Verify you can restore from the latest full plus subsequent incrementals to a known-good state. Measure restore time and ensure it meets business needs.

Why Other Options Are Wrong:
Daily full only (Option A) is safe but often impractical due to time/storage.Weekly only (Option B) risks too much data loss between backups.Fulls followed by a single incremental (Option C) inverts the efficient norm; you typically want several incrementals between fulls, not the reverse.“None of the above” is incorrect because Option D reflects the practical hybrid.

Common Pitfalls:

• Not rotating fulls, causing long incremental chains and slow restores.
• Failing to verify backups through test restores.
• Storing backups only onsite, risking correlated loss.

Final Answer:
As several incrementals, followed by an image (full) copy.