Merge pull request #105550 from MashaMSFT/20200225_sqlvmbackup

updated automated backup for sql vms

Author: v-albemi

articles/virtual-machines/windows/sql/media/virtual-machines-windows-sql-automated-backup-v2/automated-backup-blade.png

@@ -114,11 +114,7 @@ Then, on Tuesday at 10 for 6 hours, full backups of all databases start again.
 > [!IMPORTANT]
 > When scheduling daily backups, it is recommended that you schedule a wide time window to ensure all databases can be backed up within this time. This is especially important in the case where you have a large amount of data to back up.
 
-## Configure in the portal
-
-You can use the Azure portal to configure Automated Backup v2 during provisioning or for existing SQL Server 2016/2017 VMs.
-
-## Configure for new VMs
+## Configure new VMs
 
 Use the Azure portal to configure Automated Backup v2 when you create a new SQL Server 2016 or 2017 Virtual Machine in the Resource Manager deployment model.
 

articles/virtual-machines/windows/sql/media/virtual-machines-windows-sql-automated-backup/azure-sql-arm-autobackup.png

@@ -1,5 +1,5 @@
 ---
-title: Automated Backup for SQL Server 2014 Azure Virtual Machines | Microsoft Docs
+title: Automated Backup for SQL Server 2014 Azure Virtual Machines
 description: Explains the Automated Backup feature for SQL Server 2014 VMs running in Azure. This article is specific to VMs using the Resource Manager.
 services: virtual-machines-windows
 documentationcenter: na
@@ -64,30 +64,28 @@ The following table describes the options that can be configured for Automated B
 | **Encryption** | Enable/Disable (Disabled) | Enables or disables encryption. When encryption is enabled, the certificates used to restore the backup are located in the specified storage account in the same `automaticbackup` container using the same naming convention. If the password changes, a new certificate is generated with that password, but the old certificate remains to restore prior backups. |
 | **Password** | Password text | A password for encryption keys. This is only required if encryption is enabled. In order to restore an encrypted backup, you must have the correct password and related certificate that was used at the time the backup was taken. |
 
-## Configure in the portal
-
-You can use the Azure portal to configure Automated Backup during provisioning or for existing SQL Server 2014 VMs.
 
 ## Configure new VMs
 
 Use the Azure portal to configure Automated Backup when you create a new SQL Server 2014 Virtual Machine in the Resource Manager deployment model.
 
-In the **SQL Server settings** tab, scroll down to **Automated backup** and select **Enable**. You can also specify the retention period, and storage account, as well as enabling encryption, backing up system databases, and configuring a backup schedule.  The following Azure portal screenshot shows the **SQL Automated Backup** settings.
+On the **SQL Server settings** tab, scroll down to **Automated backup** and select **Enable**. The following Azure portal screenshot shows the **SQL Automated Backup** settings.
 
 ![SQL Automated Backup configuration in Azure portal](./media/virtual-machines-windows-sql-automated-backup/azure-sql-arm-autobackup.png)
 
 ## Configure existing VMs
 
 [!INCLUDE [windows-virtual-machines-sql-use-new-management-blade](../../../../includes/windows-virtual-machines-sql-new-resource.md)]
 
-For existing SQL Server virtual machines, navigate to the 
-[SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-the-sql-virtual-machines-resource) and then select **Backups**. 
+For existing SQL Server virtual machines, you can enable and disable automated backups, change the retention period, specify the storage account, and enable encryption from the Azure portal. 
+
+Navigate to the [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-the-sql-virtual-machines-resource) for your SQL Server 2014 virtual machine and then select **Backups**. 
 
 ![SQL Automated Backup for existing VMs](./media/virtual-machines-windows-sql-automated-backup/azure-sql-rm-autobackup-existing-vms.png)
 
 When finished, select the **Apply** button on the bottom of the **Backups** page to save your changes.
 
-If you are enabling Automated Backup for the first time, Azure configures the SQL Server IaaS Agent in the background. During this time, the Azure portal might not show that Automated Backup is configured. Wait several minutes for the agent to be installed, configured. After that the Azure portal will reflect the new settings.
+If you are enabling Automated Backup for the first time, Azure configures the SQL Server IaaS Agent in the background. During this time, the Azure portal might not show that Automated Backup is configured. Wait several minutes for the agent to be installed and configured. After that, the Azure portal will reflect the new settings.
 
 > [!NOTE]
 > You can also configure Automated Backup using a template. For more information, see [Azure quickstart template for Automated Backup](https://github.com/Azure/azure-quickstart-templates/tree/master/101-vm-sql-existing-autobackup-update).
@@ -97,7 +95,7 @@ If you are enabling Automated Backup for the first time, Azure configures the SQ
 You can use PowerShell to configure Automated Backup. Before you begin, you must:
 
 - [Download and install the latest Azure PowerShell](https://aka.ms/webpi-azps).
-- Open Windows PowerShell and associate it with your account with the **Connect-AzAccount** command.
+- Open Windows PowerShell and associate it with your account with the **Connect-AzAccount** command. 
 
 [!INCLUDE [updated-for-az.md](../../../../includes/updated-for-az.md)]
 

articles/virtual-machines/windows/sql/media/virtual-machines-windows-sql-automated-backup/azure-sql-rm-autobackup-existing-vms.png

@@ -130,7 +130,7 @@ For VMs that support premium SSDs, you can also store TempDB on a disk that supp
      > [!WARNING]
      > Stop the SQL Server service when changing the cache setting of Azure VM disks to avoid the possibility of any database corruption.
 
-* **NTFS allocation unit size**: When formatting the data disk, it is recommended that you use a 64-KB allocation unit size for data and log files as well as TempDB.
+* **NTFS allocation unit size**: When formatting the data disk, it is recommended that you use a 64-KB allocation unit size for data and log files as well as TempDB. If TempDB is placed on the temporary disk (D:\ drive) the performance gained by leveraging this drive outweighs the need for a 64K allocation unit size. 
 
 * **Disk management best practices**: When removing a data disk or changing its cache type, stop the SQL Server service during the change. When the caching settings are changed on the OS disk, Azure stops the VM, changes the cache type, and restarts the VM. When the cache settings of a data disk are changed, the VM is not stopped, but the data disk is detached from the VM during the change and then reattached.