SQL Server Alwayson availability groups automation

Hi all,
I had configured SQL Server always on availability groups on windows server 2012 and it was successful.
I’ve installed and successfully configured our SQL Server 2012 AlwaysOn 2-node windows cluster servers. I've gotten AlwaysOn working great, and our
Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. As we know “we must manually find, select, back-up and then
add those new databases individually to get them into AlwaysOn."
But wait; that can be quite a task, constantly checking the SQL Server back-end servers to see what databases were created, then having to add them
into AlwaysOn, 7/24!
Im looking for an automated script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then
add those databases to Always On, all automatically.
Requirements:
Every time the newly created or added databases should be full backed up once in the shared location with automated script.
Newly created database should be added into always on group and should be added to available replica automatically with the TSQL script
Regards,
SQL LOVER.

awaiting for responses.
Kindly help the bewlo request.
Newly created database should be added into always on group and should be added to available
replica automatically with the TSQL script and perform restoration.
There is no out of the box solution for this. You may want to created a SQL Job (PowerShell) which can detect database which is newly created and perform steps to add new database to AG.
1. take full backup.
2. Take log backup.
3. restore then on secondary.
4. Add database to AG
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Similar Messages

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Hi,
It is listed here:
http://technet.microsoft.com/en-us/library/dn281933.aspx
Configuration Manager 2012 r2 and DPM 2012 r2 does not support AlwaysOn.
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SQL Server 2012 availability groups

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!

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.

File Share Witness Resouces Errors in a SQL 2012 Alwayson Availability Group Environment

Hi I am getting the following error in WFC Manager and in my system event log:
Event ID1564:
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\SQL2012ClusterWitnessPath'. Please ensure that file share '\\SQL2012ClusterWitnessPath' exists and is accessible by the cluster.
Event ID 1069:
Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID 1205:
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
These errors showed up every hour on the hour and then suddenly stopped. I tried looking at the cluster.log file but there wasn't anything recorded there. The file share witness shows to be online and my AG did not fail over to another node.
The cluster has read and write permissions to the share. I did not find any error messages about the witness share on the remote server.
I am wondering what caused these series of events to occur?
Thanks.

Hi Kevin Ni,
Thanks for your reply. I have ran the validation test and I have 2 warnings. My environment has 2 nodes and 2 AG's with each node a failover for each AG. So that each node hosts and primary and a secondary of an AG. Both nodes are
on the same subnet. Here are the errors.
- Validate Multiple Subnet Properties
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener1' is set to 1. For the current cluster configuration this value should be set to 0.
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener2' is set to 1. For the current cluster configuration this value should be set to 0.
- Validate Network Communication
Node ONE.domain.com is reachable from Node TWO.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
Node TWO.domain.com is reachable from Node ONE.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
I have node TWO setup with NIC Teaming. Node ONE is also setup with NIC teaming but it also has a second IP address but the second IP address cannot communicate with node TWO.

Is it possible to move to Alwayson Availability groups from existing sql server FCI ?

Is it possible to move to Alwayson Availability groups from? existing sql server FCI ?
If yes, how to move and what are the pre-requisites?

Hi Rahul,
Based on your description, we need to verify if you want to move from Failover Cluster Instances(FCI) and database mirroring to SQL Server Alwayson Availability groups. If so, it is possible.
You can review the following articles to get more detailed information about this kind of migration.
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 1
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 2
Thanks,
Lydia Zhang

Moving the Reporting Services and Report Server DB into AlwaysON Availability Group

I have configured the new set of SQL 2012 AlwaysOn Availability Group and need to move the SSRS and it's Report Server DB into that Availability Group.
Can anyone give tell me the steps to do this move?
Can I just backup the ReportServer DB into the AG server then import that DB into the SSRS running on the new AlwasyOn AG SQL?

