I've been told by Veeam support, Case ID# 02048693, that adding a VM with a full recovery model database to an existing job will require an Active full on the job before transactional logs can be backed up and truncated. If I have a job which contains 10 VMs and I add a new Full Recovery Model Database to just one of those VMs I would have to run an active full on the job to protect this new database. This would unnecessarily run active fulls on the 9 other VMs just to get the initial backup and transactional logs running correctly on the VM with the new database.
The logic, from my perspective, seems flawed.
Does anyone have a workaround to this scenario? I would rather not create a unique VM based job for each VM which contains a full recovery model database.