Merge pull request #88098 from ThalathBhagya/master

added encrypted content

Author: v-albemi

articles/backup/backup-azure-sql-database.md

@@ -21,7 +21,7 @@ This solution leverages the SQL native APIs to take backups of your SQL database
 
 * Once you specify the SQL Server VM that you want to protect and query for the databases in it, Azure Backup service will install a workload backup extension on the VM by the name `AzureBackupWindowsWorkload` extension.
 * This extension consists of a coordinator and a SQL plugin. While the coordinator is responsible for triggering workflows for various operations like configure backup, backup and restore, the plugin is responsible for actual data flow.
-* To be able to discover databases on this VM, Azure Backup creates the account `NT SERVICE\AzureWLBackupPluginSvc`. This account is used for backup and restore and requires SQL sysadmin permissions. Azure Backup leverages the `NT AUTHORITY\SYSTEM` account for database discovery/inquiry, so this account need to be a public login on SQL. If you didn't create the SQL Server VM from the Azure Marketplace, you might receive an error **UserErrorSQLNoSysadminMembership**. If this occurs [follow these instructions](backup-azure-sql-database.md).
+* To be able to discover databases on this VM, Azure Backup creates the account `NT SERVICE\AzureWLBackupPluginSvc`. This account is used for backup and restore and requires SQL sysadmin permissions. Azure Backup leverages the `NT AUTHORITY\SYSTEM` account for database discovery/inquiry, so this account needs to be a public login on SQL. If you didn't create the SQL Server VM from the Azure Marketplace, you might receive an error **UserErrorSQLNoSysadminMembership**. If this occurs [follow these instructions](#set-vm-permissions).
 * Once you trigger configure protection on the selected databases, the backup service sets up the coordinator with the backup schedules and other policy details, which the extension caches locally on the VM.
 * At the scheduled time, the coordinator communicates with the plugin and it starts streaming the backup data from the SQL server using VDI.  
 * The plugin sends the data directly to the recovery services vault, thus eliminating the need for a staging location. The data is encrypted and stored by the Azure Backup service in storage accounts.
