Comprehensive data protection for all workloads
Post Reply
GordA
Influencer
Posts: 16
Liked: 2 times
Joined: Nov 12, 2015 9:14 pm
Full Name: Gordon Armstrong
Contact:

11.0.1.1261 P20220302 doesn't update remote components

Post by GordA »

Hi all,

We recently applied patch P20220302 and while it ran successfully, it did not update remote components on proxies or repos though that option was checked. In addition, the UI doesn't show any updates required and trying with PS also does not trigger any updates to push using

$servers = Get-VBRPhysicalHost -UpdateRequired
Update-VBRServerComponent -Component $servers
or
Update-VBRServerComponent

The veeamagent.exe version on the mgmt server does show a date modified of 3/2/2022 but the others still show as 12/11/2021

C:\Program Files (x86)\Veeam\Backup Transport\\x86\VeeamAgent.exe Version is 11.0.1.1261
Current file modified date: {second=16, minute=35, year=2021, hour=10, day=11, month=12}
File modified date for C:\Program Files (x86)\Veeam\Backup Transport\\x86\VeeamAgent.exe should be (YYYY-MM-DD HH:MM:SS): 2022-3-1 0:0:0 or higher.

Has anyone come across this?

Thanks

G
HannesK
Product Manager
Posts: 14837
Liked: 3084 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: 11.0.1.1261 P20220302 doesn't update remote components

Post by HannesK »

Hello,
yes, that's expected behavior if you upgrade from "11.0.1.1261 P20211211" to "11.0.1.1261 P20220302". The security fixes described in https://www.veeam.com/kb4245 affected only the backup server.

The different veeamagent.exe date is because it was rebuilt. There were no changes in the code.

Best regards,
Hannes
GordA
Influencer
Posts: 16
Liked: 2 times
Joined: Nov 12, 2015 9:14 pm
Full Name: Gordon Armstrong
Contact:

Re: 11.0.1.1261 P20220302 doesn't update remote components

Post by GordA »

Ok thank you.

G
Post Reply

Who is online

Users browsing this forum: Google [Bot], Gostev, Majestic-12 [Bot], sally123, Willy M. and 150 guests