https://ninithepug.wordpress.com/

Hi,

Client is looking for a solution where is wanted to run the pakages on secondary server in a event of failover. something like making a hight available solution for SSIS Pakages.

SQL Server : SQL 2012.

Hello All,

We have a client which they have production 2 node cluster environment. On it around 200 databases with single SQL instance.

Now client wants disatster plan for these 200 database. In these 200 database 3 db's are around 80 GB each databases remaing are less than 5 DB.Note: All these 200 db's are having produciton sites (i mean to say each db is having single site)

For this DR paln clinet is going to provide other DR server,they wants to setup DR between exsting produciton cluster instance to this DR server.

So in this case we have suggest SQL server AlwaysOn availability group.

Here my main question is can we keep all these databases in single AG? .If yes, could please help us with guidlines to moveup.if not, do we have any limitations.Also,Please help us with best method to setup for this DR plan.

Greatful to your time and support.Thank you

Regards,

Swamy.

B.Chaitanya Kiran

- 2 nodes cluster
- 3 SQL Server instances clustered
- Virtual machines, W2K8R2 on VMWare
- SAN using iSCSI

We have one instance that will start from the services.msc (both the engine and the agent) but not from the Failover Cluster Manager when attempting to bring the service online.  In reality the services start because during the 'Online pending' I am able to connect and query the databases on that instance although it is in the 'Online pending' state.  

The error messages suggest (at least to me) that the cluster is unable to connect to the SQL Server services that are up, therefore it goes into Failed state.  I can figure out why it can't connect to it.

The error message we are getting are the following;

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Server Native Client 10.0]SQL Server Network
Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Server Native Client 10.0]Login timeout expired

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Server Native Client 10.0]Login timeout expired

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Server Native Client 10.0]Login timeout expired

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

Fault bucket , type 0
Event Name: WSFC Resource Deadlock
Response: Not available
Cab Id: 0

