Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all 4532 articles
Browse latest View live
↧

Cluster resource Failing in AG Group

May 20, 2019, 3:31 am
$
0
0

Hi!,

I have a 2 node Azure SQL 2016 Always On cluster.

Once or twice a day it seems tries to fail over and fails. This kills any agent jobs running at the time. There are no errors in the cluster events log, but in the windows system log I get the following:

Cluster resource '<AG-GROUP>' of type 'SQL Server Availability Group' in clustered role '<AG-GROUP>' failed.

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.

Any idea what might be causing this?

Zoe

↧
Search

Distributed Availability groups - second availability group is disconnected.

May 20, 2019, 5:31 am
$
0
0

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?

↧
↧

quorum question

May 21, 2019, 5:53 am
$
0
0

Hi,

We have setup a 2 node SQL 2016 AG, in our setup we did configure our Quorum as a file share on a server that is not part of the cluster.

When we manually run a failover the Nodes changing place, but it looks like that when one of the Nodes goes ofline ( shutdown the server or removing the netwerk cable) the failover dont take place.

Any idea why is this happening? or do I mis understood how the SQL AG works.

Thanks 

Shahin

↧

do we required SA to achieve SQL Server Clustering

May 22, 2019, 2:21 am
$
0
0

Hi,

i have two virtual machine and want to do SQL Server Clustering. do i required SQL Server Software Assurance (SA) in order to achieve SQL Server Clustering.

Pls guide, may this question not relevant to this forum but really appreciate if someone help me or direct me correct forum.

pls share any link or guide which describe this.

thx

iffi

↧

Availability group & backups from secondary

May 22, 2019, 9:23 am
$
0
0

We have an availabiltiy group configured using asynchronous replication sending data to multiple read only replicas.

On the primary database we have log shipping setup for our DR solution using a 3rd party tool for better compression and to help us reach our RPO target.

We have a data warehouse that needs to read from the transaction logs however since they are being compressed from a 3rd party they cannot do so without first decompressing them.

Can I setup native log backups on one of the read only replicas and grab all of the transactions?

My hunch is that the secondary will not contain all the transactions since it is already being backed up on the primary and sending the truncation command, but thought I would ask.

↧
↧

2 Aways-On in same server

May 22, 2019, 10:45 am
$
0
0

Hello,

- My envoriment is two server with SQL 2014 - v 12.0.6024.0.
- I have two instance in use (production and homologation)

SQL01/INSTANCE01
SQL01/INSTANCE02

My problem is about SQL Aways On, in this moment just one instance work fine, but I´m problems to setting the second instance. My doubt, It´s possible have two availability groups in the same servers?

Tks

Jorge Miranda

↧

Buying the Licenses of SQL Server Stranded

May 22, 2019, 12:35 pm
$
0
0

Hello Team

we have small business and we want to buy license in Saudi Arabia, Jeddah 

but I don't know the method of purchase of License  

↧

SQL 2014 AOAG error message

May 22, 2019, 9:35 pm
$
0
0

Hi All,

I hope someone can point me to right direction.

In our environment we have asynchronous AOAG setup. We are running 2 instances on one VM (this is how I have inherited and I am not in favor of this setup). Our secondary node is not readable. We are trying to run a script on one of the db's on primary node. and getting below error message. 

NULL

Starting copy...

SQLState = 37000, NativeError = 976

Error = [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]The target database, 'XXXXXXXX', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enab

led 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.  For more information, see the ALTER AVAILABILITY GROUP statement in SQL

Server Bo

SQLState = S1000, NativeError = 0

Error = [Microsoft][ODBC Driver 11 for SQL Server]Unable to resolve column level collations

NULL

BCP copy out failed

NULL

     There is no info available in error log related to above message. This is what I have tried so far

1. Removed db from AOAG on primary node, deleted on secondary node. Still same error.

2. Dropped database from server. Restored and try without adding to AOAG still same error.

3. Added restored db to AOAG , still same error.

4. I have made sure that I am logged in on primary node.

