{"id":36884,"date":"2019-02-28T09:00:29","date_gmt":"2019-02-28T08:00:29","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=36884"},"modified":"2021-06-10T16:22:31","modified_gmt":"2021-06-10T14:22:31","slug":"veeam-re-map-moref-id-protected-vms-when-replacing-vcenter-server","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-re-map-moref-id-protected-vms-when-replacing-vcenter-server\/","title":{"rendered":"Veeam: re-map MoRef ID of protected VMs when replacing the vCenter Server"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-37807 size-full\" title=\"veeam-remap-moref-id-virtual-machine-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/02\/veeam-remap-moref-id-virtual-machine-01.jpg\" alt=\"veeam-remap-moref-id-virtual-machine-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>When you replace the\u00a0<a href=\"https:\/\/nolabnoparty.com\/en\/recover-failed-vcenter-ha\/\">vCenter Server<\/a> configured in Veeam Backup &amp; Replication, you need to re-map MoRef ID of protected VMs to <strong>complete\u00a0backup jobs successfully<\/strong>.<\/p>\n<p>During the migration to a new vCenter or if an inventory change occurs in the vCenter, the virtual machine <strong>MoRef ID changes<\/strong>\u00a0with the result of a failure of the backup job associated with\u00a0the error:<\/p>\n<blockquote><p><em>Object with reference &lt;vmname&gt; was not found in the hierarchy cache<\/em><\/p><\/blockquote>\n<p><!--more--><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-37809 size-large\" title=\"veeam-remap-moref-id-virtual-machine-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/02\/veeam-remap-moref-id-virtual-machine-02-600x98.jpg\" alt=\"veeam-remap-moref-id-virtual-machine-02\" width=\"600\" height=\"98\" \/><\/p>\n<p>This article has been written for\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/\" target=\"_blank\" rel=\"noopener noreferrer\">StarWind blog<\/a>\u00a0and can be found in\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/veeam-re-map-moref-id-of-protected-vms-when-replacing-the-vcenter-server\" target=\"_blank\" rel=\"noopener noreferrer\">this page<\/a>. It covers the full procedure to\u00a0<strong>replace the vCenter Server<\/strong>\u00a0in your vSphere infrastructure without altering the backup chains.<\/p>\n<p>&nbsp;<\/p>\n<h2>Re-map MoRef IDs with vCenter Migration Utility<\/h2>\n<p>To replace the vCenter Server configured in Veeam Backup &amp; Replication, you need to <strong>keep same MoRef IDs<\/strong> for all protected virtual machines. In vSphere 6.5 and 6.7, the <a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-vcsa-6-5-to-6-7-pt-2\/\">Upgrade option<\/a>\u00a0available in<strong> Stage 1: Deploy appliance<\/strong> wizard takes care of migrating also the virtual machine's MoRef IDs.<\/p>\n<p>If you can't perform a successfull migration using the VMware Migration utility or if the source vCenter Server is corrupted or failed, <strong>as a last resort\u00a0<\/strong>the migration can be achieved using the\u00a0<a href=\"https:\/\/www.veeam.com\/download_add_packs\/vmware-esx-backup\/kb2136-2\/\" target=\"_blank\" rel=\"noopener noreferrer\">vCenter Migration Utility<\/a> available at Veeam website. Although is <strong>not officially supported by Veeam<\/strong>, this tool allows to\u00a0<strong>re-map the MoRef ID's<\/strong>\u00a0keeping the\u00a0backup\u00a0<strong>incremental chains intact<\/strong>.<\/p>\n<p>If you use Cloud Connect repository, the <strong>tool cannot fix jobs targeting<\/strong> a Cloud Connect repository but an\u00a0<strong>Active Full backup<\/strong> should be used instead.<\/p>\n<p>After <strong>re-mapping the MoRef ID<\/strong> of protected VMs, the backup job is executed and completed successfully.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-37811 size-large\" title=\"veeam-remap-moref-id-virtual-machine-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/02\/veeam-remap-moref-id-virtual-machine-03-600x459.jpg\" alt=\"veeam-remap-moref-id-virtual-machine-03\" width=\"600\" height=\"459\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Compatibility<\/h2>\n<p>The tool works also to migrate the MoRef IDs from <strong>vCenter version 6.7 U3l to version 7.0 U2b<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<p>Read the\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/veeam-re-map-moref-id-of-protected-vms-when-replacing-the-vcenter-server\" target=\"_blank\" rel=\"noopener noreferrer\">full article<\/a>\u00a0on StarWind blog.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you replace the\u00a0vCenter Server configured in Veeam Backup &amp; Replication, you need to re-map MoRef ID of protected VMs to complete\u00a0backup jobs successfully. During the migration to a new vCenter or if an inventory change occurs in the vCenter, the virtual machine MoRef ID changes\u00a0with the result of a failure of the backup job associated with\u00a0the error: Object with reference &lt;vmname&gt; was not found in the hierarchy cache<\/p>\n","protected":false},"author":3,"featured_media":37807,"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":[903,2138,933],"tags":[579,1947,583,584],"class_list":["post-36884","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-backup-en","category-veeam-en","tag-backup-en","tag-moref-id","tag-vcenter-en","tag-veeam-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/36884","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=36884"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/36884\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/37807"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=36884"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=36884"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=36884"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}