Merge pull request #95955 from dcurwin/dcurwin-nov14

TedA-M · web-flow · commit 8179a18ac80c · 2019-11-14T08:28:05.000-08:00
Multiple fixes
diff --git a/articles/backup/backup-azure-alternate-dpm-server.md b/articles/backup/backup-azure-alternate-dpm-server.md
@@ -75,7 +75,7 @@ To recover data from an Azure Backup Server:
 
     ![Clear External DPM](./media/backup-azure-alternate-dpm-server/clear-external-dpm.png)
 
-## Troubleshooting Error Messages
+## Troubleshooting error messages
 
 | No. | Error Message | Troubleshooting steps |
 |:---:|:--- |:--- |
diff --git a/articles/backup/backup-azure-backup-cloud-as-tape.md b/articles/backup/backup-azure-backup-cloud-as-tape.md
@@ -64,7 +64,7 @@ By clicking **Modify** in the preceding screen, customers have further flexibili
 
 ![Modify](./media/backup-azure-backup-cloud-as-tape/modify.png)
 
-## Next Steps
+## Next steps
 
 For more information about Azure Backup, see:
 
diff --git a/articles/backup/backup-azure-backup-sharepoint-mabs.md b/articles/backup/backup-azure-backup-sharepoint-mabs.md
@@ -234,7 +234,7 @@ In the following example, the *Recovering SharePoint item* has been accidentally
     ![MABS SharePoint Protection13](./media/backup-azure-backup-sharepoint/dpm-sharepoint-protection15.png)
 5. At this point, follow the recovery steps earlier in this article to recover a SharePoint content database from disk.
 
-## Next Steps
+## Next steps
 
 See the [Back up Exchange server](backup-azure-exchange-mabs.md) article.
 See the [Back up SQL Server](backup-azure-sql-mabs.md) article.
diff --git a/articles/backup/backup-azure-dpm-azure-server-faq.md b/articles/backup/backup-azure-dpm-azure-server-faq.md
@@ -12,7 +12,7 @@ ms.author: dacurwin
 
 # Azure Backup Server and DPM - FAQ
 
-## General Questions
+## General questions
 
 This article answers frequently asked questions about the Azure Backup Server and DPM.
 
diff --git a/articles/backup/backup-azure-files-faq.md b/articles/backup/backup-azure-files-faq.md
@@ -104,7 +104,7 @@ Yes. If you chose **Retain Backup Data** when you stopped protection, then you c
 
 If an ongoing restore job is canceled, the restore process stops and all files restored before the cancellation, stay in configured destination (original or alternate location) without any rollbacks.
 
-## Manage Backup
+## Manage backup
 
 ### Can I use PowerShell to configure/manage/restore backups of Azure File shares?
 
