Backup or Die
Backup or Die
@BackupOrDie

Scheduled backups for a high-volume database are just choosing which hours of revenue to throw away

Every gap between scheduled jobs is data you've agreed to lose. For a busy store, even hourly means up to 60 minutes of orders gone in a crash.

Continuous data protection and log shipping shrink that gap to seconds.

— Scheduled: simple, predictable loss window
— CDP / log shipping: near-zero RPO, more moving parts

If each lost hour costs real money, a cron job is the wrong tool. Stream the logs. 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 за пакет по сети.