August 16, 2017 at 6:02 am
hi
i have 3 node server with alwaysOn setup 1-primary 2 -secondary 3-secondary.
wanted to reboot any of them, is there any consequences of rebooting them.
reason for reboot: server is inaccessible.
what is the sequence of rebooting servers while they are on AlwaysOn setup.
thanks
August 16, 2017 at 6:17 am
What is the secondaray node configuration is the synchronous or asynchronous?.
Regards
Durai Nagarajan
August 16, 2017 at 6:19 am
can you tell me implications of both synchronous and asynchronous?
August 16, 2017 at 6:20 am
Make sure the PRIMARY is not set to AUTO FAILOVER if that is to be rebooted.
Which one of the 3 is inaccesssible.
August 16, 2017 at 6:23 am
there are 3 server
1-primary 2 -secondary 3-secondary.
1 and 2 are not accessible due to some windows issue
August 16, 2017 at 6:28 am
Error message??
August 16, 2017 at 6:33 am
there is no error massage, when login it is stuck on "apply user setting".
but my question here is to understand reboot process in this scnerio.
and what is the standard practice of reboot servers when they configured with AlwaysON
August 16, 2017 at 6:39 am
Did you get any user escalation in terms of application connectivity, if not then leave it for off business hours and get approval and reboot , the secondary first and then production- this is move the prod to available configured secondary .
Mostly in synchronous mode it should bring the DB in sync immediately.
thanks
Regards
Durai Nagarajan
August 16, 2017 at 6:46 am
If i reboot primary server first ? (it will move to secondary), and then secondary (it will again move to primary)
August 16, 2017 at 7:01 am
It sounds like the databases are still functional and you just can't login to the servers, yes? Assuming that is the case, on node 3, fail the databases over to 3 which makes it primary. Make sure to have the connection to 3 be synchronous before doing this, or risk data loss. Once the databases are moved over to node 3, change the mode to asynchronous, and change to manual failover. Then you can reboot 1 & 2 with less risk of any problem.
When node 1 and 2 come back up, make sure they synchronize with 3 before making any attempts to move the primary/secondary status and changing the sync type and failover type.
Alan H
MCSE - Data Management and Analytics
Senior SQL Server DBA
Best way to ask a question: http://www.sqlservercentral.com/articles/Best+Practices/61537/
August 16, 2017 at 8:28 am
Is node 3 the DR server?
August 16, 2017 at 8:41 am
Zeal-DBA - Wednesday, August 16, 2017 6:46 AMIf i reboot primary server first ? (it will move to secondary), and then secondary (it will again move to primary)
Can you post the Always on configuration like synchronous or not to suggest on risks and details.
Regards
Durai Nagarajan
August 17, 2017 at 9:21 am
Zeal-DBA - Wednesday, August 16, 2017 6:02 AMhi
i have 3 node server with alwaysOn setup 1-primary 2 -secondary 3-secondary.
wanted to reboot any of them, is there any consequences of rebooting them.reason for reboot: server is inaccessible.
what is the sequence of rebooting servers while they are on AlwaysOn setup.
thanks
On the server thats accessible or from ssms on another server, fail over the availability group to the accessible server.
Reboot the other 2 and then move the group back as required
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply