pkelly_sts wrote:so there would be a big .VIB for the day you added the extra VMs, until that VIB was "ingested" & expired by the coming merge.
That's correct. Newly added VMs will be included in the next incremental run and injected in the .vbk according to the retention policy.
pkelly_sts wrote:However, with a per-vm backup repository, should I expect it to merge the originally added VMs as per schedule, and also the later-added VMs won't be merged until they reach their own 15th RP?
If I get you right, under merge you mean injection of incremental files to the full backup, then yes, originally added VMs will start to merge according to the retention policy. Thanks!