What's changed: Deepened DP-300 Chapter 5 (ja figures; comparison tables/scenarios/FAQ/traps/deep paragraphs in all sections)
5.1Backup and Restore
Understand Azure SQL automated backups and point-in-time restore (PITR), long-term retention (LTR), geo-restore, and retention (RPO/RTO concepts). The basis of recovering from data loss.
Azure SQL takes automated backups against accidental deletion and failures. You can restore to a point in time or to another region as needed.
5.1.1Backup and restore types
- Automated backups: full/differential/transaction-log taken automatically; can be stored geo-redundantly by default.
- Point-in-time restore (PITR): restore to any time within retention (good for recovering from mistakes).
- Long-term retention (LTR): retain weekly/monthly/yearly for years (for compliance).
- Geo-restore: restore from geo-redundant backups in another region (on regional failure).
Common on DP-300: restore to before a mistake = PITR, multi-year retention = LTR, restore to another region = geo-restore, acceptable data loss = RPO, acceptable downtime = RTO. Design backup/HA-DR per the required RPO/RTO.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.