intermediateNoSQL Production Best Practices — Backup, Monitoring, Security & RBAC

Why doesn't replication protect you against a bad write or an accidental mass delete?

Replication propagates every write — good or bad — to every replica, typically within milliseconds, with no delay window in which a mistake exists on the primary but hasn't reached the replicas yet. Only an independent, point-in-time backup lets you recover to a moment before the mistake happened; replication faithfully reproduces the mistake everywhere just as fast as it would a correct write.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Databases Mastery library.

Why doesn't replication protect you against a bad write or an accidental mass delete?

Next Step

Continue to What's wrong with confirming a backup job 'succeeded' without ever testing a restore from it?← Back to all NoSQL questions