Use of Per-VM backup repository setting

[unsichtbarre]

I have a Veeam Backup server where one job has 53 VMs and a 5TB Full Backup. with 30-days retention and weekly synthetic full backups, this one job nearly fills up a 30TB Repository, and that's all the space on the device!

We'd like to switch to per-VM policy on the repository and eventually to scale-out repository.Here are the questions:

1. After we switch the repository to per-VM, do we have to manually do an active full to get per-VM to apply?
2. Will per-VM apply automatically after a weekly synthetic full that runs by default on Saturday?
3. If we switch the policy from weekly synthetic full to active-full, will per-VM apply after the automatic active full?
4. Will backups me more, equal or less space-efficient using a per-VM policy. eg: if the full backup is not 5TB for 53 VMs, will the aggregate of all 53 individual full VM backup files be more, equal or less on overall space?

THX

[foggy]

Hi John,

1. Yes.
2. No, see p.1.
3. Yes.
4. Per-VM backup chains do not provide deduplication between VMs, since each VM has its own backup chain, so you would need more space.

[unsichtbarre]

Thanks!

[unsichtbarre]

Another question: If we switch the local (incremental) backup repository to Per-VM, how will that impact the backup copy jobs to an offsite repository?

[foggy]

Backup copy jobs will not be affected (they will have to read from more files but mot likely you will hardly notice the difference).