Use service accounts at AlwaysOn Availability Groups

Valued readers,
We have a AlwaysOn Availability Group consisting of 2 SQL servers. Both servers have their own service account for the sql services. I read in all sorts of documents on the internet that it is recommended that the sql service account on all servers within
the same availability group are using the same serviceaccount. This would have to do with registering the SPN of the virtual server for kerberos. What impact does it have if I don’t change the serviceaccount ?

Hello Sean,
No I do not think so. Do you mean this :
“Find your service account and hit the Security tab
Select “SELF” in the “Groups or user names” listbox
Find “Write public information” in the “Permissions for SELF” listbox
and check “Allow”
After, you’ll need to restart SQL Server for the SPN to register. Use setspn -l domain\account to verify that the account has
properly registered.
Should you also register the virtual server name? And what about if you use different service accounts?
With best regards, Albert

Similar Messages

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

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]

Cross-domain AlwaysOn Availability Groups

I had a colleague of mine comment in a meeting that SQL Server 2014 supports cross-domain data synchronisation using AlwaysOn Availability Groups. I didn't contradict that immediately because, even though I thought it wasn't the case, I couldn't find
any documentation either confirming or denying it.
Looking at the Network Access section for troubleshooting AlwaysOn AG (http://msdn.microsoft.com/en-us/library/ff878308.aspx#NetworkAccess), the inference is that you
can have AlwaysOn AG spanning different domains. However, one of the pre-requisities for creating a WSFC is that all servers that are to be added as cluster nodes are joined to the same Active Directory domain (http://technet.microsoft.com/en-us/library/dn505754.aspx).
So I guess the question is - can you have a cross-domain implementation of AlwaysOn AG? And if so, how?

Check this blog -
http://sqlha.com/2012/04/13/allans-alwayson-availability-groups-faq/
Q: Do all of my WSFC nodes need to be part of the same domain?
A: Yes. This will be a change for those who are looking to upgrade existing log shipping or DBM deployments where Instance A and Instance B are not in the same domain.
The fact that all the participating nodes in an Always ON availability group has to be members of the same WSFC makes it clear that we cannot have cross domain Always ON.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

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.

AlwaysOn Availability groups and unable to backup LOG files

Hi,
I have an issue where we are using AlwaysOn availability groups, however my transaction log backup jobs are not working for any databases that are part of the groups. Databases which are standalone backup fine. I've tried using the builtin maintenance
plans as well as the 'maintenance script' from Ola Hallengren which is my preference.
All the jobs are reporting success even though nothing is bring written to disk, the jobs complete within a few seconds.
If I backup the log files individually myself they work fine. After
going a bit of Googling this appears to have been a known issue that was fixed in CU7, unfortunately I'm running CU9 and still have the issue.
I've tried changing the backup preference to any, as well as primary or secondary only to no avail.
I'm using SQL Server SP1 CU9, 2 nodes in the group. Anyone have any suggestions?
Marcus

Hi,
I understand that you have tried every options in Backup Preferences. I still suggest you enable the “For availability database. Ignore Replica Priority for Backup and Backup on Primary Settings” when you define the maintenance plan and check how it works.
This settings is off by default. And the maintenance plan will detect the availability group's AUTOMATED_BACKUP_PREFERENCE setting when deciding to backup a database or log if that database is defined in the group.
'Given that an availability group's default AUTOMATED_BACKUP_PREFERENCE setting is 'SECONDARY, a maintenance plan, defined and running on a SQL Server instance hosting the primary replica, will NOT backup databases defined in the availability group.
Reference:
http://blogs.msdn.com/b/alwaysonpro/archive/2014/01/02/maintenance-plan-does-not-backup-database-or-log-of-database-that-belongs-to-availability-group.aspx
Hope it helps.
Tracy Cai
TechNet Community Support

Which Edition of Windows is required for using SQL 2012 Always On Availability Groups

I want to use the new feature of having 2 secondary mirror replicas. the first secondary replica will be sync the second one will be async.
Currently I have SQL Enterprise license and Windows 2008 R2 Standard license.
Will I be required to upgrade to Windows Enterprise license to use Always On? (since this feature depends on Windows clustering?)
Can you please confirm if SQL Always On feature can be used on Windows 2008 R2 standard or not?
MSDNStudent Knows not much!

Always On is available with Standard Edition but it supports only 2 nodes.
AlwaysOn is a bigger umbrella which covers two features. AlwaysOn Availability Groups (AG) and AlwaysOn Failover Cluster Instance (FCI).
FCI for 2 node is supported. You can't use AG feature in SQL Server Standard Edition
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

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

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

How to set WSSE credentials using Service Account in OSB

Hi Guys,
Flow Path:
OSB-A (Only Proxy Service) --> OSB-B (Both Proxy and Business service present) --> PIMWS --> PLSQL
In OSB-A i have a service account, which iam getting it in a variable using assign activity and trying to populate that in header variable using replace activity then calling OSB-B but iam getting the following exception..
When i check in the flow.. $header is not replaced with the actual WSSE: tags and credentials. How to make it to work ?
<proc:OutputParameters xmlns:proc="http://xmlns.oracle.com/apps/ap/soaprovider/plsql/xx_i024_suppliers_pkg/process_suppliers/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<proc:X_RETURN_STATUS>Missing <wsse:Security> in SOAP Header</proc:X_RETURN_STATUS>
<proc:X_RETURN_CODE>wsse:InvalidSecurity</proc:X_RETURN_CODE>
</proc:OutputParameters>
Thanks,
Vijay
Edited by: veejai24 on 16-Apr-2012 09:01

I am able to use Service Account in my OSB. The following are the steps i did.
I have created a service account and kept my username and password there in a common OSB Project.
Then in my proxy service i have an assign which is having the wsse header tags, which retrieves the username and password from service account.
I replace the header with the above information and calling the business service using routing options.
In business service, in http transport page i have used Authentication type as basic and kept the service account by browsing from my common OSB Project.
If i fire a request iam getting the response back as expected.
My question is why should i do 2 times the same thing, when i try to remove the configuration from business service iam getting exception saying "WSSE credentials are missing"
When i put it back its started working.
Thanks,
Vijay

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

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

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

Service account not inheriting AD group membership permissions on SQL Server

I am adding Active Directory groups as logins and database users to our SQL Servers. A service account added to an AD group did not inherit the group permissions that the user accounts did. Can there be different attributes of service accounts that would
prevent service accounts from inheriting the permissions of AD groups?
Example: An AD Group AD_group contains a service account user, svc_account and a user account, user_account. AD_group is added to a SQL Server as a login. User_account can log in to SQL Server but svc_account cannot.

SQL Server will use the information within the token used for authentication, so it may be possible that the service has a stale token (i.e. the token has not been refreshed or the service has not restarted) since you made the changes to the AD group.
I would recommend using a tool such as ProcessExplorer (https://technet.microsoft.com/en-us/sysinternals/bb896653) to make sure the token for the process is showing the latest group
memberships properly.
I hope this helps,
-Raul Garcia
SQL Server Security
This posting is provided "AS IS" with no warranties, and confers no rights.

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

Use service accounts at AlwaysOn Availability Groups

Similar Messages

Maybe you are looking for