Backup and Restore: Discover Best Practices for a Distributed Database Backup Strategy
summary
YugabyteDB runs online backups that are topologically independent, copying tablet-level snapshot hard links in parallel to S3/GCS/Azure or NFS with SHA-256 checksums; YCQL supports table/keyspace backups while YSQL is database-level. Restores map tablet IDs (example: RF3 → RF1) and replay data; PITR uses in-cluster snapshots plus PITR with MVCC (snapshots every 24h, three-day retention yields continuous history and microsecond RPOs). Backups 2.0 adds a per-node sidecar and delta uploads, claiming 4-5x faster backups and lower network/storage costs.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:32What Is the Purpose of Backup
- 6:50Backing Up a Database
- 8:06Create a Backup
- 13:44Restoring a Database
- 17:42Point in Time Recovery
- 21:27Point in Time Recovery Management
- 22:09Backup Studio
- 25:51Distributed Snapshots
related talks
57mNo Downtime, No Limits
27mIntroduction to YugabyteDB – Design and Architecture
26mIntroducing YugabyteDB for PostgreSQL Users
32mDay 2 Operations Best Practices
25mYugabyteDB Technical Overview
27mIntroduction to YugabyteDB: Design and Architecture
32mArchitectural Flexibility and Geo-Specificity with Cluster-to-Cluster Replication
30mBuilding Cloud Native Applications on Distributed SQL Platform
