You use datastores as the source for your backup jobs. Some VM backups are consuming too much repository disk space. They have backup files created by multiple backup jobs. What could be the reason? (Choose two.)
You use datastores as the source for your backup jobs. Some VM backups are consuming too much repository disk space. They have backup files created by multiple backup jobs. What could be the reason? (Choose two.)
When VMs are moved to different datastores, either by VMware Storage DRS (Distributed Resource Scheduler) or manually, it can cause the backup jobs to treat these as new VMs, leading to additional full backups being created. This is because the backup software may not recognize the VMs as the same ones if they have been relocated, thus increasing the amount of repository disk space consumed.
It think A & E
why? does a datastore change on the hypervisor force a new full or something (cbt)? https://forums.veeam.com/vmware-vsphere-f24/vmware-frequently-asked-questions-t9329.html#p39946
i think the idea is that many VM are copied, manually (E) or automatically (A) to the datastore source of the backups. that's why there are many jobs and backups there
A. seems nonsense. If moved they would give errors and not copy. B. is true. Per VM jobs occupy more space because they do not deduplicate blocks of the vm's. C. could be true D. no information to be found Googling this E. if moved they would not be copied anymore, give errors and not ocupy more space. I'd select B &C.
why B) per-vm "need more fulls" -> i cannot find any documentation about such an behaviour - can u give a link?
"per-vm "need more fulls" " No, it has nothing to do with more fulls. Per-VM needs more space since deduplication is not so good, as in one Job.
I think BC is correct
correct is AE
AE because of "You use datastores as the source for your backup jobs"
correct is AE
AE is correct