50 Shades of Backup
summary
Backup process becomes a configurable, testable pipeline rather than ad hoc shell scripts: a CLI tool called PHP bu copies sources (MySQL, Redis, Elasticsearch, files), runs checks (min size, diff to previous), encrypts (OpenSSL), syncs to Dropbox, S3, SFTP or local storage, cleans up by policy, and sends mail alerts. Config lives in the project, adapters pull credentials from .env or arrays, a simulate mode prints exact commands without running them, and plugins implement sources/checks; it works in practice.
AI-written summary · about
chapters (26)
- 0:0050 SHADES
- 0:49NO BACKUP
- 5:56Once upon a time...
- 6:17it evolved
- 7:09Meanwhile in the internet...
- 7:40Microservices
- 10:41What's wrong with this
- 11:32shell is no fun
- 13:23Wouldn't it be nice
- 14:48Installation
- 17:07Configuration
- 19:13Execute
- 19:33Sources
- 20:07Check
- 21:06Encryption
- 22:11Sync
- 23:17Cleanup
- 24:44Reporting
- 25:47Accomplishments
- 26:46Adapter
- 29:45Simulation
- 31:40Extending
- 34:07Setup
- 37:52Register plugin
- 40:15Benefits
- 42:15Sebastian Feldmann
related talks
59mTaking Care of Backups with Laravel
32mSchroedingers Backup
42mProd backups in staging? Why not
51mMySQL Backups
52mOrganizing reliable backups for a web project
40mThe Butler Did It: Putting Jenkins To Work For You
28mBurning Down The House: How to Plan for and Deal with Disaster Recovery in CF
43mBacking up Nextcloud-Consistent Backup and Restore of Application Data