Merge pull request #95787 from dcurwin/dcurwin-nov13

Misc fixes

Author: megvanhuygen

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

@@ -15,26 +15,25 @@ ms.author: dacurwin
 This article explains how to back up Hyper-V virtual machines using Microsoft Azure Backup Server (MABS).
 
 ## Supported scenarios
-MABS can back up virtual machines running on Hyper-V host servers in the following scenarios:
-
--   **Virtual machines with local or direct storage** - Back up virtual machines hosted on Hyper-V host standalone servers that have local or directly attached storage. For example: a hard drive, a storage area network (SAN) device, or a network attached storage (NAS) device. The MABS protection agent must be installed on all hosts.
 
--   **Virtual machines in a cluster with CSV storage** - Back up virtual machines hosted on a Hyper-V cluster with Cluster Shared Volume (CSV) storage. The MABS protection agent is installed on each cluster node.
+MABS can back up virtual machines running on Hyper-V host servers in the following scenarios:
 
+- **Virtual machines with local or direct storage** - Back up virtual machines hosted on Hyper-V host standalone servers that have local or directly attached storage. For example: a hard drive, a storage area network (SAN) device, or a network attached storage (NAS) device. The MABS protection agent must be installed on all hosts.
 
+- **Virtual machines in a cluster with CSV storage** - Back up virtual machines hosted on a Hyper-V cluster with Cluster Shared Volume (CSV) storage. The MABS protection agent is installed on each cluster node.
 
 ## Host versus guest backup
+
 MABS can do a host or guest-level backup of Hyper-V VMs. At the host level, the MABS protection agent is installed on the Hyper-V host server or cluster and protects the entire VMs and data files running on that host.   At the guest level, the agent is installed on each virtual machine and protects the workload present on that machine.
 
 Both methods have pros and cons:
 
--   Host-level backups are flexible because they work regardless of the type of OS running on the guest machines and don't require the installation of the MABS protection agent on each VM. If you deploy host level backup, you can recover an entire virtual machine, or files and folders (item-level recovery).
-
--   Guest-level backup is useful if you want to protect specific workloads running on a virtual machine. At host-level you can recover an entire VM or specific files, but it won't provide recovery in the context of a specific application. For example, to recover specific SharePoint items from a backed-up VM, you should do guest-level backup of that VM. Use guest-level backup if you want to protect data stored on passthrough disks. Passthrough allows the virtual machine to directly access the storage device and doesn't store virtual volume data in a VHD file.
-
+- Host-level backups are flexible because they work regardless of the type of OS running on the guest machines and don't require the installation of the MABS protection agent on each VM. If you deploy host level backup, you can recover an entire virtual machine, or files and folders (item-level recovery).
 
+- Guest-level backup is useful if you want to protect specific workloads running on a virtual machine. At host-level you can recover an entire VM or specific files, but it won't provide recovery in the context of a specific application. For example, to recover specific SharePoint items from a backed-up VM, you should do guest-level backup of that VM. Use guest-level backup if you want to protect data stored on passthrough disks. Passthrough allows the virtual machine to directly access the storage device and doesn't store virtual volume data in a VHD file.
 
 ## How the backup process works
+
 MABS performs backup with VSS as follows. The steps in this description are numbered to help with clarity.
 
 1. The MABS block-based synchronization engine makes an initial copy of the protected virtual machine and ensures that the copy of the virtual machine is complete and consistent.
@@ -57,8 +56,8 @@ MABS performs backup with VSS as follows. The steps in this description are numb
 >
 >Starting in Windows Server 2016, Hyper-V virtual hard disks have built-in change tracking known as resilient change tracking (RCT). MABS uses RCT (the native change tracking in Hyper-V), which decreases the need for time-consuming consistency checks in scenarios such as VM crashes. RCT provides better resiliency than the change tracking provided by VSS snapshot-based backups. MABS V3 optimizes network and storage consumption further by transferring only the changed data during any consistency checks.
 
-
 ## Backup prerequisites
+
 These are the prerequisites for backing up Hyper-V virtual machines with MABS:
 
 |Prerequisite|Details|
@@ -83,17 +82,14 @@ These are the prerequisites for backing up Hyper-V virtual machines with MABS:
 
 4. On the **Select Group Members** page, select the VMs you want to protect from the Hyper-V host servers on which they're located. We recommend you put all VMs that will have the same protection policy into one protection group. To make efficient use of space, enable colocation. Colocation allows you to locate data from different protection groups on the same disk or tape storage, so that multiple data sources have a single replica and recovery point volume.
 