@@ -114,17 +114,17 @@ Yes. Please refer to the detailed documentation [here](backup-azure-afs-automati
 
 All Snapshots taken by Azure Backup can be accessed by Viewing Snapshots in the portal, PowerShell, or CLI. To learn more about Azure Files share snapshots, see [Overview of share snapshots for Azure Files (preview)](../storage/files/storage-snapshots-files.md).
 
-### What is the maximum retention I can configure for Backups?
+### What is the maximum retention I can configure for backups?
 
 Backup for Azure file shares offers the ability to configure policies with retention up to 180 days. However, using the ["On-demand backup" option in PowerShell](backup-azure-afs-automation.md#trigger-an-on-demand-backup), you can retain a recovery point even for 10 years.
 
 ### What happens when I change the Backup policy for an Azure file share?
 
 When a new policy is applied on file share(s), schedule and retention of the new policy is followed. If retention is extended, existing recovery points are marked to keep them as per new policy. If retention is reduced, they're marked for pruning in the next cleanup job and deleted.
 
-## See also
+## Next steps
 
-This information is just about backing up Azure Files, to learn more about other areas of Azure Backup, see some of these other Backup FAQs:
+To learn more about other areas of Azure Backup, see some of these other Backup FAQs:
 
 - [Recovery Services vault FAQ](backup-azure-backup-faq.md)
 - [Azure VM backup FAQ](backup-azure-vm-backup-faq.md)
diff --git a/articles/backup/backup-azure-files.md b/articles/backup/backup-azure-files.md
@@ -190,13 +190,13 @@ To resume protection for the file share, go to the Backup Item and click Resume
 
    ![Select the job you want to monitor](./media/backup-file-shares/resume-backup-job.png)
 
-### Delete Backup data
+### Delete backup data
 
 You can delete the backup of a file share during the Stop backup job, or anytime after you have stopped protection. It may even be beneficial to wait days or weeks before deleting the recovery points. Unlike restoring recovery points, when deleting backup data, you can't choose specific recovery points to delete. If you choose to delete your backup data, you delete all recovery points associated with the item.
 
 The following procedure assumes the Backup job for the virtual machine has been stopped. Once the Backup job is stopped, the Resume backup and Delete Backup Data options are available in the Backup item dashboard. Click Delete Backup Data and type the name of the File share to confirm deletion. Optionally, provide a Reason to delete or Comment.
 
-## See Also
+## Next steps
 
 For more information on Azure file shares, see
 
diff --git a/articles/backup/backup-azure-manage-windows-server.md b/articles/backup/backup-azure-manage-windows-server.md
@@ -252,7 +252,7 @@ The Backup Storage tile in the dashboard shows the storage consumed in Azure. St
 * Cloud LRS storage usage associated with the vault
 * Cloud GRS storage usage associated with the vault
 
-## Troubleshooting Monitoring Issues
+## Troubleshooting monitoring issues
 
 **Issue:** Jobs and/or alerts from the Azure Backup agent do not appear in the portal.
 
diff --git a/articles/backup/backup-azure-monitoring-built-in-monitor.md b/articles/backup/backup-azure-monitoring-built-in-monitor.md
@@ -97,7 +97,7 @@ If the frequency was set to an hourly digest and an alert was raised and resolve
 > - If a destructive operation such as **stop protection with delete data** is performed, an alert is raised and an email is sent to subscription owners, admins, and co-admins even if notifications are NOT configured for the Recover Service vault.
 > - To configure notification for successful jobs use [Log Analytics](backup-azure-monitoring-use-azuremonitor.md#using-log-analytics-workspace).
 
-## Inactivating Alerts
+## Inactivating alerts
 
 To inactivate/resolve an active alert, you can click on the list item corresponding to the alert you wish to inactivate. This opens up a screen that displays detailed information about the alert, with an 'Inactivate' button on the top. Clicking this button would change the status of the alert to 'Inactive'. You may also inactivate an alert by right-clicking on the list item corresponding to that alert and selecting 'Inactivate'.
 
diff --git a/articles/backup/backup-azure-recovery-services-vault-overview.md b/articles/backup/backup-azure-recovery-services-vault-overview.md
@@ -70,7 +70,7 @@ The following sections contain links to articles that explain how to use a Recov
 
 - [Securing cloud backup data in Recovery Services vaults](backup-azure-security-feature.md)
 
-## Next Steps
+## Next steps
 
 Use the following articles to:</br>
 [Back up an IaaS VM](backup-azure-arm-vms-prepare.md)</br>
diff --git a/articles/backup/backup-azure-restore-files-from-vm.md b/articles/backup/backup-azure-restore-files-from-vm.md
@@ -61,24 +61,24 @@ To restore files or folders from the recovery point, go to the virtual machine a
 
     - download.microsoft.com
     - Recovery Service URLs (geo-name refers to the region where the recovery service vault resides)
-        - https:\//pod01-rec2.geo-name.backup.windowsazure.com (For Azure public geos)
-        - https:\//pod01-rec2.geo-name.backup.windowsazure.cn (For Azure China 21Vianet)
-        - https:\//pod01-rec2.geo-name.backup.windowsazure.us (For Azure US Government)
-        - https:\//pod01-rec2.geo-name.backup.windowsazure.de (For Azure Germany)
+            - <https://pod01-rec2.geo-name.backup.windowsazure.com> (For Azure public geos)
+            - <https://pod01-rec2.geo-name.backup.windowsazure.cn> (For Azure China 21Vianet)
+            - <https://pod01-rec2.geo-name.backup.windowsazure.us> (For Azure US Government)
+            - <https://pod01-rec2.geo-name.backup.windowsazure.de> (For Azure Germany)
     - outbound port 3260
 
 > [!Note]
 >
-> - The downloaded script file name will have the **geo-name** to be filled in the URL. For eg: The downloaded script name begins with \'VMname\'\_\'geoname\'_\'GUID\', like ContosoVM_wcus_12345678.....<br><br>
-> - The URL would be "https:\//pod01-rec2.wcus.backup.windowsazure.com"
+> - The downloaded script file name will have the **geo-name** to be filled in the URL. For eg: The downloaded script name begins with \'VMname\'\_\'geoname\'_\'GUID\', like ContosoVM_wcus_12345678
+> - The URL would be <https://pod01-rec2.wcus.backup.windowsazure.com>"
 
    For Linux, the script requires 'open-iscsi' and 'lshw' components to connect to the recovery point. If the components do not exist on the computer where the script is run, the script asks for permission to install the components. Provide consent to install the necessary components.
 
    The access to download.microsoft.com is required to download components used to build a secure channel between the machine where the script is run and the data in the recovery point.
 
    You can run the script on any machine that has the same (or compatible) operating system as the backed-up VM. See the [Compatible OS table](backup-azure-restore-files-from-vm.md#system-requirements) for compatible operating systems. If the protected Azure virtual machine uses Windows Storage Spaces (for Windows Azure VMs) or LVM/RAID Arrays (for Linux VMs), you can't run the executable or script on the same virtual machine. Instead, run the executable or script on any other machine with a compatible operating system.
 
-### Identifying Volumes
+### Identifying volumes
 
 #### For Windows
 
@@ -104,7 +104,7 @@ In Linux, after the connection to the recovery point is severed, the OS doesn't
 
 ## Special configurations
 
-### Dynamic Disks
+### Dynamic disks
 
 If the protected Azure VM has volumes with one or both of the following characteristics, you can't run the executable script on the same VM.
 
@@ -119,7 +119,7 @@ Windows Storage Spaces is a Windows technology that enables you to virtualize st
 
 If the protected Azure VM uses Windows Storage Spaces, you can't run the executable script on the same VM. Instead, run the executable script on any other machine with a compatible operating system.
 
-### LVM/RAID Arrays
+### LVM/RAID arrays
 
 In Linux, Logical volume manager (LVM) and/or software RAID Arrays are used to manage logical volumes over multiple disks. If the protected Linux VM uses LVM and/or RAID Arrays, you can't run the script on the same VM. Instead run the script on any other machine with a compatible OS and which supports the file system of the protected VM.
 
@@ -129,36 +129,36 @@ The following script output displays the LVM and/or RAID Arrays disks and the vo
 
 To bring these partitions online, run the commands in the following sections.
 
-#### For LVM Partitions
+#### For LVM partitions
 
 To list the volume group names under a physical volume.
 
 ```bash
 #!/bin/bash
-$ pvs <volume name as shown above in the script output>
+pvs <volume name as shown above in the script output>
 ```
 
 To list all logical volumes, names, and their paths in a volume group.
 
 ```bash
 #!/bin/bash
-$ lvdisplay <volume-group-name from the pvs command’s results>
+lvdisplay <volume-group-name from the pvs command’s results>
 ```
 
 To mount the logical volumes to the path of your choice.
 
 ```bash
 #!/bin/bash
-$ mount <LV path> </mountpath>
+mount <LV path> </mountpath>
 ```
 
-#### For RAID Arrays
+#### For RAID arrays
 
 The following command displays details about all raid disks.
 
 ```bash
 #!/bin/bash
-$ mdadm –detail –scan
+mdadm –detail –scan
 ```
 
  The relevant RAID disk is displayed as `/dev/mdm/<RAID array name in the protected VM>`
@@ -167,7 +167,7 @@ Use the mount command if the RAID disk has physical volumes.
 
 ```bash
 #!/bin/bash
-$ mount [RAID Disk Path] [/mountpath]
+mount [RAID Disk Path] [/mountpath]
 ```
 
 If the RAID disk has another LVM configured in it, then use the preceding procedure for LVM partitions but use the volume name in place of the RAID Disk name
diff --git a/articles/backup/backup-azure-sql-automation.md b/articles/backup/backup-azure-sql-automation.md
@@ -12,7 +12,7 @@ ms.author: dacurwin
 ms.assetid: 57854626-91f9-4677-b6a2-5d12b6a866e1
 ---
 
-# Back up and restore SQL Databases in Azure VMs with PowerShell
+# Back up and restore SQL databases in Azure VMs with PowerShell
 
 This article describes how to use Azure PowerShell to back up and recover a SQL DB within an Azure VM using [Azure Backup](backup-overview.md) Recovery Services vault.
 
@@ -249,7 +249,7 @@ Get-AzRecoveryServicesBackupProtectableItem -workloadType MSSQL -ItemType SQLDat
 Once the relevant protectable items are fetched, enable the backups as instructed in the [above section](#configuring-backup).
 If one doesn't want to manually detect new DBs, they can opt for autoprotection as explained [below](#enable-autoprotection).
 
-## Enable AutoProtection
+## Enable autoprotection
 
 A user can configure backup such that all DBs added in the future are automatically protected with a certain policy. To enable autoprotection, use [Enable-AzRecoveryServicesBackupAutoProtection](https://docs.microsoft.com/powershell/module/az.recoveryservices/Enable-AzRecoveryServicesBackupAutoProtection?view=azps-1.5.0) PS cmdlet.
 
@@ -337,7 +337,7 @@ In case of SQL DB restore, the following restore scenarios are supported.
 
 After fetching the relevant recovery point (distinct or log point-in-time), use [Get-AzRecoveryServicesBackupWorkloadRecoveryConfig](https://docs.microsoft.com/powershell/module/az.recoveryservices/Get-AzRecoveryServicesBackupWorkloadRecoveryConfig?view=azps-1.5.0) PS cmdlet to fetch the recovery config object as per the desired recovery plan.
 
-#### Original Workload Restore
+#### Original workload restore
 
 To override the backed-up DB with data from the recovery point, just specify the right flag and the relevant recovery point as shown in the following example(s).
 
@@ -353,7 +353,7 @@ $OverwriteWithFullConfig = Get-AzRecoveryServicesBackupWorkloadRecoveryConfig -R
 $OverwriteWithLogConfig = Get-AzRecoveryServicesBackupWorkloadRecoveryConfig -PointInTime $PointInTime -Item $bkpItem  -OriginalWorkloadRestore -VaultId $targetVault.ID
 ```
 
-#### Alternate Workload Restore
+#### Alternate workload restore
 
 > [!IMPORTANT]
 > A backed up SQL DB can be restored as a new DB to another SQLInstance only, in a Azure VM 'registered' to this vault.
@@ -532,7 +532,7 @@ $SQLContainer = Get-AzRecoveryServicesBackupContainer -ContainerType AzureVMAppC
  Unregister-AzRecoveryServicesBackupContainer -Container $SQLContainer -VaultId $targetvault.ID
 ````
 
-### Track Azure Backup Jobs
+### Track Azure Backup jobs
 
 It is important to note that Azure Backup only tracks user triggered jobs in SQL backup. Scheduled backups (including log backups) are not visible in portal/powershell. However, if any scheduled jobs fail, a [backup alert](backup-azure-monitoring-built-in-monitor.md#backup-alerts-in-recovery-services-vault) is generated and shown in portal. [Use Azure Monitor](backup-azure-monitoring-use-azuremonitor.md) to track all the scheduled jobs and other relevant information.
 
diff --git a/articles/backup/backup-azure-sql-mabs.md b/articles/backup/backup-azure-sql-mabs.md
@@ -148,6 +148,6 @@ The following steps are required to recover a protected entity (SQL Server datab
 
     Once the recovery is completed, the restored database is application consistent.
 
-### Next Steps
+### Next steps
 
-•    [Azure Backup FAQ](backup-azure-backup-faq.md)
+* [Azure Backup FAQ](backup-azure-backup-faq.md)
diff --git a/articles/backup/backup-azure-system-state-troubleshoot.md b/articles/backup/backup-azure-system-state-troubleshoot.md
@@ -125,7 +125,7 @@ To validate Windows Server Backup status, perform the steps below:
 
 If the job fails, it indicates a WSB issue that would result in MARS agent System State Backups failure.
 
-## Common Errors
+## Common errors
 
 ### VSS Writer timeout error
 
diff --git a/articles/backup/backup-azure-vms-troubleshoot.md b/articles/backup/backup-azure-vms-troubleshoot.md
@@ -45,7 +45,7 @@ Error message: Copying backed up data from vault timed out
 
 This could happen due to transient storage errors or insufficient storage account IOPS for backup service to transfer data to the vault within the timeout period. Configure VM backup using these [best practices](backup-azure-vms-introduction.md#best-practices) and retry the backup operation.
 
-## UserErrorVmNotInDesirableState - VM is not in a state that allows backups.
+## UserErrorVmNotInDesirableState - VM is not in a state that allows backups
 
 Error code: UserErrorVmNotInDesirableState <br/>
 Error message: VM is not in a state that allows backups.<br/>
@@ -156,7 +156,7 @@ The snapshot operation failed as the snapshot limit has exceeded for some of the
   * Ensure the value of **isanysnapshotfailed** is set as false in /etc/azure/vmbackup.conf
   * Schedule Azure Site Recovery at a different time, such that it does not conflict the backup operation.
 
-## ExtensionFailedTimeoutVMNetworkUnresponsive - Snapshot operation failed due to inadequate VM resources.
+## ExtensionFailedTimeoutVMNetworkUnresponsive - Snapshot operation failed due to inadequate VM resources
 
 Error code: ExtensionFailedTimeoutVMNetworkUnresponsive<br/>
 Error message: Snapshot operation failed due to inadequate VM resources.
diff --git a/articles/backup/backup-mabs-add-storage.md b/articles/backup/backup-mabs-add-storage.md
@@ -17,6 +17,8 @@ Azure Backup Server V2 and later supports Modern Backup Storage that offers stor
 > [!NOTE]
 > To use Modern Backup Storage, you must run Backup Server V2 or V3 on Windows Server 2016 or V3 on Windows Server 2019.
 > If you run Backup Server V2 on an earlier version of Windows Server, Azure Backup Server can't take advantage of Modern Backup Storage. Instead, it protects workloads as it does with Backup Server V1. For more information, see the Backup Server version [protection matrix](backup-mabs-protection-matrix.md).
+>
+> To achieve enhanced backup performances we recommend to deploy MABS v3 with tiered storage on Windows Server 2019. Please refer to the DPM article “[Set up MBS with Tiered Storage](https://docs.microsoft.com/system-center/dpm/add-storage?view=sc-dpm-2019#set-up-mbs-with-tiered-storage)” for steps to configure tiered storage.
 
 ## Volumes in Backup Server
 
@@ -60,6 +62,11 @@ Using Backup Server V2 or later with volumes as disk storage can help you mainta
 
 ## Add volumes to Backup Server disk storage
 
+> [!NOTE]
+>
+> - Add only one disk to the pool to keep the column count to 1. You can then add disks as needed afterwards.
+> - If you add multiple disks to the storage pool at a go, the number of disks is stored as the number of columns. When more disks are added, they can only be a multiple of the number of columns.
+
 To add a volume to Backup Server, in the **Management** pane, rescan the storage, and then select **Add**. A list of all the volumes available to be added for Backup Server Storage appears. After available volumes are added to the list of selected volumes, you can give them a friendly name to help you manage them. To format these volumes to ReFS so Backup Server can use the benefits of Modern Backup Storage, select **OK**.
 
 ![Add Available Volumes](./media/backup-mabs-add-storage/mabs-add-storage-7.png)
diff --git a/articles/backup/backup-mabs-files-applications-azure-stack.md b/articles/backup/backup-mabs-files-applications-azure-stack.md
@@ -129,7 +129,7 @@ To view Azure Backup Server entities in the Azure portal, you can follow the fol
 2. Click Backup Infrastructure.
 3. View Backup Management Servers.
 
-## See also
+## Next steps
 
 For information on using Azure Backup Server to protect other workloads, see one of the following articles:
 
diff --git a/articles/backup/backup-mabs-sharepoint-azure-stack.md b/articles/backup/backup-mabs-sharepoint-azure-stack.md
@@ -238,7 +238,7 @@ A: Yes, the item can be recovered to the original SharePoint site.
 Q: Can I recover a SharePoint database to the original location if SharePoint is configured by using SQL AlwaysOn?<br>
 A: Because SharePoint databases are configured in SQL AlwaysOn, they cannot be modified unless the availability group is removed. As a result, MABS cannot restore a database to the original location. You can recover a SQL Server database to another SQL Server instance.
 
-## Next Steps
+## Next steps
 
 See the [Backup files and application](backup-mabs-files-applications-azure-stack.md) article.
 See the [Backup SQL Server on Azure Stack](backup-mabs-sql-azure-stack.md) article.
diff --git a/articles/backup/backup-mabs-sql-azure-stack.md b/articles/backup/backup-mabs-sql-azure-stack.md
@@ -150,7 +150,7 @@ The following steps are required to recover a protected entity (SQL Server datab
 
     Once the recovery is completed, the restored database is application consistent.
 
-## Next Steps
+## Next steps
 
 See the [Backup files and application](backup-mabs-files-applications-azure-stack.md) article.
 See the [Backup SharePoint on Azure Stack](backup-mabs-sharepoint-azure-stack.md) article.
diff --git a/articles/backup/backup-mabs-whats-new-mabs.md b/articles/backup/backup-mabs-whats-new-mabs.md
@@ -24,7 +24,7 @@ With Modern Backup Storage (MBS) in MABS V2, we announced Workload aware storage
 
 In enterprises, MABS is managed by a team of administrators. While there are guidelines on storage that should be used for backups, an incorrect volume given to MABS as backup storage may lead to loss of critical data. With MABS V3, you can prevent such scenarios by configuring those volumes as the ones that are not available for storage using [these PowerShell cmdlets](https://docs.microsoft.com/azure/backup/backup-mabs-add-storage).
 
-## Custom Size Allocation
+## Custom size allocation
 
 Modern Backup Storage (MBS) consumes storage thinly, as and when needed. To do so, MABS calculates the size of the data being backed up when it is configured for protection. However, if many files and folders are being backed up together, as in the case of a file server, size calculation can take long time. With MABS V3, you can configure MABS to accept the volume size as default, instead of calculating the size of each file, hence saving time.
 
diff --git a/articles/backup/backup-sql-server-azure-troubleshoot.md b/articles/backup/backup-sql-server-azure-troubleshoot.md
diff --git a/articles/backup/backup-support-matrix-mars-agent.md b/articles/backup/backup-support-matrix-mars-agent.md
diff --git a/articles/backup/manage-monitor-sql-database-backup.md b/articles/backup/manage-monitor-sql-database-backup.md
diff --git a/articles/backup/troubleshoot-azure-files.md b/articles/backup/troubleshoot-azure-files.md
