Has anyone updated there production Veeam server to 12.3 and had any issues?

2 Spice ups

What is your current version ?
Are the 2 patches in 12.3 affected for your current version or setup (if u using 12.227) ?

Updated and no issues so far.

Given the severity of some of the findings, it would be in your interest to upgrade as soon as you can.

KB4693: Vulnerabilities Resolved in Veeam Backup & Replication 12.3

May also be worth noting this post - someone considering moving from Veeam.

Time to move on from Veeam? - Virtualization - Spiceworks Community

2 Spice ups

No issues with updates in my test lab.

1 Spice up

About to release the Kraken today. Will report back.

1 Spice up

I tried to update yesterday and it failed on step 1 of the upgrade. I currently have a ticket open with Veeam

1 Spice up

None yet I have not done it yet I wanted to find out before hand

Did you hear back from veeam support?

Yes, but no resolution yet. It looks like they are trying to switch from MS SQL Express to Postgresql and the Postgresql install didn’t work. but that is just my guess at the moment.

2 Spice ups

Installed VeeamOne first last week and finally upgraded B&R. I’m on PostgreSQL and install went like the others. My first Backup and SureBackup jobs ran just fine.

1 Spice up

What is your license version Advanced or higher?

I run Veeam Essentials Enterprise

1 Spice up

Upgrade to 12.3 fails on first attempt but will succeed on the second try with no changes in between. This seems to be a known issue (points to Postgress).

I’m having a problem with our existing Surebackup but have yet to identify the problem. I’ll be opening a case soon.

Its probably a Timeout if I was to guess. I noted it did install PostGresql

Thats good to note. I will have to try the installer again

Our SureBackup problem was due to the NFS Datastore was still marked as in use in VMware. I was unable to unmount it using vCenter so I needed to do the following:

  1. connect directly to the host via SSH
  2. run esxcfg-nas -l to list the names.
  3. run esxcfg-nas -d <datastore_name>
  4. reboot host so the mount would clear from vCenter, even though the operating system no longer showed it in use.
1 Spice up