12.3.2.4465 Upgrade from 4165

Hi Tony,

I did some updates yesterday evening, without any further intervention. It’s just a small patch - you can rely on existing documentations or guidelines.

Best, Markus

Hi Markus, thanks for your reply, I’m conscious if this comment in the article - https://www.veeam.com/kb4696 , under resolved issues - 

General

• When updating RHEL infrastructure servers with the DISA STIG profile enabled, the public GPG key used to validate Veeam packages will be updated as well.
  To ensure a smooth update for these systems, it's recommended to temporarily disable the fapolicyd service (if it's in use) during the update.

Hi ​@TonyHalligan - Aside from what’s in the KB you posted, and in the User Guides...none other that I’m aware of. I’m about to patch my 2 servers as I type this 😉

Best.

All went smooth. I stopped all my Veeam services (I always do this as it makes patching quicker; the patch/update does this typically, and it takes way longer for it to stop the services than stopping them manually), and ran the patch. Literally took 5mins. All good.

I did upgrades across Windows (running v12 &13_ and Linux software appliance without issue. Very easy to update.

All, can anyone pint me to the existing Veeam docs to guide me through this...thanks, there was an article for 4165 last year, by one of our members, not seen a similar one as yet...thanks

​@TonyHalligan - here is the update process listed in the User Guide for v12. Really nothing to it:

https://helpcenter.veeam.com/archive/backup/120/vsphere/updating_vbr.html

Main thing is the “Before You Begin” and “Finalizing Steps” sections:

https://helpcenter.veeam.com/archive/backup/120/vsphere/update_vbr_byb.html

https://helpcenter.veeam.com/archive/backup/120/vsphere/update_vbr_after_update.html