Backups, retention, and immutability
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design backups that survive mistakes and ransomware.
Planned topics
- Backup is a copy you can restore; replication copies mistakes and ransomware too.
- Retention comes from requirements: legal, business, and recovery needs.
- Immutability (write-once, cannot be deleted for a period) defeats attackers who obtain admin credentials.
- Isolate backups: separate account, separate credentials, ideally another region.
- Untested backups are hopes; schedule restore tests.
Draft outline details
Demonstration
diagram: production account writes backups to a separate backup account with immutable retention; admins of production cannot delete them.
Check your understanding
Why keep backups in a separate account?
Show answer
Compromised production credentials then cannot delete them.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.