You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/back-up-hyper-v-virtual-machines-mabs.md
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Back up Hyper-V virtual machines with MABS
3
3
description: This article contains the procedures for backing up and recovery of virtual machines using Microsoft Azure Backup Server (MABS).
4
4
ms.topic: how-to
5
-
ms.date: 01/16/2023
5
+
ms.date: 03/01/2023
6
6
author: jyothisuri
7
7
ms.author: jsuri
8
8
ms.service: backup
@@ -161,12 +161,14 @@ To open the Recovery Wizard and recover a virtual machine, follow these steps:
161
161
162
162
## Restore an individual file from a Hyper-V VM
163
163
164
-
You can restore individual files from a protected Hyper-V VM recovery point. This feature is only available for Windows Server VMs. Restoring individual files is similar to restoring the entire VM, except you browse into the VMDK and find the file(s) you want, before starting the recovery process.
164
+
You can restore individual files from a protected Hyper-V VM recovery point, both disk and online. This feature is only available for Windows Server VMs. Restoring individual files is similar to restoring the entire VM, except you browse into the VMDK and find the file(s) you want, before starting the recovery process.
165
165
166
166
To recover an individual file or select files from a Windows Server VM, follow these steps:
167
167
168
168
>[!Note]
169
-
>Restoring an individual file from a Hyper-V VM is available only for Windows VM and Disk Recovery Points.
169
+
> With MABS v4 and later, you can restore an individual file from a Hyper-V VM from both disk and online recovery points. The VM should be a Windows Server VM.
170
+
>
171
+
> Additionally, for item-level recovery from an online recovery point, ensure that the Hyper-V role is installed on the MABS Server, automatic mounting of volumes is enabled, and the VM VHD doesn't contain a dynamic disk. The item-level recovery for online recovery points works by mounting the VM recovery point using *iSCSI* for browsing, and only one VM can be mounted at a given time.
170
172
171
173
1. On the MABS Administrator Console, select **Recovery** view.
172
174
@@ -176,7 +178,11 @@ To recover an individual file or select files from a Windows Server VM, follow t
176
178
177
179
1. On the **Recovery Points for** pane, use the calendar to select the date that contains the desired recovery point(s). Depending on how the backup policy has been configured, dates can have more than one recovery point. Once you've selected the day when the recovery point was taken, make sure you've chosen the correct **Recovery time**. If the selected date has multiple recovery points, choose your recovery point by selecting it in the Recovery time drop-down menu. Once you chose the recovery point, the list of recoverable items appears in the Path pane.
178
180
179
-
1. To find the files you want to recover, in the **Path** pane, double-click the item in the Recoverable item column to open it. Select the file, files, or folders you want to recover. To select multiple items, press the **Ctrl** key while selecting each item. Use the **Path** pane to search the list of files or folders appearing in the **Recoverable Item** column.**Search list below** doesn't search into subfolders. To search through subfolders, double-click the folder. Use the Up button to move from a child folder into the parent folder. You can select multiple items (files and folders), but they must be in the same parent folder. You can't recover items from multiple folders in the same recovery job.
181
+
1. To find the files you want to recover, in the **Path** pane, double-click the item in the Recoverable item column to open it.
182
+
183
+
If you use an online recovery point, wait until the recovery point is mounted. Once the mount is complete, select the *VM*, *VHD disk*, and the *volume* you want to restore until the files and folders are listed.
184
+
185
+
Select the file, files, or folders you want to recover. To select multiple items, press the **Ctrl** key while selecting each item. Use the **Path** pane to search the list of files or folders appearing in the **Recoverable Item** column.**Search list below** doesn't search into subfolders. To search through subfolders, double-click the folder. Use the Up button to move from a child folder into the parent folder. You can select multiple items (files and folders), but they must be in the same parent folder. You can't recover items from multiple folders in the same recovery job.
180
186
181
187

