Error failed to execute agent management command startbackup

---

---

---

---

---

---

---

---

---

---

---

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

back error port 10006 connect

back error port 10006 connect

Post by Mr.li » Sep 01, 2021 8:52 am this post

Re: back error port 10006 connect

Post by HannesK » Sep 01, 2021 9:00 am 1 person likes this post

Hello,
the error message says that there is a network connectivity issue. That means checking the ports requirements would be the first step

I don’t see how the connection between Azure and your backup server is established. VPN, Expressroute, pure internet with NAT? (hopefully not the last option because putting a backup server directly on the internet is a bad idea from a security perspective)

If you checked all that (ping, port connectivity for example with «telnet ip port» etc.) and there is still an issue, then that sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.

Best regards,
Hannes

Who is online

Users browsing this forum: No registered users and 3 guests

• Main
• All times are UTC
• Delete cookies
• Members
• The team
• Contact us

DISCLAIMER: All feature and release plans are subject to change without notice.

Powered by phpBB® Forum Software © phpBB Limited

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

#04175281 Backup fails due to certificate/no valid private key

#04175281 Backup fails due to certificate/no valid private key

Post by adexl » May 14, 2020 11:47 am this post

Dear community, I try to backup a v-server from Strato which is running Debian. Veeam Agent was installed successfully and a rescan operation from the Veeam Backup Console works fine. But when doing a backup the operation fails with the following error message:

Error: Failed to execute agent management command startBackup. The certificate used to connect to backup server has no valid private key.

I tried to use credentials user/root and even private/public key authentication. The remote server accepts both authentication methods without any issue. Does anyone have a similar problem or even knows a solution for that? Thanks for your kind help! Alex.

Re: #04175281 Backup fails due to certificate/no valid private key

Post by HannesK » May 15, 2020 6:33 am this post

Hello,
unfortunately you did not attach logs to your case and the email address also seems to have a problem as the answer from support to you returned with «(Undelivered): 550 5.2.0 No such mailbox»

the next thing you might run into is that Strato V-Servers are Virtuozzo containers. So you need to do file based backup: veeam-agent-for-linux-f41/can-val-run-i . =Virtuozzo

I don’t know how much you want to backup, but maybe it is even easier to do NAS-backup instead of agent based backup.

Best regards,
Hannes

Re: #04175281 Backup fails due to certificate/no valid private key

Post by Mildur » Nov 25, 2020 7:46 am this post

I have the same error. Yesterday, I have upgraded 4 veeam Agents for Linux to Version 4.
Ubuntu 14.04 and Ubuntu 16.04

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Error to Agent 3.0 — Linux

Error to Agent 3.0 — Linux

Post by jcerrato1 » Jan 18, 2019 9:04 pm this post

Error: Failed to execute agent management command startBackup. Error: Another backup job is running.

1) I have uninstalled the above agent.
2) rebooted that server .
3) installed the agent again,
4) The backup will run without issues for a couple times and then give the above error. This started happening when I upgraded from version 2 to 3 agent.

Re: Error to Agent 3.0 — Linux

Post by PTide » Jan 21, 2019 11:33 am this post

What mode is that? Is it standalone or managed by VBR/Agent mode? Are you positive that there are no other jobs attempting to start at the same time? Please also provide logs (either open a support case, or provide a link to a downloadable archive)

Re: Error to Agent 3.0 — Linux

Post by mwag » Jan 21, 2019 8:59 pm this post

Re: Error to Agent 3.0 — Linux

Post by BenO » Jan 22, 2019 4:02 am this post

We also see this same issue after updating to Agent 3.0 on RHEL 7

Confirmed there are NO veeam processes running before kicking off the job and get ‘Another Job is Running’ error.

At that point, there IS a veeamjobman and veamagent process running, but they are the ones from the job thats just failed.

Re: Error to Agent 3.0 — Linux

Post by PTide » Jan 22, 2019 9:38 am this post

Although our team already has ideas about the issue, I would like to encourage you to open a support cases and provide our support team with logs as it is almost impossible to say anything regarding the problem without seeing the logs. Please also post your case ID.

Re: Error to Agent 3.0 — Linux

Post by BenO » Jan 23, 2019 1:53 am this post

I’ve raised this as case 03375684

Re: Error to Agent 3.0 — Linux

Post by MoritzB » Jan 29, 2019 1:42 pm this post

Any Updates on this Topic?

we are having the same issues when importing an Config on Debian 8.11

