June 6, 2017 at 9:56 am
Has anyone ever had CMS using AlwaysOn architecture? How was this completed? How does it work on fail over if Targets have an assigned named Master Server?
Kind regards.
¤ §unshine ¤
June 7, 2017 at 3:54 am
I use it everyday and just use the server name and not the listener name to register in CMS. As they are separate servers and need to be queried individually for information such as system db backups etc. The secondaries can also have dbs out of the AOAG if licensed and will need to be checked for backups and checkdb etc etc the usual db server and database monitoring.
Querying the CMS in this way first thing in the morning, also tells you instantly what servers are up or down.
June 7, 2017 at 8:14 am
Thank you. How do the targets know which the master is? The targets show the named server as master. However, when they will failover, the master may be unavailable and the server it failed over to, will have a different name.
¤ §unshine ¤
June 8, 2017 at 1:07 am
Hi
In an ALWAYS -ON setup only user databases are synch'd across to the secondary or secondaries. The system databases are not shared in this environment. You have to think of each server as a completely different server with just Mirrored user databases on steroids.
This is a point that is missed from most of the setups I come across. When used for HA/DR purposes changes the security/job changes on the PRIMARY is not reflected on the secondary, as most do not create a manual plan to copy security/jobs changes to the secondary server.
Main thing is to remember it is not like a FCI cluster. Just mirrored user databases between 2 different instances.
Script to find out which is the Primary
select replica_server_name
FROM sys.dm_hadr_availability_replica_states AS a
JOIN sys.availability_replicas AS b
ON b.replica_id = a.replica_id
where role_desc ='Primary'
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply