<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VMware datastore protection - rename secondary storage vol? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4224#M852</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have some VMware datastores I want to backup using OnCommand 5.01/OCHP 1.1 with VMware consistent backups and SnapVault to a remote filer. Is there a way to control what the SV destination volume ("Backup physical resource") is called? At the moment it is creating a backup volume with the same name as my primary volume which I would prefer to avoid. My secondary volume is created by a provisioning policy and I cannot edit the naming properties of the dataset via the NMC. Maybe it can be done from the CLI? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a known way to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Adam&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS I have had inconsistent results when manually renaming the secondary volume; the new name appears in some views (NMC Data\Provisioning) but not others (OCweb\Datasets\Relationship details). After renaming the backup vol and attempting to back up primary using the storage service I sometimes get the error "NDMP communication error: NDMP_SVS_MODIFY_RELATIONSHIP: 0x20500306 (SV NO RELATIONSHIP)" although &lt;STRONG&gt;snapvault status&lt;/STRONG&gt; on the secondary filer indicates the relationship is OK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:23:25 GMT</pubDate>
    <dc:creator>akw_white</dc:creator>
    <dc:date>2025-06-05T06:23:25Z</dc:date>
    <item>
      <title>VMware datastore protection - rename secondary storage vol?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4224#M852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have some VMware datastores I want to backup using OnCommand 5.01/OCHP 1.1 with VMware consistent backups and SnapVault to a remote filer. Is there a way to control what the SV destination volume ("Backup physical resource") is called? At the moment it is creating a backup volume with the same name as my primary volume which I would prefer to avoid. My secondary volume is created by a provisioning policy and I cannot edit the naming properties of the dataset via the NMC. Maybe it can be done from the CLI? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a known way to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Adam&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS I have had inconsistent results when manually renaming the secondary volume; the new name appears in some views (NMC Data\Provisioning) but not others (OCweb\Datasets\Relationship details). After renaming the backup vol and attempting to back up primary using the storage service I sometimes get the error "NDMP communication error: NDMP_SVS_MODIFY_RELATIONSHIP: 0x20500306 (SV NO RELATIONSHIP)" although &lt;STRONG&gt;snapvault status&lt;/STRONG&gt; on the secondary filer indicates the relationship is OK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:23:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4224#M852</guid>
      <dc:creator>akw_white</dc:creator>
      <dc:date>2025-06-05T06:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: VMware datastore protection - rename secondary storage vol?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4230#M853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adam,&lt;/P&gt;&lt;P&gt;You can control the naming of the secondary volume name that is generated by using "Naming Properties" of the dataset. On OC WebUI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select the dataset (of VMware type)&amp;gt;Click on Edit&amp;gt;Expand the Name(right arrow)&amp;gt;Select the Naming properties. Under this tab you can customize the way in which names are generated for Snapshot copies, Secondary volume &amp;amp; Secondary qtree. Please refer the image attached for the screenshot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Amir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jul 2012 07:03:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4230#M853</guid>
      <dc:creator>amirm</dc:creator>
      <dc:date>2012-07-05T07:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: VMware datastore protection - rename secondary storage vol?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4238#M854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adam,&lt;/P&gt;&lt;P&gt;Once you rename your volumes, snapvault modify needs to be run to notify the snapvault relationship that the volume names have been changed.&amp;nbsp; Thats the reason you get the mentioned NDMP error.BTW how do you like to name your snapvault destination volumes ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;adai&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2012 04:47:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4238#M854</guid>
      <dc:creator>adaikkap</dc:creator>
      <dc:date>2012-07-06T04:47:03Z</dc:date>
    </item>
    <item>
      <title>Re: VMware datastore protection - rename secondary storage vol?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4243#M855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks all. Amir I will need to check that because for some reason I never noticed those settings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adai - normally I use %V_dr for the secondary volume name; in this case I would probably use something like %V_vmbackup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2012 01:04:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/VMware-datastore-protection-rename-secondary-storage-vol/m-p/4243#M855</guid>
      <dc:creator>akw_white</dc:creator>
      <dc:date>2012-07-09T01:04:35Z</dc:date>
    </item>
  </channel>
</rss>

