backup-retention-policy

The 3-2-1-1-0 rule is a data protection strategy requiring three copies of data on two different media, with one offsite, one offline copy, and zero errors after validation. It improves disaster recovery by ensuring redundant, verified backups survive various failure scenarios.

You can configure AWS S3 lifecycle policies using JSON configurations to automate data tiering and retention. This Skill provides specific JSON examples to transition objects between storage classes and expire them based on compliance requirements like GDPR or SOX.

You can automate PostgreSQL and MySQL database backup rotation using bash scripts. This Skill includes practical scripting examples that handle backup creation and apply retention policies to delete outdated backups automatically.

Calculating RTO (Recovery Time Objective) and RPO (Recovery Point Objective) defines your maximum tolerable downtime and data loss during a disaster. This Skill outlines planning strategies to align your backup frequency and retention policies with these targets.

Yes, this backup retention policy guidance covers HIPAA and SOX compliance requirements. It outlines specific data lifecycle management strategies to ensure your backup rotation and storage configurations meet regulatory standards for data preservation and auditability.