{"id":1308,"date":"2021-12-09T11:09:42","date_gmt":"2021-12-09T17:09:42","guid":{"rendered":"https:\/\/zewwy.ca\/?p=1308"},"modified":"2021-12-09T11:09:42","modified_gmt":"2021-12-09T17:09:42","slug":"veeam-more-than-one-replica-candidate-found","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2021\/12\/09\/veeam-more-than-one-replica-candidate-found\/","title":{"rendered":"Veeam &#8211; More Than One Replica Candidate Found"},"content":{"rendered":"<h1 style=\"text-align: center;\"><span class=\"ez-toc-section\" id=\"Story_Time\"><\/span>Story Time!<span class=\"ez-toc-section-end\"><\/span><\/h1>\n<h2 style=\"text-align: center;\"><span class=\"ez-toc-section\" id=\"The_Problem\"><\/span>The Problem!<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>So real quick one here. I edited a Replication job and changed it source form production to a backup dataset within the Veeam Replication Job settings. I went to run the replication job and was presented with an error I have no seen before&#8230;<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/Mx9Mkw7.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/i.imgur.com\/Mx9Mkw7.png\" alt=\"\" width=\"532\" height=\"24\" \/><\/a><\/p>\n<p>I had an idea of what happened (I believe the original ESXi host might have been rebuilt) I&#8217;m not 100% sure, but just speculating. I was pretty sure the change I made on the job was not the source of the problem.<\/p>\n<p>Since I wasn&#8217;t concerned about the target VM being re-created entirely I decided to go to Veeam&#8217;s Replica&#8217;s, and right clicked the target VM, and picked Delete from Disk&#8230; to my amazement the same error was presented&#8230;<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/KLLtEkt.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/i.imgur.com\/KLLtEkt.png\" alt=\"\" width=\"752\" height=\"539\" \/><\/a><\/p>\n<p>Alright&#8230; kind of sucks, but here&#8217;s how I resolved it.<\/p>\n<h2 style=\"text-align: center;\"><span class=\"ez-toc-section\" id=\"The_Solution\"><\/span>The Solution<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Sadly I had to right click the Target VM under Veeams Replicas, and instead picked &#8220;Remove from Configuration&#8221;. What&#8217;s really annoying about this is it will remove the source VM from the replication job itself as well.<\/p>\n<p><a href=\"https:\/\/forums.veeam.com\/vmware-vsphere-f24\/replication-source-bug-t76087.html\">Why? Unno Veeams coding choices..<\/a>.<\/p>\n<p>So after successfully removing the target VM from Veeam&#8217;s configuration, I manually deleted the target VM on the host ESXi host. Then I had to reconfigure the replication job and point it to the source VM again. Again if your interested in why that&#8217;s the case see the link above.<\/p>\n<p>After that the job ran successfully. Hope this helps someone.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Story Time! The Problem! So real quick one here. I edited a Replication job and changed it source form production to a backup dataset within the Veeam Replication Job settings. I went to run the replication job and was presented with an error I have no seen before&#8230; I had an idea of what happened &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/zewwy.ca\/index.php\/2021\/12\/09\/veeam-more-than-one-replica-candidate-found\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Veeam &#8211; More Than One Replica Candidate Found&#8221;<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[5,8,236],"tags":[39,392],"class_list":["post-1308","post","type-post","status-publish","format-standard","hentry","category-hypervisors","category-server-administration","category-veeam","tag-failed","tag-replication"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1308","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=1308"}],"version-history":[{"count":1,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1308\/revisions"}],"predecessor-version":[{"id":1309,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1308\/revisions\/1309"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=1308"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=1308"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=1308"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}