Re: Error to Agent 3.0 — Linux

Post by PTide » Jan 29, 2019 2:51 pm this post

Please open a case with support team and post your case ID. They will collect logs, investigate the issue, and provide you with information about further course of action.

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Veeam Agent for Linux not working after reinstall Backup & Replication Server

Veeam Agent for Linux not working after reinstall Backup & Replication Server

Post by holladiewaldfee » Mar 07, 2020 12:32 pm this post

After upgrading my Backup & Replication Server from 9.5 to 10 it stopped working. It was not possible to start the Backup & Replication Console.
I reinstalled the Backup & Replication Server but the same happened again. After several times i installed the Backup & Replication Server in a new Database and now it’s working again.

I started a new Backup Repository and uninstall on all VM’s (Windows and Linux) the Agents. After that i installed the Agent’s again via Backup & Repository Console.

With the Windows Agent’s it’s working great. With the Linux Agent not.

If i uninstall the Veeam Agents with «apt-get remove veeam veeamsnap» and add them again in the Backup & Repository then i can make exactly one Backup.

After this i geht the following message in the Backup & Repository Console:

Skipping 10.10.10.55 Details: This backup agent is managed by the Backup server APPL.xyz.intra, ignoring control request from APPL.xyz.intra

On the Linux Machine i can see all the old Logs and the old Backup Job. If i try to delete the connection to the Backup & Replication Server with «veeamconfig repository delete -id xyz» i geht this message «This operation is not permitted if management mode is [Policy].»

And this happend to all my Linux VMs.

It looks like i big bug. does anybody has an idea?

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Backup (File) Server in DMZ

Backup (File) Server in DMZ

Post by sebkoe » Aug 20, 2021 11:18 am this post

I’m new to Veeam Backup and Replication (V11) and have been testing diligently for the last few days.

One of the last items on my checklist is file backups from a server located in our DMZ.

Here is what our setup looks like:

1x Veeam Management Server (Windows VM)
3x Storage/Proxy Server (hardware Windows with local hard disks)

All 4 servers have one IP in our LAN (10.10.149.x)

I want to backup files on a Linux server in our DMZ (public IP) for testing.

The Linux server has therefore only via NAT access to the storage servers.

I have not yet managed to implement this setup. In my search so far, I have also not become smarter. Last I had tested the backup solution from Acronis. There a file backup via NAT was no problem.

I hope to get some tips here.

Thanks and greetings
Sebastian

Re: Backup (File) Server in DMZ

Post by wishr » Aug 20, 2021 11:40 am this post

Welcome to Veeam R&D forums!

If your Linux server is accessible through NFS from the backup server/backup proxy, there should not be issues backing it up.

Re: Backup (File) Server in DMZ

Post by sebkoe » Aug 20, 2021 11:54 am this post

Hello and thank you.

So i just have to enable access from my storage/proxy Servers to the Linux Server i would like to backup via NFS?

Re: Backup (File) Server in DMZ

Post by wishr » Aug 20, 2021 1:08 pm this post

Just from the servers where your backup proxies are located, correct.

This diagram highlights a typical deployment scenario and data transmission channels.
Here you can find information on the required ports to be opened.
Also, I’m adding this link to the BP portal maintained by our system engineers (SEs) that provides a lot of useful tips and recommendations.

Re: Backup (File) Server in DMZ

Post by sebkoe » Aug 20, 2021 1:19 pm this post

ok, i did a new test setup.

i created an empty vm in the DMZ Network and made sure all my Backup Servers (Proxy/Storage/Manager) are able to connect via NFS (checked with tcpdump on the Linux Server).

I then started a tcpdump on the Linux Server, while starting a backup on my Manager Server.

I see alot of SSH traffic from the management Server via NAT to the Linux Server (which is working fine), but then i see that the Linux Servers tries to connect to my Mananger Server on Port 10006 to its LAN IP (which cant work, because i am in a DMZ and NAT is required).

After some time the Backup fails with:

«Error: Failed to execute agent management command startBackup.»

I did not see any NFS traffic in tcpdump at all (just ssh and the failing traffic to Port 10006).

So i am a little confused how that should work, when the Linux Server tries to connect to an IP that it is not able to reach directly.

PS: just to make sure we are not confusing things here. I am talking about «NAT», not «NAS». Because you posted a link with «NAS» Infos.

Re: Backup (File) Server in DMZ

