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/backup-azure-backup-server-vmware.md
+41-26Lines changed: 41 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ This article explains how to:
18
18
19
19
## Before you start
20
20
21
-
- Verify that you're running a version of vCenter/ESXi that's supported for backup - versions 6.5, 6.0, and 5.5.
21
+
- Verify that you're running a version of vCenter/ESXi that's supported for backup. Refer to the support matrix [here](https://docs.microsoft.com/azure/backup/backup-mabs-protection-matrix).
22
22
- Make sure you've set up Azure Backup Server. If you haven't, [do that](backup-azure-microsoft-azure-backup.md) before you start. You should be running Azure Backup Server with the latest updates.
23
23
24
24
## Create a secure connection to the vCenter Server
@@ -124,26 +124,41 @@ The Azure Backup Server needs a user account with permissions to access v-Center
|| Virtual Machine Contributor | Source VM that got backed up |
39
39
|| Storage Account Contributor | Storage account resource where disks are going to be restored |
40
-
| Restore managed disks from VM backup | Backup Operator | Recovery vault resource|
40
+
| Restore managed disks from VM backup | Backup Operator | Recovery Services vault|
41
41
|| Virtual Machine Contributor | Source VM that got backed up |
42
42
|| Storage Account Contributor | Temporary Storage account selected as part of restore to hold data from vault before converting them to managed disks |
43
43
|| Contributor | Resource group to which managed disk(s) will be restored |
44
-
| Restore individual files from VM backup | Backup Operator | Recovery vault resource|
44
+
| Restore individual files from VM backup | Backup Operator | Recovery Services vault|
45
45
|| Virtual Machine Contributor | Source VM that got backed up |
46
-
| Create backup policy for Azure VM backup | Backup Contributor | Recovery vault resource|
47
-
| Modify backup policy of Azure VM backup | Backup Contributor | Recovery vault resource|
48
-
| Delete backup policy of Azure VM backup | Backup Contributor | Recovery vault resource|
49
-
| Stop backup (with retain data or delete data) on VM backup | Backup Contributor | Recovery vault resource|
50
-
| Register on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Operator | Recovery vault resource|
51
-
| Delete registered on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Contributor | Recovery vault resource|
46
+
| Create backup policy for Azure VM backup | Backup Contributor | Recovery Services vault|
47
+
| Modify backup policy of Azure VM backup | Backup Contributor | Recovery Services vault|
48
+
| Delete backup policy of Azure VM backup | Backup Contributor | Recovery Services vault|
49
+
| Stop backup (with retain data or delete data) on VM backup | Backup Contributor | Recovery Services vault|
50
+
| Register on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Operator | Recovery Services vault|
51
+
| Delete registered on-premises Windows Server/client/SCDPM or Azure Backup Server | Backup Contributor | Recovery Services vault|
52
52
53
53
> [!IMPORTANT]
54
54
> If you specify VM Contributor at a VM resource scope and click on Backup as part of VM settings, it will open 'Enable Backup' screen even though VM is already backed up as the call to verify backup status works only at subscription level. To avoid this, either go to vault and open the backup item view of the VM or specify VM Contributor role at a subscription level.
0 commit comments