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

Multiple Instances and AlwaysOn Availability Groups

$
0
0

Hi,

I have 2 SQL Servers: A & B
Each has 2 instances and each instance is part of an database AlwaysOn Availability Group

Server A - instance 1, AlwaysOn Group1 & instance2, AlwaysOn Grroup2
Server B- instance 1, AlwaysOn Group 1 & instance2, AlwaysOn Grroup2

I configured 2 AlwaysOn groups, which worked for a brief amount of time:

Server A - had instance 1 (primary) and instance 2 (secondary)
Server B - had instance 1 (secondary) and instance 2 (primary)

However after a few minutes, Server A instance 1 (secondary) changed to the not synchronized state and I'm struggling to add Server A instance 1 as a replica in AlwaysOnGroup1

Can someone tell me if I'm doing something wrong? Can I have 2 instances participating in separate AlwaysOn Database Availability Groups on the same server?

I'm wondering maybe the configuration is failing because one server holds a primary and the other a secondary - perhaps each server should hold only a primary or secondary?

Thanks


Mount points vs CSV disks in SQL clusters

$
0
0

Hello

I am trying to overcome the 26 character limitation when trying to place multiple SQL Instances in a Windows cluster.

I know mount points is the solution for this, and have few questions:

Will mount points work in clustered environment?

Is CSV just a another name for mount points in a clustered environment? Or is that different from mount points?

Jobs are getting cancelled whenever fail over occurs in SQL Agent

$
0
0

Resilience Engineering Implementation possibility -

Issue:We are in process of auto triggering of cancelled jobs whenever Server fail-overs from one node to another node.

Description:When ever server fail-overs we have to manually re trigger the jobs by making the respective process instance status to 0 since all the jobs will get cancelled.

Is there any way to trigger the job automatically from SQL agent when ever server fails?


SqlWriter not working and block oters vss writers

$
0
0

Hello all,

i have ugly issue on my SQL2012 SP3 CU4. VSS SQL Writer stop working. No entry in logs. If is process up, it bloks complete VSS functionality. Like i am unamble "vssadmin list writers", backups... If i shutdown sqlwriter process, all works normaly. (Except my sql backups, and vss sql writer is missing in vssadmin list writers output). I try to complete unistall SQL VSS writer component, install it form SP1 media, aply all MSP packages from SP2, SP3, CU4, nothing helps.

Is any way to debug sqlwriter process or get some info what happends?

Second issue i have is reporting services for SCCM, but i will open it in another thread. Except this is all working nicely and server is in good state at all.

SQL 2012 Database Mirroring - Convert to Cluster

$
0
0

We have two servers running SQL2012 in a mirrored configuration on Windows Server 2012.

Assuming I configure both servers to have access to a LUN on the SAN, is it possible to convert these two servers to an AA or AP cluster without having to rebuild either of the servers?  If so, does anyone have a sequence of actions that need to be carried out?

Thanks for any help.

Pete.

iam searching in the Administrator:C:\Windows\System32\Cmd.exe, try to get my server back, had typed several commands, everycommand was ok until i typed DATE,

$
0
0
Command prompt asking new date, i don't understand what he's asking beceause i typed several date's and not 1 fit with what he's asking. Now what date can i give the program, that it again keeps running, becease now it still ask me a date : dd\mm\year??? Can someone help me please??

Database Connectivity disruption during failover and failback

$
0
0

Hi,

We are using SQL Server 2012 SP3 and we are using AlwaysOn Availablity Group for our HA-DR solution.

We have 2 node Windows Cluster (Windows Server 2012 R2 is the OS for each of the server) in two different subnets holding the SQL Server instances participating on the AlwaysOn Availability Group. As a result the Listener is also configured with two IPs (one from each subnet). Both the instances are configured for Automatic Failover.

The only changes we have made in the cluster properties are the HostRecordTTL value is set to 300 and RegisterAllProvidersIP to 0 for the Listener object, else all are kept as default.

The problem we are facing is that whenever any failover happens, the applications fail to connect the databases for few minutes after the failover completes. So wanted to know if there are any configurations that we have missed so that the failover becomes seamless from the application side i.e, no database connection disruption during or immediate after the failover.

Please let me know if any other information is required for this purpose.

Thanks and Regards,
Pinaki

SQL CLUSTRING

$
0
0
where do we keep the resource database files in cluster enviroment

SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon att

$
0
0

Hi,

I am configuring Logshipping , During the same after establishing the logshipping , i waited till the backup job in the source gets triggered in the interval. 

But the job failed with the below error :