Post by wishr » Aug 20, 2021 1:35 pm this post

Are you sure you have created a File Share backup job and exclusively selected the desired backup proxy server? I’m suggesting our file share backup since you were asking about file backups. To clarify, you would like to back up some files located on the Linux server, correct?

On the Linux server, I guess you can modify the /etc/hosts so that the server will talk back to the DMZ IP address of the backup proxy (or the IP address of the backup server if you have not selected a dedicated backup proxy in the job settings).

If you are asking about Veeam Agent backup, please, refer to this thread.

Re: Backup (File) Server in DMZ

Post by sebkoe » Aug 20, 2021 1:45 pm this post

im talking about single files/folder on a host (here Linux) not on a fileshare. Phsysical Servers, that i dont want to backup completely.

This is regular Backup Job:

Backup -> Linux Computer -> Managed by backup server -> File Level Backup -> choose directorys to backup

/etc/hosts does not help since veeam is not trying to connect to a hostname (which i could change via /etc/hosts) but directly to an IP.

Is there no «veeam way» to get the above setup working? This would be my first test with a backup software that is not able to work via NAT.

Re: Backup (File) Server in DMZ

Post by wishr » Aug 20, 2021 1:49 pm this post

Veeam Agents including VAL do not support NAT because the agent should be «talking» directly with the backup server, unfortunately. Though, there are a few workarounds mentioned in the thread I linked above.

Re: Backup (File) Server in DMZ

Post by sebkoe » Aug 20, 2021 1:52 pm 1 person likes this post

Источник

Столкнулся с такой проблемой при попытке выполнить задачу по бэкапу в Veam стала появляться ошибка:

14.12.2020 19:31:42 :: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [0]. Failed to download disk.

Нашёл на форумах veam похожую ситуацию, один из вариантов решения:

On the agent machines, add HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Endpoint BackupManagedExcludeVolumes (REG_MULTI_SZ) and add the volume as the value. e.g. HKLMSOFTWAREVeeamVeeam Endpoint BackupManagedExcludeVolumes=\?Volume{b80b6e86-a7aa-4e89-8fb6-789e24055c1d}. Restart the Veeam agent.

Прописал реестре значение параметра со своим проблемным разделом и не помогло. Где то в темах упоминалось, что проблема появлялась после обновлений.
Хотел понять я как то не корректно настраивал или это проблема совместимости агента с какими то обновлениями от Microsoft.

I am trying to install a Veeam Backup and Replication agent to an Exchange server, but it fails on me with the following error:

«Installing package Veeam Agent for Windows Error: Error 1920.Service Veeam Agent for Microsoft Windows (VeeamEndpointBackupSvc) failed to start. Verify that you have sufficient privileges to start system services.»

The error sounds like an obvious one to me, but I have tried using domain admin credentials that had local admin privileges on the Exchange server to be backed up.

Anyone experience this before or know something I may be missing?

check
Best Answer

Reboot the Exchange server, possibly twice. That fixed it here. 

(I realize that’s an idiotic solution that doesn’t make any sense given the error message, but there ya go.)

Barring that, I’ve also had to manually remove all the Veeam agent components (including the installer service, manually) and then reboot and do the remote agent install again.

Was this post helpful?
thumb_up
thumb_down

View Best Answer in replies below

13/09/2022

Reading Time: 1–2 minutes

If you try to configure agent-based VM backups with agents managed by a different Veeam Veeam Backup & Replication server, you may experience the «Failed to acquire agent managed by…» error.

This error occurs when you perform the Rescan operation of Protection Groups containing Windows or Linux machines managed by agents centrally deployed from the Veeam Backup & Replication server.

If the processed machines were previously managed by a different Veeam Backup & Replication server, you may face the error:

Failed to acquire agent managed by VBR server.

Fix «Failed to acquire agent managed by…» error

There are two ways to fix the «Failed to acquire agent managed by…» error:

• Remove the Veeam’s agent
• Add a new key in the VBR registry

The deletion of installed agents can be time consuming if the number of machines to process is quite high and generally is not the ideal solution.

Modify the Windows Registry

An easy and quick way to prevent this error is the creation of a new registry key.

From your Veeam Backup & Replication server, open the Registry Editor and go to HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Backup and Replication.

Right click Veeam Backup and Replication and select New > DWORD (32-bit) Value option.

Name the create new key as AgentDiscoveryIgnoreOwnership and enter 1 as Value data. Click OK to confirm.

