I'm trying to restore a database using SSMS GUI. In "Select backup devices" window if I click the Add button there the window and the whole process hangs like it will never work.
I tried to clear backup history, but that didn't solve it.
I tried with a couple of other databases, but same thing.
It was working fine!
Any advice please!
In our company we have a 2 node Cluster using AGs across them in an IaaS setup in Azure. For quorum we are also using a cloud witness.
Security have come to me saying they want rotate the Primary Access Key on the storage account. I understand that this means I will have to update thecloud witness using the Secondary Key Access. Is this as simple to do as running through the configure cluster quorum wizard and on the configure cloud witness screen using the Secondary Key?
Also what would I do if they also want to rotate the Secondary Access Key as well?
Hi There,
I have a 3 node AlwaysOn Availability Group cluster. Each node a has vote for quoum and there is no witness.
Node 1 and 2 are in the same data center while node 3 is in a remote data center connected by a high speed layer 2 link. All nodes are on the same subset. Node 1 is a primary for one AG1 and node 2 is a primary for AG2 while node 3 is only a secondary for both
AGs.
The other night node 3 crashed (the hypervisor went down) which seems to have caused nodes 1 and 2 both to fail at exactly the same time a few minutes later, which seems odd as the whole point of the cluster is to avoid this scenario.
In the system event log I can see the below error on nodes 1 and 2 which I believe is the result a failed health check.
Looking in the failoverclustering diagnostic log on nodes 1 and 2 I see the this error just a second later and then the cluster service is terminated on both. I've searched the internet for references to "GumLockIsStuck" but come back with
nothing but I believe this is related to updating the cluster databases with the cluster status on all nodes.
Because the above error was referring to no reporting for 600 seconds I went back 10 minutes in the same log and could a whole bunch of errors like this one stating nodes 1 and 2 were unable receive an ACK from node 3 which had of course crashed (around this time).
So what looks like has happened is node 3 has gone down and nodes 1 and 2 can't update the status of the cluster and because of that they have then stopped the cluster service on themselves. This doesn't seem right at all so can anyone explain this behavior?
Cheers
C
1- Setup full backs to happen Saturday nights.
2- Setup differential backups to happen every night, execpt Saturdays
3- This is on a VM machine, and we take a snapshot of it every Wednesday night.
4- SQL Server records the snapshot as a valid, full backup, although it is marked as is_snapshot = 1.
5- All differential backups after the snapshot are rendered useless. They are done based on the snapshot backup, not on the actual valid full backup done on Saturday.
After research I found KB article 951288 (http://support.microsoft.com/kb/951288). Apparently this is a Microsoft issue.
So, how do we tell SQL server to ignore the snapshot backup when doing the differential backups? And no, we do not want to stop doing our snapshots on Wednesdays. Is there a solution or a work around to this?
This is really annoying and dangerous that SQL Server would consider these snapshots as valid, viable full backups on which to base its differential backups.
Help much appreciated,
Raphael
rferreira
Good morning experts
Secondary replica database is in suspect state. How to troubleshoot it?
Kiran
Kiran
Dear all
We have have an AG setup,and every time after we perform the AG failover and the primary will be moved to secondary, however, ti will not be reachable anymore. we can only reboot the instance to fix this.
Because we are using the standard version, the readable secondary config in AG is set as "No".
Error message:
"Connection open error . The target database, 'A', 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",
Is this a bug for the SQL? or do you have any idea on this?
Kiran
Hello,
I have two SQL Servers with Always On Available Group at remote sites. In my topology, I need that user alocated in the remote site connect in remote SQL but when I try, this server show me information about read only
Please, as possbible turn on write function to secondary SQL server attached on Always
Regards
Jorge Miranda
We have a Sql Server 2016 multi-subnet environment with Always On availability groups to meet our high availability and DR goals.
We are also utilising Service Broker on this platform. I am unsure if there's going to be any issue with this configuration.
Now according to link at the bottom it says "SQL Server Broker is not Multisubnet aware" but I'm unsure of what issues could this have. Is this not going to be a MS supported configuration?
We are fine with freshly populating the SSB queues in case of failover dealt at our application level. Are there any issues that you see with this? Advice on any alternative routes will be useful.
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/service-broker-with-always-on-availability-groups-sql-server?view=sql-server-2017
Hi,
As per the Microsoft How much Availability we can achive with SQL Server AlwayOn 2016?
like 99% or 99.9% or 99.99% or 99.999% or 99.9999%
Reference: https://www.sqlshack.com/data-synchronization-in-sql-server-always-on-availability-groups/
Hi Team,
We have below setup of windows 2012 R2 clustering, and need to know best quorum setting and voting assignments
Primary site
2 Nodes and File share witness configured in Primary site with Dynamic witness enabled.
Secondary site
3 Nodes
------------------------------------
Primary site sustains if one by one node failure in secondary site.
Primary site will loss quorum and cluster will bring down in any one of following cases.
1 ) When secondary site fails with all nodes together
2 ) WAN breakout
3 ) How to prevent cluster down for above situations ?.
4 ) Is configuring lowerquorumprioritynodeID for one of secondary node would help this situation?.
5 ) How to remove node vote weight in Windows 2012 R2 ?.
6 ) What is the best quorum model and node weightage assignments for 2 + 3 node configuration?.
Mahadevan N
Hi,
I have requirement that user should be only connect to secondary replica for read connection through the listener. I tried various options and it didn't work such as disable login on primary replica, deny connect on primary replica.
Anyone have any suggestions here.
Regards,
-kccrga
Rahul
Hi, we are looking into 'Allow failback' option in sql cluster as we would like sql to run on its preferred owner after patching is done. Patching is done by a different team and they don't put sql back to its original node most of the times - they have some issue currently. I would rather not touch the cluster but we are looking into the option of failback anyhow.
Prevent failback is our current default - which works well.
I wanted to know what are the disadvantages of using 'Allow Failback- Immediately' option in sql cluster, Thanks.
One scenario that i can think of is during a actual issue on the current node, sql fails over to the other good node, but then tries to fallback to the 1st bad node, which fails it to 2nd good node - How long does this cycle runs for and does SQL ends up in a failed state?
D
Hi Team,
Hope someone can help.
we have got a SQL Server 2017 Availability group on a multi subnet AG.
we are trying to configure linked server connection to the availability group from another stand alone SQL server (SQL server 2014).
The Linked server is giving a timeout and i think its trying to resolve the listener name to the IP which is not active. can someone help in this?
is there a way we can configure multisubnetfailover=true for the linked server?
skv
Hi All
I'm looking at a disaster recovery solution for a SQL 2016 server which is using Polybase. Does anyone know if log shipping the three Polybase databases is supported, or if I needn't ship all three?
Thanks
Stephen
create AG Listener on Windows core server need powershell command to create new listener