Merge pull request #49663 from JulianePadrao/update-backup-restore-databases

Updates to backup-restore-databases

Author: JamesJBarnett

learn-pr/wwl-data-ai/backup-restore-databases/1-introduction.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/2-backup-restore-sql-server-running-azure-virtual-machines.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Back up and restore SQL Server running on Azure virtual machines
   description: "Back up and restore SQL Server running on Azure virtual machines"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/3-backup-sql-server-virtual-machine.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Back up a SQL Server virtual machine
   description: "Back up a SQL Server virtual machine"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/4-use-azure-sql-database.yml

@@ -1,13 +1,13 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.backup-restore-databases.backup-restore-database-using-azure-sql-database
-title: Back up and restore a database using Azure SQL Database
+title: Back up and restore a database for SQL Database and SQL Managed Instance
 metadata:
   adobe-target: true
   prefetch-feature-rollout: true
-  title: Back up and restore a database using Azure SQL Database
-  description: "Back up and restore a database using Azure SQL Database"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  title: Back up and restore a database for SQL Database and SQL Managed Instance
+  description: "Back up and restore a database SQL Database and SQL Managed Instance"
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/5-exercise-backup-url.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: Backup to URL'
   description: "Exercise: Backup to URL"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/6-knowledge-check.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/7-summary.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 07/25/2023
-  author: wwlpublish
+  ms.date: 03/25/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/backup-restore-databases/includes/1-introduction.md

@@ -1,9 +1,3 @@
-Even if you do nothing else to increase your availability with features like AGs or active geo-replication, you must have a solid backup and recovery strategy. If for some reason a feature fails, you'll have to restore databases from backups.
+Planning and implementing a robust policy for data recovery is essential to mitigate the risks associated with user errors or technology failures. This involves exploring various options for backing up and restoring databases, including on-site and off-site solutions, cloud-based services, and automated backup systems. By understanding the different methods for data back up and recovery, organizations can safeguard their critical information and maintain operational continuity in the face of unforeseen challenges.
 
-## Learning objectives
-
-In this module, you'll learn:
-
-- Database backup and restore options for IaaS
-- Virtual machine backup and restore options for IaaS
-- Backup and restore options for PaaS
+Even if you do nothing else to increase your availability with features like AGs or active geo-replication, you must have a solid backup and recovery strategy. 

learn-pr/wwl-data-ai/backup-restore-databases/includes/3-backup-sql-server-virtual-machine.md

@@ -1,12 +1,10 @@
-Azure Backup can back up VMs that contain SQL Server. These backups would contain not just SQL Server databases; they would contain everything that is in the VM so it could be restored as a whole. While this option may not be right for everyone, it can potentially protect against problems like ransomware.
+Azure Backup offers the capability to back up virtual machines (VMs) that host SQL Server. These backups contain not only the SQL Server databases but also all other contents within the VM, allowing for a complete restoration if needed. Although this approach may not be suitable for every scenario, it provides a robust safeguard against issues such as ransomware attacks.
 
-VM-level backups are SQL Server-aware, also known as application aware, so they'll create an application-consistent backup. This means that if you restore a VM-level backup, it will not ‘break’ SQL Server. If using this option, when looking in the SQL Server log you'll see that the I/O has been momentarily frozen and then starts again when complete. If this causes issues with availability features like AGs, you may want to consider another backup strategy.
+VM-level backups are SQL Server-aware, also known as application-aware, ensuring the creation of application-consistent backups. This means that restoring a VM-level backup won't disrupt SQL Server functionality. When using this option, the SQL Server log indicates that the I/O has been momentarily frozen and then resumed upon completion.
 
-Combining SQL Server backups with snapshots can potentially cause issues. If snapshot delays cause backup failures, set following registry key:
+Combining SQL Server backups with snapshots can potentially cause issues. If snapshot delays cause backup failures, set following value on the `[HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BCDRAGENT]` key:
 
-[HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BCDRAGENT]
-
-"USEVSSCOPYBACKUP"="TRUE"
+**"USEVSSCOPYBACKUP"**="TRUE"
 
 ## Use local disks or a network share for backup files
 
@@ -16,11 +14,11 @@ As with on premises SQL Server instances, databases can be backed up to disks at
 
 Another option is to configure backup to URL for the SQL Server instance installed in the VM. Unlike backups made on premises, backup and restore from URL for an IaaS VM is effectively a local option.
 
