Skip to content

Commit 7ffc189

Browse files
authored
Merge pull request #219584 from v-amallick/Nov-27-2022-QS
QS - Freshness updates
2 parents 8670319 + fe72638 commit 7ffc189

File tree

1 file changed

+38
-21
lines changed

1 file changed

+38
-21
lines changed

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

Lines changed: 38 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -2,44 +2,58 @@
22
title: About the MARS Agent
33
description: Learn how the MARS Agent supports the backup scenarios
44
ms.topic: conceptual
5-
ms.date: 08/04/2020
5+
ms.date: 11/28/2022
6+
author: v-amallick
7+
ms.service: backup
8+
ms.author: v-amallick
9+
ms.custom: engagement-fy23
610
---
711

8-
# About the Microsoft Azure Recovery Services (MARS) agent
12+
# About the Microsoft Azure Recovery Services (MARS) agent for Azure Backup
913

10-
This article describes how the Azure Backup service uses the Microsoft Azure Recovery Services (MARS) agent to back up and restore files, folders, and the volume or system state from an on-premises computer to Azure.
14+
Azure Backup uses the Microsoft Azure Recovery Services (MARS) agent to back up and recover files, folders, and the volume or system state from an on-premises computer to Azure.
15+
16+
In this article, you'll learn about:
17+
18+
> [!div class="checklist"]
19+
> - Backup scenarios
20+
> - Recovery scenarios
21+
> - Backup process
1122
1223
## Backup scenarios
1324

1425
The MARS agent supports the following backup scenarios:
1526

16-
![MARS backup scenarios](./media/backup-try-azure-backup-in-10-mins/backup-scenarios.png)
27+
![Diagram shows the MARS backup scenarios.](./media/backup-try-azure-backup-in-10-mins/backup-scenarios.png)
1728

18-
- **Files and Folders**: Selectively protect Windows files and folders.
19-
- **Volume Level**: Protect an entire Windows volume of your machine.
20-
- **System Level**: Protect an entire Windows system state.
29+
| Scenarios | Description |
30+
| --- | --- |
31+
| **Files and Folders** | Selectively protect Windows files and folders. |
32+
| **Volume Level** | Protect an entire Windows volume of your machine. |
33+
| **System Level** | Protect an entire Windows system state. |
2134

2235
### Additional scenarios
2336

2437
- **Back up specific files and folders within Azure virtual machines**: The primary method for backing up Azure virtual machines (VMs) is to use an Azure Backup extension on the VM. The extension backs up the entire VM. If you want to back up specific files and folders within a VM, you can install the MARS agent in the Azure VMs. For more information, see [Architecture: Built-in Azure VM Backup](./backup-architecture.md#architecture-built-in-azure-vm-backup).
2538

2639
- **Offline seeding**: Initial full backups of data to Azure typically transfer large amounts of data and require more network bandwidth. Subsequent backups transfer only the delta, or incremental, amount of data. Azure Backup compresses the initial backups. Through the process of *offline seeding*, Azure Backup can use disks to upload the compressed initial backup data offline to Azure. For more information, see [Azure Backup offline-backup using Azure Data Box](offline-backup-azure-data-box.md).
2740

28-
## Restore scenarios
29-
30-
The MARS agent supports the following restore scenarios:
41+
## Recovery scenarios
3142

32-
![MARS recovery scenarios](./media/backup-try-azure-backup-in-10-mins/restore-scenarios.png)
43+
The MARS agent supports the following recovery scenarios:
3344

34-
- **Same Server**: The server on which the backup was originally created.
35-
- **Files and Folders**: Choose the individual files and folders that you want to restore.
36-
- **Volume Level**: Choose the volume and recovery point that you want to restore. Then restore it to the same location or an alternate location on the same machine. Create a copy of existing files, overwrite existing files, or skip recovering existing files.
37-
- **System Level**: Choose the system state and recovery point to restore to the same machine at a specified location.
45+
![Diagram shows the MARS recovery scenarios.](./media/backup-try-azure-backup-in-10-mins/restore-scenarios.png)
3846

39-
- **Alternate Server**: A server other than the server where the backup was taken.
40-
- **Files and Folders**: Choose the individual files and folders whose recovery point you want to restore to a target machine.
41-
- **Volume Level**: Choose the volume and recovery point that you want to restore to another location. Create a copy of existing files, overwrite existing files, or skip recovering existing files.
42-
- **System Level**: Choose the system state and recovery point to restore as a System State file to an alternate machine.
47+
| Server | Recovery scenario | Description |
48+
| --- | --- | --- |
49+
| **Same Server** | | The server on which the backup was originally created. |
50+
| | **Files and Folders** | Choose the individual files and folders that you want to restore. |
51+
| | **Volume Level** | Choose the volume and recovery point that you want to restore, and then restore it to the same location or an alternate location on the same machine. Create a copy of existing files, overwrite existing files, or skip recovering existing files. |
52+
| | **System Level** | Choose the system state and recovery point to restore to the same machine at a specified location. |
53+
| **Alternate Server** | | A server other than the server where the backup was taken. |
54+
| | **Files and Folders** | Choose the individual files and folders whose recovery point you want to restore to a target machine. |
55+
| | **Volume Level** | Choose the volume and recovery point that you want to restore to another location. Create a copy of existing files, overwrite existing files, or skip recovering existing files. |
56+
| | **System Level** | Choose the system state and recovery point to restore as a System State file to an alternate machine. |
4357

4458
## Backup process
4559

@@ -49,11 +63,14 @@ The MARS agent supports the following restore scenarios:
4963
3. [Install the agent](./install-mars-agent.md#install-and-register-the-agent) and use the downloaded vault credentials to register the machine to the Recovery Services vault.
5064
4. From the agent console on the client, [configure the backup](./backup-windows-with-mars-agent.md#create-a-backup-policy) to specify what to back up, when to back up (the schedule), how long the backups should be retained in Azure (the retention policy) and start protecting.
5165

52-
![Azure Backup agent diagram](./media/backup-try-azure-backup-in-10-mins/backup-process.png)
66+
67+
The following diagram shows the backup flow:
68+
69+
![Diagra shows the bacup flow of Azure Backup agent.](./media/backup-try-azure-backup-in-10-mins/backup-process.png)
5370

5471
### Additional information
5572

56-
- The **Initial Backup** (first backup) runs according to your backup settings. The MARS agent uses VSS to take a point-in-time snapshot of the volumes selected for backup. The agent only uses the Windows System Writer operation to capture the snapshot. It doesn't use any application VSS writers, and doesn't capture app-consistent snapshots. 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.
73+
- The **Initial Backup** (first backup) runs according to your backup settings. The MARS agent uses VSS to take a point-in-time snapshot of the volumes selected for backup. The agent only uses the Windows System Writer operation to capture the snapshot. It doesn't use any application VSS writers, and doesn't capture app-consistent snapshots. After VSS agent takes the snapshot, the MARS agent creates a virtual hard disk (VHD) in the cache folder you specified during the backup configuration. The agent also stores checksums for each data block.
5774

5875
- **Incremental backups** (subsequent backups) run according to the schedule you specify. During 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. 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.
5976

0 commit comments

Comments
 (0)