June 7, 2024 at 1:43 pm
Hi
I am considering creating Contained Availability Groups in my production environment. Thinking I need to drop disabled jobs that live on both servers first?
I've searched and read allot of Contained Availability Groups articles but none of them that I can find describe the failover process once the Contained Availability Groups are setup.
During a failover from primary to secondary - does the secondary server just know to use the Contained Availability Group (the MSDB in the new contained group) and it ignores its own local MSDB and knows to use the contained version? Assuming it knows that when failing back ignore all local master and MSDB and use only what is in the Contained Availability Group? So I would need to make sure to add all the jobs. And if I create a primary and secondary can they contain different jobs from each?
So for example we have a Power BI instance that runs only on our secondary. It has its own jobs that don't run on the primary. Do I add these only in the secondary contained AG? Sorry I'm kinda confused on best way to handle this. Assuming that the jobs must match on Primary and Secondary?
June 8, 2024 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
June 8, 2024 at 5:33 pm
explained at: "What is a contained availability group?"
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply