Outdated Data Mover Service Version

[perjonsson1960]

Folks,

I upgraded B&R yesterday from 12.1.1.56 to 12.1.2.172, and everything was in the green.
However, we have two physical Linux machines, and when the backup job for them ran, I got a warning that the servers have "an outdated Data Mover service version".

When I run a rescan of those servers, it says that everything is jim-dandy, and the agents need not be updated.

Do you think that it is worth trying to restart the Veeam services in those machines, to see if the problem goes away?

Kind regards,
PJ

[Mildur]

Hi PJ

Are those machines managed servers or do they have the Veeam Agent for Linux installed?

Do you think that it is worth trying to restart the Veeam services in those machines, to see if the problem goes away?

You can try. Nothing bad will happen from a service restart (if no backup or restore sessions are running).
Please contact our customer support team if both server are still show as "outdated" and a rescan/update is not working:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[mjr.epicfail]

Maybe the old services are still being used on the servers

https://www.veeam.com/kb4298
Starting in Veeam Backup & Replication 12.1.2, both the Veeam Transport Service and Veeam Deployment Service are installed using packages.

[perjonsson1960]

That KB seems to describe how to do it in a managed server under "Backup Infrastructure".
The servers with this problem are servers being backed up by B&R, they are not part of B&R.

[mjr.epicfail]

Ok, which linux agent version are you running. Newest one is 6.1.2

[perjonsson1960]

6.1.2.1781 in Ubuntu 20.04.6.LTS
5.0.2.4567 in CentOS release 6.10 (final)

Both get the same warning. Perhaps the CentOS warning can be explained by the old and dusty OS version. But the other one?

[mjr.epicfail]

Strange, current version.

Best thing to do is create a support case if you tried the restart.

[perjonsson1960]

The backup succeeded the next time around, without warnings. And we did not restart the services.
I have no idea why there were warnings about this during the previous backup, but it certainly had to do with the upgrade to 12.1.2.172.
Anyway, I hope that the problem has gone away by itself now.

Thanks for the replies!

PJ