sql server - Questions about Active Geo-Replication (and how it interacts with local, within-datacenter, redundancy) -
i read thisactive geo-replication azure sql database article on active geo-replication , have questions. posted these questions on page article haven't gotten reply yet.
could use help!
“every forced termination results in irreversible loss of replication relationship between primary database , associated online secondary database.” irreversible mean here? mean in order re-establish replication relationship between primary database , associated online secondary database after forced termination, we’d need start on seeding online secondary database?
“local data redundancy , operational recovery standard features azure sql database. each database possesses 1 primary , 2 local replica databases reside in same datacenter, providing high availability within datacenter. means active geo-replication databases have redundant replicas. both primary , online secondary databases have 2 secondary replicas.” so, if imagine have active geo-replication , running , primary database lost reason. azure sql automatically put 1 of remaining 2 local replicas exist within same datacenter part of standard local data redundancy , operational recovery azure sql feature in place of primary database lost no impact existing connections? if so, take mean case in forced termination of replication relationship between primary database , online secondary (via geo-replication) necessary if 3 copies of database existing in local datacenter lost. right?
using active geo-replication configuration, can online secondary databases in same region primary? wanted active geo replication within same region time. doable? realize that, regional disaster perspective, having online secondaries in same region defeat purpose. still know if it’s doable.
if force terminate continuous copy link new link must established enable geo-replication on new primary database. create new database , start on seeding of online secondary database.
azure sql database has built-in high availability. geo-replication (and forced failover) needs used in event of disaster causing entire data center primary database (and replicas) unavailable.
active geo-replication can used scale out read workloads. active geo-replication can configured in same region, replica must on different server primary. see "design pattern 2".
Comments
Post a Comment