restoring files from FLR to Linux VM doesnt work

[frank.furter]

Hello,

i have an issue with veeam backup & replication and the linux agent while restoring Backups. The FLR launches correctly but when i choose a single file (for testing) and want to restore it to the linux machine it runs for ~ 10 min and then after "Batch Mode" I have two errors:

24.02.2020 15:34:11 Error Failed to start linux agent on original VM!
Failed to start client agent on the host 'bartlby'
Failed to start client agent on the host 'bartlby'
...
Failed to construct ClientAgentProtocol.
Failed to switch to root: Unknown error

24.02.2020 15:34:11 Error Restore failed Error: Failed to start linux agent on original VM!
Failed to start client agent on the host 'bartlby'
Failed to start client agent on the host 'bartlby'
...

The System on which the agent is running is Debian Stretch amd64. The storage, the Windows Server which ist running Veeam B&R and the host where the agent is running are all in the same network (129.168.x.0/24) without firewall between them. also the FLR-VM (static IP configuration) is connected to the same net.

The Linux Agent is V 4.0.0.1961 from the veeam Repos. I've also done a clean reinstall but it did not help.
Version of Backup & Replication is 9.5.4.2866

please respond if you need more specific information.

i already created a support ticket [ID# 04023272] but however i accidently closed it somehow and i can not reopen it...

Greetings,
Dave

[soncscy]

Hey Dave,

It's maybe a long shot, but I remember something similar from one of our clients a bit back on U4 where the veeamagent was segfaulting.

grep over /var/log for 'veeamagent' and see if the agent ever actually loads. If there are no segfaults, doublecheck your mount rules for /tmp, cause I've seen environments where /tmp was mounted with noexec, and that's the default directory for Veeam to do everything.

[frank.furter]

/tmp has permissions set to 777

drwxrwxrwt 13 root root 44K Feb 25 10:25 tmp

Code: Select all

root@bartlby /var/log $ grep -iR "veeamagent" *
veeam/_system/Session_20200224_161440_{96b45c18-35f6-452c-ad07-79bc9615188d}/Manager.log:[24.02.2020 16:14:41.565] <140403606903744> lpbcomm|       Executing custom script: [tar]. Arguments: [--format=gnu --update --file /tmp/veeam/veeam_logs_20200224_161441.tar /var/log/veeamagentid.log]
veeam/_system/Session_20200224_161440_{96b45c18-35f6-452c-ad07-79bc9615188d}/Manager.log:[24.02.2020 16:14:41.568] <140403606903744> lpbcomm|       Executing custom script: [tar]. Arguments: [--format=gnu --update --file /tmp/veeam/veeam_logs_20200224_161441.tar /var/log/veeamagentid.log] ok.
veeam/Backup/bartlbyvm cfg backup - 192.168.239.200/Session_20200225_000111_{0fc86d45-995e-4b5a-9125-da701eb55e00}/Job.log:[25.02.2020 00:02:57.978] <140380915463936> lpbcomm|   Looking for existing agent id in file /etc/veeamagentid
veeamagentid.log:[28.01.2020 13:48:02] <140645295778688> agentid| name: /tmp/d2b016b3e2e74474b18dbc7ce748c36e/veeamagentid
veeamagentid.log:[28.01.2020 13:49:15] <139727315491712> agentid| name: /usr/sbin/veeamagentid
veeamagentid.log:[28.01.2020 13:49:40] <140069490195328> agentid| name: /usr/sbin/veeamagentid
veeamagentid.log:[28.01.2020 21:00:37] <139683740400512> agentid| name: /tmp/e059635b2d2e45e480016fcd00494cab/veeamagentid
veeamagentid.log:[29.01.2020 21:00:26] <139752810662784> agentid| name: /tmp/dc34f4fbaa574b83b94cd37761b1a2dd/veeamagentid
veeamagentid.log:[30.01.2020 21:00:20] <140013772516224> agentid| name: /tmp/e5c19b1f52ef40f6ae52adbb4a23e1b8/veeamagentid
veeamagentid.log:[31.01.2020 21:00:27] <140046682393472> agentid| name: /tmp/b98c466f7ae449fe9b0e8c46c08e8b0e/veeamagentid
veeamagentid.log:[01.02.2020 21:00:30] <140452787288960> agentid| name: /tmp/fe24712ffe6142afac76aa150dfe6624/veeamagentid
veeamagentid.log:[02.02.2020 21:00:25] <139685151808384> agentid| name: /tmp/fc13dd88918847f9948f448dd38ddda0/veeamagentid
veeamagentid.log:[03.02.2020 21:00:34] <139768657726336> agentid| name: /tmp/c3405bda96c947d489b1e17254b312a0/veeamagentid
veeamagentid.log:[04.02.2020 21:00:27] <140556190690176> agentid| name: /tmp/bdfc84d5b72a4e77b037da4391467bf7/veeamagentid
veeamagentid.log:[05.02.2020 21:00:35] <140314559216512> agentid| name: /tmp/11aec2041a5a4bc1b61dc79970b86dff/veeamagentid
veeamagentid.log:[06.02.2020 21:00:21] <140112023575424> agentid| name: /tmp/bc106a4fca9540d89cc203750f249dde/veeamagentid
veeamagentid.log:[07.02.2020 21:00:31] <140656537910144> agentid| name: /tmp/c12cb68be9254536ad6fad35fb25194a/veeamagentid
veeamagentid.log:[08.02.2020 21:00:40] <140072357702528> agentid| name: /tmp/aed04818ca5b45618ce90bc8c46d593d/veeamagentid
veeamagentid.log:[09.02.2020 21:00:39] <140390719318912> agentid| name: /tmp/5fa8bf32475e44f28fda3d4d8ad6ba63/veeamagentid
veeamagentid.log:[10.02.2020 21:00:41] <139735046626176> agentid| name: /tmp/04a16367aa40411199b7bf03bca78a97/veeamagentid
veeamagentid.log:[11.02.2020 21:00:24] <139664574602112> agentid| name: /tmp/70c10b4ebb1449b8990ddf0495ce5563/veeamagentid
veeamagentid.log:[12.02.2020 21:00:28] <139817327881088> agentid| name: /tmp/2773fc96548c46f489994404c404a58f/veeamagentid
veeamagentid.log:[13.02.2020 21:00:39] <139649256958848> agentid| name: /tmp/d66bb1b1bdc4453f9481af7407c5038d/veeamagentid
veeamagentid.log:[14.02.2020 21:00:34] <140130648427392> agentid| name: /tmp/1a77dfcfa52442de9040ebb4f4c971c5/veeamagentid
veeamagentid.log:[15.02.2020 21:00:21] <140099746773888> agentid| name: /tmp/5ac88e367d3340538a9d50fff603bc61/veeamagentid
veeamagentid.log:[16.02.2020 21:00:38] <140163392736128> agentid| name: /tmp/36cf21e18f40403bae4fae1e846c4c92/veeamagentid
veeamagentid.log:[17.02.2020 21:00:21] <140638306884480> agentid| name: /tmp/1752b81fab424051bd946f10dba9321e/veeamagentid
veeamagentid.log:[18.02.2020 21:00:35] <140668780321664> agentid| name: /tmp/ff5db33cff2a43279126adf54fb7ec49/veeamagentid
veeamagentid.log:[19.02.2020 21:00:20] <139668224433024> agentid| name: /tmp/b17c2d4031864410848a30ee67fa5c44/veeamagentid
veeamagentid.log:[20.02.2020 21:00:40] <140082741320576> agentid| name: /tmp/8d0523f64b5b4c83bc84df148f485ee3/veeamagentid
veeamagentid.log:[21.02.2020 21:00:18] <139699244862336> agentid| name: /tmp/ab423eee05194d0784fbded2cd1716fb/veeamagentid
veeamagentid.log:[22.02.2020 21:00:34] <140116536228736> agentid| name: /tmp/c7671c69d07f4c29b7e4da99c2d1c3d5/veeamagentid
veeamagentid.log:[23.02.2020 21:00:41] <139782980139904> agentid| name: /tmp/da80cdd4aa694ae2a27682b1df7e0cb6/veeamagentid
veeamagentid.log:[24.02.2020 14:19:32] <140285124598656> agentid| name: /tmp/9df882dd2d6d4e54ae0ee902f9821444/veeamagentid
veeamagentid.log:[24.02.2020 14:20:19] <140446681815936> agentid| name: /tmp/0c44e7d61e7d4c09a97133dfc39cebe0/veeamagentid
veeamagentid.log:[24.02.2020 14:21:39] <140245041736576> agentid| name: /tmp/9c407823267941c7882a4413815adc1d/veeamagentid
veeamagentid.log:[24.02.2020 14:22:43] <140356719811456> agentid| name: /usr/sbin/veeamagentid
veeamagentid.log:[24.02.2020 14:22:44] <140491273968512> agentid| name: /tmp/dcecdce47c1345c48537ce2d4adac568/veeamagentid
veeamagentid.log:[24.02.2020 14:24:03] <140597286271872> agentid| name: /tmp/d9089c3e554e4f9481260978bcd3e2ff/veeamagentid
veeamagentid.log:[24.02.2020 14:38:36] <139820350118784> agentid| name: /tmp/8f6d3cb673e5445c9fc0f3e74403395c/veeamagentid
veeamagentid.log:[24.02.2020 14:43:52] <139911004584832> agentid| name: /usr/sbin/veeamagentid
veeamagentid.log:[24.02.2020 14:44:55] <140138947459968> agentid| name: /tmp/a62ae8643ec14d3d87864378642be9af/veeamagentid
veeamagentid.log:[24.02.2020 21:00:21] <140286612876160> agentid| name: /tmp/348efb040911432a8f9470e8faf578ba/veeamagentid

[nielsengelen]

Best is to open a new support case for assistance to see what goes wrong exactly.

[frank.furter]

Case # 04025557

[PTide]

Hi @frank.furter,

1.

Code: Select all

24.02.2020 15:34:11 Error Failed to start linux agent on original VM!
Failed to start client agent on the host 'bartlby'
Failed to start client agent on the host 'bartlby'
...
Failed to construct ClientAgentProtocol.

This error might be not directly related to VAL. In order to restore files to Linux hosts VBR attempts to deploy a helper agent which is not the same as VAL.
Kindly try to restore files to the same Debian 10 from some vSphere backup and see if the issue persists.

2.

The Linux Agent is V 4.0.0.1961 from the veeam Repos. I've also done a clean reinstall but it did not help.
Version of Backup & Replication is 9.5.4.2866

Just FYI - v4 Agents (both VAW and VAL) require VBR v10 to operate properly.

Thanks!

[frank.furter]

Just FYI - v4 Agents (both VAW and VAL) require VBR v10 to operate properly.

upgrading fixed the problem . Thx, i thought we have the newest version because we bought the license a few weeks ago...that was a wrong assumption