High-availability pairs in Azure
Contributors Download PDF of this page
A Cloud Volumes ONTAP high availability (HA) pair provides enterprise reliability and continuous operations in case of failures in your cloud environment. In Azure, storage is shared between the two nodes.
A Cloud Volumes ONTAP HA configuration in Azure includes the following components:
Note the following about the Azure components that Cloud Manager deploys for you:
- Azure Standard Load Balancer
The load balancer manages incoming traffic to the Cloud Volumes ONTAP HA pair.
- Availability Set
The Availability Set ensures that the nodes are in different fault and update domains.
Customer data resides on Premium Storage page blobs. Each node has access to the other node’s storage. Additional storage is also required for boot, root, and core data.
- Storage accounts
One storage account is required for managed disks.
One or more storage accounts are required for the Premium Storage page blobs, as the disk capacity limit per storage account is reached.
One storage account is required for data tiering to Azure Blob storage.
Starting with Cloud Volumes ONTAP 9.7, the storage accounts that Cloud Manager creates for HA pairs are general-purpose v2 storage accounts.
You can enable an HTTPS connection from a Cloud Volumes ONTAP 9.7 HA pair to Azure storage accounts when creating a working environment. Note that enabling this option can impact write performance. You can’t change the setting after you create the working environment.
RPO and RTO
An HA configuration maintains high availability of your data as follows:
The recovery point objective (RPO) is 0 seconds.
Your data is transactionally consistent with no data loss.
The recovery time objective (RTO) is 60 seconds.
In the event of an outage, data should be available in 60 seconds or less.
Storage takeover and giveback
Similar to a physical ONTAP cluster, storage in an Azure HA pair is shared between nodes. Connections to the partner’s storage allows each node to access the other’s storage in the event of a takeover. Network path failover mechanisms ensure that clients and hosts continue to communicate with the surviving node. The partner gives back storage when the node is brought back on line.
For NAS configurations, data IP addresses automatically migrate between HA nodes if failures occur.
For iSCSI, Cloud Volumes ONTAP uses multipath I/O (MPIO) and Asymmetric Logical Unit Access (ALUA) to manage path failover between the active-optimized and non-optimized paths.
|For information about which specific host configurations support ALUA, see the NetApp Interoperability Matrix Tool and the Host Utilities Installation and Setup Guide for your host operating system.|
Storage takeover, resync, and giveback are all automatic by default. No user action is required.
You can use an HA pair as an active-active configuration, in which both nodes serve data to clients, or as an active-passive configuration, in which the passive node responds to data requests only if it has taken over storage for the active node.
The following limitations affect Cloud Volumes ONTAP HA pairs in Azure:
HA pairs are supported with Cloud Volumes ONTAP Standard, Premium, and BYOL. Explore is not supported.
NFSv4 is not supported. NFSv3 is supported.
HA pairs are not supported in some regions.