You can switch a job anytime to the new per-VM chain format by changing the repo to per-vm, then detaching the old backups from the job, editing the job (if needed) and restarting the job. This will then start a new chain in the per-VM format and the old backups will appear under "Disk (Orphaned)". BTW - thanks for the confusion and the bad docs, Veeam...
Thanks for the video, Vikash! Quick question: I have a SOBR running which has per VM files enabled, but on the extents I do not have the option enabled. I have the upgrade button visible in v12. Is that a proper setup or should I enable this option on the extents aswell?
Hi, i assume that there will be impact on the backup size, until now i was using compression and deduplication, cant imagine that it will still work with one chain per VM. Is it only recommended if i have the backup files stored on a storage with compression and dedup? If yes, i dont think that it will work with encrypted backups, correct?
There are several things to consider regarding encrypted backups but using the new backup chain format can still be perfectly used so you can still benefit from it.
![[EN] Veeam Data Platform v12.2 - How-to upgrade Veeam Backup & Replication to v12.2](http://i.ytimg.com/vi/qDvReP5GGU8/mqdefault.jpg)
![[EN] Veeam Data Platform v12.2 - How-to upgrade Veeam Backup & Replication to v12.2](/img/tr.png)
excelente video amigo!!
well done mate !
You can switch a job anytime to the new per-VM chain format by changing the repo to per-vm, then detaching the old backups from the job, editing the job (if needed) and restarting the job. This will then start a new chain in the per-VM format and the old backups will appear under "Disk (Orphaned)".
BTW - thanks for the confusion and the bad docs, Veeam...
This was very helpful, Thanks!
thank you Vikash
Thanks for the video, Vikash! Quick question: I have a SOBR running which has per VM files enabled, but on the extents I do not have the option enabled. I have the upgrade button visible in v12. Is that a proper setup or should I enable this option on the extents aswell?
The extents can be little tricky to deal with. I don’t recommend that myself. Check the Veeam Knowledge Base for that
Hi,
i assume that there will be impact on the backup size, until now i was using compression and deduplication, cant imagine that it will still work with one chain per VM. Is it only recommended if i have the backup files stored on a storage with compression and dedup? If yes, i dont think that it will work with encrypted backups, correct?
There are several things to consider regarding encrypted backups but using the new backup chain format can still be perfectly used so you can still benefit from it.