From 84571bc54de22e4d67c1004d8a2dd75df283c573 Mon Sep 17 00:00:00 2001 From: Scott Seago Date: Thu, 13 Nov 2025 14:51:38 -0500 Subject: [PATCH] Added doc note around parallel backups and resource limits Signed-off-by: Scott Seago --- site/content/docs/main/customize-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/docs/main/customize-installation.md b/site/content/docs/main/customize-installation.md index d62945a35..7c1274ebf 100644 --- a/site/content/docs/main/customize-installation.md +++ b/site/content/docs/main/customize-installation.md @@ -158,7 +158,7 @@ At installation, You could set resource requests and limits for the Velero pod, |Memory limit|512Mi|N/A| {{< /table >}} -For Velero pod, through testing, the Velero maintainers have found these defaults work well when backing up and restoring 1000 or less resources. +For Velero pod, through testing, the Velero maintainers have found these defaults work well when backing up and restoring 1000 or less resources. If you are enabling concurrent backups and your backups tend to be large, you may need to increase these limits. For node-agent pod, by default it doesn't have CPU/memory request/limit, so that the backups/restores won't break due to resource throttling. The Velero maintainers have also done some [Performance Tests][13] to show the relationship of CPU/memory usage and the scale of data being backed up/restored. For repository maintenance job, it's no limit on resources by default. You could configure the job resource limitation based on target data to be backed up, some further settings please refer to [repository maintenance job][14].