Hardened Veaam Backup Reporsitory: question about Veeam Transport/Deployment versioning.

[Parnassus]

Hi all,

We have four Linux Servers (all SLES 15 SP6 based) deployed as Hardened Veeam Backup Repositories.

Those four servers were initially deployed at different times - in a pretty standardized way during last four years (as per Veeam Best Practices) - and were always being updated along with the Veeam B&R Servers they are connected to (each time we prepared them enabling sudoer to let the Veeam B&R Servers to install required updates to required RPMs).

During a normal housekeeping we found that the expected versioning of the installed:

- veeamdeployment (Veeam Linux Deployer Service)
- veeamtransport (Veeam Transport for Linux Service)

differ each other (and that was strange) at RPM versioning level:

- veeamdeployment-12.3.1.1139-1.x86_64.rpm
- veeamtransport-12.3.2.3617-1.x86_64.rpm

and the former, unexpectedly, differs with respect to the current Veeam B&R Server running version 12.3.2.3617 (and that is even more strange provided that each Veeam B&R Server update done in the past was made following best practices with regard to permitting the automatic Veeam components update on those managed items).

Is the above expected or is it a sign that we managed a Veeam B&R Server update incorrectly along the way?

[Parnassus]

It seems that the Veeam Linux Deployer Service package 12.3.1.1139 - after the change from 12.3.0.310 to 12.3.1.1139 we observed [*] during the update from Veeam B&R Server 12.3.0 to 12.3.1 (we did it on March 2025) - did not change anymore (at least it did not change with the last Veeam B&R Server 12.3.1 to 12.3.2 iteration we did on June 2025). I expected that...am I wrong?

[*] Easy to see the "history" of changes by looking at the /var/log/VeeamBackup/VeeamDeploymentSvc.log file (grep for "Executable version:", as example).