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

Setting ILB in SQL Server high Availability

February 22, 2019, 2:10 am
$
0
0

Just wanted to know if you are building Failover cluster for Always ON availability Group for same region. Do we have to run below command for both SQL VM's or for only one?

$ClusterNetworkName = "Cluster Network 1"
$IPResourceName = "EMCPRODAG_10.0.26.31"
$ListenerILBIP = "10.0.26.31"
[int]$ListenerProbePort = 59999

Import-Module FailoverClusters


Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ListenerILBIP";"ProbePort"=$ListenerProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}

$ClusterNetworkName = "Cluster Network 1"
$IPResourceName = "EMCPRODAG_10.0.26.31"
$ClusterCoreIP ="10.0.26.30"
[int]$ClusterProbePort = 58888

 Import-Module FailoverClusters

Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ClusterCoreIP";"ProbePort"=$ClusterProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}

For Failover testing on SQL Server, how the ILB work in AZure setup.  Do i have to shutdown windows machine to activate ILB to function or I can simply failover the SQL server using SSMS?  We are facing problem when your Primary SQL server failover to Seconday SQL server but Both SQL VMs are up. We cannot connect to Secondary SQL server from any other maching using  Listner.  Am I doing this test correctly or not?  Not able to figure out.

Any quick help will be greatly appreciate.

↧
Search

Report doesn't go to Alwayson secondary replica

February 22, 2019, 2:22 pm
$
0
0

Hi Gurus,

 I have setup 2 nodes Alwayson on SQL 2017. Read only routing is working fine but when I try to run report on read-only replica it only goes to primary server despite of using “ApplicationIntent=Readonly” parameter

Here is the detail of my setup

SQL Database version

  Microsoft SQL Server 2017 (RTM-CU11) (KB4462262) - 14.0.3038.14 (X64)  Sep 14 2018 13:53:44   Copyright (C) 2017 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)

Report server version

 Microsoft SQL Server 2014 - 12.0.4100.1 (X64)  Apr 20 2015 17:29:27   Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

Providers on Report server

-ADsDSOObject

- MSDAOSP

- MSDASQL

- MSOLAP

-SQLNCLI11

- SQLOLEDB

Providers on Database server

-ADsDSOObject

- MSDAOSP

- MSDASQL

- Search.CollacterDSO

- MSOLAP

-SQLNCLI11

- SQLOLEDB

- SSISOLEDB

Connection string

Provider=SQLOLEDB.1;Data Source=test_listener;Initial Catalog=test_data; Application Intent=Readonly;

  This works but goes to primary server

Provider=SQLNCLI11.1;Data Source=test_listener;Initial Catalog=test_data; Application Intent=Readonly;

This return following error

"An Error has occurred during report processing. (rsProcessingAborted)

    Query execution failed for data set  'main'. (rsErrorExecutingComand)

       For more information about this error navigate to the report server on the local server machine, or enable remote errors" 

Please help me to resolve the issue

Thanks in Advance

QJ 


↧
↧

전주오피 “uuzoa2닷com” 쓰리노 ≫유유닷컴≪ 전주1인샵

February 24, 2019, 10:18 pm
↧

SQL 2014 - Aways-on problem

February 25, 2019, 5:06 am
$
0
0

We have SQL 2014 with last service pack and implementing aways-on 

Are 2 virtual server, with same configuration and all step by step to configure was good!!

Now we have a problem when syncronize an database, they are with "Restoring" status in all databases, please, anyone saw this problem

Regards

↧

Multiple Always AG's - question

February 25, 2019, 5:47 am
$
0
0

Hello,

I have a very general question and I'm not sure if this scenario is possible.

Can you have two AlwaysOn Availability Groups on a single instance of SQL Server?  So say there will be a Primary replica (call it SQLVM1) and a Secondary replica (SQLVM2) and these two machines participate in an Availability Group called "SQLAG_1".  SQLAG_1 has DB1 and DB2 and a Listener called "LISTAG_1". 

Now I want to create a second Availability Group - SQLAG_2 containing DB3 and DB4 and a listener called "LISTAG_2" using the same SQLVM1 and SQLVM2.

