Merge pull request #184335 from v-amallick/Jan-6-2022-BkpCtr-SQL

v-ccolin · web-flow · commit e01e319ca68e · 2022-01-07T09:03:26.000Z
SQL - Backup center entry point updates
diff --git a/articles/backup/tutorial-sql-backup.md b/articles/backup/tutorial-sql-backup.md
@@ -2,7 +2,10 @@
 title: Tutorial - Back up SQL Server databases to Azure 
 description: In this tutorial, learn how to back up a SQL Server database running on an Azure VM to an Azure Backup Recovery Services vault.
 ms.topic: tutorial
-ms.date: 06/18/2019
+ms.date: 01/07/2022
+author: v-amallick
+ms.service: backup
+ms.author: v-amallick
 ---
 # Back up a SQL Server database in an Azure VM
 
@@ -66,33 +69,27 @@ We do have aliasing for Azure table unsupported characters, but we recommend avo
 
 Discover databases running on the VM.
 
-1. In the [Azure portal](https://portal.azure.com), open the Recovery Services vault you use to back up the database.
+1. In the [Azure portal](https://portal.azure.com), go to **Backup center** and click **+Backup**.
 
-2. On the **Recovery Services vault** dashboard, select **Backup**.
+1. Select **SQL in Azure VM** as the datasource type, select the Recovery Services vault you have created, and then click **Continue**.
 
-   ![Select Backup to open the Backup Goal menu](./media/backup-azure-sql-database/open-backup-menu.png)
+   :::image type="content" source="./media/backup-azure-sql-database/configure-sql-backup.png" alt-text="Screenshot showing to select Backup to view the databases running in a VM.":::
 
-3. In **Backup Goal**, set **Where is your workload running** to **Azure** (the default).
-
-4. In **What do you want to backup**, select **SQL Server in Azure VM**.
-
-    ![Select SQL Server in Azure VM for the backup](./media/backup-azure-sql-database/choose-sql-database-backup-goal.png)
-
-5. In **Backup Goal** > **Discover DBs in VMs**, select **Start Discovery** to search for unprotected VMs in the subscription. It can take a while, depending on the number of unprotected virtual machines in the subscription.
+1. In **Backup Goal** > **Discover DBs in VMs**, select **Start Discovery** to search for unprotected VMs in the subscription. It can take a while, depending on the number of unprotected virtual machines in the subscription.
 
    * Unprotected VMs should appear in the list after discovery, listed by name and resource group.
    * If a VM isn't listed as you expect, check whether it's already backed up in a vault.
    * Multiple VMs can have the same name but they'll belong to different resource groups.
 
      ![Backup is pending during search for DBs in VMs](./media/backup-azure-sql-database/discovering-sql-databases.png)
 
-6. In the VM list, select the VM running the SQL Server database > **Discover DBs**.
+1. In the VM list, select the VM running the SQL Server database > **Discover DBs**.
 
-7. Track database discovery in the **Notifications** area. It can take a while for the job to complete, depending on how many databases are on the VM. When the selected databases are discovered, a success message appears.
+1. Track database discovery in the **Notifications** area. It can take a while for the job to complete, depending on how many databases are on the VM. When the selected databases are discovered, a success message appears.
 
     ![Deployment success message](./media/backup-azure-sql-database/notifications-db-discovered.png)
 
-8. Azure Backup discovers all SQL Server databases on the VM. During discovery, the following occurs in the background:
+1. Azure Backup discovers all SQL Server databases on the VM. During discovery, the following occurs in the background:
 
     * Azure Backup register the VM with the vault for workload backup. All databases on the registered VM can only be backed up to this vault.
     * Azure Backup installs the **AzureBackupWindowsWorkload** extension on the VM. No agent is installed on the SQL database.
@@ -107,41 +104,41 @@ Discover databases running on the VM.
 
 Configure backup as follows:
 
-1. In **Backup Goal**, select **Configure Backup**.
+1. In **Backup Goal** > **Step 2: Configure Backup**, select **Configure Backup**.
 
    ![Select Configure Backup](./media/backup-azure-sql-database/backup-goal-configure-backup.png)
 
-2. Select **Configure Backup**, the **Select items to backup** pane appears. This lists all the registered availability groups and standalone SQL Servers. Expand the chevron to the left of the row to see all the unprotected databases in that instance or Always on AG.  
+1. Select **Add Resources** to see all the registered availability groups and standalone SQL Server instances.
 
-    ![Displaying all SQL Server instances with standalone databases](./media/backup-azure-sql-database/list-of-sql-databases.png)
+    ![Select add resources](./media/backup-azure-sql-database/add-resources.png)
 
-3. Select all the databases you want to protect > **OK**.
+1. In the **Select items to backup** screen, select the arrow to the left of a row to expand the list of all the unprotected databases in that instance or Always On availability group.
+
+    ![Select items to backup](./media/backup-azure-sql-database/select-items-to-backup.png)
+
+1. Choose all the databases you want to protect, and then select **OK**.
 
    ![Protecting the database](./media/backup-azure-sql-database/select-database-to-protect.png)
 
    To optimize backup loads, Azure Backup sets a maximum number of databases in one backup job to 50.
 
-     * Alternatively, you can enable auto-protection on the entire instance or Always On Availability group by selecting the **ON** option in the corresponding dropdown in the **AUTOPROTECT** column. The auto-protection feature not only enables protection on all the existing databases in one go but also automatically protects any new databases that will be added to that instance or the availability group in future.  
-
-4. Select **OK** to open the **Backup policy** pane.
+     * To protect more than 50 databases, configure multiple backups.
+     * To [enable](/azure/backup/backup-sql-server-database-azure-vms#enable-auto-protection) the entire instance or the Always On availability group, in the **AUTOPROTECT** drop-down list, select  **ON**, and then select **OK**.
 
-    ![Enable auto-protection on the Always On availability group](./media/backup-azure-sql-database/enable-auto-protection.png)
+         > [!NOTE]
+         > The [auto-protection](/azure/backup/backup-sql-server-database-azure-vms#enable-auto-protection) feature not only enables protection on all the existing databases at once, but also automatically protects any new databases added to that instance or the availability group.  
 
-5. In **Choose backup policy**, select a policy, then select **OK**.
+1. Define the **Backup policy**. You can do one of the following:
 
-   * Select the default policy: HourlyLogBackup.
+   * Select the default policy as *HourlyLogBackup*.
    * Choose an existing backup policy previously created for SQL.
    * Define a new policy based on your RPO and retention range.
 
      ![Select Backup policy](./media/backup-azure-sql-database/select-backup-policy.png)
 
-6. On **Backup** menu, select **Enable backup**.
+1. Select **Enable Backup** to submit the **Configure Protection** operation and track the configuration progress in the **Notifications** area of the portal.
 
-    ![Enable the chosen backup policy](./media/backup-azure-sql-database/enable-backup-button.png)
-
-7. Track the configuration progress in the **Notifications** area of the portal.
-
-    ![Notification area](./media/backup-azure-sql-database/notifications-area.png)
+   ![Track configuration progress](./media/backup-azure-sql-database/track-configuration-progress.png)
 
 ### Create a backup policy
 
@@ -151,59 +148,62 @@ A backup policy defines when backups are taken and how long they're retained.
 * Multiple vaults can use the same backup policy, but you must apply the backup policy to each vault.
 * When you create a backup policy, a daily full backup is the default.
 * You can add a differential backup, but only if you configure full backups to occur weekly.
-* [Learn about](backup-architecture.md#sql-server-backup-types) different types of backup policies.
+* Learn about [different types of backup policies](backup-architecture.md#sql-server-backup-types).
 
 To create a backup policy:
 
-1. In the vault, select **Backup policies** > **Add**.
-2. In **Add** menu, select **SQL Server in Azure VM** to define the policy type.
+1. Go to **Backup center** and click **+Policy**.
+
+1. Select **SQL Server in Azure VM** as the datasource type, select the vault under which the policy should be created, and then click **Continue**.
+
+   :::image type="content" source="./media/backup-azure-sql-database/create-sql-policy.png" alt-text="Screenshot showing to choose a policy type for the new backup policy.":::
+
+1. In **Policy name**, enter a name for the new policy.
 
-   ![Choose a policy type for the new backup policy](./media/backup-azure-sql-database/policy-type-details.png)
+   :::image type="content" source="./media/backup-azure-sql-database/sql-policy-summary.png" alt-text="Screenshot to showing to enter policy name.":::
 
-3. In **Policy name**, enter a name for the new policy.
-4. In **Full Backup policy**, select a **Backup Frequency**, choose **Daily** or **Weekly**.
+1. Select the **Edit** link corresponding, to **Full backup**, to modify the default settings.
 
-   * For **Daily**, select the hour and time zone when the backup job begins.
-   * You must run a full backup as you can't turn off the **Full Backup** option.
-   * Select **Full Backup** to view the policy.
-   * You can't create differential backups for daily full backups.
-   * For **Weekly**, select the day of the week, hour, and time zone when the backup job begins.
+   * Select a **Backup Frequency**. Choose either **Daily** or **Weekly**.
+   * For **Daily**, select the hour and time zone when the backup job begins. You can't create differential backups for daily full backups.
 
-     ![New backup policy fields](./media/backup-azure-sql-database/full-backup-policy.png)  
+   :::image type="content" source="./media/backup-azure-sql-database/sql-backup-schedule-inline.png" alt-text="Screenshot showing new backup policy fields." lightbox="./media/backup-azure-sql-database/sql-backup-schedule-expanded.png":::
 
-5. For **Retention Range**, by default all options are selected. Clear any undesired retention range limits you don't want to use, and set the intervals to use.
+1. In **RETENTION RANGE**, all options are selected by default. Clear any retention range limits that you don't want, and then set the intervals to use.
 
-    * Minimum retention period  for any type of backup (full/differential/log) is seven days.
+    * Minimum retention period for any type of backup (full, differential, and log) is seven days.
     * Recovery points are tagged for retention based on their retention range. For example, if you select a daily full backup, only one full backup is triggered each day.
-    * The backup for a specific day is tagged and retained based on the weekly retention range and your weekly retention setting.
-    * The monthly and yearly retention ranges behave in a similar way.
+    * The backup for a specific day is tagged and retained based on the weekly retention range and the weekly retention setting.
+    * Monthly and yearly retention ranges behave in a similar way.
 
-   ![Retention range interval settings](./media/backup-azure-sql-database/retention-range-interval.png)
+    :::image type="content" source="./media/backup-azure-sql-database/sql-retention-range-inline.png" alt-text="Screenshot showing the retention range interval settings." lightbox="./media/backup-azure-sql-database/sql-retention-range-expanded.png":::
 
-6. In the **Full Backup policy** menu, select **OK** to accept the settings.
-7. To add a differential backup policy, select **Differential Backup**.
+1. Select **OK** to accept the setting for full backups.
+1. Select the **Edit** link corresponding to **Differential backup**, to modify the default settings.
 
-   ![Retention range interval settings](./media/backup-azure-sql-database/retention-range-interval.png)
-   ![Open the differential backup policy menu](./media/backup-azure-sql-database/backup-policy-menu-choices.png)
+    * In **Differential Backup policy**, select **Enable** to open the frequency and retention controls.
+    * You can trigger only one differential backup per day. A differential backup can't be triggered on the same day as a full backup.
+    * Differential backups can be retained for a maximum of 180 days.
+    * The differential backup retention period can't be greater than that of the full backup (as the differential backups are dependent on the full backups for recovery).
+    * Differential Backup isn't supported for the master database.
 
-8. In **Differential Backup policy**, select **Enable** to open the frequency and retention controls.
+    :::image type="content" source="./media/backup-azure-sql-database/sql-differential-backup-inline.png" alt-text="Screenshot showing the differential Backup policy." lightbox="./media/backup-azure-sql-database/sql-differential-backup-expanded.png":::
 
-    * At most, you can trigger one differential backup per day.
-    * Differential backups can be retained for a maximum of 180 days. If you need longer retention, you must use full backups.
+1. Select the **Edit** link corresponding to **Log backup**, to modify the default settings
 
-9. Select **OK** to save the policy and return to the main **Backup policy** menu.
+    * In **Log Backup**, select **Enable**, and then set the frequency and retention controls.
+    * Log backups can occur as often as every 15 minutes and can be retained for up to 35 days.
+    * If the database is in the [simple recovery model](/sql/relational-databases/backup-restore/recovery-models-sql-server), the log backup schedule for that database will be paused and so no log backups will be triggered.
+    * If the recovery model of the database changes from **Full** to **Simple**, log backups will be paused within 24 hours of the change in the recovery model. Similarly, if the recovery model changes from **Simple**, implying log backups can now be supported for the database, the log backups schedules will be enabled within 24 hours of the change in recovery model.
 
-10. To add a transactional log backup policy, select **Log Backup**.
-11. In **Log Backup**, select **Enable**, and then set the frequency and retention controls. Log backups can occur as often as every 15 minutes, and can be retained for up to 35 days.
-12. Select **OK** to save the policy and return to the main **Backup policy** menu.
+    :::image type="content" source="./media/backup-azure-sql-database/sql-log-backup-inline.png" alt-text="Screenshot showing the log Backup policy." lightbox="./media/backup-azure-sql-database/sql-log-backup-expanded.png":::
 
-    ![Edit the log backup policy](./media/backup-azure-sql-database/log-backup-policy-editor.png)
+1. On the **Backup policy** menu, choose whether to enable **SQL Backup Compression** or not. This option is disabled by default. If enabled, SQL Server will send a compressed backup stream to the VDI. Azure Backup overrides instance level defaults with COMPRESSION / NO_COMPRESSION clause depending on the value of this control.
 
-13. On the **Backup policy** menu, choose whether to enable **SQL Backup Compression**.
-    * Compression is disabled by default.
-    * On the back end, Azure Backup uses SQL native backup compression.
+1. After you complete the edits to the backup policy, select **OK**.
 
-14. After you complete the edits to the backup policy, select **OK**.
+> [!NOTE]
+> Each log backup is chained to the previous full backup to form a recovery chain. This full backup will be retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume you have a weekly full backup, daily differential and 2 hour logs. All of them are retained for 30 days. But, the weekly full can be really cleaned up/deleted only after the next full backup is available, that is, after 30 + 7 days. For example, a weekly full backup happens on Nov 16th. According to the retention policy, it should be retained until Dec 16th. The last log backup for this full happens before the next scheduled full, on Nov 22nd. Until this log is available until Dec 22nd, the Nov 16th full can't be deleted. So, the Nov 16th full is retained until Dec 22nd.
 
 ## Run an on-demand backup
 