The new AgentDiscoveryIgnoreOwnership registry key has been created successfully.

Now go to the Inventory area and select Physical Infrastructure section. Right click the Protection Group to process and select Rescan.

The rescan operation for Windows machines is now completed successfully.

Also the rescan operation for Linux machines completes successfully.

With this simple configuration it is now possible to complete the rescan procedure without problems.

About The Author

Paolo Valsecchi

System Engineer, VCP-DCV, VCP-DM, vExpert, VMCE, VMCA, Veeam Vanguard. Working experience focused on VMware vSphere, Microsoft Active Directory, and backup/DR solutions.

# 2 года, 5 месяцев назад (отредактировано 2 года, 5 месяцев назад)

Темы: 24 Сообщения: 281 Участник с: 26 сентября 2011

так вы его от root запускаете? Не понял вопрос. По дефолту же все сервисы от root запускаются. и что это за скрипт /etc/init.d/srv1cv83, что там внутри? Это стандартный файл запуска сервера, которые идёт в поставке. Ничего предосудительного в нём на первый взгляд нет. вам надо запустить Согласно выхлопу systemctl status systemd-networkd-wait-online, этот сервис включен и отрабатывает. ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/usr/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: disabled) Active: active (exited) since Thu 2020-09-03 19:07:21 MSK; 3h 2min ago Docs: man:systemd-networkd-wait-online.service(8) Process: 418 ExecStart=/usr/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS) Main PID: 418 (code=exited, status=0/SUCCESS) сен 03 19:07:18 cg-office systemd[1]: Starting Wait for Network to be Configured... сен 03 19:07:21 cg-office systemd[1]: Finished Wait for Network to be Configured.

indeviral	# 2 года, 5 месяцев назад (отредактировано 2 года, 5 месяцев назад)
Темы: 39 Сообщения: 3170 Участник с: 10 августа 2013	Ну так ошибки посмотрите при загрузке, в чём проблема? Чего гадать. Ошибки в тексте-неповторимый стиль автора©

genues	# 2 года, 5 месяцев назад
Темы: 24 Сообщения: 281 Участник с: 26 сентября 2011	indeviral Ну так ошибки посмотрите при загрузке, в чём проблема? Чего гадать. Так не пишет никаких ошибок. Ну или я не знаю, где их искать. В журнале ничего интересного нет. Сам скрипт запуска пишет что запуск успешен.

indeviral	# 2 года, 5 месяцев назад (отредактировано 2 года, 5 месяцев назад)
Темы: 39 Сообщения: 3170 Участник с: 10 августа 2013	У вас не указан интерпритатор bash или sh ExecStart=/usr/bin/bash /etc/init.d/srv1cv83 start А так вообще, соедствами systemd без стартовых скриптов обычно можно и обойтись. Зависит от содержания. Ошибки в тексте-неповторимый стиль автора©

genues

# 2 года, 5 месяцев назад

Темы: 24 Сообщения: 281 Участник с: 26 сентября 2011

У вас не указан интерпритатор bash или sh Не помогло. Вообще интерпритатор указан в самом скрипте. Да и запуск скрипта точно происходит. В частности он выдаёт сообщения, что сервер якобы запущен. Опять таки ручной запуск срабатывает. А так вообще, соедствами systemd без стартовых скриптов обычно можно и обойтись. Зависит от содержания. Это правильно, но моих познаний для этого не достаточно. Опять таки, процесс реестра кластеров запускается, а вот дочерние, которые этот главный процесс должен запустить, уже нет. Думается, проблема не с скриптом запуска, а с какими-то разрешениями/зависимостями/etc.

indeviral	# 2 года, 5 месяцев назад (отредактировано 2 года, 5 месяцев назад)
Темы: 39 Сообщения: 3170 Участник с: 10 августа 2013	Сверьте status между ручным и автом запуском. Хотя бы увидим какие именно дочернии процессы не запустились. # systemctl status ваш сервис Ошибки в тексте-неповторимый стиль автора©

vs220	# 2 года, 5 месяцев назад (отредактировано 2 года, 5 месяцев назад)
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	genues какими-то сервис в ручную запускается ( systemctl start ваш сервис при disable) а при старте системы нет ( systemctl enable) ? Задержку в пару минут не пробовали добавить для проверки?

genues

# 2 года, 5 месяцев назад

Темы: 24 Сообщения: 281 Участник с: 26 сентября 2011