Hello,
Based on your description, it seems that you want to move the Report Server database to a different server. If so, both the reportserver and reportservertempdb databases must be moved or copied together. You can move the databases by using Detaching
and Attaching or Backup and Restore.
What's more, you should also backup the encryption keys for the report server database you want to move and then restore to the new server.
You can configure report server databases in Always On Availability Group to be part of a replica; however Reporting Services will not automatically use a different replica for the report server databases when a failover occurs
Reference:
Moving the Report Server Databases to Another Computer
Reporting Services with AlwaysOn Availability Groups (SQL Server)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

2012 SQL AlwaysOn Availability Group - JDBC re-connection not happening in case of Multisubnet failover

Hi There,
Having some problem with MultiSubNet AG failover re-connection using SQL JDBC driver 4. Details given below.
SETUP:
We have a three node 2012 Windows Server Cluster, on top it we have 2012 SQL Sever AlwaysOn Availability Group.
Two nodes are in one subnet and other in a different subnet to make this as a multisubnet AlwaysOn AG.
An AG Listener is configured with a DNS name and two VIP assigned (For two subnet) to it. We were able to failover from one subnet to other using the SQL Studio successfully.
NEED:
We have a java application which will be connected to AG Listener name. In case of failover, automatic re-connection to DB/AG Listener name should happen.
For this we use "sqljdbc4.jar" and added
'multiSubnetFailover=true' in our connection string. The connection String is given below.
cURL="jdbc:sqlserver://testsqlag:1433;databaseName=SalesDB;multiSubnetFailover=true;loginTimeout=200;applicationName=MyApp";
THE PROBLEM:
In case of AG failover, driver is not trying to re-connect to the AG Listener name. Not sure how to make it work.
Is this supported in SQL Server 2012 ?
Thanks,
Krishna.

Hi Sean,
Thanks for your answer.
I looked at the link earlier, but it was not very clear that, whether the mssql jdbc driver will automatically re-connect to AG Listener name in case of failure of Primary replica which will result in Multisubnet failover. Pasted the confusing statements
from the link
http://msdn.microsoft.com/en-us/library/gg558121(v=sql.110).aspx.
Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects.
Connecting With MultiSubnetFailover :
During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, the Microsoft JDBC Driver for SQL Server will aggressively retry the TCP connection.
Thanks,
Krishna.

SQL 2012 Database Availability Group - Force Automatic Failover

Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
Bob

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

Initermittent Connection Timeout at Post-Login when connect to AlwaysOn Availability Group listener

Hi,
I'm using SQL 2014 AlwaysOn Availability Group and my ASP .Net application is connected to the database thru the availability group listener (tcp:[myHAGroup],14330).
Things work most of the time, but recently I started to see the following Connection Timeout exception in Event Log. It looks like under heavy traffic the application can't connect to the availability group listener.
Timestamp: 8/17/2014 10:07:28 AM
Message: System.Data.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=2; handshake=0; [Login] initialization=0; authentication=0; [Post-Login] complete=15008; ---> System.ComponentModel.Win32Exception: The wait operation timed out
--- End of inner exception stack trace ---
I've checked SQL Profiler and don't see any memory or CPU peak at that time. Looks like somethings happened during the Post-Login stage, but I couldn't figure out what or why....
I'm using 2 SQL servers (1 primary, 1 secondary): SQL 2014 ENT, 8GB RAM, 8 core 2.67 Xeon X5650.
Application: ASP .Net, framework 4.0.
All servers are VMWare virtualization servers, running on 1 virtual switch, so internal traffic should not be a problem.
Comments/ideas are appreciated.
Eric.

