<?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: Can Snapmirror Volume would be Read/Write 24*7 in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42735#M10054</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do not mix to things:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cloning of the SnapMirror destination doesn't allow to change anything in the parent volume, yet you logically see a full, read/write accessible entity. So taking this further, if you change every single block in your clone, you will effectively create a 100% size capacity overhead. Or - if you wish to do so - you can split the clone earlier &amp;amp; you straight away have two physical copies: one read-only parent &amp;amp; the new read/write accessible child volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bottom line: you can write to the clone, no matter whether you split it, or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Sep 2009 22:48:40 GMT</pubDate>
    <dc:creator>radek_kubka</dc:creator>
    <dc:date>2009-09-11T22:48:40Z</dc:date>
    <item>
      <title>Can Snapmirror Volume would be Read/Write 24*7</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42726#M10050</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know can Secondary Snapmirror Volume would be Read/Write 24*7 so that if i create a clones of secondary snapmirror volume it will also be available Read/Write 24*7..........Can it be possible ???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per my understanding so far Snapmirror Volumes are read only and if i create a clone of it then that will also be a read only where as to make a Clone writeable we need to split the realation ship of&amp;nbsp; Snapmirror.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly suggest where is the gap asap...........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Rohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:24:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42726#M10050</guid>
      <dc:creator>rohit_kalia</dc:creator>
      <dc:date>2025-06-05T07:24:11Z</dc:date>
    </item>
    <item>
      <title>Re: Can Snapmirror Volume would be Read/Write 24*7</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42730#M10052</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rohit,&lt;/P&gt;&lt;P&gt;when a source volume and destination volume are in snapmirrored state and you schedule the relation ship between to update secondary volume then destination will be read- only, untill and unless you break the relation ship between the existing the volumes then the&amp;nbsp; snapmirrored destination volume can be read and write. when you clone the secondary volume it can be read and write when you split it from parent volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Sep 2009 18:07:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42730#M10052</guid>
      <dc:creator>netappnasadmin</dc:creator>
      <dc:date>2009-09-11T18:07:41Z</dc:date>
    </item>
    <item>
      <title>Re: Can Snapmirror Volume would be Read/Write 24*7</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42735#M10054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do not mix to things:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cloning of the SnapMirror destination doesn't allow to change anything in the parent volume, yet you logically see a full, read/write accessible entity. So taking this further, if you change every single block in your clone, you will effectively create a 100% size capacity overhead. Or - if you wish to do so - you can split the clone earlier &amp;amp; you straight away have two physical copies: one read-only parent &amp;amp; the new read/write accessible child volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bottom line: you can write to the clone, no matter whether you split it, or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Sep 2009 22:48:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Can-Snapmirror-Volume-would-be-Read-Write-24-7/m-p/42735#M10054</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2009-09-11T22:48:40Z</dc:date>
    </item>
  </channel>
</rss>

