SQL Server 2012 availability groups

Question

Hi, I'm new to SQL 2012 and availability groups. We have it setup for SharePoint 2013 for an Intranet and all is well. I migrated some ASP.NET applications from SQL 2005 and created a new group for them. It all seemed fine and was sync'd up ok but lately
I'm having to manually resume the data movement via Management Studio. The databases seem to be in a paused state although the database is up as far as the applications are concerned.
Should I have completed some kind of database upgrade prior to moving over to 2012? Is there anything I can do or check? Is there a way of automating the resume data movement rather than me manually doing this?
Thanks!

Answer 1

Suspending and resuming an AlwaysOn secondary database does not directly affect the availability of the primary database. However, suspending a secondary database can impact redundancy and failover capabilities for the primary database, until the suspended
secondary database is resumed. This is in contrast to database mirroring, where the mirroring state is suspended on both the mirror database and the principal database until mirroring is resumed. Suspending an AlwaysOn primary database suspends data movement
on all the corresponding secondary databases, and redundancy and failover capabilities cease for that database until the primary database is resumed.
You can obviously automate this: all you need to do is check if the status is suspended and then resume with the help of T-SQL command - how about writing a job which checks it every 5 min to 30 mins. depending upon your requirement and execute the T-SQL
command to fix it.
The Command would be:
ALTER DATABASE database_name SET HADR RESUME
Sarabpreet Singh Anand
SQL Server MVP Blog ,
Personal website
This posting is provided , "AS IS" with no warranties, and confers no rights.
Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.