-5. On the **Select Data Protection Method** page, specify a protection group name. Select **I want short-term protection using Disk** and select **I want online protection** if you want to back up data to Azure using the Azure Backup service. 
-
+5. On the **Select Data Protection Method** page, specify a protection group name. Select **I want short-term protection using Disk** and select **I want online protection** if you want to back up data to Azure using the Azure Backup service.
 
 6. In **Specify Short-Term Goals** > **Retention range**, specify how long you want to retain disk data. In **Synchronization frequency**, specify how often incremental backups of the data should run. Alternatively, instead of selecting an interval for incremental backups you can enable **Just before a recovery point**. With this setting enabled, MABS will run an express full backup just before each scheduled recovery point.
 
     > [!NOTE]
     >
     >If you're protecting application workloads, recovery points are created in accordance with Synchronization frequency, provided the application supports incremental backups. If it doesn't, then MABS runs an express full backup, instead of an incremental backup, and creates recovery points in accordance with the express backup schedule.
 
-    
-
 7. In the **Review disk allocation** page, review the storage pool disk space allocated for the protection group.
 
    **Total Data size** is the size of the data you want to back up, and **Disk space to be provisioned on MABS** is the space that MABS recommends for the protection group. MABS chooses the ideal backup volume, based on the settings. However, you can edit the backup volume choices in the **Disk allocation details**. For the workloads, select the preferred storage in the dropdown menu. Your edits change the values for **Total Storage** and **Free Storage** in the **Available Disk Storage** pane. Underprovisioned space is the amount of storage MABS suggests you add to the volume, to continue with backups smoothly in the future.
@@ -105,9 +101,10 @@ 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 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.
 
@@ -127,7 +124,6 @@ The following are requirements for maintaining protection during 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.
@@ -136,7 +132,7 @@ Note the following for backup during live migration:
 
     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/" />```
+    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
@@ -169,7 +165,6 @@ To set up protection for live migration:
 
    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:
@@ -182,7 +177,6 @@ After you complete the steps in the previous sections, and the MABS Summary Mana
 
 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:
@@ -219,12 +213,12 @@ When you can recover a backed up virtual machine, you use the Recovery wizard to
 
 4. On the **Select Recovery Type** screen, select where you want to restore the data and then click **Next**.
 
-    -   **Recover to original instance**: When you recover to the original instance, the original VHD is deleted. MABS recovers the VHD and other configuration files to the original location using Hyper-V VSS writer. At the end of the recovery process, virtual machines are still highly available.
+    - **Recover to original instance**: When you recover to the original instance, the original VHD is deleted. MABS recovers the VHD and other configuration files to the original location using Hyper-V VSS writer. At the end of the recovery process, virtual machines are still highly available.
         The resource group must be present for recovery. If it isn't available, recover to an alternate location and then make the virtual machine highly available.
 
-    -   **Recover as virtual machine to any host**: MABS supports alternate location recovery (ALR), which provides a seamless recovery of a protected Hyper-V virtual machine to a different Hyper-V host, independent of processor architecture. Hyper-V virtual machines that are recovered to a cluster node will not be highly available. If you choose this option, the Recovery Wizard presents you with an additional screen for identifying the destination and destination path.
+    - **Recover as virtual machine to any host**: MABS supports alternate location recovery (ALR), which provides a seamless recovery of a protected Hyper-V virtual machine to a different Hyper-V host, independent of processor architecture. Hyper-V virtual machines that are recovered to a cluster node will not be highly available. If you choose this option, the Recovery Wizard presents you with an additional screen for identifying the destination and destination path.
 
-    -   **Copy to a network folder**: MABS supports item-level recovery (ILR), which allows you to do item-level recovery of files, folders, volumes, and virtual hard disks (VHDs) from a host-level backup of Hyper-V virtual machines to a network share or a volume on a MABS protected server. The MABS protection agent doesn't have to be installed inside the guest to perform item-level recovery. If you choose this option, the Recovery Wizard presents you with an additional screen for identifying the destination and destination path.
+    - **Copy to a network folder**: MABS supports item-level recovery (ILR), which allows you to do item-level recovery of files, folders, volumes, and virtual hard disks (VHDs) from a host-level backup of Hyper-V virtual machines to a network share or a volume on a MABS protected server. The MABS protection agent doesn't have to be installed inside the guest to perform item-level recovery. If you choose this option, the Recovery Wizard presents you with an additional screen for identifying the destination and destination path.
 
 5. In **Specify Recovery Options** configure the recovery options and click **Next**:
 
@@ -236,6 +230,6 @@ When you can recover a backed up virtual machine, you use the Recovery wizard to
 
 7. The **Recovery Status** screen provides information about the recovery job.
 
-
 ## Next steps
