{"id":35624,"date":"2018-10-18T09:00:10","date_gmt":"2018-10-18T07:00:10","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=35624"},"modified":"2020-03-15T18:06:59","modified_gmt":"2020-03-15T17:06:59","slug":"veeam-backup-fails-after-installing-vsphere-6-7-update-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-backup-fails-after-installing-vsphere-6-7-update-1\/","title":{"rendered":"Veeam backup fails after installing vSphere 6.7 Update 1"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-35625 size-large\" title=\"veeam-backup-fails-vsphere-67-update1-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/veeam-backup-fails-vsphere-67-update1-01-600x201.jpg\" alt=\"veeam-backup-fails-vsphere-67-update1-01\" width=\"600\" height=\"201\" \/><\/p>\n<p>After installing VMware vSphere 6.7 Update 1, Veeam backup fails due to a <strong>change in the\u00a0vSphere\u00a0API\u00a06.7<\/strong> introduced by VMware.<\/p>\n<p>The processed backup jobs fail with the error \"Object reference not set to an instance of an object\".<!--more--><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35907 size-large\" title=\"veeam-backup-fails-vsphere-67-update1-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/veeam-backup-fails-vsphere-67-update1-02-600x174.jpg\" alt=\"veeam-backup-fails-vsphere-67-update1-02\" width=\"600\" height=\"174\" \/><\/p>\n<p>If you use Veeam as your backup solution, <strong>avoid updating<\/strong> your infrastructure with vSphere 6.7 Update 1 until the issue has been fixed.<\/p>\n<p>&nbsp;<\/p>\n<h2>Workaround for Veeam Backup<\/h2>\n<p>Currently there is not a fix for this problem but <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-backup-and-replication-9-5-update-3a-now-available\/\">Veeam<\/a> provided a <strong>temporary workaround<\/strong> to allow the jobs to be completed successfully.<\/p>\n<p>In Veeam Backup and Replication Server you need to <strong>create a registry key<\/strong> in the\u00a0<strong>HKLM\\SOFTWARE\\Veeam\\Veeam Backup and Replication<\/strong> section.<\/p>\n<p>Open the <strong>Registry Editor<\/strong>, right click the <strong>Veeam Backup and Replication<\/strong> item and select <strong>New &gt; Multi-String Value<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35629 size-large\" title=\"veeam-backup-fails-vsphere-67-update1-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/veeam-backup-fails-vsphere-67-update1-03-600x342.jpg\" alt=\"veeam-backup-fails-vsphere-67-update1-03\" width=\"600\" height=\"342\" \/><\/p>\n<p>Create the key\u00a0<strong>VMwareOverrideApiVersion<\/strong> and assign the value <strong>6.7.1=6.7<\/strong>. Click <strong>OK<\/strong> to confirm.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35633 size-large\" title=\"veeam-backup-fails-vsphere-67-update1-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/veeam-backup-fails-vsphere-67-update1-04-600x339.jpg\" alt=\"veeam-backup-fails-vsphere-67-update1-04\" width=\"600\" height=\"339\" \/><\/p>\n<p>The created new registry key.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35635 size-large\" title=\"veeam-backup-fails-vsphere-67-update1-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/veeam-backup-fails-vsphere-67-update1-05-600x339.jpg\" alt=\"veeam-backup-fails-vsphere-67-update1-05\" width=\"600\" height=\"339\" \/><\/p>\n<p>After creating this registry key, <strong>reboot the server<\/strong> and <strong>re-run the failed backup jobs<\/strong>. This time the backup job completes successfully.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35912 size-large\" title=\"veeam-backup-fails-vsphere-67-update1-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/10\/veeam-backup-fails-vsphere-67-update1-06-600x196.jpg\" alt=\"veeam-backup-fails-vsphere-67-update1-06\" width=\"600\" height=\"196\" \/><\/p>\n<p>As stated by Veeam in the <a href=\"https:\/\/www.veeam.com\/kb2784\" target=\"_blank\" rel=\"noopener noreferrer\">KB2784<\/a>, <strong>this is just a workaround<\/strong> since overriding the API version may affect other Veeam functionalities.<\/p>\n<p>The official support for vSphere 6.7 Update 1 will be included in the <strong>upcoming Veeam Backup and Replication 9.5 Update 4<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h4>UPDATE<\/h4>\n<p>The issue has been fixed in <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-backup-replication-9-5-update-4-upgrade-procedure\/\">Veeam Backup &amp; Replication 9.5 Update 4<\/a>.<\/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>After installing VMware vSphere 6.7 Update 1, Veeam backup fails due to a change in the\u00a0vSphere\u00a0API\u00a06.7 introduced by VMware. The processed backup jobs fail with the error \"Object reference not set to an instance of an object\".<\/p>\n","protected":false},"author":3,"featured_media":35625,"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,875,584,1985],"class_list":["post-35624","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-backup-en","category-veeam-en","tag-backup-en","tag-update-1-en","tag-veeam-en","tag-vsphere-6-7-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35624","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=35624"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35624\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/35625"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=35624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=35624"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=35624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}