Hi,
We have 2 nodes running Ubuntu 16.04 and SQL server 2019.
The error we get when we try to enable log shipping is:
Msg 32018, Level 16, State 3, Server mssql02, Procedure master.dbo.sp_add_log_shipping_secondary_primary, Line 129
Log shipping is not installed on this instance.
RegQueryValueEx() returned error 2, 'The system cannot find the file specified.'
Can't figure out what the problem is.
Have you seen this error or have any tip on how to solve it?
↧
Unable to enable log shipping on Linux
↧
This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED
Hi Guys
I am having an issue with an SQL Availability Group and am wondering if you can lend a hand troubleshooting:
I have 2 SQL Servers on 2017 running on 2012R2.
I have set them up in an Always on Availability Group with Availability mode set to Synchronous Commit and Readable secondary set to No.
I thought this was all working fine but when I was doing something unrelated in Microsoft SQL Management Studio I noticed that the Availability Replicas status for the secondary had a red cross by it. I then checked the availability group dashboard and can now see under the secondary:
Synchronization status: Not Synchronizing
Failover Readiness: Data Loss
This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.
The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database should be in the SYNCHRONIZED state.
I have checked firewall ports and 5022 is open and not blocked. I have also checked netstat to confirm sqlsrvr.exe is using 5022 which it is. I am now starting to think this could be permission related.
Can anyone help point me in the right direction on where to go from here?
Many thanks!
↧
↧
AlwaysOn vs. Read-Scale
Hello,
I wanted to kindly ask about the differences between AlwaysOn and ReadScale, regarding the following context:
- We have a live Business Central Server and now want to create replicas of it, for various apps to hit them instead of the live (of course, this means that "real time" sync is a paramount)
- For this, we were trying the Transactional Replication, but since we wanted to mirror the Server settings also (not just the data(bases)), we decided to look at Availability Group Clustering
- I am aware that there are two options when it comes to Availability Groups
- AlwaysOn (requires an underlying WSFC)
- Read-Scale (no Cluster Manager required)
However, since I have no prior experience with Clustering, I am trying to avoid spending days on trying to set up something I will end up having to replace, so, please, if you could point me to the right direction:
- In general, practical terms, what is the difference between the AlwaysOn and Read-Scale (apart from the Cluster Manager)
- If I do not need the overhead of the HA solution, but just want the server settings and the data to be mirrored to n number of replicas, would Read-Scale suffice (or what I want is intrinsically tied to an HA solution, hence the Clustering)?
- If you have any other advice regarding an optimal solution, please do share.
With thanks and kind regards,
Bogdan
BogdanU
↧
Replication distribution database in Always On availability group
Hi,
I have configured distributor in always on. One thing I am noticing don't know it's default behavior, not able to find full details on "Monitor and sync replication agent jobs" on how it works. I have to always drop replication jobs Log reader agent, snapshot agent, distribution agent jobs on secondary then only when I do fail-over all jobs are syncing successfully to new primary(prior secondary where I have dropped all jobs). If I don't drop replication jobs on secondary then when I do fail-over "Monitor and sync replication agent jobs" is not enabling or adding replication jobs on new primary. Is it default behavior?
Thanks
↧
Always-on Hardening interruption and the default Always-on xevent
suppose I am having a AG with 2 replica , both in Sync mode. And we know in order to commit a transaction , the log required to be hardened in the secondary replica and acknowledge the primary it's hardened.
So what's the mechanism on the primary to give up to receive the acknowledgement from secondary (Suppose the hardening for log is successful ) and commit the transaction without waiting it ??
And secondly is that the default always-on xevent should be turn on ? will it draw so much overhead on the overall system ?
↧
↧
Rebuild SQL Server "fail-over Cluster Installation" Node in a 2 Node- Clustering Environment
Environment:
Windows Server - 2008 R2
SQL Server - 2008 R2 SP2 Enterprise (x64) ; Type- Cluster
Nodes part of SQL Cluster-
Server-A and Server-B
Server-A( failover Cluster Installation done)
Server-B(Add node Installation done)
Scenario:
i.We had issues with 'Server-A' where it got corrupted and Windows team has asked us to rebuild the Server-A and the SQL Installation as well
Query:
1.Will the SQL setup will allow us to perform "add node" Installation, which is the rebuilded node, where previously (SQL- failover Installation ) was performed
** SQL Server "Add node installation" succeeds based on the current Active node(where SQL Services are up and running) of the cluster -or- the node where SQL"failover cluster installation" is performed first during initial SQL Cluster Installation.
Solution:
a.If, the Add node installation is correct option , please get me the blogs/forums that justify it
or
b.If I need to rebuild the complete SQL Cluster, please get me the blogs/forums that justify it
PREM GOKULL
↧
Rebuild SQL Server "fail-over Cluster Installation" Node in a 2 Node- Clustering Environment
Environment:
Windows Server - 2008 R2
SQL Server - 2008 R2 SP3 Enterprise (x64) ; Type- Cluster
Nodes part of SQL Cluster-
Server-A and Server-B
Server-A( failover Cluster Installation done)
Server-B(Add node Installation done)
Issue : Server A got shutdown abruptly and systems team is unable to get it back online and has asked to rebuild the server .
Since Server A had Full installation in this case what steps should I follow to get the server rebuilt from scratch and add to the cluster .
Is Add node installation is correct option here ?
KSH
↧
SQL 2017 Always On High Availability cannot connect to read-only replica
Used the following instructions to try and setup for the secondary replica to be read-only through the listener.
Every connection that I try still goes to primary for read-only.
↧
Event ID 35201 and 35206
What's the difference between these two error? If using the default session timeout 10s. disabling the replication network interface more than 10s will have Event 35201 and 35206
However disabling the replication network less than <10s , still have event ID 35206. WHy ?
Image may be NSFW.
Clik here to view.
↧
↧
Preffered owner for Windows Cluster IP
Suppose I have 4 nodes of Windows cluster node , 2 in Production site, and 2 in DR site .
The cluster IP was owner by node 1 in Production . When I boot the node 1, the cluster IP failover to the Node of DR .
Can I control to failover to node 2 of Prod site only ?
Windows is from Windows sever 2019 , and the roles is a SQL Server always-on role
↧
How to recover data from backed up * .MDF, * .LDF files
Hi. everybody.
I want to recover important data that was deleted 2 years ago. While upgrading the server a while agoI have mdf and ldf files backed up on the sql server.
In this case, I want to recover the deleted query execution history (query, execution date, etc.) and deleted data.
in this case. If there is a backed up .MDF or .LDF file, is it possible to obtain the above deleted query history and deleted data?
Please let me know how to do this.
Thank you.
↧
AG groups and cluster witness
Hello,
We are currently running SQL2014 ent on Windows 2012. We have a 2 node cluster with 4 SQL AG, 2 primary replica residing on node1 and 2 residing on node2 for load balancing purposes. We also use a file share as the witness, but are thinking about moving to a disk share witness as we seem to have failover issues that seem related to possible network latency/connection issue? Both nodes are in the same LAN. Was told the shared disk witness may offer more resilience to network issues.
Anyone switched from file share to disk witness?
thanks,
plucki
↧
.ldf files are too bigger than .mdf files in SCOM databases
Hi There,
I have a production issue where all SCOM databases (SQL 2012 SP3) ldf files are getting bigger than mdf files. All SCOM database are pointing to always-on group with two diffrent AG's.
The current size of databases are:
DB NAME .mdf Size .ldf Size
--------------------------------------------------------------------------
OpertManager 30GB 167GB
VirtualManager 2GB 130GB
Orch 8GB 15GB
VManagerDW 100GB 71GB
we have also log backup job is running everyday but doesn't look like much difference. I don't want to shrink the log files as all 4 databases are in AG's group.
Can someone please help me to fix the issue?
Cheers,
Ken
↧
↧
SQL server availability group cannot access database after disabling sql service
Hello everyone,
I''ve completed this setup:
OS: Windows server 2016
Database: SQL Server 2017
2 node availability group configured with automatic failover on both nodes. Fileshare witness configured, both nodes enabled readable secondary replicas.
Database showing synchronized on both nodes. Availability group state: Healthy, configured normal quorum and Fileshare witness and node 1, node 2 all three has 1 vote and state is online.
The question is i cannot access database when i stopped SQL service on one of nodes. Failover occurs to DB2 and status changed to primary when i stopped SQL service on DB1. When I try to select from BikeStores in DB2 this error shows:
database lacks a quorum of nodes for high availability.
Is my configuration wrong? or am I using try to achieve not possible scenario in availability group?
↧
SQL Server Cluster is offline but AG works
I am trying to understand the AG scenario that is configured in the past and is working currently.
This is a multi subnet scenario but the cluster was configured with just 1 IP address. Probably a mistake that was made in the past. But surprisingly everything works just fine.
I have a cluster clust-prod that is configured with 1 static IP address say 10.x.x.x
I have 2 nodes from 2 different subnets
Node1: arz-db1
Node2: kty-db2
I have an AG ProdAGdbmarketing setup. I have listener DBprodlstn1 configured with 2 static IPS
ListIP1: 10.y.y.y
ListIP2 : 10.z.z.z
Currently the cluster in Failover cluster manager says offline & IP address says offline
Cluster Core Resources:
Name: clust-prod Offline
IP Address 10.x.x.x Offline
Ping clust-prod (cluster name) does not work
But surprisingly ping of Listener name, Availability group works just fine. I tried a manual fail over to Node Node2: kty-db2 which works fine. Then failing back to Node1 also works fine.
I would think, the cluster is setup incorrectly to begin with. I should have been setup with 2 IPs instead of one.
Although the cluster shows offline, how can AG, listener, failing over work?
Could anyone figure out how this works.
↧
Restore master database will join back to the AG ?
If the master database was crashed on one of the AG replica . then I restore the master database will make this replica automatically join back to the AG ?
↧
SQL Always On - Database becomes inaccessible through Listener after failover
Always On configuration with 2 Azure SQL VMs and Cloud Witness.
Server1 - Primary Node
Server2 - Secondary Node
Listener1 - AlwaysOn Listener
I connect to SQL instance through Listener1. All looks good, database synchronized and accessible, replicas are in sync and all is healthy in AlwaysOn Dashboard.
SELECT @@SERVERNAME
Shows - Server1.
Now I failover.
Disconnect from Listener1 in SSMS. Connect to Listener1 in SSMS. Run same command:
SELECT @@SERVERNAME
Shows - Server2.
But now database becomes inaccessible:
The database AdventureWorks2016 is not accessible. (ObjectExplorer)
AlwaysOn Group shows as secondary and Server2 with question mark:
Image may be NSFW.
Clik here to view.
Is this normal behavior, what could be wrong?
Thanks
↧
↧
Multiple instance of CRM Async service running in SQL Server Windows Fail Over Clustering
How should we install and configure CRM Async service in a Clustered SQL Instance (Windows Fail Over Clustering) so that only one instance of Async services should run on an Active/Passive node. While I move the node, I want to automatically run the async
services installed in Sql Node 2. ie. When SQL Node 1 is active , all CRM services installed should be running and SQL Node 2 should have all CRM Services with status not running mode. When I switch to Node 2, all CRM Async services should automatically run
in Node2. Can anybody please help. Thanks in advance
Many Thanks, Suresh Kumar VC
Many Thanks, Suresh Kumar VC
Suresh Kumar VC
↧
Unused Indexes in alwayson
I have two nodes in alwayson, primary is used for write and i have used secondary for read. The usage of indexes is different in the two servers. How can I properly determine the unused indexes?
I have doubt that the indexes which are affecting the operations in primary might be helping reading data in secondary.
↧
SQL Server 2019 log shipping setting error on Linux. 'Log shipping is not installed on this instance'
Hi,
We have running SQL server 2019 on
CentOS 7.
The error we get when we try to enable log shipping is:
Msg 22001, Level 1, State 1
Msg 32018, Level 16, State 3, Procedure master.dbo.sp_add_log_shipping_secondary_primary, Line 129
Log shipping is not installed on this instance.
Can't figure out what the problem is.
Have you seen this error or have any tip on how to solve it?
↧