March 28, 2017 at 9:35 am
I understand it like this:
Secundary databases in the group are syncronized either synchronous or asynchronous from the primary database, the same goes for a secondary/primary "replica".
Is this design with group and replica so that the group insures recovery and availability on database level and "Replica" on server level?
March 28, 2017 at 2:19 pm
I think I follow what you are asking for clarification on - The word "replica" has been made to be confusing. It technically means the Sql Server instance involved with an Availability Group. However, you will see the term again used to signify a database within the Availability Group. So, in your statement, "Replica" on a server level pertains to the Sql Server Instance housing the AG which would be at the server level since it is clustered behind the scenes. Availability at the database level also exists due to all the databases within an availability group are failed over all at the same time. The Asynchronous/Synchronous mode settings are set at the AG level - this is seen from the properties of the AG.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply