Back up multiple VMs at the same time with one data mover node.
In previous versions of Data Protection for VMware, backups were processed serially: each data mover node processed only one VM backup at a time. To back up VMs in parallel, multiple data mover nodes must be created.
- vmmaxparallel
- This option controls the number of overall VMs that are allowed to be backed up at a single time. This option works in concert with vmlimitperhost and vmlimitperdatastore. The default value is 1. The maximum value is 50. The minimum value is 1.
- vmlimitperhost
- This option limits how many VMs are backed up from a single ESX or ESXi host at the same time. The maximum value is 50. The minimum value is 1.
- vmlimitperdatastore
- This option limits the maximum number of VMs that are backed up at the same time for a single data store. The maximum value is 50. The minimum value is 1. When VMs contain data that is distributed across multiple data stores, the vmlimitperdatastore value is applied to each of the distributed data stores. For example, when a VM contains data that is distributed between datastore_1 and datastore_2, the vmlimitperdatastore value is applied to both data stores until that VM backup is complete.
Parallel backup scenario
In this scenario, the Data Protection for VMware 6.3 environment contains 2 ESX hosts. Each host contains 6 VM guests that are connected to three data stores. Three scheduled backup operations run every night. Each schedule has its own instance (data mover node) that is configured to process one of the three schedules. Each schedule targets VM guests that use the same data store. By using this method, parallel backups are run without causing contention among the three data stores. At any moment, 3 VMs are backed up that do not share a data store.
vmmaxparallel 3
vmlimitperdatastore 1
vmlimitperhost 0