{"id":713,"date":"2011-02-08T07:34:39","date_gmt":"2011-02-07T21:34:39","guid":{"rendered":"https:\/\/www.penguinpunk.net\/blog\/?p=713"},"modified":"2011-02-08T07:36:40","modified_gmt":"2011-02-07T21:36:40","slug":"vmware-srm-advanced-setting-for-snap-prefix","status":"publish","type":"post","link":"https:\/\/www.penguinpunk.net\/blog\/vmware-srm-advanced-setting-for-snap-prefix\/","title":{"rendered":"VMware &#8211; SRM advanced setting for snap prefix"},"content":{"rendered":"<p>We haven&#8217;t been doing this in our production configurations, but if you want to change the behaviour of SRM with regards to the &#8220;snap-xxx&#8221; prefix on replica datastores, you need to modify an advanced setting in SRM. So, go to the vSphere client &#8211; SRM, and right-click on Site Recovery and select Advanced Settings. Under SanProvider, there&#8217;s an option called &#8220;SanProvider.fixRecoveredDatastoreNames&#8221; with a little checkbox that needs to be ticked to prevent the recovered datastores being renamed with the unsightly prefix.<\/p>\n<p>You can also do this when manually mounting snapshots or mirrors with the help of the esxcfg-volume command &#8211; but that&#8217;s a story for another time.<\/p>\n<p style=\"text-align: center;\"><a href=\"https:\/\/www.penguinpunk.net\/blog\/wp-content\/uploads\/2011\/02\/SRM.Advanced.Settings.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-717\" title=\"SRM.Advanced.Settings\" src=\"https:\/\/www.penguinpunk.net\/blog\/wp-content\/uploads\/2011\/02\/SRM.Advanced.Settings.png\" alt=\"\" width=\"580\" height=\"486\" srcset=\"https:\/\/www.penguinpunk.net\/blog\/wp-content\/uploads\/2011\/02\/SRM.Advanced.Settings.png 725w, https:\/\/www.penguinpunk.net\/blog\/wp-content\/uploads\/2011\/02\/SRM.Advanced.Settings-300x251.png 300w\" sizes=\"auto, (max-width: 580px) 100vw, 580px\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>We haven&#8217;t been doing this in our production configurations, but if you want to change the behaviour of SRM with regards to the &#8220;snap-xxx&#8221; prefix on replica datastores, you need to modify an advanced setting in SRM. So, go to the vSphere client &#8211; SRM, and right-click on Site Recovery and select Advanced Settings. Under [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[356,4],"tags":[358,9,793,92,40,359,216,357,26,19,786],"class_list":["post-713","post","type-post","status-publish","format-standard","hentry","category-srm-vmware","category-vmware","tag-advanced","tag-esx","tag-esxi","tag-mirrorview","tag-san","tag-snap","tag-srm","tag-srm4","tag-virtualcenter","tag-virtualisation","tag-vmware"],"_links":{"self":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts\/713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/comments?post=713"}],"version-history":[{"count":5,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts\/713\/revisions"}],"predecessor-version":[{"id":719,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts\/713\/revisions\/719"}],"wp:attachment":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/media?parent=713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/categories?post=713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/tags?post=713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}