Message
2016-08-22 16:45:09.60*** Error: Failed to connect to server WIN-VQ6QHC236G6.(Microsoft.SqlServer.ConnectionInfo) ***
2016-08-22 16:45:09.60*** Error: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.(.Net SqlClient Data Provider) ***
2016-08-22 16:45:09.60----- END OF TRANSACTION LOG BACKUP   -----

the server is not in domain , but in the same office. where it is rechable to each machine. 

both the instances run with same user account in differnt machine with admin rights(groups) included in it. 

Can you please tell me how to resolve the above problem , 

furthur logs to give you better picture on the error . 

2016-08-22 16:10:26.75 spid52      Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2016-08-22 16:10:26.76 spid52      Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2016-08-22 16:10:53.74 Logon       Error: 17806, Severity: 20, State: 14.
2016-08-22 16:10:53.74 Logon       SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon attempt failed   [CLIENT: 10.30.14.70]
2016-08-22 16:10:53.74 Logon       Error: 18452, Severity: 14, State: 1.
2016-08-22 16:10:53.74 Logon       Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.30.14.70]

Please suggest me the right way to log on. 


hemadri

Looking for manual for .mdf file

$
0
0

Hi guys!

I'm a frugal person and so before something to pay, I will look for different ways to solve the problem free. So I'm looking for quality of the user how can I restore corrupted .mdf file after virus attacks. If this is not possible manually to do this, then maybe there is a good tool for this and it doesn't matter it is paid or free. I know there are a lot of tips and tools, but I don't know good they are or not. So I'm hoping for recommendations of professionals. Thanks in advance!  MSSQL 2012 ManagementStudio

SQL CLUSTRING 2012

$
0
0

I am not able to move the resource from Node1 to Node2 Server and Node1 sql cluster up and running fine. I escalated to storage team that storage not connected from Node 2 .Moreover, able to see the following errors in cluster log file. My question is why i am getting this issue even not configured for

 alwaysOn :Cluster resource 'New SQL Server Availability Group' of type 'SQL Server Availability Group'  

in clustered role 'SQL Server (MSSQLSERVER)' failed.

1. Clustered role 'SQL Server (MSSQLSERVER)' 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.

2. The Cluster service failed to bring clustered role 'SQL Server (MSSQLSERVER)' completely online or offline. 

One or more resources may be in a failed state. This may impact the availability of the clustered role.

3. Cluster resource 'New SQL Server Availability Group' of type 'SQL Server Availability Group'   in clustered role 'SQL Server (MSSQLSERVER)' 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.

4. Cluster resource 'New SQL Server' of type 'SQL Server' in clustered role 'SQL Server (MSSQLSERVER)' failed.


Node2:

 



AlwaysOn. Problems with REDO rate on secondary replica. REDO queue grows enormously.

$
0
0

Hi!