Hi Eric Nguyen,
According to your description and error message, we need to verify if there are some queries/transaction lock your database via SQL trace. If yes,
you have to find out which queries are blocking and rewrite them/run them at other time to avoid blocking other processes.
In addition, you can use performance monitor to track connection pool connections. If you set default connection limit and timeout limit with a small number, the error of “wait operation timed out” will occur. Meanwhile, you also need to monitor disk usage
on SQL Server , and set the auto increment size of your transaction log and database with a fixed size instead of a percentage of the current files due to avoid transaction timeout. For more information, see:
http://stackoverflow.com/questions/7743725/how-to-troubleshoot-intermittent-sql-timeout-errors
There is an similar issue about connection failed from webservers to SQL Server AlwaysOn Listener, you can review it.
http://stackoverflow.com/questions/23416492/connection-timeouts-when-using-multisubnetfailover-true
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Sql Server High availability failover trigger

Hello,
We are implementing sql server 2012 availability groups (AG). Our secondary databases are not accessible in order to save licenses.
We have a lot of issues concerning monitoring, backup and SSIS. They all come down to the fact that they want basic information from the secondary, that is not accessible. We are implementing SSIS, which is supported on AG, but the SSISDB is encrypted.
Backup problem
The secondary instance does not know anything about the backups made in the primary instance. After a failover differential backups fail.
SSIS problem:
There is a blog (http://blogs.msdn.com/b/mattm/archive/2012/09/19/ssis-with-alwayson.aspx) that suggest to make a job that checks whether the status has changed from secondary to primary. If so, you can decrypt and encrypt again.
This job has to be executed every minute. Which is way too much effort for an event that happens once in a while. There are a few other problems with this solution. The phrase "use ssisdb" has to be included in the a job step. And the
jobstep fails. The secondary is not accessible.
Monitoring problems:
We use Microsoft tooling for monitoring: SCOM. Scom does not recognize a non readable secondary and tries to login continuously.
There are a few solutions that I can think of:
- sql server build in failover trigger
- Special status of secondary database.
Failover trigger:
We would like a build-in failover trigger, in stead of a time based job, that starts a few standard maintenance actions if only at the time (or directly after) a failover has occurred. Because now our HA cluster is not really high available until :
- SSISDB works and is accessible after failover
- Backup information is synchronised
- SCOM monitoring skips the secondary database (scom produces loads of login failures)
Does anyone have any suggestion how to fix this?

No built in trigger can achieve your requirement.

Maintenance plan for SQL Server 2012 Database in AlwaysOn Availability Group

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Thank you very much for your help!
Jake

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Regular maintenance plan would work. Only thing to remember is that when you create log backup plan, there is a checkbox which says whether it should honor backup preference or not.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

SQL AlwaysOn Availability Group modifies preferred owner node on move/failover

I have a two node Windows Server 2012 R2 failover cluster with two SQL Server 2012 Enterprise AlwaysOn Availability groups configured. Within the cluster I have configured a preference order on which node a AlwaysOn Availability Group should run.
Get-ClusterGroup -Name "AlwaysOn1" | Set-ClusterOwnerNode -Owners "node1","node2";
Get-ClusterGroup -Name "AlwaysOn2" | Set-ClusterOwnerNode -Owners "node2","node1";
After configuring the preference and retrieving the preference order it is configured as it should be. When I do a failover the preference order is adjusted to first the node it currently runs on and second the other node instead of leaving the preference
order as it was. It doesn't matter if I use the PowerShell "Move-ClusterGroup" or the "ALTER AVAILABILITY GROUP [AlwaysOn1] FAILOVER" T-SQL command. From the cluster log it is shown that the preference is modified after the resource
has been moved.
INFO [GUM] Node 2: executing request locally, gumId:15859, my action: /rcm/gum/SetGroupPreferredOwners, # of updates: 1
INFO [RCM] rcm::RcmGum::SetGroupPreferredOwners(AlwaysOn1,<vector len='2'>
The default groups within the cluster "Available Storage" and "Cluster Group" keep their preference setting when configured (only configured for testing to verify it has to do with the SQL Server Availability Group resource type).
The Windows Server 2012 R2 servers are updated using the latest Windows Updates and SQL 2012 has build number 11.0.5556.
For other cluster groups which I have configured in the past like file, Hyper-V (used for affinity to get VM's which have a lot of traffic between them within the same virtual switch to reduce latency and additional hops. it would be nice if vNext will have
a affinity option for cluster groups besides the anti-affinity within the current version)
I would like to know if someone could explain why the SQL Server Availability Group resource always modifies the group preference. I might understand this with a three node cluster where the first two are running in Synchronous commit mode and the third
one in Asynchronous commit mode.
Thanks in advance,
Dennis van den Akker

Hi Dennis van den Akker,
Do not use the Failover Cluster Manager to manipulate availability groups, for example:
Do not add or remove resources in the clustered service (resource group) for the availability group.
Do not change any availability group properties, such as the possible owners and preferred owners. These properties are set automatically by the availability group.
Do not use the Failover Cluster Manager to move availability groups to different nodes or to fail over availability groups. The Failover Cluster Manager is not aware of the synchronization status of the availability replicas, and doing so can lead to extended
downtime. You must use Transact-SQL or SQL Server Management Studio.
The related KB:
Failover Clustering and AlwaysOn Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff929171.aspx
The similar thread:
SQL Server Clustering 2008 (Multi Node)
https://social.msdn.microsoft.com/Forums/sqlserver/zh-CN/c35fe863-3fed-4a6e-830b-b79aa032c198/sql-server-clustering-2008-multi-node?forum=sqldisasterrecovery
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Alwayson Availability groups for a WSFC hosting mutliple SQL FCI's

Hello,
I have a question regarding SQL server FCI's and alwayson availability groups.
Today I have a customer running a 2 node WSFC hosting 9 different SQL FCI's.
Plan is to introduce on this setup SQL alwayson availability groups one per SQL FCI.
Per SQL FCI, running on the 2 node WSFC, we are planning to introduce a dedicated
alwayson availability group with 2 replicas. On replica as primary linked with the
FCI and one replica as secondary on 1 extra node added to the WSFC.
Question i have is, is this a supported configuration?
Thanks in advance
Regards
Raf

This is a supported scenario. However, make sure that no FCI node will run a SQL Server instance acting as a replica. This means you cannot install a standalone instance on one of the FCI nodes and make it an AG replica. You also cannot configure another
FCI in the same WSFC to be a secondary replica in an AG. If you intend to configure AG per SQL Server FCI, you need to add another node in the WSFC and install a SQL Server instance on that node. This can be a SQL Server FCI (which means you need to add two
more nodes instead of just one) or a standalone instance. Also, having an FCI in an AG configuration means that you lose the ability to do automatic failover on the AG-level. This is because the FCI takes care of automatic failover on the instance-level.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Backup Maintenance Plan on SQL AlwaysOn Availability Group Secondary Read-Only node

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.
The backup job within SQL Maintenance plan is failing with the following error:
Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"
Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Thanks.
Tracy Cai
TechNet Community Support

Monitoring scripts for AlwaysOn Availability Group

Does anyone have any any monitoring scripts for AlwaysOn AG using Transact SQL or stored procedures? I'm not a strong coder and don't know Powershell at all. But if there are some Powershell scripts we may be able to use them. I've
seen the dashboard but that's only good if you're logged onto it.
I'm looking for things like monitoring when a database is suspended, send an alert to us but also tries to do the resume.
Thanks for any info.

Start with this list
http://technet.microsoft.com/en-us/library/ff877954.aspx
Automating the issue resolution has to conform to your operational standards. For example, if you use a file share witness for your quorum configuration and your monitoring tells you that it is offline, do you automate bringing it online or do you escalate
to your infrastructure team so that they can look into it? If the database is suspended or the Availability Group in offline state, do you just bring it online or do you check other dependencies like the quorum configuration and instead perform a forced quorum?
I'm a big fan of automation but make sure you define your process first so that you don't cause more issues as a result.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL Server Alwayson availability groups automation

Similar Messages

Maybe you are looking for