1. Proposed title of this feature request

Ability to have multiple replicas of velero to make the backup, restore, delete processing run parallel and faster

2. What is the nature and description of the request?

Related case 03516835

Customer has velero schedules that run hourly.

There are 111 backup schedules on their cluster. (1 backup schedule, per 1 namespace - one-to-one mapping)

It takes about 1 minute to complete 1 backup. This means that it's taking close to 2 hours to complete all the backups (1 minute * 111 backups = 111 minutes).

This ends up creating a bottleneck. There are more backup requests that gets added each hour than it takes time to process all the backups.

It was mentioned on the above case that each velero task (i.e restore, backup, delete) runs on a single thread.

Given that this issue is a limitation on velero, it was suggested that we tackle this problem using a cron job.

i.e get rid of all the velero backup schedules, and create velero backups using a cron job to have greater flexibility to tackle the bottleneck situation.

Customer’s ask:

Requesting an enhancement request to have concurrency added to velero backups, and ability to have multiple replicas of velero to make the backup, restore, delete processing run parallel and faster.

3. Why does the customer need this? (List the business requirements here)

it's taking close to 2 hours to complete all the backups (1 minute * 111 backups = 111 minutes). Need faster solution.

4. List any affected packages or components.

velero