backup-strategy

Design backup strategies with 3-2-1 rule, retention policies, and verification methods.

50|13|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/chaterm/terminal-skills --skill backup-strategy-chaterm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backup-strategy
Source: https://github.com/chaterm/terminal-skills/tree/main/backup/backup-strategy
Command: npx skills add https://github.com/chaterm/terminal-skills --skill backup-strategy-chaterm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users design and implement effective backup strategies, ensuring data safety and recoverability through best practices like the 3-2-1 rule and various retention policies.

Core Features & Use Cases

  • 3-2-1 Backup Strategy: Understand and implement the core principles of having multiple copies, media, and locations for backups.
  • Backup Types: Learn to perform full, incremental, and differential backups.
  • Retention Policies: Design and implement retention strategies like Grandfather-Father-Son (GFS) and rolling retention.
  • Verification: Implement methods for verifying backup integrity and conducting recovery tests.
  • Use Case: Implement a daily backup of critical data to a local drive, a weekly backup to a NAS, and a monthly backup to cloud storage, with a clear plan for how long each backup is retained.

Quick Start

Design a backup strategy that follows the 3-2-1 rule and includes daily, weekly, and monthly retention policies.

Frequently Asked Questions about backup-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a backup strategy using the 3-2-1 rule?

A 3-2-1 backup strategy requires keeping three copies of your data on two different media, with one copy stored offsite. This approach ensures recoverability by mitigating single-point hardware failures and localized data loss disasters.

What is the difference between full, incremental, and differential backups?

Full backups copy all data, differential backups copy changes since the last full backup, and incremental backups copy changes since the last backup of any type. Combining them optimizes storage space and recovery time objectives.

What's the best way to implement backup retention policies like GFS?

Grandfather-Father-Son (GFS) retention rotates daily, weekly, and monthly backups, keeping recent copies frequently and older copies longer. Rolling retention automatically deletes the oldest backup when a new one is created.

How do I verify backup integrity for disaster recovery?

Verify backup integrity by performing automated checksum validation and scheduling routine recovery tests. These verification methods identify corrupted files or incomplete transfers, ensuring your backup data is actually recoverable during a disaster.

Can I use shell scripts with tar and rsync for automated backups?

Yes, shell scripts using tar and rsync can automate full, incremental, and differential backup workflows. These tools can be combined with cloud CLIs to implement local and offsite copies for disaster recovery.

When should I not use rolling retention for my backups?

Rolling retention is not suitable when regulatory compliance requires keeping specific historical snapshots for extended periods. Grandfather-Father-Son (GFS) policies are better for maintaining long-term monthly or yearly archives.