I am testing with success V13 in Azure Stack HCI (local onsite Hyper-V) environment. Great to see most daily things can be done from the web GUI. Other one-time creation of for example Deduplication Repository no problem to do that in the Windows GUI, guess this low priority will come later in the web GUI as well.
But when connecting with V13 to a Hyper-V host it need to update the Veeam-software on that host from V12 to V13. So that host cannot be used anymore with V12.
With earlier version upgrades that was no problem because there was a whole in-place upgrade or new install with whole Veeam database migrated to new versions. But in V13 there is no (not yet) database migration. So you have to do it in 1 shot: recreate all credentials, Repositories, importing backups, recreate all Jobs, importing tape server and many tapes (!) et cetera.
Is there any trick to test/use V12 and V13 mixed on the same hosts in a Hyper-V environment?
(BTW: we also signed up for the later support when a complete migration scenario will come available).
But when connecting with V13 to a Hyper-V host it need to update the Veeam-software on that host from V12 to V13. So that host cannot be used anymore with V12.
With earlier version upgrades that was no problem because there was a whole in-place upgrade or new install with whole Veeam database migrated to new versions. But in V13 there is no (not yet) database migration. So you have to do it in 1 shot: recreate all credentials, Repositories, importing backups, recreate all Jobs, importing tape server and many tapes (!) et cetera.
Is there any trick to test/use V12 and V13 mixed on the same hosts in a Hyper-V environment?
(BTW: we also signed up for the later support when a complete migration scenario will come available).
Statistics: Posted by dali@iae.nl — Sep 24, 2025 6:23 am
![Madonna – Who’s That Girl (1987/2020) [FLAC 24bit/192kHz]](http://imghd.xyz/images/2023/06/08/0093624951148_6004dceff9e1db710a9.jpg)
