Articles → AWS → Multi-AZ Database Instance Deployment In AWS

Multi-AZ Database Instance Deployment In AWS

In this article, we will discuss multi-AZ database instance deployment.

Purpose

Multi-AZ database instance deployment creates another standby database in different AZ. The purpose is to provide failover support.

Which Events Are Failover Events?

The following scenarios are considered as the failover activities: -

Loss of primary AZ
Primary DB instance failure
Loss of network connectivity on primary
Patching activity on the primary database instance
Manual failover of primary database

How Is The Database Synchronized In Multi-AZ Instance Deployment?

If we modify the existing database and enable multi-AZ instance deployment then: -

RDS takes a snapshot of the primary database
RDS restores the snapshot in another AZ

For synchronization, RDS set up the synchronous replication between the primary and standby database instances.

How To Enable Multi-AZ Database Instance Deployment?

If you are creating a new database or modifying the existing database then you can select the radiobutton Create a standby instance (recommended for production usage) in the Availability & durability section.

Picture showing enabling the option for creating the multi AZ DB

Click to Enlarge

Once the option is saved, the value of the Multi-AZ flag is Yes.

Picture showing the value of Multi-AZ column as Yes

Click to Enlarge

Can We Use SQL Server For Multi-AZ Database Instance Deployment?

No.

Is There Any Cost Associated With Data Transfer Between The Primary And Standby Databases?

No.

How The Maintenance Activities Are Done In Multi-AZ?

The maintenance activity is done in the following way: -

Perform operations on standby
Promote standby to primary
Perform operations on new standby (demoted primary)

Posted By -	Karan Gupta

Posted On -	Friday, January 14, 2022

Updated On -	Wednesday, February 7, 2024

Query/Feedback

Your Email Id		**

Subject		*

Query/Feedback	Characters remaining 250	**