indeviral Сверьте status между ручным и автом запуском. Хотя бы увидим какие именно дочернии процессы не запустились. # systemctl status ваш сервис Ручной запуск. ● srv1cv83.service - /etc/init.d/srv1cv83 compatibility Loaded: loaded (/usr/lib/systemd/system/srv1cv83.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2020-09-04 09:15:50 MSK; 33min ago Process: 989 ExecStart=/etc/init.d/srv1cv83 start (code=exited, status=0/SUCCESS) Main PID: 1004 (ragent) Tasks: 527 (limit: 38335) Memory: 3.3G CGroup: /system.slice/srv1cv83.service ├─1004 /opt/1C/v8.3/x86_64/ragent -daemon ├─1024 /opt/1C/v8.3/x86_64/rmngr -port 1541 -host cg-office -range 1560:1591 -clstid 2307c48f-92db-4572-98e0-b0d998c8c61d ├─1120 /opt/1C/v8.3/x86_64/rmngr -port 1542 -host 10.0.0.1 -range 1560:1591 -clstid 6fb3f7de-584e-4ddd-afee-d8c4233a336b ├─1227 /opt/1C/v8.3/x86_64/rmngr -port 1543 -host 10.0.2.1 -range 1560:1591 -clstid e8701d14-e2ea-4209-8f8f-973885c6f4a9 ├─1317 /opt/1C/v8.3/x86_64/rphost -range 1560:1591 -reghost cg-office -regport 1541 -pid a317cd43-fe98-4ec2-a2ee-405560297191 ├─1320 /opt/1C/v8.3/x86_64/rphost -range 1560:1591 -reghost 10.0.0.1 -regport 1542 -pid 8bacf1e0-4860-4431-a8c8-90492e0eced8 └─1324 /opt/1C/v8.3/x86_64/rphost -range 1560:1591 -reghost 10.0.2.1 -regport 1543 -pid 029dc5a6-131f-478e-946b-5d2f154afc10 сен 04 09:15:45 cg-office systemd[1]: Starting /etc/init.d/srv1cv83 compatibility... сен 04 09:15:45 cg-office su[1001]: (to usr1cv8) root on none сен 04 09:15:45 cg-office su[1001]: pam_unix(su-l:session): session opened for user usr1cv8(uid=971) by (uid=0) сен 04 09:15:45 cg-office su[1001]: pam_unix(su-l:session): session closed for user usr1cv8 сен 04 09:15:50 cg-office srv1cv83[989]: Starting 1C:Enterprise 8.3 server: OK сен 04 09:15:50 cg-office systemd[1]: Started /etc/init.d/srv1cv83 compatibility. Автоматический. ● srv1cv83.service - /etc/init.d/srv1cv83 compatibility Loaded: loaded (/usr/lib/systemd/system/srv1cv83.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2020-09-04 09:51:21 MSK; 396ms ago Process: 456 ExecStart=/etc/init.d/srv1cv83 start (code=exited, status=0/SUCCESS) Main PID: 601 (ragent) Tasks: 18 (limit: 38335) Memory: 68.6M CGroup: /system.slice/srv1cv83.service └─601 /opt/1C/v8.3/x86_64/ragent -daemon сен 04 09:51:16 cg-office systemd[1]: Starting /etc/init.d/srv1cv83 compatibility... сен 04 09:51:16 cg-office su[485]: (to usr1cv8) root on none сен 04 09:51:16 cg-office su[485]: pam_unix(su-l:session): session opened for user usr1cv8(uid=971) by (uid=0) сен 04 09:51:16 cg-office su[485]: pam_unix(su-l:session): session closed for user usr1cv8 сен 04 09:51:21 cg-office srv1cv83[456]: Starting 1C:Enterprise 8.3 server: OK сен 04 09:51:21 cg-office systemd[1]: Started /etc/init.d/srv1cv83 compatibility.

vs220	# 2 года, 5 месяцев назад
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	И в деб пакете сервера вроде есть готовый системд сервис запуска, может глянуть и сравнить с вашим

genues	# 2 года, 5 месяцев назад
Темы: 24 Сообщения: 281 Участник с: 26 сентября 2011	vs220 сервис в ручную запускается ( systemctl start ваш сервис при disable) а при старте системы нет ( systemctl enable) ? Запускается, но как бы не полностью. vs220 Задержку в пару минут не пробовали добавить для проверки? Пробовал ExecStartPre=/bin/sleep 30