Is this possible?

Thanks

↧
↧

Best way to migrate existing database under Always on (2012) to new AG (2016) with minimal downtime (under 5 mins)

February 19, 2019, 4:51 am
$
0
0

Hi Experts,

We are looking to migrate our existing DB server configured for always on (SQL 2012) to a new AG group with SQL 2016 with minimal downtime (under 5 mins)

Current Architecture(Windows Server 2012 and SQL Server 2012):

Node1 and Node2 (ABC data center with synchronous mode) and Node3  (XYZ data center with Asynchronous mode)

New Architecture (Windows Server 2016 and SQL Server 2016):

Node1 and Node2  (ABC data center with synchronous mode) and Node3  (XYZ data center with Asynchronous mode)



↧

Microsoft always on availability cluster failing occasionally.

February 12, 2019, 2:18 pm
$
0
0

I have three 3 node clusters created in my environment.  There are two synchronous nodes at one data center and one asynchronous node at another data center.  Each node has its own disks so there's no shared storage.  Occasionally maybe once a month, my test cluster becomes unavailable.  It won't ping and clients can't connect to the SQL cluster listener.  It happened again this morning and was unavailable for about a half hour, then without changing anything, it came back to life.  In the past, I was able to initiate a manual failover/failback and it would come back right away but I'd like to find out why this is happening in the first place.  This does not happen with the other clusters.

There are no cluster errors registered in event viewer.  No nodes fail, I can connect to each one individually.  The cluster name does not ping and neither does the SQL listener, so that leads me to believe it is a Microsoft clustering problem and probably not a SQL issue.

I did a get-clusterlog and have been pouring through it.   I do see DBG messages like:


[Verbose] 000009ac.00001678::2019/02/12-09:46:49.619 DBG   [GEM] Node 1: GEM Id 3565 has been ack'ed by every node. Unacknowledged Message Count = 5
[Verbose] 000009ac.00001678::2019/02/12-09:46:49.619 DBG   [GEM] Node 1: GEM Id 3566 has been ack'ed by every node. Unacknowledged Message Count = 4
[Verbose] 000009ac.00001678::2019/02/12-09:46:49.621 DBG   [GEM] Node 1: GEM Id 3567 has been ack'ed by every node. Unacknowledged Message Count = 3
[Verbose] 000009ac.00001678::2019/02/12-09:46:49.621 DBG   [GEM] Node 1: GEM Id 3568 has been ack'ed by every node. Unacknowledged Message Count = 2
[Verbose] 000009ac.00001678::2019/02/12-09:46:49.621 DBG   [GEM] Node 1: GEM Id 3569 has been ack'ed by every node. Unacknowledged Message Count = 1
[Verbose] 000009ac.00001678::2019/02/12-09:46:49.621 DBG   [GEM] Node 1: GEM Id 3570 has been ack'ed by every node. Unacknowledged Message Count = 0

Around the time it came back up.

Also entries like this often - the possible owners list size is 0 message is interesting.


[Verbose] 00001a40.00002920::2019/02/12-09:48:17.162 INFO  [RES] Distributed Network Name <CAUSACSQvu8>: Netname received Refresh clones message
[Verbose] 00001a40.00002920::2019/02/12-09:48:17.162 INFO  [RES] Distributed Network Name <CAUSACSQvu8>:Possible owners list size is 0
[Verbose] 00001a40.000007d0::2019/02/12-09:48:17.165 INFO  [RES] Network Name: Agent: InitializeModule, Trying to initialize Module(ad4aa780-67db-41df-977e-35ef8ac4be5f,Client) when there is one already in Initialized/Idle state
[Verbose] 00001a40.00002920::2019/02/12-09:48:17.165 INFO  [RES] Distributed Network Name <CAUSACSQvu8>: StartupClone - Client module already exists.
[Verbose] 00001a40.000007d0::2019/02/12-09:48:17.165 INFO  [RES] Distributed Network Name <CAUSACSQvu8>: Client: Synching with slow operation

