Reboot required after agent installation

[perjonsson1960]

Folks,

I have today upgraded B&R to v11a. In our file server cluster, two machines, I get a "reboot required" after the installation of the agent.

1. Will the backup still work before the servers have been restarted, perhaps with the old agent?
2. Is it possible to activate the new agent without rebooting, for example by restarting some services instead?

PJ

[Mildur]

It depends.
If you have installed the cbt driver on the machine, you need to reboot the system to load the new driver version.
But backup should work with the old Agent, until you reboot the machine.

If you only have the agent installed, most of the time, a reboot is not required.

[perjonsson1960]

The driver is indeed installed, so we'll have to reboot then.
But it is good that the old agent should work until that time.

Thank you!

PJ

[lowlander]

how can we check the latest CBT driver version ? Is there an overview of the agent versions for Windows with corresponding CBT versions ?

[Mildur]

Hi

Unfortunately, we only have the following table, but none for the CBT driver.
https://www.veeam.com/kb2683
With Agent 5.0.3.4708 installed, you will have CBT driver build 10.0.0.5015.

Thanks
Fabian

[lowlander]

Hi Fabian,

When we rely on the VBR information all information looks to be ok. However in the add remove program section of the correspondant server the CBT driver version is still outdated. Is this expected behaviour an can we ignore this, or will this be fixed in future releases ?

For now, is it ok to rely on the VBR information for the agents or should there be a double check just to be sure on the agent operating system computers/servers ?

[Mildur]

Hi

We also saw that inconsistency in our environment and have opened a case ourselves.
As soon we have the answers, we will let you know.

Thanks
Fabian

[lowlander]

Hi Fabian,

you may refer to case number #05583364.

Currently we are getting an answer that doesn't satisfy us

[Mildur]

Thanks for the case number.

So it seems, to update the number in Control Panel\Programs\Programs and Features, a rescan of the protection group after the upgrade is necessary. I checked my test machine, and after a manual rescan it shows also 10.0.0.5015 as the new build in the windows control panel.

You can also check the loaded CBT Driver from this location with "right click > properties" on VeeamVolumeCT.sys:
"C:\Windows\System32\drivers\VeeamVolumeCT.sys"

[lowlander]

Hi Fabian,

good to know, I will let you know if the rescan of the PG will also update the servers version numbers in Control Panel, programs and features for the corresponding servers.

thanks !

[lowlander]

Hi Fabian, we did a manual rescan on the protection group. However this did not update the number in Control Panel\programs and features on the source servers being backed up with the agent.

Is this expected behaviour or more like a bug ?

[Mildur]

Can you let your support engineer know, that a rescan doesn't update the build number? That the build is still the same as in the last few days? Does the file "C:\Windows\System32\drivers\VeeamVolumeCT.sys" have the correct build number?

[Mildur]

Hi
I have an answer about this issue.
It's now confirmed as a bug and plan is to resolve it with VBR V12/ VAW V6.

Best
Fabian