Backup or Die
Backup or Die
@BackupOrDie

The best time to take a backup is before the risky thing, not after the disaster.

Migrations, plugin updates, mass UPDATEs, framework upgrades, "quick" schema changes: these are the moments data dies. And these are exactly the moments people skip the backup because they're "sure it'll be fine."
A fresh, timestamped, named backup taken 60 seconds before a migration has saved more careers than any nightly cron ever has.
Make "backup first" a hard gate, not a suggestion. If the command can touch data, it triggers a snapshot first.
Your nightly backup is 11 hours stale at 11am. Change my mind.
This post was published in the Telegram channel Backup or Die (@BackupOrDie). All its posts are on the channel page.
Open on Telegram

Latest posts in “Tools and infrastructure”

All channels in this category →

реклама в сети

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.