Learn Veeam - Data Protection History: 3-2-1 & Retention

#Introduction

Now that the repository is sorted in episode 6, let's step back for a moment to understand why retention and duplicate copies matter. In episode 7 we trace the history of data protection concepts — from single-copy tape to the 3-2-1 rule — then apply it in Veeam with GFS retention and Backup Copy Jobs.

Most organizations die not because backups fail, but because they design retention wrong or keep all their eggs in one basket. This episode answers the classic question: how long should data be kept, and where?

#Data Protection History

#The Tape Era: One Copy, One Location

Before the digital age, backups were made by copying data to tape and carrying it to another location. The problem: one copy (prone to damage), slow restores (you had to search the tape for the right position), and no routine verification. Many admins discovered their tape was damaged after the disaster happened — exactly when it was needed.

#The Birth of the 3-2-1 Rule

As disaster recovery spread, industry practice formulated a rule that is now the gold standard:

• 3 copies of the data (1 production + 2 backups).
• 2 different media/technologies (e.g. disk + tape, or disk + object storage).
• 1 off-site copy (in a location different from the production data).

Copy 1: production data (hypervisor)
Copy 2: backup at the main site (local repository)
Copy 3: backup at a second site (off-site / cloud)
  └── different media (disk vs object storage)
  └── different location (site A vs site B)

Why "in a different location"? Because the worst-case events (data center fire, mass ransomware, natural disasters) destroy everything in one place. The off-site copy is the last safety net.

#Retention: GFS and KeepN

#Restore Points and the KeepN Policy

Every backup leaves a restore point — a point in time you can restore from. The KeepN policy is simple: keep the last N restore points, delete the older ones. Example: Keep 14 restore points means the last 14 daily backups.

#GFS (Grandfather-Father-Son)

GFS extends retention to four time levels:

• Daily (Son): daily backups — e.g. keep 7 days.
• Weekly (Father): weekly backups — e.g. keep 4 weeks.
• Monthly (Grandfather): monthly backups — e.g. keep 12 months.
• Yearly: yearly backups — e.g. keep 3 years.

$gfs = New-VBRRetentionOptions -KeepDaily 7 -KeepWeekly 4 `
    -KeepMonthly 12 -KeepYearly 3 -WeeklyBackupOn Sunday -MonthlyBackupOn LastDay
Set-VBRJob -Job $job -RetentionOptions $gfs

The advantage of GFS: it meets compliance and legal requirements (old data is still there) without storing every daily restore point — dramatically saving storage.

#Backup Copy Jobs: The Second (Off-Site) Copy

#Why Backup Alone Is Not Enough

The primary backup in the local repository can be lost together with production data in a disaster. Veeam's solution: Backup Copy Jobs — copying restore points from the primary job to a second repository (in a different location or the cloud).

#How Backup Copy Works

• The copy job points to the primary backup job and the destination repository.
• It runs separately from the primary schedule (e.g. at night after the backup completes).
• Veeam only transfers block changes since the last copy — efficient over WAN.

$sourceJob = Get-VBRBackup -Name "Backup WebServer-01"
$targetRepo = Get-VBRBackupRepository -Name "OffsiteRepo"
Add-VBRBackupCopyJob -Name "Copy WebServer-01" -Backup $sourceJob `
    -Repository $targetRepo

#Off-Site Made Easy

Paired with episode 19 (cloud & hybrid), a copy job can copy to cloud object storage (S3/Azure/GCP) or a repository at the DR site — realizing the "1 off-site copy" of the 3-2-1 rule automatically and on schedule.

#Applying 3-2-1 in Veeam

The complete setup in Veeam:

1. Backup job → local repository (copy 2, disk media).
2. Backup copy job → off-site repository or SOBR capacity tier (copy 3, object storage media, different location).
3. GFS retention → Daily/Weekly/Monthly/Yearly history for compliance.
4. Tape-out (optional) → a third medium for long-term archive.

#Verification

Get-VBRBackupCopyJob | Format-Table Name,TargetRepoName,LastResult -AutoSize
Get-VBRRestorePoint -Backup "Backup WebServer-01" | Format-Table CreationTime -AutoSize

Make sure the restore points from the copy job appear in the off-site repository.

#Closing

Key takeaways:

• The 3-2-1 rule: 3 copies, 2 media, 1 off-site — the gold standard of data protection.
• KeepN for simple retention; GFS (Daily/Weekly/Monthly/Yearly) for compliance.
• Backup Copy Jobs copy backups to a second repo efficiently (block-level).
• 3-2-1 + immutability + verification = 3-2-1-1-0.
• Off-site can be a DR site repository or cloud object storage.

In the next episode, episode 8, we will cover restores: instant & granular — running a VM directly from backup with Instant Recovery, migrating back (re-host), Instant File Recovery, application item restore via Explorers, and verification with SureBackup/Instant VM. Time to prove your backups can really be brought back!