Availability Group database stays in Reverting for too long after a failoverSQL AlwaysOn Failover Due to...
Should a new user just default to LinearModelFit (vs Fit)
Coombinatorics- The number of ways of choosing with parameters
Possible issue with my W4 and tax return
Equivalent of "illegal" for violating civil law
What can I do to encourage my players to use their consumables?
Context html export bibliography
What does からか mean?
If I tried and failed to start my own business, how do I apply for a job without job experience?
Why did Luke use his left hand to shoot?
Why does typing a variable (or expression) print the value to stdout?
"Starve to death" Vs. "Starve to the point of death"
How do I avoid the "chosen hero" feeling?
How to fly a direct entry holding pattern when approaching from an awkward angle?
What would be some possible ways of escaping higher gravity planets?
Word for something that's always reliable, but never the best?
How much light is too much?
Case protection with emphasis in biblatex
Where does documentation like business and software requirement spec docs fit in an agile project?
Is `Object` a function in javascript?
Does it take energy to move something in a circle?
Does diversity provide anything that meritocracy does not?
What is a good reason for every spaceship to carry gun on board?
Caron Accent v{a} doesn't render without usepackage{xeCJK}
Is it really OK to use "because of"?
Availability Group database stays in Reverting for too long after a failover
SQL AlwaysOn Failover Due to Missed HeartbeatsSQL Server AlwaysOn database stuck in Not Synchronizing / In Recovery mode after upgrading. Error: Cannot open database '…' version 782Log space used stuck around 5%SQL Server 2017 Availability Groups - Can a Long-running transactions on a primary replica block a secondary replica from seeing updates?AlwaysOn High Availability Take database offline from primaryAlwaysOn commit on Primary if Secondary goes downAlways On group does not sync after failoverAvailability Group being PARTIALLY_HEALTHYAlways On - Restore a node from a Veeam backupAlways On Availability groups resolving state after failover - Remote harden of transaction 'GhostCleanupTask' failed
Architecture:
I have 2 Node Sync-Commit AlwaysOn configuration running on Multi-Subnet Failover Cluster. Primary node is in Europe and Secondary node is in US. I have only one database in the Availability Group which is OperationsManager db of SCOM.
Problem:
When I initiate a failover, database fails over from Primary to Secondary node successfully in seconds. However, new secondary(old primary) database goes into Reverting / In Recovery phase and stays there for 30 minutes approximately.
Findings:
I searched about this on internet and read documentation to investigate the issue. When role change from Primary to Secondary is finished, new secondary database goes through 3 phases:
Synchronization State: “NOT SYNCHRONIZING” ; Database State: ONLINE
Synchronization State: “NOT SYNCHRONIZING” ; Database State: RECOVERING
Synchronization State: “REVERTING” ; Database State: RECOVERING
In my case, all time has spent on last step. I also monitored the undo process by looking into perfmon counter "SQLServer:Database Replica Log remaining for undo"
I checked primary site before failover tests to spot any long running transactions or open transactions but couldn't find one. After failover, "Log remaining for undo" was around 30MB and it took 30 minutes for secondary database to go back to "Synchronized" state. When taking into consideration that we are running in Sync-Commit mode and there is a little workload on primary, it shouldn't take 30 minutes for redo phase imho.
Have you ever seen this problem before? Do you have any recommandations?
sql-server availability-groups
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
add a comment |
Architecture:
I have 2 Node Sync-Commit AlwaysOn configuration running on Multi-Subnet Failover Cluster. Primary node is in Europe and Secondary node is in US. I have only one database in the Availability Group which is OperationsManager db of SCOM.
Problem:
When I initiate a failover, database fails over from Primary to Secondary node successfully in seconds. However, new secondary(old primary) database goes into Reverting / In Recovery phase and stays there for 30 minutes approximately.
Findings:
I searched about this on internet and read documentation to investigate the issue. When role change from Primary to Secondary is finished, new secondary database goes through 3 phases:
Synchronization State: “NOT SYNCHRONIZING” ; Database State: ONLINE
Synchronization State: “NOT SYNCHRONIZING” ; Database State: RECOVERING
Synchronization State: “REVERTING” ; Database State: RECOVERING
In my case, all time has spent on last step. I also monitored the undo process by looking into perfmon counter "SQLServer:Database Replica Log remaining for undo"
I checked primary site before failover tests to spot any long running transactions or open transactions but couldn't find one. After failover, "Log remaining for undo" was around 30MB and it took 30 minutes for secondary database to go back to "Synchronized" state. When taking into consideration that we are running in Sync-Commit mode and there is a little workload on primary, it shouldn't take 30 minutes for redo phase imho.
Have you ever seen this problem before? Do you have any recommandations?
sql-server availability-groups
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
add a comment |
Architecture:
I have 2 Node Sync-Commit AlwaysOn configuration running on Multi-Subnet Failover Cluster. Primary node is in Europe and Secondary node is in US. I have only one database in the Availability Group which is OperationsManager db of SCOM.
Problem:
When I initiate a failover, database fails over from Primary to Secondary node successfully in seconds. However, new secondary(old primary) database goes into Reverting / In Recovery phase and stays there for 30 minutes approximately.
Findings:
I searched about this on internet and read documentation to investigate the issue. When role change from Primary to Secondary is finished, new secondary database goes through 3 phases:
Synchronization State: “NOT SYNCHRONIZING” ; Database State: ONLINE
Synchronization State: “NOT SYNCHRONIZING” ; Database State: RECOVERING
Synchronization State: “REVERTING” ; Database State: RECOVERING
In my case, all time has spent on last step. I also monitored the undo process by looking into perfmon counter "SQLServer:Database Replica Log remaining for undo"
I checked primary site before failover tests to spot any long running transactions or open transactions but couldn't find one. After failover, "Log remaining for undo" was around 30MB and it took 30 minutes for secondary database to go back to "Synchronized" state. When taking into consideration that we are running in Sync-Commit mode and there is a little workload on primary, it shouldn't take 30 minutes for redo phase imho.
Have you ever seen this problem before? Do you have any recommandations?
sql-server availability-groups
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
Architecture:
I have 2 Node Sync-Commit AlwaysOn configuration running on Multi-Subnet Failover Cluster. Primary node is in Europe and Secondary node is in US. I have only one database in the Availability Group which is OperationsManager db of SCOM.
Problem:
When I initiate a failover, database fails over from Primary to Secondary node successfully in seconds. However, new secondary(old primary) database goes into Reverting / In Recovery phase and stays there for 30 minutes approximately.
Findings:
I searched about this on internet and read documentation to investigate the issue. When role change from Primary to Secondary is finished, new secondary database goes through 3 phases:
Synchronization State: “NOT SYNCHRONIZING” ; Database State: ONLINE
Synchronization State: “NOT SYNCHRONIZING” ; Database State: RECOVERING
Synchronization State: “REVERTING” ; Database State: RECOVERING
In my case, all time has spent on last step. I also monitored the undo process by looking into perfmon counter "SQLServer:Database Replica Log remaining for undo"
I checked primary site before failover tests to spot any long running transactions or open transactions but couldn't find one. After failover, "Log remaining for undo" was around 30MB and it took 30 minutes for secondary database to go back to "Synchronized" state. When taking into consideration that we are running in Sync-Commit mode and there is a little workload on primary, it shouldn't take 30 minutes for redo phase imho.
Have you ever seen this problem before? Do you have any recommandations?
sql-server availability-groups
sql-server availability-groups
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
asked 5 mins ago
Bahtiyar Samet ÇobanBahtiyar Samet Çoban
1406
1406
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230663%2favailability-group-database-stays-in-reverting-for-too-long-after-a-failover%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230663%2favailability-group-database-stays-in-reverting-for-too-long-after-a-failover%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
