Skip to main content
Solved

Estimated Upgrade Time from VBR 12.3.2 to 13.0.2 with 150TB Local Repository

  • July 15, 2026
  • 5 comments
  • 32 views
B
  • bf001
  • Not a newbie anymore

Hello,

I am planning to upgrade Veeam Backup & Replication from v12.3.2 to v13.0.2 and would like to understand the expected downtime and processing time.

Current environment:

  • Veeam Backup & Replication: 12.3.2
  • Target version: 13.0.2
  • Local backup repository: approximately 150 TB
  • Repository type: Local repository (Windows)
  • Number of backup jobs: 80
  • Number of restore points: 2560 (if relevant)

I have two questions:

  1. How long does the VBR application upgrade itself typically take when upgrading from 12.3.2 to 13.0.2?
  2. After the upgrade, how long should I expect any backup chain metadata upgrades or repository upgrades to take for a repository containing approximately 150 TB of backup data?

I understand the actual duration depends on hardware performance and repository design, but I would appreciate any real-world experiences or guidance from others who have performed a similar upgrade.

Thank you.

Best answer by eblack

2-4hr sounds about right. We just did a 64core/96g and it didn’t seem to matter; it was still 2.5hrs in total. An hour of that was the catalog/db. At one point I started checking PID and MSI activities just to make sure it was still chugging along.  No issues at all honestly, it just took the time it took. 

      5 comments

      Stabz
      Forum|alt.badge.img+9
      • Stabz
      • Veeam Legend
      • July 15, 2026

      hi ​@bf001 
      If you have only VBR and no Veeam One or Veeam Enterprise Manager, you should allow between 2 and 4 hours.

      Ensure that the backup server has sufficient disk space. 


      Legacy per-machine backup format with single metadata file must be upgrade before the installation

      Same for legacy backup copy jobs.

      Find the checklist here : https://helpcenter.veeam.com/docs/vbr/userguide/upgrade_vbr_byb.html

      After the upgrade there is no backup chain upgrade, you must upgrade the product components running on remote servers.( Proxy/Repository/Etc...)

      I recommend to make somes exploitation tests (Backup/Backup Copy/Restore/etc...)

      Philippe DUPUIS |Veeam Certified Engineer | https://original-network.com/
        B
        • bf001
        • Author
        • Not a newbie anymore
        • July 15, 2026

        ​@Stabz 
         

        Thank you for your response.

        Since this environment only has Veeam Backup & Replication (VBR) deployed, I will plan the maintenance window based on an estimated upgrade duration of 2–4 hours.

        Could you please let me know how I can verify whether all backup chains in my environment are already using a single metadata format?

        I would like to check this before proceeding with the upgrade to better understand whether any metadata or backup chain conversion process may be required afterward.

        Thank you.

          Andanet
          Forum|alt.badge.img+13
          • Andanet
          • Veeam Legend
          • July 15, 2026

          Hi ​@bf001 welcome to the community. 

          It is not simple to estimate the exact timings that depend on your server's hardware performance (CPU, RAM, disk speed) and your database engine (SQL vs. PostgreSQL), from number of your proxies and if you have Veeam One or VRO too. 

          Normally when I planning an upgrade I ask a windows of 6/8 to be sure all is ok. 

          First of all use the checklist in the official documentartion:  

          https://helpcenter.veeam.com/docs/vbr/userguide/upgrade_vbr_byb.html?ver=13

           

          For metadata that’s a different matter. 

          If you're using a native 12.x version, you don't need to check for metadata format conversions; otherwise, you should check everything, and you can do so with a simple PowerShell command like the one I found on the forum 

          Get-VBRBackup | Where-Object {($_.IsTruePerVmContainer -eq 0) -And (($_.TypeToString -eq "VmWare Backup") -or ($_.TypeToString -eq "HyperV Backup" ) -or ($_.TypeToString -eq "Backup Copy" ))} | ft -AutoSize

          please check and modify the script based on your infrastructure.
          With 150 TB of data, scanning and updating the components in your local Windows repository should take between 15 and 60 minutes. 

          I can suggest you to follow these two articles with step explained: 

          Article 1

          Article 2

          LEt us know 

          Antonio D'Andrea | VMCE | VMCA | Veeam Legend | VUG Italy Leader | Object First Ace | I want it written on my tombstone "Please start a restore to the last valid backup"
            eblack
            Forum|alt.badge.img+3
            • eblack
            • Influencer
            • Answer
            • July 15, 2026

            2-4hr sounds about right. We just did a 64core/96g and it didn’t seem to matter; it was still 2.5hrs in total. An hour of that was the catalog/db. At one point I started checking PID and MSI activities just to make sure it was still chugging along.  No issues at all honestly, it just took the time it took. 

              B
              • bf001
              • Author
              • Not a newbie anymore
              • July 16, 2026

              ​@Andanet  ​@eblack 
               

              Thank you for your response.

              As this environment was originally deployed with V12, I understand that there is no need to perform this check.

              Our environment is similar in size to eblack's, so we'll use their reported upgrade time as a reference when planning our maintenance window.

              Thank you.

              Terms & ConditionsAccessibility statement