<?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 Re: Workflow for cDot equivalent of 7dot Protection Manager topology &amp;quot;Backup, Then Mirror&amp;quot; in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74546#M15534</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Agree, but the difference is that dfm dataset concepts require provisioning primary, backup and mirror while the policies and schedules are to be pre-created.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Sep 2013 09:40:22 GMT</pubDate>
    <dc:creator>mmodi</dc:creator>
    <dc:date>2013-09-26T09:40:22Z</dc:date>
    <item>
      <title>Workflow for cDot equivalent of 7dot Protection Manager topology "Backup, Then Mirror"</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74534#M15527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks to our technical PS colleagues, I have been able to achieve with cDot / WFA, what 7Dot and Protection Manager enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that the schedules and snapmirror polices need to exist before hand during the deployment stage.&lt;/P&gt;&lt;P&gt;This is to ensure the workflow inputs remain simple.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:53:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74534#M15527</guid>
      <dc:creator>mmodi</dc:creator>
      <dc:date>2025-06-05T05:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow for cDot equivalent of 7dot Protection Manager topology "Backup, Then Mirror"</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74540#M15531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just FYI. WFA 2.1 has a similar workflow called "Create SnapVault then SnapMirror cascade". You could also use that as a starting point and then add the primary provisioning functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;neelesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Sep 2013 16:21:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74540#M15531</guid>
      <dc:creator>nthakur</dc:creator>
      <dc:date>2013-09-25T16:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow for cDot equivalent of 7dot Protection Manager topology "Backup, Then Mirror"</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74546#M15534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Agree, but the difference is that dfm dataset concepts require provisioning primary, backup and mirror while the policies and schedules are to be pre-created.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 09:40:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Workflow-for-cDot-equivalent-of-7dot-Protection-Manager-topology-quot-Backup/m-p/74546#M15534</guid>
      <dc:creator>mmodi</dc:creator>
      <dc:date>2013-09-26T09:40:22Z</dc:date>
    </item>
  </channel>
</rss>

