Skip to main content

What would prevent migrating from Veeam v.12.3 to Veeam v.13

  • December 4, 2025
  • 13 comments
  • 44 views

AndrePulia
Forum|alt.badge.img+9

Hi Community, good day!

 

In my article, you will find information about some conditions that may prevent upgrading from version 12.3 to version 13, such as:

  • Unsupported OS for the VBR server;
  • Unsupported SQL Server version;
  • Unsupported .NET version;
  • Old components still registered (Cloud Connect, Enterprise Manager, Console, Agent, Plug-ins);
  • Legacy license type, and more.

Here a small table that can be used as a reference to organize the upgrade process in the best possible way; keep in mind that this is just a small example based on a very simplistic scenario.

 

 

Build a table like below:

Scenario

  • VBR 12.3 on Windows Server 2016
  • SQL Server 2016
  • VMware ESXi 7.0 U1
  • Windows Server 2016 ReFS repository

 



Check the full article on my Blog https://pulia.com.br/what-would-prevent-migrating-from-veeam-v12-3-to-veeam-v13/

13 comments

coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • December 4, 2025

Pretty cool table reference Andre’! Thanks for sharing!


Forum|alt.badge.img
  • New Here
  • December 4, 2025

Thanks for this valuable information. I’d like to add that the VBR PowerShell module in V13 will only work with PowerShell 7. Had many issues with custom scripts after the migration to the latest release. CheckMK monitoring also uses PowerShell scripts for VBR Job statistics that unfortunately get triggered in PowerShell 5 - as far as I know.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • December 4, 2025

Great chart but I would also add more columns on the benefits of upgrading too. 😉


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • December 4, 2025

Valuable additional points ​@iDoBackups ​@Chris.Childerhose 😊


kciolek
Forum|alt.badge.img
  • Not a newbie anymore
  • December 4, 2025

Thanks for the great information! 


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • December 4, 2025

Great! Read your blog post yesterday ​@AndrePulia. It was indeed very informative.


AndrePulia
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • December 4, 2025

Great chart but I would also add more columns on the benefits of upgrading too. 😉

Yes Chris, that is only one idea to make people think of that. thank you for your comment.


AndrePulia
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • December 4, 2025

Great! Read your blog post yesterday ​@AndrePulia. It was indeed very informative.

Thank you, you do very useful articles as well. :-) I like them.


AndrePulia
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • December 4, 2025

Thanks for the great information! 

:-), my pleasure


AndrePulia
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • December 4, 2025

Valuable additional points ​@iDoBackups ​@Chris.Childerhose 😊

Sure Shane. I lke the way we work, everyone can add some spcies :-)


AndrePulia
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • December 4, 2025

Pretty cool table reference Andre’! Thanks for sharing!

Thank you Shane


AndrePulia
Forum|alt.badge.img+9
  • Author
  • Veeam Vanguard
  • December 4, 2025

Thanks for this valuable information. I’d like to add that the VBR PowerShell module in V13 will only work with PowerShell 7. Had many issues with custom scripts after the migration to the latest release. CheckMK monitoring also uses PowerShell scripts for VBR Job statistics that unfortunately get triggered in PowerShell 5 - as far as I know.

Thank you for bring this up :-) 


Jean.peres.bkp
Forum|alt.badge.img+8

Excelente meu amigo!