{"id":54475,"date":"2022-09-13T09:00:42","date_gmt":"2022-09-13T07:00:42","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=54475"},"modified":"2022-09-11T13:45:49","modified_gmt":"2022-09-11T11:45:49","slug":"veeam-failed-to-acquire-agent-managed-by-error","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-failed-to-acquire-agent-managed-by-error\/","title":{"rendered":"Veeam: \"Failed to acquire agent managed by...\" error"},"content":{"rendered":"

\"veeam-failed-to-acquire-agent-managed-by-01\"<\/p>\n

If you try to configure agent-based VM backups with agents managed by a different Veeam Veeam Backup & Replication<\/a> server, you may experience the \"Failed to acquire agent managed by...\" error.<\/p>\n

This error occurs when you perform the Rescan operation <\/strong>of Protection Groups<\/a> containing Windows or Linux machines managed by agents centrally deployed<\/strong>\u00a0from the Veeam Backup & Replication server.<\/p>\n

\"veeam-failed-to-acquire-agent-managed-by-02\"<\/p>\n

If the processed machines were previously managed<\/strong> by a different Veeam Backup & Replication<\/a> server, you may face the error:<\/p>\n

Failed to acquire agent managed by VBR server.<\/p><\/blockquote>\n

\"veeam-failed-to-acquire-agent-managed-by-03\"<\/p>\n

 <\/p>\n

Fix \"Failed to acquire agent managed by...\" error<\/h2>\n

There are two ways to fix the \"Failed to acquire agent managed by...<\/em>\" error:<\/p>\n

    \n
  • Remove the Veeam's agent<\/li>\n
  • Add a new key in the VBR registry<\/li>\n<\/ul>\n

    The deletion of installed agents can be time consuming<\/strong> if the number of machines to process is quite high and generally is not the ideal solution.<\/p>\n

     <\/p>\n

    Modify the Windows Registry<\/h4>\n

    An easy and quick way to prevent this error is the creation of a new registry key<\/strong>.<\/p>\n

    From your Veeam Backup & Replication server, open the Registry Editor<\/strong> and go to HKEY_LOCAL_MACHINE\\SOFTWARE\\Veeam\\Veeam Backup and Replication<\/strong>.<\/p>\n

    Right click Veeam Backup and Replication<\/strong> and select New > DWORD (32-bit) Value<\/strong>\u00a0option.<\/p>\n

    \"veeam-failed-to-acquire-agent-managed-by-04\"<\/p>\n

    Name the create new key as AgentDiscoveryIgnoreOwnership<\/strong> and enter 1 as Value data<\/strong>. Click OK<\/strong> to confirm.<\/p>\n

    \"veeam-failed-to-acquire-agent-managed-by-05\"<\/p>\n

    The new AgentDiscoveryIgnoreOwnership<\/em> registry key has been created successfully.<\/p>\n

    \"veeam-failed-to-acquire-agent-managed-by-06\"<\/p>\n

    Now go to the Inventory<\/strong> area and select Physical Infrastructure<\/strong> section. Right click the Protection Group to process and select Rescan<\/strong>.<\/p>\n

    The rescan operation for Windows machines<\/strong> is now completed successfully.<\/p>\n

    \"veeam-failed-to-acquire-agent-managed-by-07\"<\/p>\n

    Also the rescan operation for Linux machines<\/strong> completes successfully.<\/p>\n

    \"veeam-failed-to-acquire-agent-managed-by-08\"<\/p>\n

    With this simple configuration it is now possible to complete the rescan procedure<\/strong> without problems.<\/p>\n

    \"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

    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\u00a0from 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 <\/p>\n","protected":false},"author":3,"featured_media":54476,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2138,933],"tags":[942,2514,579,2513],"class_list":["post-54475","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","tag-agent-en","tag-agentdiscoveryignoreownership","tag-backup-en","tag-failed-to-acquire-agent-managed-by","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/54475","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=54475"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/54475\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/54476"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=54475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=54475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=54475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}