+
 [Recover data from Azure Backup Server](https://docs.microsoft.com/azure/backup/backup-azure-alternate-dpm-server)

articles/backup/backup-architecture.md

@@ -129,7 +129,7 @@ Azure VMs need internet access for control commands. If you're backing up worklo
     - The MARS agent uses only the Windows system write operation to capture the snapshot.
     - Because the agent doesn't use any application VSS writers, it doesn't capture app-consistent snapshots.
 1. After taking the snapshot with VSS, the MARS agent creates a virtual hard disk (VHD) in the cache folder you specified when you configured the backup. The agent also stores checksums for each data block.
-1. Incremental backups run according to the schedule you specify, unless you run an ad-hoc backup.
+1. Incremental backups run according to the schedule you specify, unless you run an on-demand backup.
 1. In incremental backups, changed files are identified and a new VHD is created. The VHD is compressed and encrypted, and then it's sent to the vault.
 1. After the incremental backup finishes, the new VHD is merged with the VHD created after the initial replication. This merged VHD provides the latest state to be used for comparison for ongoing backup.
 
@@ -143,7 +143,7 @@ Azure VMs need internet access for control commands. If you're backing up worklo
     - With DPM/MABS, you can protect backup volumes, shares, files, and folders. You can also protect a machine's system state (bare metal), and you can protect specific apps with app-aware backup settings.
 1. When you set up protection for a machine or app in DPM/MABS, you select to back up to the MABS/DPM local disk for short-term storage and to Azure for online protection. You also specify when the backup to local DPM/MABS storage should run and when the online backup to Azure should run.
 1. The disk of the protected workload is backed up to the local MABS/DPM disks, according to the schedule you specified.
-4. The DPM/MABS disks are backed up to the vault by the MARS agent that's running on the DPM/MABS server.
+1. The DPM/MABS disks are backed up to the vault by the MARS agent that's running on the DPM/MABS server.
 
 ![Backup of machines and workloads protected by DPM or MABS](./media/backup-architecture/architecture-dpm-mabs.png)
 

articles/backup/backup-azure-backup-cloud-as-tape.md

@@ -9,6 +9,7 @@ ms.date: 04/30/2017
 ms.author: dacurwin
 ---
 # Move your long-term storage from tape to the Azure cloud
+
 Azure Backup and System Center Data Protection Manager customers can:
 
 * Back up data in schedules which best suit the organizational needs.
@@ -18,6 +19,7 @@ Azure Backup and System Center Data Protection Manager customers can:
 This article explains how customers can enable backup and retention policies. Customers who use tapes to address their long-term-retention needs now have a powerful and viable alternative with the availability of this feature. The feature is enabled in the latest release of the Azure Backup (which is available [here](https://aka.ms/azurebackup_agent)). System Center DPM customers must update to, at least, DPM 2012 R2 UR5 before using DPM with the Azure Backup service.
 
 ## What is the Backup Schedule?
+
 The backup schedule indicates the frequency of the backup operation. For example, the settings in the following screen indicate that backups are taken daily at 6pm and at midnight.
 
 ![Daily Schedule](./media/backup-azure-backup-cloud-as-tape/dailybackupschedule.png)
@@ -27,13 +29,15 @@ Customers can also schedule a weekly backup. For example, the settings in the fo
 ![Weekly Schedule](./media/backup-azure-backup-cloud-as-tape/weeklybackupschedule.png)
 
 ## What is the Retention Policy?
+
 The retention policy specifies the duration for which the backup must be stored. Rather than just specifying a “flat policy” for all backup points, customers can specify different retention policies based on when the backup is taken. For example, the backup point taken daily, which serves as an operational recovery point, is preserved for 90 days. The backup point taken at the end of each quarter for audit purposes is preserved for a longer duration.
 
 ![Retention Policy](./media/backup-azure-backup-cloud-as-tape/retentionpolicy.png)
 
 The total number of “retention points” specified in this policy is 90 (daily points) + 40 (one each quarter for 10 years) = 130.
 
 ## Example – Putting both together
+
 ![Sample Screen](./media/backup-azure-backup-cloud-as-tape/samplescreen.png)
 
 1. **Daily retention policy**: Backups taken daily are stored for seven days.
@@ -55,11 +59,13 @@ The total number of recovery points is 56.
 >
 
 ## Advanced configuration
+
 By clicking **Modify** in the preceding screen, customers have further flexibility in specifying retention schedules.
 
 ![Modify](./media/backup-azure-backup-cloud-as-tape/modify.png)
 
 ## Next Steps
+
 For more information about Azure Backup, see:
 
 * [Introduction to Azure Backup](backup-introduction-to-azure-backup.md)