Of course it is possible that even temp snapshots will fill a datastore - no matter how they are created.
However, like for the 'normal' backups clients, you can create groups and workflows and select the VMs like clients. The principle is pretty similar - only the way to select them is a bit different. And in your case, it would make sense to organize them 'per datastore'.
Not sure if you have considered this already but you would need room on your datastore to deploy the vProxy hosts as well. As @bingo.1 mentioned, group the VM's that belong to one Data store to one workflow and keep the parallelism as minimum as you would want it to be.
bingo.1
2.4K Posts
0
August 19th, 2019 07:00
Of course it is possible that even temp snapshots will fill a datastore - no matter how they are created.
However, like for the 'normal' backups clients, you can create groups and workflows and select the VMs like clients. The principle is pretty similar - only the way to select them is a bit different. And in your case, it would make sense to organize them 'per datastore'.
crazyrov
4 Operator
•
1.3K Posts
0
August 19th, 2019 08:00
Not sure if you have considered this already but you would need room on your datastore to deploy the vProxy hosts as well. As @bingo.1 mentioned, group the VM's that belong to one Data store to one workflow and keep the parallelism as minimum as you would want it to be.