ober72 wrote:Sorry might have missed this, but what if I want to change a job to a per-vm job. If I create a new job in a repository that is per-vm then map the new job to the old job will it then in the new job be a per-vm vbk job.
Do you mean copying the old single full backup chain to the repository configured for per-VM chains and then mapping the new job to it? It will continue as not per-VM until the next active full.
ober72 wrote:one other question if you seed from a job that was created in Veeam 8 with no bitlooker will the new job use the bitlooker for the whole vm? My understanding is that If you turn on the bitlooker on a job that was created in Veeam 8 that was just upgraded it would need to do a new full backup to avoid the dirty bits.
For BitLooker it doesn't matter what do you have in existing backup files. When you enable BitLooker on a job, it will do its job during the next cycles, however, only for data copied within the particular job run. So if you want it to process the entire VM, you need to perform an active full.