![\"\"](\"https:\/\/i.imgur.com\/A4FVOP2.png\")
<\/a><\/p>\nI didn’t have a paid product license, so my download section was full of free trial links. Since I’m using CE (community edition) from here: Free Backup Software For Windows, VMware, & More – Veeam<\/a><\/p>\n Step 2) Download the ISO, it’s a doosy at 13 GBs<\/p>\n Step 3) Read the update notes for any expected issues\/outcomes.<\/p>\n For all the FAQs go here: Veaam Upgrade FAQs<\/a><\/p>\n For basic System Requirements and release notes see here: Veeam Backup & Replication 12.3 Release Notes<\/a><\/p>\n The main thing will be the change of the server SQL service, moving from MS SQL Express, to PostgresDB, Though it’s not directly mentioned from what I can see other than the step 8 in the Upgrade path: Upgrading to Veeam\u00a0Backup\u00a0&\u00a0Replication 12.3 – User Guide for VMware vSphere<\/a><\/p>\n Step 4) Attach the ISO to the server being upgraded or installed on<\/p>\n My case a 12.1 based server.<\/p>\n My case it’s a VM, so I just attach it via VMRC.<\/p>\n Step 5) Run the Installer<\/p>\n Make sure you stop any “continuous” jobs, and close the B&R Console.<\/p>\n Double Click Setup.exe on the mounted ISO’s main directory.<\/p>\n If you haven’t guessed it, click Upgrade. Yes, nice to see coding done where it just does a check and knows it’s a Veeam server, so the only option is to Upgrade.<\/p>\n In my case I again only have one option to choose from.<\/p>\n How long we wait is based on the Matrix. Looking at the VM resource usage, and my machines based on the setup, looks like it’s reading from the ISO to load installation files. and writing it somewhere to disk, my setup only yielded me about 40 MB’s and took roughly 8 minutes.<\/p>\n Agree to the EULA.<\/p>\n Upgrade the server, here’s you have a checkbox to update remote components automatically (such as Veeam proxies). In my lab the setup is very simply so I have none. I just click next.<\/p>\n License upgrade: (I’ll try not selecting this since CE, nope wizard wouldn’t let me for CE, shucks hahah)<\/p>\n Service account, Local System (recommended). I left this default, next.<\/p>\n Here’s the OG MS SQL instance:<\/p>\n … yes?<\/p>\n For the Veeam Hunter service… ignore<\/a> (Shrug)<\/p>\n free space… needs more than 40 Gigs… holy molly….<\/p>\n 43.1 GB required, 41 GB Available. Unreal, guess I’ll extend the drive, great part of running VMs. \ud83d\ude42<\/p>\n Finally! Let’s Gooooo! and sure enough first step.. here comes the new SQL instance.. this is probably why it requires over 40 gigs to do the install, to migrate the SQL instance from MS SQL to Postgres…. Wonder if space will be reclaimed by removal of the MS SQL Express instance….<\/p>\n Roughly half hour later…<\/p>\n Mhmmm checking the services I see the orginal MS SQL instance is still there running. I see a postgres service.. not running… uhhhh mhmmm…<\/p>\n All Veeam services are running, open the Veeam B&R console, connect, and yup it opens. The upgrade component wizard automatically opened, and it updated the only item.. itself.<\/p>\n *UPDATE* Patch for latest CVE of 9.9. If you have a domain joined Veeam server.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n