Backup and Recovery Availability Zones (AZ) Failure


What are Availability Zones (AZ)?


An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. AZ's give customers the ability to operate production applications and databases that are more highly available, fault-tolerant, and scalable than would be possible from a single data canter. All AZ's in an AWS Region are interconnected with high-bandwidth, low-latency networking, over fully redundant, dedicated metro fiber providing high-throughput, low-latency networking between AZ's. All traffic between AZ's is encrypted. The network performance is sufficient to accomplish synchronous replication between AZ's. AZ's make partitioning applications for high availability easy. If an application is partitioned across AZ's, companies are better isolated and protected from issues such as power outages, lightning strikes, tornadoes, earthquakes, and more. AZ's are physically separated by a meaningful distance, many kilometres, from any other AZ, although all are within 100 km (60 miles) of each other.


*AWS Description for Availability Zones. More information is in the following link: Regions and Availability Zones


Backup and Recovery, AZ failure

  • As described above, AWS data centers employ redundant architecture.
  • The Availability Zone (AZ) architecture ensures high availability for broadcast services even in case of AZ failure.
  • For fast Recovery of the MCM9000, we highly recommend setting a duplicate MCM9000 Instance in a different AZ or even a different Region.
  • The redundant Instance can be in a 'Stop' state and ready to run with the same MCM9000 system configuration.
  • In order to duplicate the system, please see our previous Architecture /wiki/spaces/UPGRADES/pages/447742158 and follow the step as described in MCM9000 Backup and Recovery.