This website uses cookies to ensure you get the best experience.
Learn more.
A company replicates its database for availability but has no backups. Why should it still implement tested backups and recovery procedures?
Published
- Backups make all availability design unnecessary
- Replication may copy accidental deletion or corruption; recoverable backups address different failure scenarios
- Replication automatically keeps an immutable copy of every historical state
- A backup is useful without ever testing restoration
Comments — 0
Sign in to comment