backup policies in Veeam

[rtheseeker]

- do we have the concept of policies in Veeam backup and replication world or is it all manual when creating a job
- policies do not exist as sperate object and can be asisgned to jobs
- say if you have hundreds of job how are you going to assign those to a certain policy say like some other products

[Gostev]

Veeam jobs are like policies because normally you set them to use a dynamic scope (most people use VM tags for this, some VM folders or other objects) so you never have to manage their content manually. Plus, with Veeam you don't need "hundreds" of jobs because these days they scale to thousands machines in each.

You can also transparently move VMs from one job to another, like you would with a policy-based approach. Disable individual VMs from processing, trigger individual VM backups w/out running the whole job etc. So all the flexibility of policy-based approach remains.

So basically Veeam jobs provide the best combination of both worlds these days. Instead of creating 5-10 policies, you create 5-10 jobs at Veeam. Thanks to them being jobs you get to maintain more control over execution and when they start/run, which is not usually not possible with policies. Yet you get all the flexibility of policies too as it comes to assigning VM to policies or moving VMs between them.