Great Video. Since the SQL Server MI takes long time(6 hrs) for creation it will affect the RTO in case of disaster. Creating the HA SQL MI instance across multiple regions is not cost effective. Do you suggest any cost effective way of stopping the SQL Managed instance in the DR region and restore from backups from storage account? Do you suggest that approach can be taken for RTO 2-3 hrs without much data loss in case of DR?
@SQLTalk
3 жыл бұрын
One thing you can do is set up a lower tier Managed Instance in the DR region. This way you have a hot DR standby but are not paying the full cost of the production Managed Instance. Also, if you already own the SQL licenses on-prem and have Software Assurance (SA) you can save a lot of money on both the production and DR instances.
@jdneilso
4 жыл бұрын
Great video, very informative. Do you know if the scheduled jobs, database mail, and those types of things are also replicated, or do they need to be created separately?
@SQLTalk
4 жыл бұрын
Unfortunately no. That functionality works with a failover cluster instance where the entire cluster moves to another node.
@jdneilso
4 жыл бұрын
@@SQLTalk Thanks for your quick reply!
@kthulasiraman
4 жыл бұрын
Hi, If any DR happened in region our managed instance not moved to other region automatically correct ?
Пікірлер: 6