Skip to content

Commit f0340a6

Browse files
sseagokaovilai
andauthored
Update site/content/docs/main/customize-installation.md
Co-authored-by: Tiger Kaovilai <passawit.kaovilai@gmail.com> Signed-off-by: Scott Seago <sseago@redhat.com>
1 parent 21f36b0 commit f0340a6

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

site/content/docs/main/customize-installation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -346,7 +346,7 @@ you may need to instruct Velero to trust that certificate. See [use Velero with
346346

347347
By default, only one backup is processed in the `InProgress` phase at a time. The install flag `concurrent-backups`, which takes an integer argument, configures Velero to process multiple backups at the same time, up to a max of `concurrent-backups`. The other restriction on parallel backup processing is that two backups which have any included namespaces in common may not run at the same time. For example, if `concurrent-backups` is set to 2 and two backups for "namespace1" are submitted at the same time, only one of those will be processed at the same time. On the other hand, if a backup for "namespace1" and another for "namespace2" are submitted, then both can be processed in parallel. Note that a whole-cluster backup (one which does not restrict to a set list of namespaces) includes all namespaces, and therefore it will not run in parallel with any other backup.
348348

349-
Enabling parallel backups can provide a significant performance benefit for backups which contain a large number of kubernetes resources or ones which contain a large number of smaller volumes. Backups dominated by large volumes will not see as much benefit, since the majority of time for those backups is spent waiting for the async phase to complete. A larger `concurrent-backups` configuration may require additional memory and CPU resources for the velero container.
349+
Enabling parallel backups can provide a significant performance benefit for backups which contain a large number of Kubernetes resources or ones which contain a large number of smaller volumes. Backups dominated by large volumes will not see as much benefit, since the majority of time for those backups is spent waiting for the async phase to complete. A larger `concurrent-backups` configuration may require additional memory and CPU resources for the velero container.
350350

351351
## Additional options
352352

0 commit comments

Comments
 (0)