AHV Metro Availability provides a synchronous replication solution for zero-RPO disaster recovery.

For this to function correctly within an NC2 on AWS environment, the clusters must be architected to survive anAvailability Zone (AZ)failure while maintaining the extremely low latency required for synchronous operations. The supported configurations include havingtwo NC2 clusters running in the same AWS region but in different AZs, ensuring that if one zone goes offline, the other can immediately take over. Additionally, asingle-node NC2 clustercan be used as a target in a different AZ within the same region for specific low-footprint synchronous requirements. Deploying across different regions is not suitable for Metro Availability due to the high latency of inter-region traffic, which would exceed the requirements for synchronous data writes.