This website uses cookies to ensure you get the best experience.
Learn more.
A team has a highly available database and assumes it no longer needs a backup strategy. What should it understand?
Published
- High availability prevents every user from deleting data
- Availability and recovery from accidental or corrupt changes address different failure modes
- Backups are useful only for applications on premises
- A second provider name guarantees restoration of every earlier data version
Comments — 0
Sign in to comment