Backing up CephFS
summary
CERN backs selected CephFS shares with restic plus an orchestrator, avoiding snapshots for performance reasons; a 2 PB dataset contains roughly 400 million files, so full tree walks trigger MDS cap-release alerts and take days. Teams use per-share or per-user job splitting, recursive mtime heuristics, rsync/hardlink chains, rclone, Bacula/TSM/tape and S3-mounted FUSE to TSM. Newer Ceph releases expose a snapdiff API (and planned byte-range diffs) that may make snapshot-based, MDS-friendly incremental backups practical.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 1:04Current backup approach at CERN
- 3:33Audience experiences and challenges
- 14:34Backup targets and strategies
- 16:28Snapshot-based backup methods
- 19:29Restore experiences and testing
- 21:02Server-side vs user-exposed backups
- 24:13Backup frequency and retention
- 27:06Challenges in CephFS backups
- 31:57Snapshot performance and improvements
- 35:56Final thoughts and recommendations
- 38:47Q&A and closing remarks