5. Most of recommendations on google says enable secondary replica to 'readable'. Which would not apply because same script is working as expected on other databases on server.

Any help is appreciated.


↧
Search

DB Alias

May 24, 2019, 9:51 am
$
0
0

What is the use of DB alias?

Let me explain, 

applicaiton name is: sales.

DB server name is: server1.abc.com

DB name is : DB1

but instead of using actual DB server name, we are using salesdb.abc.com,1433

i know that this is best practice to use alias name instead of actual DB servername?

What is the advantage?

↧
↧

SQL Server Patching on AlwaysOn Servers

May 26, 2019, 11:57 pm
$
0
0

Hi,

we have 4 node cluster and SQL serversrs are running as below:
Primary DC:
SQLA1
SQLA2
SQLA3
SQLA4

DR :
SQLB1
SQLB2
SQLB3
SQLB4

Current Owner Node is running under SQLB1 and there is Alwasyson AG configured in between nodes
AG1: SQLA1 & SQLA2
AG2: SQLA3 & SQLA4
AG3: SQLB1 & SQLB2
AG4: SQLb3 & SQLB4
Async AG from AG1 to AG3
Replication(Transactional) Between these nodes:
AG1 & AG2
AG3 & AG4
Now i would like to do SQL Server patching (Production Environment)on all 8 servers, for that which is the feasible way to proceed. Kindly suggest the way forward

Suggest me in that way if suppose anything happen during patching between first two nodes so that we can rollback easily.

Also what kind of rollback steps need to be take care.. Thanks

Regards,

DBA

DBA

↧

Maintenance Plan Log Backup File are heavier in size than normal.

May 27, 2019, 2:56 am
$
0
0
Hello all. I have setup DB backup jobs (including Full, Differential and log) on SQL Server 2008 R2 with SP3 - OD (which is our production physical server) through maintenance plan wizard. The concern is regarding the log file backups which is getting heavier in size (from 600 KB to 5 GB sometimes) than the normal log backup which consumes mostly 600 KB to 800 KB. The same job has been setup in another instance but there the log file is only 200 KB to 300 KB. There is only 1 database (Full-recovery) in this server and it is connected to an application doing OLTP (very I/O intensive). I have set the log backups with compression. Although we have enough space to accommodate the log files in the shared drive, but this seems unusual. What is that I am doing wrong? Can anyone assist? Please let me know in case you need additional info. Thank you!
↧

Permission problem on sys.availability_groups

May 27, 2019, 5:36 am
$
0
0

Given two separate SQL Server (both have version Microsoft SQL Server 2016 (SP2-CU5) (KB4475776) - 13.0.5264.1 (X64) )
with having some AlwaysOn High Availability groups.
We created a SQL Login on both server with only public rights with the script show below. 
The problem is that on ServerA the user can see the content of sys.availability_groups while on ServerB it cannot see anything.
By default the user shouldn't see any content of the system view.

USE [master]
GO
CREATE LOGIN [test_user] WITH PASSWORD=N'passw0rd', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
GO
CREATE USER [test_user] FOR LOGIN [test_user]
GO
execute as login = 'test_user'
go
select suser_name()
GO
SELECT * FROM [master].[sys].[availability_groups];

The following script is used to check the existing rights:

select * from sys.server_permissions per 
join sys.server_principals pri on per.grantee_principal_id = pri.principal_id
where per.permission_name in ('VIEW DEFINITION', 'VIEW ANY DEFINITION')
  and pri.name = 'test_user'


↧

connection closed

May 28, 2019, 6:03 am
$
0
0

Hi Guy's,

We have setup SQL 2016 AG in a single Subnet envirorment.

We can Faiover from Node1 to Node2, but we have a problem with application that accessing the DB in SQL AG.

when we do a manuall failover we can see that application lost its connection to the DB.

We did change the TTL at the cluster to 60 second but still application lost connection to the DB.

Application use ODBC 11 to connect to the DB.

Any idea on how to correct this? we dont want to force the users to close their connection to the DB and restart the application.

Thanks

Shahin

↧
↧

Enabling/Configuring Log Shipping while DB is online