182
188
@@ -194,6 +200,15 @@ To recover an individual file or select files from a Windows Server VM, follow t
194
200
195
201
1. On the **Summary** screen, review your settings and select **Recover** to start the recovery process. The **Recovery status** screen shows the progression of the recovery operation.
196
202
203
+
>[!Tip]
204
+
>You can perform item-level restore of online recovery points for Hyper-V VMs running Windows also from *Add external DPM Server* to recover VM files and folders quickly.
205
+
206
+
>[!Note]
207
+
>By default, *eight parallel recoveries* are supported. You can increase the number of parallel restore jobs by adding the following registry key:
208
+
>**Key Path**: `HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\ MaxParallelRecoveryJobs`
209
+
>-**32 Bit DWORD**: HyperV
210
+
>-**Data**: `<number>`
211
+
197
212
## Next steps
198
213
199
214
[Recover data from Azure Backup Server](./backup-azure-alternate-dpm-server.md)
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-backup-server-vmware.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Back up VMware VMs with Azure Backup Server
3
3
description: In this article, learn how to use Azure Backup Server to back up VMware VMs running on a VMware vCenter/ESXi server.
4
4
ms.topic: how-to
5
-
ms.date: 01/18/2023
5
+
ms.date: 03/03/2023
6
6
author: jyothisuri
7
7
ms.author: jsuri
8
8
ms.service: backup
@@ -12,9 +12,6 @@ ms.custom: engagement-fy23
12
12
13
13
This article describes how to back up VMware VMs running on VMware ESXi hosts/vCenter Server to Azure using Azure Backup Server (MABS).
14
14
15
-
>[!Note]
16
-
>With MABS v3 Update Rollup 2 release, you can now back up VMware 7.0 VMs as well.
17
-
18
15
## VMware VM protection workflow
19
16
20
17
To protect VMware VM using Azure Backup you need to:
@@ -45,6 +42,7 @@ MABS provides the following features when backing up VMware virtual machines:
45
42
46
43
| MABS versions | Supported VMware VM versions for backup |
47
44
| --- | --- |
45
+
| MABS v4 | VMware server 8.0, 7.0, 6.7, or 6.5 (Licensed version) |
48
46
| MABS v3 UR2 | VMware server 7.0, 6.7, 6.5, or 6.0 (Licensed Version) |
49
47
| MABS v3 UR1 | VMware server 6.7, 6.5, 6.0, or 5.5 (Licensed Version) |
50
48
@@ -60,6 +58,7 @@ Before you start backing up a VMware virtual machine, review the following list
60
58
- MABS can't protect VMware VMs with pass-through disks and physical raw device mappings (pRDM).
61
59
- MABS can't detect or protect VMware vApps.
62
60
- MABS can't protect VMware VMs with existing snapshots.
61
+
- MABS v4 doesn't support the *DataSets* feature for VMware 8.0.
63
62
64
63
## Before you start
65
64
@@ -435,9 +434,9 @@ You can modify the number of jobs by using the registry key as shown below (not
435
434
> [!NOTE]
436
435
> You can modify the number of jobs to a higher value. If you set the jobs number to 1, replication jobs run serially. To increase the number to a higher value, you must consider the VMware performance. Consider the number of resources in use and additional usage required on VMWare vSphere Server, and determine the number of delta replication jobs to run in parallel. Also, this change will affect only the newly created protection groups. For existing protection groups you must temporarily add another VM to the protection group. This should update the protection group configuration accordingly. You can remove this VM from the protection group after the procedure is completed.
437
436
438
-
## VMware vSphere 6.7and 7.0
437
+
## VMware vSphere 6.7, 7.0, and 8.0
439
438
440
-
To back up vSphere 6.7and 7.0, follow these steps:
439
+
To back up vSphere 6.7, 7.0, and 8.0, follow these steps:
441
440
442
441
- Enable TLS 1.2 on the MABS Server
443
442
@@ -470,9 +469,6 @@ Windows Registry Editor Version 5.00
470
469
471
470
With MABS V3 UR1 (and later), you can exclude the specific disk from VMware VM backup. The configuration script **ExcludeDisk.ps1** is located in the `C:\Program Files\Microsoft Azure Backup Server\DPM\DPM\bin folder`.
472
471
473
-
> [!NOTE]
474
-
> This feature is applicable for MABS V3 UR1 (and later).
475
-
476
472
To configure the disk exclusion, follow these steps:
477
473
478
474
### Identify the VMware VM and disk details to be excluded
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-sql-mabs.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Back up SQL Server by using Azure Backup Server
3
3
description: In this article, learn the configuration to back up SQL Server databases by using Microsoft Azure Backup Server (MABS).
4
4
ms.topic: how-to
5
-
ms.date: 01/16/2023
5
+
ms.date: 03/01/2023
6
6
author: jyothisuri
7
7
ms.author: jsuri
8
8
ms.service: backup
@@ -20,7 +20,7 @@ Microsoft Azure Backup Server (MABS) provides backup and recovery for SQL Server
20
20
21
21
## Supported scenarios
22
22
23
-
- MABS v3 UR2 supports SQL Server Failover Cluster Instance (FCI) using Cluster Shared Volume (CSV).
23
+
- MABS v3 UR2, MABS v4, or later supports SQL Server Failover Cluster Instance (FCI) using Cluster Shared Volume (CSV).
24
24
- Protection of SQL Server FCI with Storage Spaces Direct on Azure, and SQL Server FCI with Azure shared disks is supported with this feature. The DPM server must be deployed in the Azure Virtual Machine to protect the SQL FCI instance, deployed on the Azure VMs.
25
25
- A SQL Server Always On availability group with theses preferences:
26
26
- Prefer Secondary
@@ -99,9 +99,8 @@ To protect SQL Server databases in Azure, first create a backup policy:
99
99
100
100

101
101
102
-
By default, MABS creates one volume per data source (SQL Server database). The volume is used for the initial backup copy. In this configuration, Logical Disk Manager (LDM) limits MABS protection to 300 data sources (SQL Server databases). To work around this limitation, select **Co-locate data in DPM Storage Pool**. If you use this option, MABS uses a single volume for multiple data sources. This setup allows MABS to protect up to 2,000 SQL Server databases.
103
-
104
-
If you select **Automatically grow the volumes**, then MABS can account for the increased backup volume as the production data grows. If you don't select **Automatically grow the volumes**, then MABS limits the backup storage to the data sources in the protection group.
102
+
*Total data size* is the size of the data you want to back up, and disk space to be provisioned on DPM is the space that MABS recommends for the protection group. DPM 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. The edits change the values for *Total Storage* and *Free Storage* in the **Available Disk Storage** pane. *Underprovisioned space* is the amount of storage that DPM suggests you add to the volume for continuous smooth backups.
103
+
105
104
1. If you're an administrator, you can choose to transfer this initial backup **Automatically over the network** and choose the time of transfer. Or choose to **Manually** transfer the backup. Then select **Next**.
106
105
107
106

0 commit comments