I don't see a cause and effect relationship when this fails so I can't trigger it.  It's like chasing a ghost.  If anyone has a place to start looking, I'd appreciate it.

↧

AG Backps On Secondary

February 25, 2019, 3:35 pm
$
0
0
If i offload a backups on ALwaysOn Secondary replica in 2016, where can i query backup history? I mean from which MSDB (Primary/Secondary)
↧
Search

Unable to delete a .bak file.

March 28, 2012, 3:53 am
$
0
0

Hi everyone,

I have a .bak file of 200Gb, i copied it to the test server, it took around 6 hours to copy.

Now when I tried to delete it from the main server i got the below error:

"Error deleting file or folder
Cannot delete [name of folder]: It is being used by another person or program. Close any programs that might be using the file and try again."

I restarted the SqlServer services but no gain.I even logged off from server ,but no effect.

Please suggest what is to be done.

Regards,

Hunt

↧
↧

Cannot connect to ReadOnly when database is specified

February 26, 2019, 3:38 am
$
0
0

Hi,

We have recently set up ReadOnly for our 2 AlwaysOn nodes (SQL 2017 CU 11). When I connect via SSMS I can successfully connect by adding the ApplicationIntent=ReadOnly in to the Additional Connection Parameters field. However, if I also specify a database name in there (Database=database_name) then I get the following error:

TITLE: Connect to Server
------------------------------

Cannot connect to servername.

------------------------------
ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

------------------------------

The specified network name is no longer available

------------------------------

If I remove the ApplicationIntent then it connects and if I remove the Database= then it works. Any ideas how I can get them both working together?

Many thanks.


↧

Can failovers cause corruption?

February 26, 2019, 8:06 am
$
0
0

Greetings. I just started w a company that's experience frequent outages w the following error in the log:

Source                  spid50s

Message

Always On: The availability replica manager is going offline because the local Windows Server Failover Clustering (WSFC) node has lost quorum. This is an informational message only. No user action is required.

My knee jerk is to delve into this and get w the sysadmins on what appears to be a cluster issue. However, this isn't a high priority for others like it is for me, so I've somewhat been asked to stand down.

My thought is these frequent outages can lead to corruption, but I can't find any supporting evidence of this specifically.

Can anyone point me in this direction?

Thanks in advance! ChrisRDBA

↧

Our SQL 2014 AG has readable secondary column set to yes for all secondaries. Will it cause a lock down of DB transactions if we change the readable secondary to no and perform a shrink operation on the DB?

February 27, 2019, 8:02 am
$
0
0
We have SQL 2014 with AG setup. We have one primary server and three secondary DB servers. The DB is in full recovery mode. Now we tried to do maintenance for logs, to do that we tried setting the column of readable secondary to no and we did shrink a test DB it worked out well. But the question is changing readable secondary column to no, does it cause any problems like DB transaction lock downs during the shrink operation?

↧

Read Only Primary on SQL AG?

February 27, 2019, 4:31 pm
$
0
0

Hello,

I have a client who wants a read-only db on primary node to be part of an AG which has a non-readable secondary.

Is this topography implementable on SQL AG (client does not want log shipping as they want the automatic failover capability).

SQL Server 2014 Ent 12.0.5540

Thanks.

↧
↧

Unable to add SQL Server Analysis Services on Failover Cluster Instance Setup

February 28, 2019, 6:10 am
$
0
0

Hello,

We have a SQL Server 2014 Failover Cluster Instance setup (FCI) with database engine services. (Server A and Server B). But, now we have a requirement to add SQL Server Analysis Services, and SQL Server Integration Services to the existing FCI setup.

We were able to add the features (SSIS), and (SSAS). At the end of the installation SSIS was successful, but SSAS resulted in failure. We found the log stating,

Detailed results:
  Feature:                       Analysis Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Analysis Services
  Component error code:          0x84B40002
  Error description:             Install of feature Analysis_Server_Full is not supported on clustered instance
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4487.0&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402

Please advise whether is there any other way to add SQL Server Analysis Services feature to an existing SQL Server 2014 Failover Cluster Instance setup successfully.

