Skip to content

Commit d2bb4e5

Browse files
authored
Merge pull request #8417 from MicrosoftDocs/SQL_redo_queue_pijocoder_031325
AB#4449: SQL redo queueing - update title and a sentence
2 parents 7dd51b7 + c8afc2c commit d2bb4e5

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

support/sql/database-engine/availability-groups/troubleshooting-recovery-queuing-in-alwayson-availability-group.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Troubleshooting recovery queueing in an Always On availability group
2+
title: Troubleshooting recovery (redo) queueing in an Always On availability group
33
description: This article helps you to troubleshoot problems that are related to recovery queueing in an Always On availability group.
4-
ms.date: 02/10/2023
4+
ms.date: 03/11/2023
55
ms.custom: sap:Always On Availability Groups (AG)
6-
ms.reviewer: ramakoni, v-jayaramanp
6+
ms.reviewer: ramakoni, v-jayaramanp, jopilov
77
---
88

9-
# Troubleshooting recovery queueing in an Always On availability group
9+
# Troubleshooting recovery (redo) queueing in an Always On availability group
1010

1111
This article provides resolutions to problems related to recovery queueing.
1212

@@ -28,7 +28,7 @@ For more information, see the [Data latency on secondary replica](/sql/database-
2828

2929
### Failover time is longer or RTO is exceeded
3030

31-
Recovery Time Objective (RTO) is the maximum database downtime that an organization can handle. RTO also describes how quickly the organization can regain access to the database after an outage. If substantial recovery queueing is present on a secondary replica when a failover occurs, recovery may take longer. After recovery, the database will transition to the primary role and represent the state of the database that existed before the failover. A longer recovery time can delay how quickly production resumes after a failover.
31+
Recovery Time Objective (RTO) is the maximum database downtime that an organization can handle. RTO also describes how quickly the organization can regain access to the database after an outage. If substantial recovery queueing is present on a secondary replica when a failover occurs, recovery might take longer than the RTO. After recovery, the database will transition to the primary role and represent the state of the database that existed before the failover. A longer recovery time can delay how quickly production resumes after a failover.
3232

3333
### Various diagnostic features report availability group recovery queueing
3434

0 commit comments

Comments
 (0)