SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


AlwaysOn : Unable to resume data movement


AlwaysOn : Unable to resume data movement

Author
Message
Sreejith!
Sreejith!
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1969 Visits: 616


Hello
Few of the databases are showing as 'Not synchronizing' in AlwaysOn dashboard

Error logs :
AlwaysOn Availability Groups connection with secondary database terminated for primary database 'DB name' on the availability replica with Replica ID: {}. This is an informational message only. No user action is required.

The target database, 'DB name', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server


On the secondary replica there was a pause icon & red cross next to the Availability Databases(only few DB's in same AG). On primary all green.These databases are configured as synchronous commit & non-readable. Unable to resume the data movements as the AO replica manager is failing to start WSFC(Error 35220).All cluster services are online

log_reuse_wait column for these databases are showing as AVAILABILITY_REPLICA and could find any blocks or long running transaction. Can some one please help?

Thanks in advance


Lincoln Burrows
Lincoln Burrows
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15627 Visits: 1781
Restart the SQL Server machine & reset the SQL Server service status to Started. sometimes solve these issue.
Ricky Valencia
Ricky Valencia
Default port
Default port (1.4K reputation)Default port (1.4K reputation)Default port (1.4K reputation)Default port (1.4K reputation)Default port (1.4K reputation)Default port (1.4K reputation)Default port (1.4K reputation)Default port (1.4K reputation)

Group: General Forum Members
Points: 1433 Visits: 1052
Hi
This happened to us few months back. We rebooted the secondary replica server and it resolved the issue.

Best Regards,
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)

Group: General Forum Members
Points: 202684 Visits: 18548
Johnson Welch - Tuesday, June 20, 2017 11:20 PM
Restart the SQL Server machine & reset the SQL Server service status to Started. sometimes solve these issue.

Ricky Valencia - Thursday, July 20, 2017 12:32 AM
Hi
This happened to us few months back. We rebooted the secondary replica server and it resolved the issue.

Best Regards,


This would lead me to conclude the mirroring endpoint wasnt started, it's easy to check using the following query

select name, type_desc, state_desc, is_encryption_enabled,

connection_auth_desc, encryption_algorithm_desc

from sys.database_mirroring_endpoints



-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
davidmsdw
davidmsdw
SSC-Enthusiastic
SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)

Group: General Forum Members
Points: 177 Visits: 21
There are multiple items which can be checked for Always On Availability Groups so I put together a blog post to start:

https://justdaveinfo.wordpress.com/2017/08/02/sql-server-availability-groups-items-to-check/

If there is still an issue, please let us know.

Regards,
David.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search