best backup scheme

[AlexL]

We have multiple hosts and multiple VM's per host, what would be the "best" way to create the backup jobs considering the following:

- every VM must be in the daily backup
- if a new VM is created or a VM is deleted NO reconfiguration of the jobs should be neccessary
- the backup window is roughly 11pm till 7am
- 1 job for the entire environment does not fit in the backup window
- concurrency must keep to acceptably levels due to IOPS considerations; running 30 jobs concurrent is not an option

We're using SAN mode (FC).

Any help much appreciated.

[Gostev]

Most customers choose to create jobs using VM folders (by grouping similar VMs together for better deduplication results), or using cluster (or higher level) objects. Then you create one job per folder (or cluster), and run them in parallel. This addresses all requirements stated above. Thanks!

[AlexL]

I'll have to think about the folder approach, currently we have things largerly grouped by customer and with 50+ customers this might mean 50+ jobs if I would go the 1 job per folder route, perhaps grouping multiple customer folders per job would work for us. Back to the drawing board... Thanks

[Gostev]

Yes, multiple folders per job would work well.
By the way, are you a hosting/cloud service provider?

[AlexL]

Yes, we are.

[Gostev]

Have you ever been in touch with our hosting/cloud team? If not, I am sure they would love to talk about your specifics needs as a service provider. They have been scoping functionality required around backup and management that is specific to service provider needs. If you don't mind talking with them, I can put you in contact - please let me know.

[AlexL]

I've spoken a few times with Diana Markova from Sales, never with the hosting/cloud team. They're free to contact me by email, please do not contact me by phone.