Error data mover in job of File Backup

Hi ​@Peterson_Lopes - Welcome to the Community!

It looks like from what I read you’ve done about all I would recommend. So at this point I recommend you simply open a Veeam Support case for them to get you sorted as we aren’t Support here, but fellow Veeam users 😊

You could look at the logs to see if they show anything more definitive. Where the specific logs are located are dependent upon what VBR platform you’re using (Windows vs Linux). See:

https://helpcenter.veeam.com/docs/vbr/userguide/logging.html?ver=13

But, Support is probably your best option since this has been happening to you for seemingly quite a while. Kinda sounds like maybe the Installer or Transport daemon/service may be stopping on your Linux box (Proxy/Worker) though. 

The only place I can think of to check would be in the logs - C:\ProgramData\Veeam\Backup\Jobname

If that does not point you anywhere, then a support ticket is a better bet.

Thanks for the quick reply, friends...

Analyzing the logs in the folder 

 C:\ProgramData\Veeam\Backup\Jobname , I found the following information at the time the error occurs:

[01.05.2026 15:24:19.860]    <30> [000A]    Info (3)    Create caching agent certificate creator for job session 3be2eff3-e8e8-4222-95fa-6546fb9b489b
[01.05.2026 15:24:19.861]    <30> [000A]    Info (3)    Product version is 13.0.1.2067, Veeam Data Mover service version installed on server 192.168.78.5 is 0.0.
[01.05.2026 15:24:19.862]    <30> [000A]   Error (1)    Failed to create NASBackup source agent
[01.05.2026 15:24:19.862]    <30> [000A]   Error (1)    Veeam Data Mover service installed on 192.168.78.5 is out of date. (Veeam.Backup.Common.CComponentOutdatedException)

I found it very strange that it detected this version 0.0…
 

When the backup occurs normally, it also detects the correct version:
[06.05.2026 10:00:35.299]    <30> [000A]    Info (3)    Create caching agent certificate creator for job session f4b91900-8a50-43d5-b49a-39b23c294854
[06.05.2026 10:00:35.299]    <30> [000A]    Info (3)    Product version is 13.0.1.2067, Veeam Data Mover service version installed on server 192.168.78.5 is 13.0.1.2067.
[06.05.2026 10:00:35.312]    <30> [000A]    Info (3)    [TransportService] Connecting to transport service, host '192.168.78.5', addresses [192.168.78.5], port '6162', protocol: Vcp.

I believe that if no one has encountered this error before, the solution will be to contact support. However, I use the community version of Veeam, and we are in the process of acquiring a license... I believe that to open a support ticket, I must first have the license. Is that correct?

Hi ​@Peterson_Lopes,

... from your log, the Veeam Data Mover service version installed on your server 192.168.78.5 is "0.0" means that VBR is unable to properly query the remote transport service on 192.168.78.5. Since you have performed other validations/trobleshooting. Why not switch the server enteries from IP to FQDN. To aviod wierd issues as you are experiencing now, I will recommend to use "Fully Qualified Domain Names (FQDN)" over IP addresses for secure, stable operations, and certificate-based authentication. Using IP addresses can cause failed validations due to skipped PTR lookups etc

​@Peterson_Lopes - no, you can open a case with the CE version of VBR, but Support is ‘best effort’. You’ll more than likely not get a response due to “not enough Support resources”. Having a license first would be ideal...yes. In the meantime, can you check your Transport (Data Mover) Service on the Linux server to make sure it’s running when you get the error? My guess is it isn’t running, thus the “0” version you’re getting in the error. If it’s not running, the next thing would be to determine why the service isn’t running during those times.

You can open a support ticket with Community Edition it is just best effort support so if you can wait for the license you will have better support options.