Lastly, the multi-site strategy, also known as hot standby, helps you to achieve near-zero RTO and RPO. In multi-site, your disaster recovery site is an exact replica of the primary site with continuous data replication and traffic flow. It is known as multi-site architecture due to the automated load balancing of traffic across regions or between on premise and the cloud. 

As shown in the following diagram, multi-site is the next level of disaster recovery to have a fully functional system running in the cloud at the same time as on-premises systems:

The advantage of the multi-site approach is that it is ready to take a full production load at any moment. It's similar to warm standby but running full capacity in the disaster recovery site. If the primary site goes down, all traffic can be immediately failed over to the disaster recovery site.

A multi-site disaster recovery pattern is most expensive as it requires a duplicate of everything. However, in this scenario, the RTO objective is much quicker for all workloads, while the RPO objective largely depends upon the replication type. Let's explore some best practices around disaster recovery to make sure your system is running reliably.