Problem signature:
P1: SQL Server (MVSTG)
P2: SQL Server
P3: ONLINERESOURCE
P4:
...
P10:

Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_SQL Server (MVST_f6c6c38b8673478d1cca2c1659ac3f41af00e9_134c2c06

Analysis symbol:
Rechecking for solution: 0
Report Id: c8cfec1e-ef81-11e0-a201-0daf324d05056be606f
Report Status: 4

The content of the the file/log refered to in the Resource Deadlock message is the following:

Version=1
EventType=WSFC Resource Deadlock
EventTime=129623137530033421
ReportType=1
Consent=1
ReportIdentifier=c8cfec1e-ef81-11e0-a201-005056be606f
Response.type=4
Sig[0].Name=Resource Name
Sig[0].Value=SQL Server (MVSTG)
Sig[1].Name=Resource Type
Sig[1].Value=SQL Server
Sig[2].Name=Call Type
Sig[2].Value=ONLINERESOURCE
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
FriendlyEventName=WSFC Resource Deadlock
ConsentKey=WSFC Resource Host Monitor
AppName=Failover Cluster Resource Host Subsystem
AppPath=C:\Windows\Cluster\rhs.exe
ReportDescription=WSFC Resource Deadlock

Can anyone help?  Thanks in advance!!!

Hello all,

We're working on a POC for AlwaysOn and readable replicas, but we're hitting an issue while trying to enable the AlwaysOn High Availability feature of SQL 2012.

I'm following the steps on this link, http://msdn.microsoft.com/en-us/library/ff878259.aspx, but when I get to the AlwaysOn High Availability tab, I see the following information:

The AlwaysOn Availability Groups feature requires the x86(non-WOW) or x64 Enterprise Edition of SQL Server 2012 (or later version) running on Windows Server 2008 (or later version) with WSFC hotfix KB 2494036 installed. This SQL Server edition and/or Windows Server System does not meet one or more of the requirements.

For more information about pre requisites, restriction and recommendations for AlwaysOn Availability Groups, see SQL Books Online.

The only problem here is that I'm running an Enterprise version of SQL 2012 (Evaluation), on a Windows Server 2008 R2 x64. I don't understand what the problem is.

Also, I did install the hotfix mentioned, which installed the "Data-Tier App Framework"

Have you guys seeing this issue? Can someone help?

--- Best Regards, Igor Santos Twitter: @sqlsantos Blog: sqlsantos.wordpress.com

I have set up Alwayson on a database db1, Server1 is Primary, Server2 is secondary. Now I am trying to add a user to both Primary and secondary servers. But when I add the user to the secondary server, getting below error:

The target database, db1 is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability group is not enabled for read access. 

The availability mode is in synchronous mode and secondary is not readable. So how do we add new users who needs access to the database db1 which is configured with ALwayson. Any ideas?

Thanks.

sqldev

Hello. I have a SQL 2014 cluster with two nodes. The nodes run Enterprise edition but I am not using any of the Enterprise features. I want to switch those to Standard edition. Questions:

- Can I do an in-place downgrade of the Enterprise to Standard?

- If not, can I remove (Enterprise) node 2 and install/add a new Standard node? 

Thanks

I'm confused about the expected functionality and interoperability of availability groups and transactional replication. We would like our published DB to be part of an availability group. We have that up, but when we fail over to the secondary, replication doesn't not function as new DML occurs in the secondary (now primary). It does pick back up after we fail back to the original primary.  Is there a way to configure it such that replication continues seamlessly after a failover?

Thank you!

-Peter

PS Here is what replication monitor has to say when the original primary is down:

"replicated transactions are waiting for the next log backup or for the mirroring partner to catch up"

Hi

I'm new to Sql Server and want to install SQL server alwayson clustering on my test environment. I followed the steps by this site:
http://www.derekseaman.com/2014/10/sql-2014-always-ag-pt-10-aag-setup.html
On each node I can connect to SQL Server but why my 2nd node is not available so that I can add it as my 2ndary Replica?
According to this site, till "Always-On Availability Group Configuration" everything was successful.

Hi,

Is there any Capacity/Performace monitoring single(one) 3rd party tool or Microsoft tools for SQL Server,DB2,Oracle,Sybase?

Thanks

We have 2 AlwaysOn servers running on 2 different sites (Site1 and Site2), with the secondary replica NOT READABLE in Site2. All backups are performed on the primary replica in Site1. I have found that AlwaysOn always failover to Site2 on Monday morning, making the replica in SITE2 primary and the replica in SITE1 secondary. I am still troubleshooting why the failover, but this is not my question so far.

What I would like to know if there is anyway I can setup so that if the original primary replica (in Site1) is seen as ONLINE and reachable, the AlwaysOn will always failover back to the original primary replica from Site2?

I want to add a new AD user to give access to the database that is in the Always on availability group. So here is what I did:

1. Added the AD user in the primary replica  & gave access to the db

2. Then added that user on the secondary replica. 

But that user is not getting synchronized on the db that's in the secondary replica. 

Also the master db is not set to be synchronized. Please let me know what I am missing, so that the user can be added to the db on the secondary replica.

Thanks.

sqldev

My transaction log shipping keeps failing

Reference this blog post:

http://blogs.technet.com/b/mdegre/archive/2009/08/11/logshipping-secondary-server-is-out-of-sync-and-lsrestore-job-failing.aspx

I ran the query and the record of transaction logs from the backupset is @ 1:26am.  There are still backups of the transaction logs being taken (see below).  But when I try to apply the log right after the record in the backupset in msdb I get the following error: 

Why is SQL not recording the subsequent Log backups and why won't the next existing .trn file restore

      How do I add my second (secondary) node in my AlwaysOn Availability Group, after adding my head node, and the secondary node is a virtual machine.
    See based on the attached file if it is the correct way?

Getting below error while working on Microsoft Virtual Lab:

https://technet.microsoft.com/en-us/virtuallabs

System Name : SQL Two

"unable to save the alwayson high availability settings return code 0x80070046"

Getting above error while enabling Always on Availability group from SQL Server Configuration Manager.

Dear Guru's, 

I have recently set up a 2 node cluster on top of VMWare with file share witness and need some help. 

First of all, I wanted your view as whether you can see any concern with this set up or any issue that this is not going to work?

Secondly, the issue I am having is every 24 hours or less the cluster services are getting disabled on both nodes. We have already looked at the cluster logs but are not able to pin point where the issue is. 

Kindly shed some light into this.

Many thanks, 

Mohan

After manual AG fail-over from primary to secondary the application is not able to connect the listener name for atleast for 5 - 10 mins

The telnet fails during this time from app server, the listener ip is on muti-subnet.

At the same when i try to connect it from SSMS from a remote machine it works fine. Can someone point me any pointer to stat my troubleshooting.

Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped.

I have had a serious issue with a production AlwaysOn cluster whereby the service did not successfully transition to the secondary node and I cannot find the root cause of the issue.

Some details: It is a 2 node cluster (same datacenter) with a shared disk quorum, Windows Server 2012, both are virtual machines running on VMWare vSphere  5.5. SQL Server version is 2012 Enterprise SP2 CU6

The failover occurred because of a network incident (a spanning tree recalculation caused a connection timeout between both nodes). Initial entries in the SQL Log look normal for this event, for example:

05/08/2015 11:18:06: A connection timeout has occurred on a previously established connection to availability replica 'FIN-IE-PA078' with id [6910F4A9-87E7-4836-BA79-0F41BE90266D].  Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.

05/08/2015 11:18:06: AlwaysOn Availability Groups connection with secondary database terminated for primary database 'UserManagement' on the availability replica with Replica ID: {6910f4a9-87e7-4836-ba79-0f41be90266d}. This is an informational message only. No user action is required.

05/08/2015 11:18:07: Stopped listening on virtual network name 'FIN-IE-PA080'. No user action is required.

05/08/2015 11:18:08: AlwaysOn: The local replica of availability group 'PI-STD-AG' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.

05/08/2015 11:18:08: The state of the local availability replica in availability group 'PI-STD-AG' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.

05/08/2015 11:18:08: AlwaysOn Availability Groups connection with secondary database terminated for primary database 'UserManagement' on the availability replica with Replica ID: {6910f4a9-87e7-4836-ba79-0f41be90266d}. This is an informational message only. No user action is required.

05/08/2015 11:18:08: The availability group database "UserManagement" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.

05/08/2015 11:18:08: Nonqualified transactions are being rolled back in database UserManagement for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.

At this point, there are repeated messages in the log file relating to Remote harden of transactions, all connected to GhostCleanupTask, for example:

05/08/2015 11:18:36: Nonqualified transactions are being rolled back in database UserManagement for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.

This message repeats about once every 1 to 2 minutes, until a point where i manually initiated a failover on the server that was originally primary. At this point, the availability group came back online and the secondary database re-synchronized.

05/08/2015 11:36:31: The state of the local availability replica in availability group 'PI-STD-AG' has changed from 'RESOLVING_NORMAL' to 'RESOLVING_PENDING_FAILOVER'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.

05/08/2015 11:36:41: AlwaysOn: The local replica of availability group 'PI-STD-AG' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.

05/08/2015 11:36:41: Started listening on virtual network name 'FIN-IE-PA080'. No user action is required.

05/08/2015 11:36:42: A connection for availability group 'PI-STD-AG' from availability replica 'FIN-IE-PA077' with id  [98F8CD93-0C9D-44E5-BD6B-68964D391B15] to 'FIN-IE-PA078' with id [6910F4A9-87E7-4836-BA79-0F41BE90266D] has been successfully established.  This is an informational message only. No user action is required.

That is the picture from the SQL Server Error Log. Now for the windows log:

05/08/2015 11:18:02: Cluster network 'Cluster Network 1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

05/08/2015 11:18:02: Cluster network interface 'FIN-IE-PA077 - Ethernet' for cluster node 'FIN-IE-PA077' on network 'Cluster Network 1' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

05/08/2015 11:18:03: Health check for IP interface 'IP Address 192.168.57.62' (address '192.168.57.62') failed (status is '1117'). Run the Validate a Configuration wizard to ensure that the network adapter is functioning properly.

This message repeats several times

05/08/2015 11:18:08: Cluster resource 'PI-STD-AG_192.168.57.59' of type 'IP Address' in clustered role 'PI-STD-AG' failed.

05/08/2015 11:18:08: 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.

05/08/2015 11:18:08: The Cluster service failed to bring clustered service or application 'PI-STD-AG' 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.

05/08/2015 11:18:08: Clustered role 'PI-STD-AG' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made to bring the role online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

My interpretation of this is that the cluster failover attempts failed, because the network condition still persisted. The network interruption lasted approximately 2 minutes, and I would have expected the cluster to come back online at this point, after the restart delay period as suggested in the last entry in the error log. However this did not happen.

Appreciate any support on this.