addressed pre-review inputs

Author: AbhishekMallick-MS

articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent.md

@@ -25,7 +25,7 @@ To configure backup for a new Azure VM with agentless multi-disk crash-consisten
 
 3. Select **OK**.
 
-## Move a VM from application/file-system-consistent to crash-consistent backup.
+## Move a VM from application/file-system-consistent to crash-consistent backup
 
 If you have VMs backed up with Enhanced Policy, you can move them from agent based application/file-system-consistent backups to agentless crash-consistent backups by:
 

articles/backup/backup-azure-vms-introduction.md

@@ -13,7 +13,7 @@ This article describes how the [Azure Backup service](./backup-overview.md) back
 
 Azure Backup provides independent and isolated backups to guard against unintended destruction of the data on your VMs. Backups are stored in a Recovery Services vault with built-in management of recovery points. Configuration and scaling are simple, backups are optimized, and you can easily restore as needed.
 
-As part of the backup process, a [snapshot is taken](#snapshot-creation), and the data is transferred to the Recovery Services vault with no impact on production workloads. The snapshot provides different levels of consistency, as described [here](#snapshot-consistency). You can opt for an agent-based application consistent/file-consistent backups or an agentless crash consistent backup in the backup policy.
+As part of the backup process, a [snapshot is taken](#snapshot-creation), and the data is transferred to the Recovery Services vault with no impact on production workloads. The snapshot provides different levels of consistency, as described [here](#snapshot-consistency). You can opt for an agent-based application-consistent/file-consistent backup or an agentless crash-consistent backup in the backup policy.
 
 Azure Backup also has specialized offerings for database workloads like [SQL Server](backup-azure-sql-database.md) and [SAP HANA](sap-hana-db-about.md) that are workload-aware, offer 15 minute RPO (recovery point objective), and allow backup and restore of individual databases.
 
@@ -43,7 +43,7 @@ BEKs are also backed up. So, if the BEKs are lost, authorized users can restore
 Azure Backup takes snapshots according to the backup schedule.
 
 >[!Note]
->If you have opted for application or file-system consistent backups, the VM needs to have a backup extension installed to coordinate for the snapshot process. For *agentless multi-disk crash consistent* backups, the VM agent is not required for snapshots.
+>If you have opted for application or file-system consistent backups, the VM needs to have a backup extension installed to coordinate for the snapshot process. For *agentless multi-disk crash-consistent* backups, the VM agent is not required for snapshots.
 
 - **Windows VMs:** For Windows VMs, the Backup service coordinates with VSS to take an app-consistent snapshot of the VM disks.  By default, Azure Backup takes a full VSS backup (it truncates the logs of application such as SQL Server at the time of backup to get application level consistent backup).  If you're using a SQL Server database on Azure VM backup, then you can modify the setting to take a VSS Copy backup (to preserve logs). For more information, see [this article](./backup-azure-vms-troubleshoot.md#troubleshoot-vm-snapshot-issues).
 
@@ -61,7 +61,7 @@ The following table explains the different types of snapshot consistency:
 --- | --- | --- | ---
 **Application-consistent** | This is the default setting in the VM backup policy. App-consistent backups capture memory content and pending I/O operations. App-consistent snapshots use a VSS writer (or pre/post scripts for Linux) to ensure the consistency of the app data before a backup occurs. | When you're recovering a VM with an app-consistent snapshot, the VM boots up. There's no data corruption or loss. The apps start in a consistent state. | Windows: All VSS writers succeeded<br/><br/> Linux: Pre/post scripts are configured and succeeded
 **File-system consistent** | This is the default setting in the VM backup policy. File-system consistent backups provide consistency by taking a snapshot of all files at the same time.<br/><br/> | When you're recovering a VM with a file-system consistent snapshot, the VM boots up. There's no data corruption or loss. Apps need to implement their own "fix-up" mechanism to make sure that restored data is consistent. | Windows: Some VSS writers failed <br/><br/> Linux: Default (if pre/post scripts aren't configured or failed)
-**Crash-consistent** | Crash-consistent snapshot is an opt-in setting in the VM backup policy. Azure Backup also takes crash consistent backups if the VM is not running during backup and when application/file-consistent backups fail.   <br><br>   Only the data that already exists on the disk at the time of backup is captured and backed up. | Starts with the VM boot process followed by a disk check to fix corruption errors. Any in-memory data or write operations that weren't transferred to disk before the crash are lost. Apps implement their own data verification. For example, a database app can use its transaction log for verification. If the transaction log has entries that aren't in the database, the database software rolls transactions back until the data is consistent. | VM is in shutdown (stopped/ deallocated) state.
+**Crash-consistent** | Crash-consistent snapshot is an opt-in setting in the VM backup policy. Azure Backup also takes crash-consistent backups if the VM is not running during backup and when application/file-consistent backups fail.   <br><br>   Only the data that already exists on the disk at the time of backup is captured and backed up. | Starts with the VM boot process followed by a disk check to fix corruption errors. Any in-memory data or write operations that weren't transferred to disk before the crash are lost. Apps implement their own data verification. For example, a database app can use its transaction log for verification. If the transaction log has entries that aren't in the database, the database software rolls transactions back until the data is consistent. | VM is in shutdown (stopped/ deallocated) state.
 
 >[!NOTE]
 > If the provisioning state is **succeeded**, Azure Backup takes file-system consistent backups. If the provisioning state is **unavailable** or **failed**, crash-consistent backups are taken. If the provisioning state is **creating** or **deleting**, that means Azure Backup is retrying the operations.
@@ -73,7 +73,7 @@ The following table explains the different types of snapshot consistency:
 **Disk** | Backup of VM disks is parallel. For example, if a VM has four disks, the Backup service attempts to back up all four disks in parallel. Backup is incremental (only changed data).
 **Scheduling** |  To reduce backup traffic, back up different VMs at different times of the day and make sure the times don't overlap. Backing up VMs at the same time causes traffic jams.
 **Preparing backups** | Keep in mind the time needed to prepare the backup. The preparation time might include installing or updating the backup extension and triggering a snapshot according to the backup schedule.
-**Data transfer** | Consider the time needed for Azure Backup to identify the incremental changes from the previous backup.<br/><br/> In an incremental backup, Azure Backup determines the changes by calculating the checksum of the block. If a block is changed, it's marked for transfer to the vault. The service analyses the identified blocks to attempt to further minimize the amount of data to transfer. After the evaluation of all changed blocks is complete, Azure Backup transfers the changes to the vault.<br/><br/> There might be a lag between taking the snapshot and copying it to vault. At peak times, it can take up to eight hours for the snapshots to be transferred to the vault. The backup time for a VM will be less than 24 hours for the daily backup.
+**Data transfer** | Consider the time needed for Azure Backup to identify the incremental changes from the previous backup.<br/><br/> In an incremental backup, Azure Backup determines the changes by calculating the checksum of the block. If a block is changed, it's marked for transfer to the vault. The service analyzes the identified blocks to attempt to further minimize the amount of data to transfer. After the evaluation of all changed blocks is complete, Azure Backup transfers the changes to the vault.<br/><br/> There might be a lag between taking the snapshot and copying it to vault. At peak times, it can take up to eight hours for the snapshots to be transferred to the vault. The backup time for a VM will be less than 24 hours for the daily backup.
 **Initial backup** | The total backup time for incremental backups is less than 24 hours, which might not be the case for the first backup. The time needed for the initial backup will depend on the size of the data and when the backup is processed.
 **Restore queue** | Azure Backup processes restore jobs from multiple storage accounts at the same time, and it puts restore requests in a queue.
 **Restore copy** | During the restore process, data is copied from the vault to the storage account.<br/><br/> The total restore time depends on the I/O operations per second (IOPS) and the throughput of the storage account.<br/><br/> To reduce the copy time, select a storage account that isn't loaded with other application writes and reads.
@@ -118,7 +118,7 @@ Billing for a specified VM stops only if the protection is stopped and all backu
 If you have opted for agent-based application consistent or file-system consistent backups, the protected-instance size calculation is based on the *actual* size of the VM. The VM's size is the sum of all the data in the VM, excluding the temporary storage. Pricing is based on the actual data that's stored on the data disks, not on the maximum supported size for each data disk that's attached to the VM.
 
 >[!Note]
->For [agentless crash consistent backups](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md), you're currently charged for 0.5 protected instance (PI) per VM during preview.
+>For [agentless crash-consistent backups](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md), you're currently charged for 0.5 protected instance (PI) per VM during preview.
 
 Similarly, the backup storage bill is based on the amount of data that's stored in Azure Backup, which is the sum of the actual data in each recovery point.
 

articles/backup/backup-support-matrix-iaas.md

@@ -60,7 +60,7 @@ The following table summarizes the supported operating systems when you're backi
 **Scenario** | **OS support**
 --- | ---
 Back up with the Azure VM agent extension for application-consistent backup | - Windows 11 client (64 bit only) <br/><br/> - Windows 10 client (64 bit only) <br/><br/>- Windows Server 2022 (Datacenter, Datacenter Core, and Standard)   <br/><br/>- Windows Server 2019 (Datacenter, Datacenter Core, and Standard) <br/><br/> - Windows Server 2016 (Datacenter, Datacenter Core, and Standard) <br/><br/> - Windows Server 2012 R2 (Datacenter and Standard) <br/><br/> - Windows Server 2012 (Datacenter and Standard) <br/><br/> - Windows Server 2008 R2 (RTM and SP1 Standard)  <br/><br/> - Windows Server 2008 (64 bit only) <br><br> Note that *32 bit Operating Systems* aren't supported.
-[Back up Azure VM directly using agentless crash-consistent backup]() | Agentless crash-consistent backups are operating system agnostic. 
+[Back up Azure VM directly using agentless crash-consistent backup](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md) | Agentless crash-consistent backups are operating system agnostic. 
 Back up with the MARS agent | [Supported](backup-support-matrix-mars-agent.md#supported-operating-systems) operating systems
 Back up with DPM or MABS | Supported operating systems for backup with [MABS](backup-mabs-protection-matrix.md) and [DPM](/system-center/dpm/dpm-protection-matrix)
 
@@ -71,15 +71,15 @@ Here's what's supported if you want to back up Linux machines.
 **Action** | **Support**
 --- | ---
 Back up Linux Azure VMs with the Linux Azure VM agent | Supported for file-consistent backup.<br/><br/> Also supported for app-consistent backup that uses [custom scripts](backup-azure-linux-app-consistent.md).<br/><br/> During restore, you can create a new VM, restore a disk and use it to create a VM, or restore a disk and use it to replace a disk on an existing VM. You can also restore individual files and folders.
-[Back up Azure VM directly by using agentless crash-consistent backup]() | Agentless crash-consistent backups are operating system agnostic.
+[Back up Azure VM directly by using agentless crash-consistent backup](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md) | Agentless crash-consistent backups are operating system agnostic.
 Back up Linux Azure VMs with the MARS agent | Not supported.<br/><br/> The MARS agent can be installed only on Windows machines.
 Back up Linux Azure VMs with DPM or MABS | Not supported.
 Back up Linux Azure VMs with Docker mount points | Currently, Azure Backup doesn't support exclusion of Docker mount points because these are mounted at different paths every time.
 Backup Linux Azure VMs with ZFS Pool Configuration | Not supported
 
 ## Operating system support (Linux)
 
-For Linux VM backups by using the Linux Azure VM agent, Azure Backup supports the list of [Linux distributions endorsed by Azure](../virtual-machines/linux/endorsed-distros.md). Note the following:
+For Linux VM backups using the Linux Azure VM agent, Azure Backup supports the list of [Linux distributions endorsed by Azure](../virtual-machines/linux/endorsed-distros.md). Note the following:
 
 - Agent-based VM backup doesn't support CoreOS Linux.
 - Agent-based VM backup doesn't support 32-bit operating systems.

articles/backup/backup-support-matrix.md

@@ -65,7 +65,7 @@ The following table lists the supported scenarios for backup of Azure VMs:
 
 **Machine** | **What's backed up** | **Location** | **Features**
 --- | --- | --- | ---
-**Azure VM backup by using VM extension** <br > or **by using agentless crash consistent backup** | Entire VM | Back up to vault. | Supports both agent-based and agentless backups.  <br/><br/> Back up multiple times a day.<br/><br/> App-aware backup for Windows VMs; file-consistent backup for Linux VMs. You can configure app-consistency for Linux machines by using custom scripts.   <br><br> You can also opt for agentless crash consistent backups for Windows or Linux. [Learn more](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md).     <br/><br/> Restore VM or disk.<br/><br/>[Backup and restore of Active Directory domain controllers](active-directory-backup-restore.md) is supported.<br><br> Can't back up an Azure VM to an on-premises location.
+**Azure VM backup by using VM extension** <br > or **by using agentless crash-consistent backup** | Entire VM | Back up to vault. | Supports both agent-based and agentless backups.  <br/><br/> Back up multiple times a day.<br/><br/> App-aware backup for Windows VMs; file-consistent backup for Linux VMs. You can configure app-consistency for Linux machines by using custom scripts.   <br><br> You can also opt for agentless crash-consistent backups for Windows or Linux. [Learn more](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md).     <br/><br/> Restore VM or disk.<br/><br/>[Backup and restore of Active Directory domain controllers](active-directory-backup-restore.md) is supported.<br><br> Can't back up an Azure VM to an on-premises location.
 **Azure VM backup by using MARS agent** | - Files, folders <br><br> - System state | Back up to vault. | - Back up three times a day. <br><br> - Back up once a day. <br/><br/> If you want to back up specific files or folders rather than the entire VM, the MARS agent can run alongside the VM extension.
 **Azure VM with DPM** | Files, folders, volumes, system state, app data | Back up to local storage of Azure VM that's running DPM. DPM then backs up to vault. | App-aware snapshots.<br/><br/> Full granularity for backup and recovery.<br/><br/> Linux supported for VMs (Hyper-V/VMware).<br/><br/> Oracle not supported.
 **Azure VM with MABS** | Files, folders, volumes, system state, app data | Back up to local storage of Azure VM that's running MABS. MABS then backs up to the vault. | App-aware snapshots.<br/><br/> Full granularity for backup and recovery.<br/><br/> Linux supported for VMs (Hyper-V/VMware).<br/><br/> Oracle not supported.

articles/backup/toc.yml

@@ -174,7 +174,7 @@
     items:
     - name: Overview
       href: backup-azure-vms-introduction.md
-    - name: Agentless multi-disk crash consistent VM backup
+    - name: Agentless multi-disk crash-consistent VM backup
       href: backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md
   - name: SAP HANA database on Azure VM backup
     items:
@@ -262,7 +262,7 @@
         href: backup-during-vm-creation.md
       - name: Back up an Azure VM using Enhanced policy
         href: backup-azure-vms-enhanced-policy.md
-      - name: Back up Azure VM with agentless multi-disk crash consistent backup
+      - name: Back up Azure VM with agentless multi-disk crash-consistent backup
         href: backup-azure-vms-agentless-multi-disk-crash-consistent.md
       - name: Back up an Azure VM from VM settings
         href: backup-azure-vms-first-look-arm.md

articles/backup/whats-new.md

@@ -88,7 +88,7 @@ You can learn more about the new releases by bookmarking this page or by [subscr
 
 ## Agentless multi-disk crash-consistent backups for Azure VMs (preview)
 
-Azure Backup now supports agentless VM backups by using multi-disk crash consistent restore points (preview). Crash consistent backups are OS agnostic, do not require any agent, and quiesce VM I/O for a shorter period compared to application or file-system consistent backups for performance sensitive workloads.
+Azure Backup now supports agentless VM backups by using multi-disk crash-consistent restore points (preview). Crash consistent backups are OS agnostic, do not require any agent, and quiesce VM I/O for a shorter period compared to application or file-system consistent backups for performance sensitive workloads.
 
 For more information, see [About agentless multi-disk crash-consistent backup for Azure VMs (preview)](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md).
 

includes/azure-vm-backup-process.md

@@ -10,7 +10,7 @@ ms.author: v-amallick
 1. If you have opted for application or file-system consistent backups, the VM needs to have a backup extension installed to coordinate for the snapshot process.
 
    >[!Note]
-   >If you have opted for crash consistent backups, no agents are required in the VMs.
+   >If you have opted for crash-consistent backups, no agents are required in the VMs.
 
 1. During the first backup, a backup extension is installed on the VM if the VM is running.
     - For Windows VMs, the [VMSnapshot extension](../articles/virtual-machines/extensions/vmsnapshot-windows.md) is installed.