@@ -55,8 +55,7 @@ Azure Backup has recently announced support for [EOS SQL Severs](https://docs.mi
 2. .NET Framework 4.5.2 and above needs to be installed on the VM
 3. Backup for FCI and mirrored databases isn’t supported
 
-Users will not be charged for this feature until the time it is generally available. All of the other [feature considerations and limitations](#feature-consideration-and-limitations) apply to these versions as well. Kindly refer to the [prerequisites](backup-sql-server-database-azure-vms.md#prerequisites) before you configure protection on SQL Servers 2008 and 2008 R2, which include setting the [registry key](backup-sql-server-database-azure-vms.md#add-registry-key-to-enable-registration) (this step would not be required when the feature is generally available).
-
+Users will not be charged for this feature until the time it is generally available. All of the other [feature considerations and limitations](#feature-consideration-and-limitations) apply to these versions as well. Kindly refer to the [prerequisites](backup-sql-server-database-azure-vms.md#prerequisites) before you configure protection on SQL Servers 2008 and 2008 R2.
 
 ## Feature consideration and limitations
 

articles/backup/backup-sql-server-database-azure-vms.md

@@ -6,7 +6,7 @@ author: dcurwin
 manager: carmonm
 ms.service: backup
 ms.topic: conceptual
-ms.date: 06/18/2019
+ms.date: 09/11/2019
 ms.author: dacurwin
 
 
@@ -32,8 +32,7 @@ Before you back up a SQL Server database, check the following criteria:
 1. Identify or create a [Recovery Services vault](backup-sql-server-database-azure-vms.md#create-a-recovery-services-vault) in the same region or locale as the VM hosting the SQL Server instance.
 2. Verify that the VM has [network connectivity](backup-sql-server-database-azure-vms.md#establish-network-connectivity).
 3. Make sure that the SQL Server databases follow the [database naming guidelines for Azure Backup](#database-naming-guidelines-for-azure-backup).
-4. Specifically for SQL 2008 and 2008 R2, [add registry key](#add-registry-key-to-enable-registration) to enable server registration. This step will be not be required when the feature is generally available.
-5. Check that you don't have any other backup solutions enabled for the database. Disable all other SQL Server backups before you back up the database.
+4. Check that you don't have any other backup solutions enabled for the database. Disable all other SQL Server backups before you back up the database.
 
 > [!NOTE]
 > You can enable Azure Backup for an Azure VM and also for a SQL Server database running on the VM without conflict.
@@ -94,22 +93,6 @@ Avoid using the following elements in database names:
 
 Aliasing is available for unsupported characters, but we recommend avoiding them. For more information, see [Understanding the Table Service Data Model](https://docs.microsoft.com/rest/api/storageservices/Understanding-the-Table-Service-Data-Model?redirectedfrom=MSDN).
 
-### Add registry key to enable registration
-
-1. Open Regedit
-2. Create the Registry Directory Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WorkloadBackup\TestHook (you will need to create the 'Key' TestHook under WorkloadBackup which in turn needs to be created under Microsoft).
-3. Under the Registry Directory Path, create a new 'string value' with the string name **AzureBackupEnableWin2K8R2SP1** and value: **True**
-
-    ![RegEdit for enabling registration](media/backup-azure-sql-database/reg-edit-sqleos-bkp.png)
-
-Alternatively, you can automate this step by running .reg file with the following command:
-
-```csharp
-Windows Registry Editor Version 5.00
-
-[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WorkloadBackup\TestHook]
-"AzureBackupEnableWin2K8R2SP1"="True"
-```
 
 [!INCLUDE [How to create a Recovery Services vault](../../includes/backup-create-rs-vault.md)]
 
@@ -258,18 +241,6 @@ To create a backup policy:
 
 14. After you complete the edits to the backup policy, select **OK**.
 
-
-### Modify policy
-Modify policy to change backup frequency or retention range.
-
-> [!NOTE]
-> Any change in the retention period will be applied retrospectively to all the older recovery points besides the new ones.
-
-In the vault dashboard, go to **Manage** > **Backup Policies** and choose the policy you want to edit.
-
-  ![Manage backup policy](./media/backup-azure-sql-database/modify-backup-policy.png)
-
-
 ## Enable auto-protection  
 
 You can enable auto-protection to automatically back up all existing and future databases to a standalone SQL Server instance or to an Always On availability group.

articles/backup/manage-monitor-sql-database-backup.md

@@ -5,7 +5,7 @@ author: dcurwin
 manager: carmonm
 ms.service: backup
 ms.topic: conceptual
-ms.date: 03/14/2018
+ms.date: 09/11/2019
 ms.author: dacurwin
 
 
@@ -137,6 +137,32 @@ Unregister a SQL Server instance after you disable protection but before you del
 
    ![Select Delete](./media/backup-azure-sql-database/delete-protected-server.jpg)
 
+
+## Modify policy
+Modify policy to change backup frequency or retention range.
+
+> [!NOTE]
+> Any change in the retention period will be applied retrospectively to all the older recovery points besides the new ones.
+
+In the vault dashboard, go to **Manage** > **Backup Policies** and choose the policy you want to edit.
+
+  ![Manage backup policy](./media/backup-azure-sql-database/modify-backup-policy.png)
+
+  ![Modify backup policy](./media/backup-azure-sql-database/modify-backup-policy-impact.png)
+
+Policy modification will impact all the associated Backup Items and trigger corresponding **configure protection** jobs. 
+
+#### Inconsistent Policy 
+
+Sometimes, a modify policy operation can lead to an **inconsistent** policy version for some backup items. This happens when the corresponding **configure protection** job fails for the backup item after a modify policy operation is triggered. It appears as follows in the backup item view:
+ 
+  ![Inconsistent policy](./media/backup-azure-sql-database/inconsistent-policy.png)
+
+You can fix the policy version for all the impacted items in one click:
+
+  ![Fix inconsistent policy](./media/backup-azure-sql-database/fix-inconsistent-policy.png)
+ 
+
 ## Re-register extension on the SQL Server VM
 
 Sometimes, the workload extension on the VM may get impacted for one reason or the other. In such cases, all the operations triggered on the VM will begin to fail. You may then need to re-register the extension on the VM. **Re-register** operation reinstalls the workload backup extension on the VM for operations to continue.  <br>