Patch in KB3039

[perjonsson1960]

Folks,

Just installed the patch in KB3039. When I had installed it and re-launched the console, it said nothing to reflect that it updated the other managed servers. And the version number is still 9.5.4.2866. Is this as it should be?

Regards,
Per Jonsson
Sweden

[Egor Yakovlev]

Hi Per!

Yes, build number shall remain the same.
Just in case, you can go Backup Infrastructure and hit Rescan on managed servers manually.

/Thanks!

[foggy]

Hi Per, the patch doesn't need to update any remote components, the actual fix is performed in the service components on the backup server itself. I will pass this info to the responsible person to update the KB, p.6 should be removed. Thanks for the heads up!

[perjonsson1960]

Anytime!
Maybe p.6 instead could read something like "Start all the Veeam services again before attempting to re-launch the console."

[foggy]

It is not required either - the patch setup stops and starts the services when necessary.

[perjonsson1960]

Then p.3 should be shortened a little...

[Gostev]

Looks like it's done!

[arosas]

We use Exagrid as our primary landing space with Azure SOBR extents. I was told by support (Case#03868669) that we should install it, which we have. One thing I noted during the installation of KB3039 I received a message that stated "Once the update is installed, you must open Veeam Backup & Replication user interface, and follow the Upgrade wizard to update all remote components."

Support confirmed (Case#03871289) that this message does not apply in this situation and can be ignored. Just thought I'd share in case anyone installed the patch and expected other components to be installed.

[Gostev]

Right, I think this is just the default behavior of our patch engine to throw this message at the end of hotfix installation.