Comprehensive data protection for all workloads
Post Reply
mkretzer
Veeam Legend
Posts: 1340
Liked: 491 times
Joined: Dec 17, 2015 7:17 am
Contact:

Our 13.1 Upgrade experience and "Problems"

Post by mkretzer »

Hello,

finally we did our 13.1 (from 12.1) upgrade. Mostly it worked well (still on Windows/MSSQL) and upgrade was quite fast but we had some issues:
  • Proxmox Backup did no longer work after upgrade (Case 08206449): Our self-signed certificate was from 2019 which lead to "Waiting for available workers" and workers unable to connect. At first the SSL message was not even visible and it looked more like an idrac interface on Veeam Server is causing the issue. Renewing the Veeam server certificate fixes the issue. Sadly, Veeam support was not very helpful and also only saw the interface at fault.
  • Component update with warnings (Case 08206359): One of our Linux repos showed warnings in the component update. We do not know what the warning was and also support could not tell us. The Linux server in question was in healthy state, without any upgraded needed directly after the warning.
  • Two of our VMs normally using persistent guest agent failed as connection could not be established via this agent - using non-persistent agent works right away - we might open another case for that.
  • VSphere Tag issues (Case 08207269): All our jobs use exclusion for one VSphere Tag Category. Since yesterday, some of the jobs "fail" (the VMs are still backed up but it fails nevertheless) because the tag category is "unavailable" (which never happened with 12.1 and even with 13.1 is transient). I that is true we might have a larger issue as some jobs are configured to backup everything in a folder "but" the tag category which is backed up by another job.

All in all this is one of the smoothest major version upgrade!

Markus
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], Semrush [Bot] and 909 guests