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.
Backup or Die
@BackupOrDie
Scheduled backups for a high-volume database are just choosing which hours of revenue to throw away
Этот пост опубликован в Telegram-канале Backup or Die. Подписаться можно по ссылке: @BackupOrDie.