<?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: why it is necessary to restrict a destination volume for volume snapmirror? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/why-it-is-necessary-to-restrict-a-destination-volume-for-volume-snapmirror/m-p/8838#M2007</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For the initialize the volume can't be online since it gets a block for block baseline from the source and wipes out any data (if any) already in the volume so it is restricted before that process.&amp;nbsp; After initialization the volume automatically comes online read only.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2013 15:31:59 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2013-03-01T15:31:59Z</dc:date>
    <item>
      <title>why it is necessary to restrict a destination volume for volume snapmirror?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/why-it-is-necessary-to-restrict-a-destination-volume-for-volume-snapmirror/m-p/8834#M2005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;why it is necessary to restrict a destination volume for volume snapmirror?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:08:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/why-it-is-necessary-to-restrict-a-destination-volume-for-volume-snapmirror/m-p/8834#M2005</guid>
      <dc:creator>abhisheksri</dc:creator>
      <dc:date>2025-06-05T06:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: why it is necessary to restrict a destination volume for volume snapmirror?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/why-it-is-necessary-to-restrict-a-destination-volume-for-volume-snapmirror/m-p/8838#M2007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For the initialize the volume can't be online since it gets a block for block baseline from the source and wipes out any data (if any) already in the volume so it is restricted before that process.&amp;nbsp; After initialization the volume automatically comes online read only.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 15:31:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/why-it-is-necessary-to-restrict-a-destination-volume-for-volume-snapmirror/m-p/8838#M2007</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2013-03-01T15:31:59Z</dc:date>
    </item>
  </channel>
</rss>