We have constant problem with growing REDO queue on one of our secondaries, which is used for reporting and different calculations – analytic server in some way.
The environment is deployed within Azure VMs. So, we cannot control much ((
We have 1 primary and 2 secondaries. Primary and one of the secondaries are the same servers (8 cpu, 56Gb RAM) and the problem secondary is different (4 CPU, 28 GB RAM). ALL the servers though have the same disk configuration – Premium for t-logs (2400 iops, 150Mb/sec) and data (5000 iops, 200Mb/sec), formatted with 64K cluster size.
All the secondaries are in synchronous mode.

Analytic server is under heavy jobs sometimes which select a lot of data from AlwaysOn-databases and insert it into analytic databases on other disks.

Another secondary server is a warm standby, it does nothing, besides AlwaysOn processing.

The strange thing is that the Redo Rate on analytic secondary which we have problem with is something about 1 000 - 3 000 KB/sec and never raises above 5 000 KB/sec.
While on another secondary it is about 30 000 KB/sec – many times more.
Redo Queue Size is periodically growing enormously on the analytic secondary – up to several GBs and more and it cannot catch up for hours – sometimes we have to delete it from configuration and completely re-add database it from backup.
It is strange because the disks are same on both secondaries and the disks are really fast.
Log Send Rate is pretty intensive all the time and is about 30 000-50 000 KB/sec

I collected WAIT_INFO XEvent during one of the problem periods.
First strange thing is that query to identify session_id for the needed database REDO (STARTUP_DB) for me shows 2 rows with for the problem database with the same session_id for waits:
-ASYNC_IO_COMPLETION
-SLEEP_BPOOL_FLUSH

Then, after collecting wait data for 5 minutes, grouping and aggregating I see the following picture (sorted by SUM duration DESC):


The picture of TOP waits is as above.

So, what can be the cause of the problem?
Is that something with the disks? Or it might be something else? I cannot believe it’s a problem with disks, because they host only always on logs and data and are declared really fast.
Or some other activity might cause these problems with redo queue?
Maybe I need to dig into other causes like:

  • Long-running active transactions
  • High network latency / low network throughput
  • Blocked REDO thread
  • Shared REDO Target

?

Help is greatly appreciated.

I'm almost thinking about switching to good old LogShipping )))


MSDTC in a Failover Cluster

$
0
0

Hi Guys

I am about to build a SQL 2012 two node failover cluster. Just a couple questions:

Q1:

Do I really need to Cluster MSDTC???

Q2:

Would dynamic quorum be suffice??? or do I need a File Share Witness???

Copying MDF/LDF files without stopping SQL service

$
0
0

HI

Is there a way to copy  MDF/LDF files without stopping SQL service??

I need to take backup from SQL but i have to stop service,any tools or software to do that?


Thanks

SQL Server 2016 Licensing policy related

$
0
0

Dear Sir,

We are planning to move on SQL server 2008 R2 to SQL Server 2016 with DR support and larger infrastructure. At present we are going for 12 DB servers 8 core each on cloud(VMs). Same is for DR setup also. DR DB servers are in high availability groups to sync data from Primary servers. How many SQL licenses we will need to setup this requirement. As per my understanding we need to by 12*8/2=48 SQL Server 2016 licenses but the vendor is proposing same number of licenses for DR site also.

At DR site we are doing nothing with DB servers but servers are in High Availability Groups for failover. Is it mandatory to buy SQL Server 2016 licenses for DR site also. Please guide.


Cluster + Log Shipping, allowed/advisable?

$
0
0

I'm looking to implement AlwaysOn Cluster but my concern is the single storage (although this will be SAN) is it possible to combine Clustering with Log Shipping; so running log shipping from the cluster to another server outwith the cluster? SAN mirroring is not an option at the moment.

I can find information on both clustering and log shipping but I can't seem to find if they are interoperable.

Regards,

PeteL.

Column Encrypted Database and AlwaysOn

$
0
0

How do I put a database with symmetric encrypted columns on and AlwaysOn group? I get the following error:

This database is encrypted by database master key, you need to provide valid password when adding it to the availability group.

I've looked for documentation and all I see is TDE AlwaysOn instructions. My cert is in the database itself.

This is SQL Server 2016 with one secondary


SQL Server 2016 AlwaysOn Full Synchronisation issue

$
0
0

Hello,

We are trying to set up AlwaysOn on SQL Server 2016 (13.0.1601.5) with SQLServer Management Studio.

When we want to add a database to the availability group, we check the Full option and a network share to synchronize the database.

But when we finish the wizard, the database is just join to the availability group, no backup are done and no restore to the secondary. At the end of the wizard when we look at the generated script this is want we got :

--- YOU MUST EXECUTE THE FOLLOWING SCRIPT IN SQLCMD MODE.
:Connect server\instance

USE [master]

GO

ALTER AVAILABILITY GROUP [dag]
ADD DATABASE [test];

GO


GO

It looks like a bug in the Add database wizard.

Does somebody have seen the same issue ?

Thank you,

MSDB Keeps going "Recovery Pending"

$
0
0

Hi everyone.  First time posting.

I have a small issue with a production AG cluster.  One of the nodes of the server is having an issue with the MSDB database going "recovery pending".  When this happens, everything fails over to another node, so no loss of service.  But it's a pain to have to restore these databases once in awhile.

My current theory is that windows updates are rebooting the active node without a proper failover.  In response to my theory, I've just setup cluster aware updating as of yesterday. 

The odd thing is, I don't have MSDB added to the AG.  And in the logs, it's telling me the reason for "recovery pending" is that the log file is corrupt.

Can someone advise a place i can look to determine the root cause? Does my theory of windows update rebooting the server sound possible?

How to Setup Always On-SQL Server 2014 STD Edition

$
0
0

Hi,

Please let me know what is exact difference between 

1. Alwayson Failover Cluster Instances and AlwaysOn Availability Groups

2. I want to configure Alwayson Active/Active Cluster using SQL Server 2014 Std Edition at Primary Site

    I know in SQL 2014 Enterprise Edition we can configure AlwaysOn Availability Groups

  How to Set Up Standard Edition AlwaysOn Availability Groups in SQL Server 2014 Std Edition

  

Regards,

Nikhil P Desai

Viewing all 4689 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>