May 28, 2019, 1:10 pm
$
0
0

Is enabling/configuring log shipping something that needs to be done while the database is not serving traffic at 3 am and apps turned off?  Or can this safely be done during regular but lower traffic times?
Using SQL server 2016 sp2 Standard Edition, the DB is currently in Simple recovery mode

Thanks!

Patrick 

↧

Disk owner and role did not failover to other node

May 29, 2019, 10:09 am
$
0
0

I have a two node windows cluster .I am Facing an issue .After fail-over, Owner  node for role and Disk are not changing . 

How fix this issue.I searched in google i have not seen any useful link.

↧
Search

Always on : Primary database relocation

May 30, 2019, 4:13 am
$
0
0
If I would like to relocate a database files to another faster drive in the primary replica, is it required to rebuild the whole replication ???
↧

Failover of AG not happening after upgrade from SQL 2016 to SQL 2017

May 30, 2019, 6:06 am
$
0
0

Hi,

I am in a weird situation. I have a Distributed AG setup between London and Flint servers(2 London and 2 Flint). London is the global primary and Flint is the global secondary). I did the rolling upgrade on these servers. After the upgrade, AG in Flint (on which Distributed AG was created) does not failover to the other node while regular Ags on flint are failing over w/o any issue.

Moreover, Same distributed AG on the London servers can failover w/o any issue.

I have set Sync mode to SYNCHRONOUS COMMIT and failover mode to MANUAL. As soon as I change failover mode to AUTOMATIC, DAG can failover. Issue is with the MANUAL failover mode.

It shows error which is weird. Databases are SYNCHRONIZED still following error appears:-

ERR [RES] SQL Server Availability Group <xxx>: [hadrag] Failed to execute SQL command to perform the requested operation
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] ODBC Error: [42000] [Microsoft][SQL Server Native Client 11.0][SQL Server]The availability replica for availability group 'xxxx' on this instance of SQL Server cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group. If the availability replica uses the asynchronous-commit mode, consider performing a forced manual failover (with possible
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planned manual failover to this secondary replica (without data loss). For more information, see SQL Server Books Online. (41142)
ERR [RES] SQL Server Availability Group <xxx>: [hadrag] Failed to execute availability group command stored procedure
INFO [RES] SQL Server Availability Group <xxx>: [hadrag] Disconnect from SQL Server

Please suggest what is wrong.

P.S. This behavior was not there when it was SQL SERVER 2016. It started happening only after upgrade to SQL SERVER 2017. Additionally, regular AGs on those servers are not causing any problem.

ravinder1483@gmail.com


↧
↧

Can you use the primary SQL server during AG replication process?

May 30, 2019, 7:53 am
$
0
0

Can you use the primary SQL server during AG replication process?

We are planning on creating a two or more replicas for SQL AG.   Can we use the primary node during the process of adding the databases to the replication and asynch all the replicas in the AG?   In other words, we have a very large database which is over 4 TB and am wondering if we add to a four node SQL AG if we can connect our application to the primary node while the replicas are going into synch?   Note that we are adding this database for the first time to this AG.


dsk

↧

Can you manipulate the properties of a database for a PaaS SQL database?

May 30, 2019, 7:56 am
$
0
0

Can you manipulate the properties of a database for a PaaS SQL database as we do with a IaaA SQL database within computer management studio?

What the limitations of PaaS SQL computer management console versus IaaS SQL computer management console?


dsk


↧

Large data warehouse recommendations for high availability and DR solutions?

May 30, 2019, 8:05 am
$
0
0

Large data warehouse recommendations for high availability (HA) and DR (disaster recovery) solutions?

We have a 10 TB of databases and am considering HA solutions and DR solutions?

We want to have minimal downtime when setting up this system and will likely have to restore the database before cutting over to a live production environment.   The backup will also be huge approaching 10 TB which will be used for a copy/restore at the DR site or site recovery could be used.   

From best practices is it feasible to use SQL AG for data warehouse?

dsk

↧
Viewing all 4532 articles
Browse latest View live
Search