-Backup to URL requires an Azure storage account and uses the Azure blob storage service. Inside the storage account, there are containers, and the blobs are stored there. Unlike a path on your local disk, the path to a backup file will look something like `https://ACCOUNTNAME.blob.core.windows.net/ContainerName/MyDatabase.bak`. You can include more folder names under your container for easier identification of backups (for example, FULL, DIFF, LOG).
+Back up to URL requires an Azure storage account and uses the Azure blob storage service. Inside the storage account, there are containers, and the blobs are stored there. Unlike a path on your local disk, the path to a backup file looks something like `https://ACCOUNTNAME.blob.core.windows.net/ContainerName/MyDatabase.bak`. You can include more folder names under your container for easier identification of backups (for example, FULL, DIFF, LOG).
 
-To backup to or restore from a URL, authentication must be established between the SQL Server instance and Azure. Remember that inside of an Azure VM, SQL Server doesn't know it's running on Azure. A SQL Server Credential can be composed of the Azure storage account name and access key authentication or a Shared Access Signature. If the former is used, the backup will be stored as a page blob and if the latter, it will be stored as a block blob. Starting with SQL Server 2016, only block blob is available so you should use a Shared Access Signature. From a cost perspective, block blobs are also cheaper, and Shared Access Signature tokens offer better security control.
+To back up to or restore from a URL, authentication must be established between the SQL Server instance and Azure. Remember that inside of an Azure VM, SQL Server doesn't know it's running on Azure. A SQL Server Credential can be composed of the Azure storage account name and access key authentication or a Shared Access Signature. If the former is used, the backup is stored as a page blob and if the latter, it's stored as a block blob. Starting with SQL Server 2016, only block blob is available so you should use a Shared Access Signature. From a cost perspective, block blobs are also cheaper, and Shared Access Signature tokens offer better security control.
 
-Restoring from a URL is as simple as restoring from disk or a network share. In the SQL Server Management Studio UI, select URL from the backup media type in the Wizard. If using Transact-SQL, instead of using FROM DISK, you would use FROM URL with the appropriate location and backup file name(s). Here are some sample statements:
+Restoring from a URL is as simple as restoring from disk or a network share. In the SQL Server Management Studio UI, select URL from the backup media type in the Wizard. If using Transact-SQL, instead of using FROM DISK, you would use FROM URL with the appropriate location and backup file name. Here are some sample statements:
 
 The following statement would back up a transaction log.
 
@@ -41,13 +39,13 @@ WITH NORECOVERY
 
 Any IaaS VM that has SQL Server installed can use the SQL Server resource provider. One of its options is the ability to configure automated backups so Azure takes care of backing up SQL Server databases. It requires the use of a storage account.
 
-One benefit of implementing backups this way is that you can manage retention times for the backups. Another benefit is that you can ensure RPO due to the ability to take database and transaction log backups all in one easy-to-configure place. The image below shows an example of what configuring an automated backup looks like in the Azure portal.
+One benefit of implementing backups this way is that you can manage retention times for the backups. Another benefit is that you can ensure RPO due to the ability to take database and transaction log backups all in one easy-to-configure place. The following image shows an example of what configuring an automated backup looks like in the Azure portal.
 
 :::image type="content" source="../media/module-77-high-availability-final-15.png" alt-text="Configuring automated backups for SQL Server in a VM in the Azure portal":::
 
 The automated backup option is currently only available for Windows Server-based SQL Server installations.
 
 > [!IMPORTANT]
-> You choose one method of backing up databases with IaaS-based SQL Server deployments. For example, if you use automated backups, especially with transaction log backups, do not also configure those at the instance level inside the VM. You could cause problems with the log chain with restoring a database if things are uncoordinated, because each log backup clears the log and you must have an entire unbroken chain of log backups in order to do a log restore. For example, if transaction log backups happen inside the guest as well as at the Azure level, you may have to piece together the backups to do a restore.
+> You choose one method of backing up databases with IaaS-based SQL Server deployments. For example, if you use automated backups, especially with transaction log backups, don't also configure those at the instance level inside the VM. You could cause problems with the log chain with restoring a database if things are uncoordinated, because each log backup clears the log and you must have an entire unbroken chain of log backups in order to do a log restore. For example, if transaction log backups happen inside the guest and at the Azure level, you may have to piece together the backups to do a restore.
 
 While the backups can be automated, restores can't be. You would need to configure and use the restore from URL functionality within SQL Server.

learn-pr/wwl-data-ai/backup-restore-databases/includes/4-use-azure-sql-database.md

@@ -1,36 +1,40 @@
 
