Specify number of tasks which can be performed concurrently on a datastore or physical host as per bandwidth and storage performance.

Max Backup Tasks per Datastore: Specifies number of concurrent backup tasks per datastore based on bandwidth and storage performance. Not applicable to backup tasks on virtual datastore.

Backup Copy Tasks per Datastore: Specifies number of concurrent backup copy tasks per datastore based on bandwidth and storage performance.

Archiving Tasks per Datastore:

Data Fetching Tasks per Node: Specifies number of data fetching tasks per node based on storage performance.

Max Backup Tasks per Node:

1. You can configure the maximum number of concurrent backup tasks per node. A higher value increases datastore I/O and requires more memory and CPU resources.
2. For each additional concurrent task, up to 256 MB of memory can be used per disk during VM backup.
3. If node resources are overloaded, lower the value to minimize resource usage.
4. If node resources are sufficient, increase the value to meet higher backup RPO requirements.

Merging Tasks per Datastore: For a virtual datastore, the maximum number of concurrent backup merging tasks should be the exact number of nodes involved in that datastore. However, the actual VM run location and storage IO may not allow this maximum number to be reached in some situations to ensure more reasonable resource scheduling.

VMs with Backup Health Check per Datastore: Concurrent backup health check tasks are allowed only for the specified number of VMs at most if their backups are stored on the same datastore.

Table: Max Concurrent Tasks