Taking Care of Backups with Laravel
summary
A concrete backup workflow: a package called laravel backup dumped MySQL and zipped application files, copies archives to multiple disks (local and S3), and enforces retention with a grandfather father son rotation. It sends notifications via mail Slack Telegram Pushover, reports unhealthy backups when the newest backup is too old or storage exceeds a threshold, and has no automatic restore. Demo copies to S3 and local, cleans old archives to meet size limits, and the project reports 250,000 downloads and growing.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:16Open source software
- 5:24Laravel Dashboard
- 5:47Laravel Uptime monitor
- 6:45Fractalistic
- 12:20Horror Story #1
- 13:52Horror Story #3
- 15:58A bash script
- 17:40BackupPC
- 20:53Backup files & databases
- 21:37Cleanup old backups
- 22:49Grandfather-father-son rotation scheme
- 23:43Monitor backups
- 38:57Monitoring best practices
- 41:21Benefits
- 41:50Drawbacks
- 43:59Requirements
- 44:50Summary
related talks
35mTaking care of backups with Laravel
43m50 Shades of Backup
42mProd backups in staging? Why not
41mServer Automation with Laravel Zero
32mDesign Patterns and Packages for Excellent Laravel Backoffices
30mLegacy to Laravel in 30 minutes
46mHandling media in a Laravel application
50mWeb‑Scale Backups for MySQL