Bitzu

AZ-305 ยท Backup and disaster recovery

Backup and restore for Azure databases

Azure SQL automated backups, point-in-time restore window, long-term retention, geo-restore, backup storage redundancy; Azure Backup for SQL Server in VMs; Cosmos DB periodic vs continuous backup.

Key points

  • Azure SQL Database: full weekly, differential 12 or 24 hours, log about every 10 minutes.
  • PITR: 7 days default, 1-35 days; always a new database.
  • LTR: weekly, monthly, yearly full backups up to 10 years.
  • Redundancy: LRS, ZRS, GRS (default), GZRS; geo-restore needs GRS or GZRS.
  • SQL Server in a VM: Azure Backup, Recovery Services vault, 15-minute RPO, restore to the second.
  • Cosmos DB continuous backup: 7, 30 or 35 days.

Source: https://learn.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview

Practice questions

Single choice

What is the default point-in-time restore retention for a new database in Azure SQL Database?

  1. 1 day
  2. 7 days
  3. 35 days
  4. 10 years
Show answer

Answer: B. 7 days

New databases keep enough backups for PITR over the last 7 days by default. You can change it to anything from 1 to 35 days; 10 years is the LTR maximum.

Select all that apply

Which statements about backup storage redundancy in Azure SQL Database are correct?

  1. Moving a database to locally redundant backup storage disables geo-restore
  2. Changing the redundancy applies to future backups only
  3. For Hyperscale, backup storage redundancy can be set only when the database is created
  4. Zone-redundant backup storage keeps a copy in the paired region
  5. You can download the automatic backup files to on-premises storage
Show answer

Answer: A. Moving a database to locally redundant backup storage disables geo-restore, B. Changing the redundancy applies to future backups only, C. For Hyperscale, backup storage redundancy can be set only when the database is created

Switching to LRS or ZRS disables geo-restore, a redundancy change applies only to future backups, and Hyperscale redundancy can be set only at creation. ZRS keeps copies across zones within the primary region, not in the paired region, and automatic backups cannot be downloaded.

True or false

A point-in-time restore in Azure SQL Database overwrites the existing database in place.

Show answer

Answer: False

False. PITR always creates a new database on the same server with a different name. If needed, you then rename or delete the original and rename the restored database.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module