Ghost Records
SQL Cluster with issues when disconnecting network card from Primary Replica
Hello
Need one hint on HA to a prob i have in a test env.
- Cluster of 2x nodes SQL Server 2016 @ Windows server 2012R2
- Have 3 databases in HA group and running fine.
- Did some switchover within the SQL and runned fine so far.
- Did tests to the Windows server and they were not so good, on of the tests was to disconnect primary Replica _network card_ on the cluster and Everything stopped.
- Got only one Network card per Node
- If i have Node1 as primary and fail it over, the cluster crashes
- If i have Node 2 as primary and fail it over, the cluster stays ok and the SQL HA is pointed to the node1
The secondary replica that should be taking over, did not, and left the Windows Server Failover Cluster
The databases become unused on Secondary Replica.
To repair this, i do: turn back the network on primary replica, re-add the secondary replica to the cluster, make the Role to go Online on the Secondary Replica. Seems very odd
Im running this infra on a VM environment.
And i'm doing my first SQL Server HA setup.
What am i missing?
Thanks in advance
Convert help of .backpack to .BAK in on premise SQL server
Hi Team
I have sql server 2016 ,the backup file which is exported in the form of .bacpac to .BAK format in the on premise.
Followed the below link but no luck
https://stackoverflow.com/questions/7847189/azure-sql-database-bacpac-local-restore
https://vimvq1987.com/import-bacpac-sql-server/
Is there any way can we convert.
Also https://github.com/shawnweisfeld/SqlAzureBakMaker I dont know the storage key license n other stuff.
Just need to extrack as .BAK then restore in the on premise of sql server 2016.
Regards, S_NO "_"
How to add a second a-sync read-only node in always on AG? (for a 24/7 mission critical system)
Hi All,
How to add a second a-sync read-only node in always on AG? (for a 24/7 mission critical system)
SQL Server 2016 SP2
Windows server 2016
Following is the architecture.
Node1 , Node2, Node3 (new node) in primary DC
Node4 in Secondary DC
Regards, Ashif Shaikh
Distributed Availability Group for a Data Warehouse.
Greetings.
I was told that we're going to use an AG to migrate our DW environment about 800 miles from one data center to the other. Obviously my concern here is if the AG will be able to stay in sync, specifically because it's not an OLTP system, but instead has hundreds of jobs that manipulate large amounts of data.
Yes, I've already expressed my concerns.
To make this already awesome situation even better, most of these aren’t currently in an AG, and running in SIMPLE mode.
All said, my first stop is to try and estimate if the pipe is going to be able to handle the potentially hundreds of gigs of changes each night, but as mentioned these DB’s are in SIMPLE mode so I don’t even know how much data is changing.
My thought of how to figure all of this out is to put the DB’s into FULL recovery model and start taking uncompressed transaction log backups. I believe (not positive) the size of the backups would effectively represent how big the changes are?
I’m open to other ideas for figuring this out, so please don’t be shy.
Thanks in advance! ChrisRDBA
Availability Group questions.
Greetings. I've been doing some research on using an AG for a migration from one data center to another, separated by 800 miles. Seems doable if the pipe in between can keep up.
However, something I keep reading about is folks having an AG in one DC (both Primary and one Secondary), then a second Secondary in another DC. So 3 nodes in total.
This would make sense if my plan was to leave this up and running for the long term, but I it's not. My plan is to have this up for a short time (like a month, then get rid of it).
That said, is having 2 nodes in my current DC a real requirement? Or instead can I just have my Primary in the current DC, and the Secondary in the DC we're migrating to?
I plan on running this in aSync mode, withOUT auto failover. I realize the risk here is that if my Primary tanks it would take some manual intervention to failover, but are there any other risks associated w this?
Edit:
Another question. It looks like 2016 now allows AG's to be ran in Standard Edition. Can one node be Enterprise and one node be Standard?
Thanks!
Thanks in advance! ChrisRDBA
Change shared network location accessible by all replicas on aoag
I want to change the shared network location accessible by all replicas I first set up in an aoag. A new server has been stood up specifically to act as a file share witness and now I have to change the existing share network location
to point to directories I have created and shared on the new server. I've updated it on the server cluster through theconfigure cluster quorum settings wizard, but not sure where to do it on sql server aoag. Is that something that updates itself automatically or do I need to go somewhere in the aoag and manually update?
Best Quorum Configuration and Voting assignments for 5 node cluster ( 3 + 2 ), 1 FSW
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
1 ) How to prevent cluster down for above situations ?.
2 ) Is configuring lowerquorumprioritynodeID for one of secondary node would help this situation?.
3 ) How to remove node vote weight in Windows 2012 R2 ?.
4 ) What is the best quorum model and node weightage assignments for 2 + 3 node configuration?.
Mahadevan N
Nodeweight vs LowerQuorumPriorityNodeidin Windows 2012 R2
Hi Team,
Can we set Nodeweight = 0 in Windows 2012 R2. I've noticed that nodeweight replaced by LowerQuorumPriorityNodeid ?.
Mahadevan N
Database goes into recovery mode and wont accessible for long
Hi All,
I think this is the question I will eagerly wait to see answer from you.
We have the database which goes In recovery after restoring it for about 6 hours and we were just waiting whole day because of it.
While the restore status shows 100% completes though. I tried to expand the db but it says"The database IMDB is not accessible. (ObjectExplorer)"
Can anyone who have face in the past please help me out.
Help must be appreciated!!
Dilip Patil..
Best Quorum Configuration and Voting assignments for 5 node cluster ( 2 + 3 ), 1 FSW
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
1 ) How to prevent cluster down for above situations ?.
2 ) Is configuring lowerquorumprioritynodeID for one of secondary node would help this situation?.
3 ) How to remove node vote weight in Windows 2012 R2 ?.
4 ) What is the best quorum model and node weightage assignments for 2 + 3 node configuration?.
Mahadevan N
SQL Server 2017 Fail-over Cluster License
Good day!
I have an SQL Server Failover Cluster Setup (2 nodes). When I installed SQL Server 2017, I used enterprise evaluation first. And then I clustered the SQL Servers. My problem now is I want to use my SQL License for standard edition and I'm trying to upgrade my sql servers from evaluation to standard edition. But I encountered this error:
Rule "SQL Server 2017 Failover Cluster Edition Downgrade" failed.The edition of the selected SQL Server instance is not supported in this SQL Server Edition downgrade scenario. The source Evaluation edition and the target Standard edition is not supported path.
My question is what does this error means? Is standard edition license compatible with the SQL Failover Cluster?
I hope someone could help me with my problem.
Can Replication co-exist with Basic Always On Availability Groups
Hi All,
I need to set up a 2 node Always -on AG cluster . This will be Basic Availability Group. That means, database on secondary node is node is not readable. This is because we are using Standard edition and not Enterprise Edition.
I would like to know if I can have replication enabled on this Always-On AG database and have replication seamlessly resuming after failover. In this replication scenerio, I will be using a standalone instance to host the subscriber database .
If that is possible, is it best to configure replication first and then AG or the other way around?
Please advise.
Fileshare Witness (FSW) and AD Service Account Permissions
Hello,
Win2k12 r2 OS, 2 node fail-over cluster, single instance SQL2k12 Ent ed hosting few user databases.
The VNN's CNO needs to be part of FSW (a windows share on a remote machine residing on the same subnet where the two node Alwayson SQL servers are residing) and should be granted the permissions to the FSW. However, not sure whether AD SQL Server service account that is used with the AlwaysOn sql servers needs to be granted similar permissions to the FSW or not.
If anyone can confirm this along with some supporting reasons, that would be great.
Thanks.
Victor
Victor
Is it possible to configure Always On between two SQL 2016 between two different data centers
Is it possible to configure Always On between two SQL 2016 between two different data centers
Data center 1
Server A --->SQL standalone Instance1
Server B --->SQL standalone Instance2
Data center 2
Server C --->SQL standalone Instance3
Server D --->SQL standalone Instance4
two subnets are used for two data centers
Is Always on possible between these data centers? and also automatic failover
How many Listener we need to create?
Regards,
vignesh
check if database is READ_WRITE then running backup
Hi,
I have this database that is participating in an aoag and I want to have some intelligence in the backup jobs to check if the current db is the primary replica and if it is, to proceed with the backup. But I specifically want to include this section of t-sql in the overall script;
SELECT (DATABASEPROPERTYEX('database_name','Updateability'))
this will return READ_WRITE or READ_ONLY
is there any way to use this to get the job set up?
Basic Availability Group Question
I have a source SQL Server database setup in AWS (Standard Edition). I would like to bring copy of the data to in-house for reporting and feeding data for ETL processing via Informatica.
Now, I found this article
That says BASIC AG doesn't allow read access at replica. My understanding is Full/Advanced AG will need Enterprise Edition on both ends and the same will be true for BASIC AG (Standard on both ends). I assume even if I have an Enterprise Edition on the secondary server still I can only setup BASIC AG.
The reason for this clarification is that we have Enterprise Edition in our internal environment and we want to read the data as stated above.
Will it be possible?
Connect to secondary replica from SSMS
Hi,
I have a HA Always On set up with 2 nodes. I am looking for a possibility :) to connect to secondary read-only replica from SSMS. I read several articles that says set ApplicationIntent=ReadOnly in advanced options, which I already did. Every time when I connect to listener, I end up in connecting to primary server. I created a sql user 'test', I set deny connect in primary, then I connect with this user login to secondary as this user is active[grant status] in secondary. I am getting login failed error. I am new to HA Always On. So wanted to check if this is the expected behavior, if not how can I make my scenario working. Also, when I use ApplicationIntent=ReadOnly in SSMS and connect to AG listener, will the @@servername show secondary replica server name?
Thanks in advance for any help or suggestions!!!
Migration of SQL databases server to new hardware
Hi Gurus,
Thanks everyone for all your help and support!
I have small query regarding migration of all existing VM's (SQL server 2012 databases servers) to new hardware (prime quest).
With existing db servers we have cluster (3 node cluster) with one primary node and other two is secondary node (one is in auto fail over and other is in manual ) with Always On setup.
I am little worried as these is production environment and too big databases...have few queries like :-
- When we migrate these servers to new hardware what happen to AG's group? will it work?
- Do I need to follow any sequence or steps like start migrating with secondary servers first or failover to other node in order to move the node first.. ?
- Always On will work after migrating to new h/w or I need to configure AG from scratch?
- Do I need outage when we migrate these servers?
Regards,
ManishaK
Distributed Availability groups - second availability group is disconnected.
Hello there,
I am setting up distributed availability group with SQL server 2016 . Both the availability groups are in different domains.I have followed the steps mentioned at https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-distributed-availability-groups?view=sql-server-2016
and as these AGs are in different domains I have also configured the certificates on all replicas as mentioned here,
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/domain-independent-availability-groups?view=sql-server-2017
But after completing distributed availability group setup, second availability group as well as listener for secondary availability group is showing in disconnected state.
The remote listener "AG_Listener2.remote.r" is directly accessible from the local primary replica. Could anyone help me understand how can I get secondary availability group in a connected state?