{"id":14117,"date":"2015-10-07T10:00:00","date_gmt":"2015-10-07T08:00:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=14117"},"modified":"2020-03-15T18:11:01","modified_gmt":"2020-03-15T17:11:01","slug":"veeam-8-nfc-storage-unavailable-error-with-vsphere-6-0-upd1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-8-nfc-storage-unavailable-error-with-vsphere-6-0-upd1\/","title":{"rendered":"Veeam 8 NFC storage unavailable error with vSphere 6.0 Upd1"},"content":{"rendered":"<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg01.jpg\" alt=\"veeamerror60upd1upg01\" width=\"602\" height=\"202\" border=\"0\" \/><\/p>\n<p>After applying vSphere 6.0 Update 1, Veeam backup job fails with an \"NFC storage unavailable\" error due to the protocol SSLv3 disabled by VMware for security reasons.<\/p>\n<p>Since Veeam Backup &amp; Replication is <strong>designed to use TSL or SSL<\/strong>, due to a bug in the parsing the list of supported SSL\/TLS protocol versions, Veeam backup job fails because doesn't use TLS for NFC communications if SSL fails.<\/p>\n<p><!--more--><\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg02.jpg\" alt=\"veeamerror60upd1upg02\" width=\"600\" height=\"382\" border=\"0\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Workaround<\/h2>\n<p>Fastest but less secure workaround is to enable the support for <strong>SSLv3 on Authd service 902<\/strong> in ESXi again.<\/p>\n<p>Connect the host ESXi to edit using an <strong>SSH client<\/strong> like PuTTY.<\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg03.jpg\" alt=\"veeamerror60upd1upg03\" width=\"600\" height=\"166\" border=\"0\" \/><\/p>\n<p>Make a backup of <em>\/etc\/vmware\/config<\/em> file.<\/p>\n<p><span style=\"color: #0000a0;\"># cp \/etc\/vmware\/config \/etc\/vmware\/config.bak<\/span><\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg04.jpg\" alt=\"veeamerror60upd1upg04\" width=\"600\" height=\"38\" border=\"0\" \/><\/p>\n<p>Edit the <em>\/etc\/vmware\/config<\/em> file and <strong>append the following line<\/strong> at the end of the file:<\/p>\n<blockquote><p>vmauthd.ssl.noSSLv3 = false<\/p><\/blockquote>\n<p><span style=\"color: #0000a0;\"># vi \/etc\/vmware\/config<\/span><\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg05.jpg\" alt=\"veeamerror60upd1upg05\" width=\"600\" height=\"115\" border=\"0\" \/><\/p>\n<p>Restart the <strong>rhttpproxy service<\/strong> with the command:<\/p>\n<p><span style=\"color: #0000a0;\"># \/etc\/init.d\/rhttpproxy restart<\/span><\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg06.jpg\" alt=\"veeamerror60upd1upg06\" width=\"600\" height=\"83\" border=\"0\" \/><\/p>\n<p>Repeat <strong>same procedure<\/strong> for all other hosts in the cluster.<\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg07.jpg\" alt=\"veeamerror60upd1upg07\" width=\"600\" height=\"87\" border=\"0\" \/><\/p>\n<p>Run the failed Veeam <strong>backup job<\/strong> again.<\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg08.jpg\" alt=\"veeamerror60upd1upg08\" width=\"600\" height=\"443\" border=\"0\" \/><\/p>\n<p>This time the backup job has been completed successfully.<\/p>\n<p><img decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin: 0px auto; display: block; padding-right: 0px; border: 0px;\" title=\"veeamerror60upd1upg09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2015\/10\/veeamerror60upd1upg09.jpg\" alt=\"veeamerror60upd1upg09\" width=\"600\" height=\"474\" border=\"0\" \/><\/p>\n<p>Veeam has a hotfix to solve this matter that will be included in the upcoming <strong>Veeam Backup &amp; Replication 8.0 Update 3<\/strong>.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"firma\" title=\"\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>After applying vSphere 6.0 Update 1, Veeam backup job fails with an \"NFC storage unavailable\" error due to the protocol SSLv3 disabled by VMware for security reasons. Since Veeam Backup &amp; Replication is designed to use TSL or SSL, due to a bug in the parsing the list of supported SSL\/TLS protocol versions, Veeam backup job fails because doesn't use TLS for NFC communications if SSL fails.<\/p>\n","protected":false},"author":3,"featured_media":14108,"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,903],"tags":[2165,584],"class_list":["post-14117","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","category-vmware-en","tag-nfc-storage-unavailable-en-2","tag-veeam-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/14117","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=14117"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/14117\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/14108"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=14117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=14117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=14117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}