Skip to content

Commit ff3f50a

Browse files
Merge pull request #266911 from sooryar12/patch-15
Update backup-azure-backup-server-vmware.md
2 parents ded6d1d + 54d8e0b commit ff3f50a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/backup/backup-azure-backup-server-vmware.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -427,8 +427,10 @@ With earlier versions of MABS, parallel backups were performed only across prote
427427
428428
You can modify the number of jobs by using the registry key as shown below (not present by default, you need to add it):
429429
430-
**Key Path**: `Software\Microsoft\Microsoft Data Protection Manager\Configuration\ MaxParallelIncrementalJobs\VMware`<BR>
431-
**Key Type**: DWORD (32-bit) value.
430+
**Key Path**: `HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\ MaxParallelIncrementalJobs`<BR>
431+
**Key Type**: DWORD (32-bit) VMware.
432+
**Data**: number
433+
The value should be the number (decimal) of virtual machines that you select for parallel backup.
432434
433435
> [!NOTE]
434436
> 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.

0 commit comments

Comments
 (0)