-
- Lurker
- Posts: 2
- Liked: never
- Joined: Feb 08, 2022 4:13 pm
- Full Name: Matt
- Contact:
Failed to acquire agent managed by (other) server
While attempting to add an existing backed up server to the physical infrastructure with an existing agent to a second backup device I receive the error message "Skipping (backed up server) Details: Failed to acquire agent managed by (first backup device) VBR server.
I have two backup up devices and a collection of servers to backup with agents installed on those servers. I was attempting to replicate the backup jobs on the second backup device and run backup jobs at different intervals on the two backup devices. This error leads me to believe this may not be possible? I am attempting to create a redundant backup in the event my primary backup device is down and am wondering what is possible.
Using Enterprise Plus edition.
Thanks.
I have two backup up devices and a collection of servers to backup with agents installed on those servers. I was attempting to replicate the backup jobs on the second backup device and run backup jobs at different intervals on the two backup devices. This error leads me to believe this may not be possible? I am attempting to create a redundant backup in the event my primary backup device is down and am wondering what is possible.
Using Enterprise Plus edition.
Thanks.
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Failed to acquire agent managed by (other) server
Hello Matt,
It's not possible to manage agent via multiple backup servers. You can create a backup copy job from your primary repository to a secondary repository if you are looking for a way to achieve data redundancy. Hope it helps!
It's not possible to manage agent via multiple backup servers. You can create a backup copy job from your primary repository to a secondary repository if you are looking for a way to achieve data redundancy. Hope it helps!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Feb 08, 2022 4:13 pm
- Full Name: Matt
- Contact:
Re: Failed to acquire agent managed by (other) server
Hi Dima,
I was looking to achieve backup infrastructure redundancy along with Data redundancy. Thank you for you response I will keep the backup copy job in mind if I need it.
I was looking to achieve backup infrastructure redundancy along with Data redundancy. Thank you for you response I will keep the backup copy job in mind if I need it.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Oct 02, 2022 10:09 am
- Full Name: mohamed abuelatta
- Contact:
Re: Failed to acquire agent managed by (other) server
HI
i have the same problem but now i dont want to have more than 1 manager i just want to reset the other manager and make the current server manager to itself how to make that ?
how to delete the new manager i already uninstalled veeam from the other device.
i have the same problem but now i dont want to have more than 1 manager i just want to reset the other manager and make the current server manager to itself how to make that ?
how to delete the new manager i already uninstalled veeam from the other device.
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Failed to acquire agent managed by (other) server
Mohamed,
Remove the machine from your old B&R server and add it to a new B&R server - that should work. Thanks!
Remove the machine from your old B&R server and add it to a new B&R server - that should work. Thanks!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Mar 24, 2023 1:45 am
- Full Name: Rodrigo Miranda
- Contact:
Re: Failed to acquire agent managed by (other) server
Open regedit in client, search to
\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam EndPoint Backup
Delete the key: VBRServerId
and: VBRServerName
Try again to add this client.
\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam EndPoint Backup
Delete the key: VBRServerId
and: VBRServerName
Try again to add this client.
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Failed to acquire agent managed by (other) server
Hi Rodrigo
I didn't tested your solution, but we have a official registry key which allows a new VBR to take over an agent:
Veeam Backup & Replication Pre-V12 versions:
Veeam Backup & Replication V12
Please note:
- Make sure, the old Veeam Server is powered off
- Remove the key immediately after the new VBR server has taken over the agent
Best,
Fabian
I didn't tested your solution, but we have a official registry key which allows a new VBR to take over an agent:
Veeam Backup & Replication Pre-V12 versions:
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
AgentDiscoveryIgnoreOwnership DWORD=1
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
ProtectionGroupIgnoreOwnership DWORD=1
- Make sure, the old Veeam Server is powered off
- Remove the key immediately after the new VBR server has taken over the agent
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 8 guests