Merge pull request #197649 from v-amallick/May-10-2022-SQLFAQ

Section restructuring

Author: Maggiemouse1

articles/backup/faq-backup-sql-server.yml

@@ -5,7 +5,9 @@ metadata:
   ms.reviewer: vijayts
   ms.topic: faq
   ms.service: backup
-  ms.date: 08/20/2021
+  ms.date: 05/16/2022
+  author: v-amallick
+  ms.author: v-amallick
 
 
 title: FAQ about SQL Server databases that are running on an Azure VM backup
@@ -14,7 +16,7 @@ summary: |
   
 
 sections:
-  - name: Ignored
+  - name: Backup
     questions:
       - question: |
           Can I use Azure Backup for IaaS VM as well as SQL Server on the same machine?
@@ -36,11 +38,11 @@ sections:
       - question: |
           Can I cancel an auto-heal backup job?
         answer: |
-          No, you can’t cancel an auto-heal job. However, you can opt-out of it by following these steps:
+          No, you can’t cancel an auto-heal job. However, you can opt out of it by following these steps:
           
           1. On the SQL Server instance, in the *C:\Program Files\Azure Workload Backup\bin* folder, create or edit the **ExtensionSettingsOverrides.json** file.
           1. In the **ExtensionSettingsOverrides.json** file, set *{"EnableAutoHealer": false}*.
-          1. Save the changesl and close the file.
+          1. Save the changes and close the file.
           1. On the SQL Server instance, open **Task Manage**, and then restart the **AzureWLBackupCoordinatorSvc** service.
           
       - question: |
@@ -66,11 +68,6 @@ sections:
         answer: |
           No. Successful backup jobs don't generate alerts. Alerts are sent only for backup jobs that fail. Detailed behavior for portal alerts is documented [here](backup-azure-monitoring-built-in-monitor.md). However, if you're interested in having alerts even for successful jobs, you can use [Monitoring using Azure Monitor](backup-azure-monitoring-use-azuremonitor.md).
           
-      - question: |
-          Can I see scheduled backup jobs in the Backup Jobs menu?
-        answer: |
-          The **Backup Job** menu shows all scheduled and on-demand operations, except the scheduled log backups since they can be very frequent. For scheduled log jobs, use [Monitoring using Azure Monitor](backup-azure-monitoring-use-azuremonitor.md).
-          
       - question: |
           Are future databases automatically added for backup?
         answer: |
@@ -83,43 +80,51 @@ sections:
           
           The correct way to stop protecting this database is to do **Stop Backup** with **delete data** on this database.  
           
+      - question: |
+          Can I protect databases on virtual machines that have Azure Disk Encryption (ADE) enabled?
+        answer: |
+          Yes, you can protect databases on virtual machines that have Azure Disk Encryption (ADE) enabled.
+
+      - question: |
+          Can I protect databases that have TDE (Transparent Data Encryption) turned on and will the database stay encrypted through the entire backup process?
+        answer: |
+          Yes, Azure Backup supports backup of SQL Server databases or server with TDE enabled. Backup supports [TDE](/sql/relational-databases/security/encryption/transparent-data-encryption) with keys managed by Azure, or with customer-managed keys (BYOK).  Backup doesn't perform any SQL encryption as part of the backup process so the database will stay encrypted when backed up.
+          
+      - question: |
+          Does Azure Backup perform a checksum operation on the data stream?
+        answer: |
+          We do perform a checksum operation on the data stream. However, this isn't to be confused with [SQL checksum](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server).
+          Azure workload backup computes the checksum on the data stream and stores it explicitly during the backup operation. This checksum stream is then taken as a reference and cross-verified with the checksum of the data stream during the restore operation to make sure that the data is consistent.
+
+  - name: Manage
+    questions:
+      - question: |
+          Can I see scheduled backup jobs in the Backup Jobs menu?
+        answer: |
+          The **Backup Job** menu shows all scheduled and on-demand operations, except the scheduled log backups since they can be very frequent. For scheduled log jobs, use [Monitoring using Azure Monitor](backup-azure-monitoring-use-azuremonitor.md).
+
       - question: |
           If I do stop backup operation of an autoprotected database what will be its behavior?
         answer: |
           If you do **stop backup with retain data**, no future backups will take place and the existing recovery points will remain intact. The database will still be considered as protected and be shown under the **Backup items**.
           
           If you do **stop backup with delete data**, no future backups will take place and the existing recovery points will also be deleted. The database will be considered un-protected and be shown under the instance in the Configure Backup. However, unlike other up-protected databases that can be selected manually or that can get autoprotected, this database appears greyed out and can’t be selected. The only way to re-protect this database is to disable auto-protection on the instance. You can now select this database and configure protection on it or re-enable auto-protection on the instance again.
-          
+
       - question: |
           If I change the name of the database after it has been protected, what will be the behavior?
         answer: |
           A renamed database is treated as a new database. So the service will treat this situation as if the database weren't found and with fail the backups.
           
           You can select the database, which is now renamed and configure protection on it. If the auto-protection is enabled on the instance, the renamed database will be automatically detected and protected.
-          
+
       - question: |
           Why can’t I see an added database for an autoprotected instance?
         answer: |
           A database that you [add to an autoprotected instance](backup-sql-server-database-azure-vms.md#enable-auto-protection) might not immediately appear under protected items. This is because the discovery typically runs every 8 hours, and the actual protection of the system can take additional time as it depends on the size of the VM. However, you can discover new databases immediately if you manually run a discovery by selecting **Rediscover DBs**, as shown in the following image:
           
-            ![Manually discover a newly added database](./media/backup-azure-sql-database/view-newly-added-database.png)
-          
-      - question: |
-          Can I protect databases on virtual machines that have Azure Disk Encryption (ADE) enabled?
-        answer: |
-          Yes, you can protect databases on virtual machines that have Azure Disk Encryption (ADE) enabled.
+            :::image type="content" source="./media/backup-azure-sql-database/view-newly-added-database.png" alt-text="Screenshot of manually discover a newly added database."
+
 
-      - question: |
-          Can I protect databases that have TDE (Transparent Data Encryption) turned on and will the database stay encrypted through the entire backup process?
-        answer: |
-          Yes, Azure Backup supports backup of SQL Server databases or server with TDE enabled. Backup supports [TDE](/sql/relational-databases/security/encryption/transparent-data-encryption) with keys managed by Azure, or with customer-managed keys (BYOK).  Backup doesn't perform any SQL encryption as part of the backup process so the database will stay encrypted when backed up.
-          
-      - question: |
-          Does Azure Backup perform a checksum operation on the data stream?
-        answer: |
-          We do perform a checksum operation on the data stream. However, this isn't to be confused with [SQL checksum](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server).
-          Azure workload backup computes the checksum on the data stream and stores it explicitly during the backup operation. This checksum stream is then taken as a reference and cross-verified with the checksum of the data stream during the restore operation to make sure that the data is consistent.
-          
 additionalContent: |
 
   ## Next steps