Mulitple Changes

Author: David Curwin

articles/backup/back-up-hyper-v-virtual-machines-mabs.md

@@ -95,83 +95,6 @@ These are the prerequisites for backing up Hyper-V virtual machines with MABS:
 
     After you create the protection group, initial replication of the data occurs in accordance with the method you selected. After initial replication, each backup takes place in line with the protection group settings. If you need to recover backed up data, note the following:
 
-## Back up virtual machines configured for live migration
-
-When virtual machines are involved in live migration, MABS continues to protect the virtual machines as long as the MABS protection agent is installed on the Hyper-V host. The way in which MABS protects the virtual machines depends on the type of live migration involved.
-
-**Live migration within a cluster** - When a virtual machine is migrated within a cluster MABS detects the migration, and backs up the virtual machine from the new cluster node without any requirement for user intervention. Because the storage location hasn't changed, MABS continues with express full backups.
-
-**Live migration outside the cluster** - When a virtual machine is migrated between stand-alone servers, different clusters, or between a stand-alone server and a cluster, MABS detects the migration, and can back up the virtual machine without user intervention.
-
-### Requirements for maintaining protection
-
-The following are requirements for maintaining protection during live migration:
-
-- The Hyper-V hosts for the virtual machines must be located in a System Center VMM cloud, on a VMM server, running at least System Center 2012 with SP1.
-
-- The MABS protection agent must be installed on all Hyper-V hosts.
-
-- MABS servers must be connected to the VMM server. All Hyper-V host servers in the VMM cloud must also be connected to the MABS servers. This allows MABS to communicate with the VMM server so MABS can find out on which Hyper-V host server the virtual machine is currently running, and to create a new backup from that Hyper-V server. If a connection can't be established to the Hyper-V server, the backup fails with a message that the MABS protection agent is unreachable.
-
-- All MABS servers, VMM servers, and Hyper-V host servers must be in the same domain.
-
-### Details about live migration
-
-Note the following for backup during live migration:
-
-- If a live migration transfers storage, MABS performs a full consistency check of the virtual machine, and then continues with express full backups. When live migration of storage occurs, Hyper-V reorganizes the virtual hard disk (VHD) or VHDX, which causes a one-time spike in the size of the MABS backup data.
-
-- On the virtual machine host, turn on auto-mount to enable virtual protection, and disable TCP Chimney Offload.
-
-- MABS uses port 6070 as the default port for hosting the DPM-VMM Helper Service. To change the registry:
-
-    1. Navigate to **HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration**.
-    2. Create a 32-bit DWORD value: DpmVmmHelperServicePort, and write the updated port number as part of the registry key.
-    3. Open ```<Install directory>\Azure Backup Server\DPM\DPM\VmmHelperService\VmmHelperServiceHost.exe.config```, and change the port number from 6070 to the new port. For example: ```<add baseAddress="net.tcp://localhost:6080/VmmHelperService/" />```
-    4. Restart the DPM-VMM Helper service, and restart the DPM service.
-
-### Set up protection for live migration
-
-To set up protection for live migration:
-
-1. Set up the MABS server and its storage, and install the MABS protection agent on every Hyper-V host server or cluster node in the VMM cloud. If you're using SMB storage in a cluster, install the MABS protection agent on all cluster nodes.
-
-2. Install the VMM console as a client component on the MABS server so that MABS can communicate with the VMM server. The console should be the same version as the one running on the VMM server.
-
-3. Assign the MABSMachineName$ account as a read-only administrator account on the VMM management server.
-
-4. Connect all Hyper-V host servers to all MABS servers with the `Set-DPMGlobalProperty` PowerShell cmdlet. The cmdlet accepts multiple MABS server names. Use the format: `Set-DPMGlobalProperty -dpmservername <MABSservername> -knownvmmservers <vmmservername>`. For more information, see [Set-DPMGlobalProperty](https://docs.microsoft.com/powershell/module/dataprotectionmanager/set-dpmglobalproperty?view=systemcenter-ps-2019).
-
-5. After all virtual machines running on the Hyper-V hosts in the VMM clouds are discovered in VMM, set up a protection group and add the virtual machines you want to protect. Automatic consistency checks should be enabled at the protection group level for protection under virtual machine mobility scenarios.
-
-6. After the settings are configured, when a virtual machine migrates from one cluster to another all backups continue as expected. You can verify live migration is enabled as expected as follows:
-
-   1. Check the DPM-VMM Helper Service is running. If it isn't, start it.
-
-   2. Open Microsoft SQL Server Management Studio and connect to the instance that hosts the MABS database (DPMDB). On DPMDB run the following query: `SELECT TOP 1000 [PropertyName] ,[PropertyValue] FROM[DPMDB].[dbo].[tbl_DLS_GlobalSetting]`.
-
-      This query contains a property called `KnownVMMServer`. This value should be the same value you provided with the `Set-DPMGlobalProperty` cmdlet.
-
-   3. Run the following query to validate the *VMMIdentifier* parameter in the `PhysicalPathXML` for a particular virtual machine. Replace `VMName` with the name of the virtual machine.
-
-      ```sql
-      select cast(PhysicalPath as XML) from tbl_IM_ProtectedObject where DataSourceId in (select datasourceid from tbl_IM_DataSource   where DataSourceName like '%<VMName>%')
-      ```
-
-   4. Open the .xml file that this query returns and validate that the *VMMIdentifier* field has a value.
-
-### Run manual migration
-
-After you complete the steps in the previous sections, and the MABS Summary Manager job completes, migration is enabled. By default, this job starts at midnight and runs every morning. If you want to run a manual migration, to check everything is working as expected, do the following:
-
-1. Open SQL Server Management Studio and connect to the instance that hosts the MABS database.
-
-2. Run the following query: `SELECT SCH.ScheduleId FROM tbl_JM_JobDefinition JD JOIN tbl_SCH_ScheduleDefinition SCH ON JD.JobDefinitionId = SCH.JobDefinitionId WHERE JD.Type = '282faac6-e3cb-4015-8c6d-4276fcca11d4' AND JD.IsDeleted = 0 AND SCH.IsDeleted = 0`. This query returns the **ScheduleID**. Note this ID as you will use it in the next step.
-
-3. In the SQL Server Management Studio, expand **SQL Server Agent**, and then expand **Jobs**. Right-click **ScheduleID** that you noted, and select **Start Job at Step**.
-
-Backup performance is affected when the job runs. The size and scale of your deployment determines how much time the job takes to finish.
-
 ## Back up replica virtual machines
 
 If MABS is running on Windows Server 2012 R2 or greater, then you can back up replica virtual machines. This is useful for several reasons:

articles/backup/backup-azure-exchange-mabs.md

@@ -47,7 +47,7 @@ To install the MABS protection agent on the Exchange server, follow these steps:
     After you select this option, backup consistency checking will be run on MABS to avoid the I/O traffic that's generated by running the **eseutil** command on the Exchange server.
 
    > [!NOTE]
-   > To use this option, you must copy the Ese.dll and Eseutil.exe files to the C:\Program Files\Microsoft Azure Backup\DPM\DPM\bin directory on the MAB server. Otherwise, the following error is triggered:  
+   > To use this option, you must copy the Ese.dll and Eseutil.exe files to the C:\Program Files\Microsoft Azure Backup\DPM\DPM\bin directory on the MABS server. Otherwise, the following error is triggered:  
    > ![eseutil error](./media/backup-azure-backup-exchange-server/eseutil-error.png)
    >
    >
@@ -60,7 +60,7 @@ To install the MABS protection agent on the Exchange server, follow these steps:
    >
 10. Configure the goals for **Short-Term backup**, and then click **Next**.
 11. Review the available disk space, and then click **Next**.
-12. Select the time at which the MAB Server will create the initial replication, and then click **Next**.
+12. Select the time at which the MABS Server will create the initial replication, and then click **Next**.
 13. Select the consistency check options, and then click **Next**.
 14. Choose the database that you want to back up to Azure, and then click **Next**. For example:
 

articles/backup/backup-azure-file-folder-backup-faq.md

@@ -54,6 +54,10 @@ Backup data is sent to the datacenter of the vault in which the server is regist
 
 Yes. The MARS agent converts the deduplicated data to normal data when it prepares the backup operation. It then optimizes the data for backup, encrypts the data, and then sends the encrypted data to the vault.
 
+### Do I need administrator permissions to install and configure the MARS agent?
+
+Yes, the installation of the MARS Agent and configuration of backups using the MARS console need the user to be a local administrator on the protected server.
+
 ## Manage backups
 
 ### What happens if I rename a Windows machine configured for backup?

articles/backup/backup-azure-mabs-troubleshoot.md

@@ -21,7 +21,7 @@ We recommend you perform the below validation, before you start troubleshooting
 - If registration is failing, then ensure the server on which you are trying to install Azure Backup Server is not already registered with another vault
 - If Push install fails, check if DPM agent is already present. If yes, then uninstall the agent and retry the installation
 - [Ensure no other process or antivirus software is interfering with Azure Backup](https://docs.microsoft.com/azure/backup/backup-azure-troubleshoot-slow-backup-performance-issue#cause-another-process-or-antivirus-software-interfering-with-azure-backup)<br>
-- Ensure that the SQL Agent service is running and set to automatic in MAB server<br>
+- Ensure that the SQL Agent service is running and set to automatic in the MABS server<br>
 
 ## Invalid vault credentials provided
 

articles/backup/backup-azure-mars-troubleshoot.md

@@ -128,6 +128,13 @@ Set-ExecutionPolicy Unrestricted
 > [!TIP]
 > To ensure changes are applied consistently, restart the server after performing the preceding steps.
 
+## Resource not provisioned in service stamp
+
+Error | Possible causes | Recommended actions
+--- | --- | ---
+The current operation failed due to an internal service error "Resource not provisioned in service stamp". Please retry the operation after some time. (ID: 230006) | The protected server was renamed. | <li> Rename the server back to the original name as registered with the vault. <br> <li> Re-register the server to the vault with the new name.
+
+
 ## Troubleshoot restore problems
 
 Azure Backup might not successfully mount the recovery volume, even after several minutes. And you might receive error messages during the process. To begin recovering normally, take these steps:

articles/backup/install-mars-agent.md

@@ -32,6 +32,7 @@ The data that's available for backup depends on where the agent is installed.
 * Review [what's supported and what you can back up](backup-support-matrix-mars-agent.md) by the MARS agent.
 * Make sure that you have an Azure account if you need to back up a server or client to Azure. If you don't have an account, you can create a [free one](https://azure.microsoft.com/free/) in just a few minutes.
 * Verify internet access on the machines that you want to back up.
+* Ensure the user performing the installation and configuration of the MARS agent has local administrator privileges on the server to be protected.
 
 [!INCLUDE [How to create a Recovery Services vault](../../includes/backup-create-rs-vault.md)]