Thank you, Anand

Anand Franklin

↧

Fileshare Witness issue in SQL Server 2016

February 28, 2019, 4:38 pm
$
0
0

Hi Team,

These are the error we can frequently getting from Cluster log.

Environment: SQL Server 2016 with AG configured (1 Primary+2Secondaries)

Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.

File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\share01\QuorumFileShareWitness'. Please ensure that file share '\\share01\QuorumFileShareWitness' exists and is accessible by the cluster.

↧
Search

"No backupset selected to be restored" - Cannot restore SQL Server 2014 Database backup with TDE enabled on to a new instance

February 28, 2019, 4:32 pm
$
0
0

Hello,

I am using SQL Server 2014, SP2, Enterprise edition, on both old and new instances. I am trying to restore a backup (about 360 GB) of a TDE enabled database on to the new instance.   The certificate had expired on the source server, so, created a new certificate on source and then restored on to the new instance.  I also created the master key on the new instance.  I made a copy-only backup of the database and copied on to the server where new instance is located.  When I tried to restore the database I keep getting "No backupset selected to be restored" error.  Restore Filelistonly and Restore Verifyonly check on backup file come back with no issues on the new instance.   However, Restore Headeronly comes back with error below.

Msg 3013, Level 16, State 1, Line 118
RESTORE HEADERONLY is terminating abnormally.

After this attempt failed, I created a blank database manually and enabled encryption on after running the following in the database context.

CREATE DATABASE ENCRYPTION KEY
WITH ALGORITHM = AES_256
ENCRYPTION BY SERVER CERTIFICATE <cert name>

Now I am trying to restore on top of the new database using SSMS but it is stuck at "Reading backup device header" file for more than an hour.

Please shed some light on this.

Thanks in advance.

Prasad Koukuntla

  

↧

Azure Windows Cluster SQL Server Always ON setup with 2 nodes VM

February 28, 2019, 1:51 am
$
0
0

I am facing issue with my current setup as I am not able to connect my Secondary node when its primary through SQL Listeners.  Does anyone know wht will be the issue?

I am using Windows 2016 Datacentre and SQL Server 2016 enterprise version  for SQL VMs.

While connecting to Secondary Node SQL server when it is primary i am getting following error

EMCPRODSQLCAP - SQL Listener10.0.26.31,10.0.26.44Target computer not accessible2/27/2019 12:19:33 PM

Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: The wait operation timed out.
.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

C:\windows\system32>

↧
↧

After deleting availability group, listener remains in the system table.

February 28, 2019, 8:52 am
$
0
0

Hello.

We have come across an issue where we deleted an availability group, but the listener remained in sys.availability_group_listeners.

The method used to delete the AG was not correct. It was connected in SSMS via the listener and  then we deleted the AG for that listener which of course caused and error, but did still delete the AG. Therefore we know cause.

Having done some investigation I have been unable to find any reference to this issue. 

I want to remove the listener from here. Does anyone have any suggestions?

We have tried removing directly from sys.availability_group_listeners (in a lab environment) but as expected we get the error stating "Ad hoc updates to system catalogs are not allowed."

Thanks in advance.

↧

Is having a listener configured required for the alwayson to work after a failover?

March 1, 2019, 4:14 am
$
0
0

Hi,

I have two nodes windows cluster with a fileshare as a witness. the AG resource is configured to also failover associated IP addresses whenever there is a failover. One of such IP+Name is used by the applications to connect to the sql server. But it is not setup as a listener name in the AG configuration.

whle this works fine right now, do I must configure this name as a listener? would it cause issues if/when there is a failover?

BTW: the AG is configured for automatic failover.

Thank you in advance.

Drupal

↧

Distributed Availability Group standalone FCI between two standalone FCI (without domain)

March 1, 2019, 8:49 am
$
0
0

I have standalone FCI without domain win2016\sql2016sp2

My target is;setup DR site using Distributed Availability Group, the problem is there is no domain for authentication; how i can setup certificates between two Availability Group to be used as authentication?

↧
Viewing all 4689 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>