-Back up and restore on SQL Server PaaS offering work differently than on IaaS. Backups are generated automatically for Azure SQL Database, and Azure SQL Managed Instance. A full backup is created once a week, a differential every 12 hours, and transaction log backups every 5 – 10 minutes. All backups are located in read-access, geo-redundant (RA-GRS) blobs replicated to a datacenter that is paired based on Azure rules. That means backups are safe from an outage in a single data center.
+Back up and restore on SQL Server PaaS offering work differently than on IaaS. Backups are generated automatically for Azure SQL Database, and Azure SQL Managed Instance. A full backup is created once a week, a differential every 12 hours, and transaction log backups every 5 to 10 minutes. All backups are located in read-access, geo-redundant (RA-GRS) blobs replicated to a datacenter that is paired based on Azure rules. That means backups are safe from an outage in a single data center.
 
 ## Database backup and restore for SQL Database
 
-SQL Database can assist you to be compliant with mandatory backups for regulatory purposes with retention policies. Backup policies can be configured per database as shown in the image below:
+Database backups are an essential part of any business continuity and disaster recovery strategy because they help protect your data from corruption or deletion.
+
+SQL Database can assist you to be compliant with mandatory backups for regulatory purposes with retention policies. Backup policies can be configured per database as shown in the following image:
 
 :::image type="content" source="../media/module-77-high-availability-final-16.png" alt-text="Configuring automated backups for Azure SQL Database":::
 
-If the server containing the database is deleted, all backups will be deleted at the same time, and there's no way to recover them. If the server isn't deleted but the database is, you can restore the database normally.
+If the server containing the database is deleted, all backups are deleted at the same time, and there's no way to recover them. If the server isn't deleted but the database is, you can restore the database normally.
 
 Both SQL Database, and SQL Managed Instance have a feature called Accelerated Database Recovery (ADR). This feature is enabled by default, and its purpose is to decrease the time it takes to deal with long running transactions so they don't affect the recovery time. Although Accelerated Database Recovery was developed for Azure and was originally an Azure-based feature, ADR was implemented in SQL Server 2019 as well.
 
 > [!NOTE]
-> You can't restore SQL Database Managed Instance backups on SQL Database.
+> You can't restore SQL Database Azure SQL Managed Instance backups on SQL Database.
+
+Automated database backups are also avaialable on [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/automated-backups-overview). SQL Server database engine backups are automatically managed by Microsoft, and stored on Microsoft-managed Azure storage accounts.
 
 ### Point in time restore
 
 To restore a database to a specific point in time on SQL Database, you can use either Azure portal, Azure PowerShell, Azure CLI, or REST API.
 
 > [![Restoring a database on SQL Database through Azure portal](../media/restore-sql-database.png)](../media/restore-sql-database.png#lightbox)
 
-The image above shows the SQL Database restore page on Azure portal, where you can restore a database to a specific point in time.
+The following image shows the SQL Database restore page on Azure portal, where you can restore a database to a specific point in time.
 
 Restore in place isn't supported on SQL Database, and SQL Managed Instance. You need to make sure the database doesn't exist before attempting the restore operation. By default, point in time retention policy is set to seven days, and you can change it to up to 35-days.
 
 ### Restore a deleted database
 
-Both SQL Database, and SQL Managed Instance have a feature to restore a deleted database to the last point in time available before the `DROP DATABASE` took place.
+Both SQL Database, and SQL Managed Instance have a feature to restore a deleted database to the last point in time available before the `DROP DATABASE` took place. To recover a deleted database to the deletion time by using the Azure portal, open the server's overview page and select **Deleted databases**. Select a deleted database that you want to restore, and then enter the name for the new database that will be created with data restored from the backup.
 
 > [![Restoring a deleted database on SQL Database through Azure portal](../media/restore-sql-database-deleted.png)](../media/restore-sql-database-deleted.png#lightbox)
 
-The image above shows how to restore a deleted database on SQL Database. The *deleted databases* page shows a list of deleted databases available to restore, the database deletion time in UTC, and the database creation time in UTC. Once you select the database, the *Create SQL Database - Restore database* page will open. On that page you'll find the earliest restore point in time available for the selected database.
+The image shows how to restore a deleted database on SQL Database. The *deleted databases* page shows a list of deleted databases available to restore, the database deletion time in UTC, and the database creation time in UTC. Once you select the database, the *Create SQL Database - Restore database* page opens. On that page you find the earliest restore point in time available for the selected database.
 
 ## Database backup and restore for SQL Managed Instance
 
@@ -47,4 +51,4 @@ WITH COPY_ONLY
 ```
 
 > [!NOTE]
-> You can't restore SQL Database Managed Instance backups on SQL Database.
+> You can't restore SQL Database SQL Managed Instance backups on SQL Database.