wasabi3689
asked on
Migrating AGs between Azure and Cloud (non-Azure)
We have Always On set up currently by SQL 2016 both HA and DR in cloud platform. Now we plan to do Azure and cloud migration. We want to have Azure environment for HA and keep current cloud for DR. We will still use SQL 2016 enterprise How to do always-on between Azure and cloud platform? or other better solution like Log shipping and mirroring? I mean HA I always-on solution, and DR in log shipping
How to do mirroring AG in HA site to DR site? or can we mirror AG between HA site and DR site?
How to do mirroring AG in HA site to DR site? or can we mirror AG between HA site and DR site?
ASKER
Can someone tell me what are the advantages and disadvantages of distributed always on approach?
Distributed Availability groups feature starts from SQL Server 2016 and above which supports having a DR node distributed across another WSFC cluster.
From 2017 onwards, it supports DR across Linux or Windows or any Cloud solutions..
One disadvantage I would see using DAG is usage of FORCE_FAILOVER_ALLOW_DATA_ LOSS which can cause some data loss in worst case scenarios..
From 2017 onwards, it supports DR across Linux or Windows or any Cloud solutions..
Here are the three main usage scenarios for a distributed availability group:https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/distributed-availability-groups?view=sql-server-2017
Disaster recovery and easier multi-site configurations
Migration to new hardware or configurations, which might include using new hardware or changing the underlying operating systems
Increasing the number of readable replicas beyond eight in a single availability group by spanning multiple availability groups
One disadvantage I would see using DAG is usage of FORCE_FAILOVER_ALLOW_DATA_
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
1. HA can be configured within a single Cloud provided either Azure or non-Azure system and not across them.
2. DR can be configured across Azure and Non-Azure systems but the DR failover should be manual and not automatic..
Got a nice article which might be helpful to you..
https://blogs.msdn.microsoft.com/igorpag/2013/09/25/sql-server-vm-disaster-recovery-between-azure-and-amazon/