<?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 Looking to automate clones creation of cifs and nfs shares on mirror-vault destination volumes in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Looking-to-automate-clones-creation-of-cifs-and-nfs-shares-on-mirror-vault/m-p/168947#M6429</link>
    <description>&lt;P&gt;Looking to automate the clone, mount and share creation from snapmirror destination volumes. I was toying with the idea of creating a snapshot from a script at the source (something as simple as DR), and then creating a script at the destination that would create a clone using "DR" as the parent. This doesn't work because we are using the mirror-vault relationships, and this won't copy all snapshots (I would hope they would change this at some point, but I am not holding my breath).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can update the snapshot policy to create a single snapshot with the smlabel DR, and that sorta works out here. The snapshot winds up being named:&lt;/P&gt;&lt;P&gt;dr.2021-08-02_1555&lt;/P&gt;&lt;P&gt;If there is only one of these at the destination, I am looking for a way to select whatever is labeled "dr.*" as the parent snapshot.&lt;/P&gt;&lt;P&gt;I can do something like this:&lt;/P&gt;&lt;P&gt;Get-ncSnapshot $vol_name | ?{ $_.Name -like "dr.*"}&lt;/P&gt;&lt;P&gt;and only get a return of the "dr.*" snapshot, but I don't know to get a clone based off of this:&lt;/P&gt;&lt;P&gt;get-ncvol $vol_name | New-Ncvolclone -CloneVolume syseng_DR -parentsnapshot { 'Get-ncSnapshot syseng_sm | ?( $_.Name -like "dr.*")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 10:17:27 GMT</pubDate>
    <dc:creator>SomeGuy</dc:creator>
    <dc:date>2025-06-04T10:17:27Z</dc:date>
    <item>
      <title>Looking to automate clones creation of cifs and nfs shares on mirror-vault destination volumes</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Looking-to-automate-clones-creation-of-cifs-and-nfs-shares-on-mirror-vault/m-p/168947#M6429</link>
      <description>&lt;P&gt;Looking to automate the clone, mount and share creation from snapmirror destination volumes. I was toying with the idea of creating a snapshot from a script at the source (something as simple as DR), and then creating a script at the destination that would create a clone using "DR" as the parent. This doesn't work because we are using the mirror-vault relationships, and this won't copy all snapshots (I would hope they would change this at some point, but I am not holding my breath).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can update the snapshot policy to create a single snapshot with the smlabel DR, and that sorta works out here. The snapshot winds up being named:&lt;/P&gt;&lt;P&gt;dr.2021-08-02_1555&lt;/P&gt;&lt;P&gt;If there is only one of these at the destination, I am looking for a way to select whatever is labeled "dr.*" as the parent snapshot.&lt;/P&gt;&lt;P&gt;I can do something like this:&lt;/P&gt;&lt;P&gt;Get-ncSnapshot $vol_name | ?{ $_.Name -like "dr.*"}&lt;/P&gt;&lt;P&gt;and only get a return of the "dr.*" snapshot, but I don't know to get a clone based off of this:&lt;/P&gt;&lt;P&gt;get-ncvol $vol_name | New-Ncvolclone -CloneVolume syseng_DR -parentsnapshot { 'Get-ncSnapshot syseng_sm | ?( $_.Name -like "dr.*")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:17:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Looking-to-automate-clones-creation-of-cifs-and-nfs-shares-on-mirror-vault/m-p/168947#M6429</guid>
      <dc:creator>SomeGuy</dc:creator>
      <dc:date>2025-06-04T10:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: Looking to automate clones creation of cifs and nfs shares on mirror-vault destination volumes</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Looking-to-automate-clones-creation-of-cifs-and-nfs-shares-on-mirror-vault/m-p/169045#M6430</link>
      <description>&lt;P&gt;What error do you get from your last line of code? You can see an example done here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-NcVolClone-suggestions-for-DR-Recovery-Script/td-p/111689" target="_blank" rel="noopener"&gt;https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/New-NcVolClone-suggestions-for-DR-Recovery-Script/td-p/111689&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The traditional way of DR in ONTAP is just a standard snapmirror (or MirrorAndVault if you want to control the retention),&amp;nbsp; and failing-over using the base snapshot, that's a bit more straightforward with reverse, and also (if done right) locks your source to write while you active in DR.&lt;/P&gt;&lt;P&gt;&lt;A href="https://practical-admin.com/blog/netapp-powershell-toolkit-101-data-protection/" target="_blank" rel="noopener"&gt;https://practical-admin.com/blog/netapp-powershell-toolkit-101-data-protection/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With this, you can also pre-create your CIFS shares and NFS exports. I simply compare them nightly between the two filers with PS compare-object to see the ACL and settings are identical.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Aug 2021 20:33:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Looking-to-automate-clones-creation-of-cifs-and-nfs-shares-on-mirror-vault/m-p/169045#M6430</guid>
      <dc:creator>GidonMarcus</dc:creator>
      <dc:date>2021-08-05T20:33:34Z</dc:date>
    </item>
  </channel>
</rss>

