<?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: Volumes in cloud HA in Cloud Volumes ONTAP</title>
    <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/Volumes-in-cloud-HA/m-p/146221#M161</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/34910"&gt;@heightsnj&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;I am confused with how volumes should be created in OnTap cloud HA environment:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. &amp;nbsp;When I create a volume, &amp;nbsp;do I need to specify two aggregates in two respective nodes in a active-active HA? How can they get synced? As I understand, if one node gets failed, then the other will be taking over, so, the volume will have to be consistent in across two nodes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Unlike SVM in a regular cluster, whereas I use the SVM’s NFS lif for exporting a share, in cloud,I would have to use a floating IP that point a node for exporting NFS share. Correct? If yes, what will happen if this node gets failed?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please advise. Thanks!&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/34910"&gt;@heightsnj&lt;/a&gt;, the nice part about Cloud Volumes ONTAP is that the volumes are automatically synchronised if using the HA configuration&amp;nbsp;- you don't have to specify the aggregate on the secondary node.&amp;nbsp;The storage replication&amp;nbsp;is managed by the ONTAP OS. This is an active/passive configuration where the second node is only used in the event of a failover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want to use the second node for active workloads then you would need to create a data aggregate on the second node.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The failover&amp;nbsp;of LIFs depends on the configuration of your&amp;nbsp;Cloud Volumes ONTAP instance in AWS:&lt;/P&gt;
&lt;P&gt;* Single node, or both nodes in the same Availability Zone:&amp;nbsp;You do not need to use a floating IP address.&amp;nbsp; Clients will access the&amp;nbsp;data IP&amp;nbsp;address of the SVM.&lt;/P&gt;
&lt;P&gt;* Nodes in different Availability Zones: A floating IP address is automatically created and managed by the mediator node.&amp;nbsp;&amp;nbsp;During failover, the floating IP address will be migrated by the mediator node to point to the surviving node's data LIF.&amp;nbsp; You can also access the data LIF on the node directly, and&amp;nbsp;re-point DNS during a failover.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Jan 2019 16:59:51 GMT</pubDate>
    <dc:creator>phoebeg</dc:creator>
    <dc:date>2019-01-28T16:59:51Z</dc:date>
    <item>
      <title>Volumes in cloud HA</title>
      <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/Volumes-in-cloud-HA/m-p/145870#M158</link>
      <description>&lt;P&gt;I am confused with how volumes should be created in OnTap cloud HA environment:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. &amp;nbsp;When I create a volume, &amp;nbsp;do I need to specify two aggregates in two respective nodes in a active-active HA? How can they get synced? As I understand, if one node gets failed, then the other will be taking over, so, the volume will have to be consistent in across two nodes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Unlike SVM in a regular cluster, whereas I use the SVM’s NFS lif for exporting a share, in cloud,I would have to use a floating IP that point a node for exporting NFS share. Correct? If yes, what will happen if this node gets failed?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please advise. Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:57:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/Volumes-in-cloud-HA/m-p/145870#M158</guid>
      <dc:creator>heightsnj</dc:creator>
      <dc:date>2025-06-04T12:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: Volumes in cloud HA</title>
      <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/Volumes-in-cloud-HA/m-p/146221#M161</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/34910"&gt;@heightsnj&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;I am confused with how volumes should be created in OnTap cloud HA environment:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. &amp;nbsp;When I create a volume, &amp;nbsp;do I need to specify two aggregates in two respective nodes in a active-active HA? How can they get synced? As I understand, if one node gets failed, then the other will be taking over, so, the volume will have to be consistent in across two nodes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Unlike SVM in a regular cluster, whereas I use the SVM’s NFS lif for exporting a share, in cloud,I would have to use a floating IP that point a node for exporting NFS share. Correct? If yes, what will happen if this node gets failed?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please advise. Thanks!&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/34910"&gt;@heightsnj&lt;/a&gt;, the nice part about Cloud Volumes ONTAP is that the volumes are automatically synchronised if using the HA configuration&amp;nbsp;- you don't have to specify the aggregate on the secondary node.&amp;nbsp;The storage replication&amp;nbsp;is managed by the ONTAP OS. This is an active/passive configuration where the second node is only used in the event of a failover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want to use the second node for active workloads then you would need to create a data aggregate on the second node.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The failover&amp;nbsp;of LIFs depends on the configuration of your&amp;nbsp;Cloud Volumes ONTAP instance in AWS:&lt;/P&gt;
&lt;P&gt;* Single node, or both nodes in the same Availability Zone:&amp;nbsp;You do not need to use a floating IP address.&amp;nbsp; Clients will access the&amp;nbsp;data IP&amp;nbsp;address of the SVM.&lt;/P&gt;
&lt;P&gt;* Nodes in different Availability Zones: A floating IP address is automatically created and managed by the mediator node.&amp;nbsp;&amp;nbsp;During failover, the floating IP address will be migrated by the mediator node to point to the surviving node's data LIF.&amp;nbsp; You can also access the data LIF on the node directly, and&amp;nbsp;re-point DNS during a failover.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jan 2019 16:59:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/Volumes-in-cloud-HA/m-p/146221#M161</guid>
      <dc:creator>phoebeg</dc:creator>
      <dc:date>2019-01-28T16:59:51Z</dc:date>
    </item>
  </channel>
</rss>

