With Azure PaaS services, the duplication of the stateless application components in reduced capacity is simple and cheap, and most services can subsequently be scaled in minutes to meet the production performance needs. Furthermore, if you have an automated and consistent deployment process, the services can be brought up from scratch in a consistent and very fast manner. Thus, if your RTO allows for a few minutes of downtime, you might be able to meet it even with a warm DR site.
Most importantly, the asynchronous geo-replication of data is typically a feature built into the data store, which you can enable with a couple of clicks or script commands. All of the preceding makes the hot DR site implementation very ...
