So, today I’m gonna show you a simple comparison with 1 VM per job versus 2 or more VM per jobs.
On my scenario I have 2 VM for my Active Directory environment with 40GB size each.
----------------------------------------------------------------------------------------------------------------------------
So, in first example I create 1 job per VM:
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/71fb1ed8-6cd5-4fe0-868d-7764200397fb.png)
In this shape it consume exactly 40GB on my repository:
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/5f2c2c72-fb5a-45b3-b973-78a9110d15e3.png)
----------------------------------------------------------------------------------------------------------------------------
In the second example a create a unique job for the same 2 VM’s:
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/17a3e3cf-a5a0-4a01-92e2-4cbbe28df04b.png)
And in this shape it consume 37GB on my repository:
![](https://uploads-eu-west-1.insided.com/veeam-en/attachment/bbf84fd8-ee8e-4fd2-82cf-e377f6923914.png)
----------------------------------------------------------------------------------------------------------------------------
How can we see deduplication of Veeam B&R gives a good space on our backups.
In this environment was only 2 small VMs, but now you can imagine how this impact an entire datacenter.