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

Hyper-v replica of SQL Server 2014 erroring during application consistent replica

October 1, 2014, 12:23 pm
$
0
0

Windows 2012 R2 VM with SQL 2014 on Hyper-v 2012 core is throwing SQL errors during VSS replica.  I have ran a test failover and the recovery point seems fine.  It almost looks like no database changes have occurred and the VSS engine is aborting the thread inappropriately.  If this is not an actual error is there any way to suppress these messages?

BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.

BackupVirtualDeviceFile::SendFileInfoBegin:  failure on backup device '{F93039AB-B6A8-4944-93B2-6B2737228FEB}2'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1972. Thread=7360. Client. Instance=. VD=Global\{F93039AB-B6A8-4944-93B2-6B2737228FEB}3_SQLVDIMemoryName_0. 

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file "{F93039AB-B6A8-4944-93B2-6B2737228FEB}2:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 11.0
Error message: Processed 0 pages for database 'msdb', file 'MSDBData' on file 1.
↧
Search

"Recovery Time" huge every day, after index reorganize

September 19, 2016, 2:34 am
$
0
0

Hi 

We have recently migrated from SQL 2012 to SQL 2016 on new more powerful servers. Now we started to experience huge "Estimated Recovery Time" and "Redo Queue Size" that takes most of the day to recover from. Estimated Recovery Time is often around +30000 seconds.

We have set up a job that monitors the "Redo Queue Size" and know that the problem appears shortly after a nightly index reorganize job starts.

We never used to se this on the old servers, so we just don't understand why this happens? It seems to be an SQL 2016 issue.

Setup information:

HP Proliant DL580,  4 x CPU E7-8893 V3, 2TB RAM, 2 x 2TB NVME Intel fusion card. Dedicated 10gbe network for Sync.

↧
↧

creating cluster nodes

September 20, 2016, 8:15 am
$
0
0

Hi ,

 We need to Set up SQL server ALWAYS-ON Across to different Data centre in two places .. 

On a single WFSC ( WINDOWS CLUSTER)  can i have both machines ( NODES) . 

If Both the machines from different DC are in the cluster it is easy to configure ALWAYS-ON . 

Will this work. will there be any restrictions on that ..  

How to do that > 

Please advice ..

Regards

K.Muthus 

k.muthus

↧

SQL 2005 Clustering Issues

June 13, 2008, 5:40 pm
$
0
0
Hi all,

I'm having issues with my SQL 2005 SP5, CU5 cluster.  I swapped out a clustered disk and restarted SQL and now it's unable to come back up.  The errors that I'm getting are:


2008-06-13 20:21:25.82 Server      Error: 26054, Severity: 16, State: 1.
2008-06-13 20:21:25.82 Server      Could not find any IP address that this SQL Server instance depends upon.  Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available.  Error code: 0x103.
2008-06-13 20:21:25.84 Server      Error: 17182, Severity: 16, State: 1.
2008-06-13 20:21:25.84 Server      TDSSNIClient initialization failed with error 0x103, status code 0xa.
2008-06-13 20:21:25.84 Server      Error: 17182, Severity: 16, State: 1.
2008-06-13 20:21:25.84 Server      TDSSNIClient initialization failed with error 0x103, status code 0x1.
2008-06-13 20:21:25.84 Server      Error: 17826, Severity: 18, State: 3.
2008-06-13 20:21:25.84 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2008-06-13 20:21:25.84 Server      Error: 17120, Severity: 16, State: 1.
2008-06-13 20:21:25.84 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.



I've Googled around and was unable to find another.  VIA is disabled (fairly common suggestion when Googling) and I have my clustered SQL Server resource dependent upon the network name.  The name/ip/disks are fine, but SQL refuses to start.  I'm not really sure what do to other than reroll the default instance.

Any help would be much appreciated.  Thanks!
↧

Transactional Replication - restore replicated databases

September 20, 2016, 10:30 am
$
0
0

Hi All,

I have question on Restoring replicated databases on to another Publisher and Subscriber. After restring databases I have to maintain the existing replication. Please suggest on this and below is the scenario,

  • Server A: have 5 databases – Publisher
  • Server B: have 5 databases – Subscriber
  • Now I want to restore copy of Server1(publisher) and Server2(Subscriber) databases on to anotherServer C(publisher) and Server D(Subscriber) – all the databases which are in Replication. 

Please help me on above senario. Let me know if question not clear

Regards,

Syed Jakeer,

Syed Jakeer

↧
↧

How to identify primary server from secondary in logshipping

April 27, 2011, 10:09 pm
$
0
0

Hi ,

I would like to know primary db from secondary db those are located on different servers.

Ex : In Server ABC database name is  test = primary

       In Server DEF database name is  test(Standby\read-only) shows this db is in log shipping also secondary db..

here my question is i know only DEF server don't know ABC server how to find this ABC server or primary DB...

Any idea.... ?

 

Yangamuni Prasad M
↧

SQL2016 Basic HA Group - Database Resolving State Error when SQL Server service is stopped

September 21, 2016, 1:03 am
$
0
0

I've created the following set-up:

a two-node 2012 R2 failover cluster, file-share quorum.

Installed SQL 2016 Basic on each node, enabled High Availability (Basic used due to budget concerns)

Set up several databases, created a basic HA group for each database. Automatic fail-over is enabled.

My problem is as follows:

Manual failover of all databases works. Shutting down, rebooting, or disconnecting the NIC on either server triggers the databases to fail over quickly & reliably. 

If I simulate the SQL server service having a problem (kill sqlservr.exe or gracefully stop it), then fail-over is inconsistent. Sometimes all databases remain in a resolving state, sometimes some fail over and some are stuck resolving. I need to resolve this before I can trust the system as live.

Thanks in advance for any advice!


↧

ALWAYS -ON LOGINS and JOBS

September 21, 2016, 10:15 pm
$
0
0

Hi all ,

 Please help how to automate the logins and SQL  JOBS to the Secondary node .. 

Now i am doing it manually .

Regards

K.Muthus 

k.muthus

↧
Search

Backing up and transaction log truncation in alwaysON availabilty group.

September 22, 2016, 2:13 am
$
0
0

Hi all,

I am new to SQLserver.

I have a 2 node WSFC with node1 hosting the primary replica and node2 the secondary replica.
Synchronous sync with manual failover is configured for the replicas.

I intend to use my secondary replica for backup and read only traffic.

However, thinking back a core theory that I have read previously,  transaction logs are only truncated/reuse when they are backup.

q1) Does that means I have to

  • a) backup the database and transaction logs as usual in the secondary replica
  • b) backup the transaction logs in the primary replicaeven though no backup is done on it so as to prevent the transaction logs in the primary replica from growing ?

q2) can the transactions logs backup in the primary replica be use in the restoration of the secondary replica with the secondary replica backup ? or I should just delete way the primary replica transaction logs backup

What is the simple , newbie but proper setup for such scenario above ?

Regards,
Noob

↧
↧

Database is Not Synchronizing/Suspect on the secondary server

September 3, 2016, 6:39 pm
$
0
0


I am running scripts to partition two tables.  The database is a part of a high availability group.  Normally I would remove the database from the high availability group, change the recovery mode to simple, and run the scripts.  However, the individual that I report to wants me to run the scripts with the database still in the high availability group.  I think because they don't want to take the databasse down in production.

I am currently running a test in development and the scripts ran find but I discovered that the database is Not Synchronizing/Suspect on the secondary server.

I tried to resume data movement but it fails.  I get an error message "A timeout occurred while waiting for the operation to complete.  Object Explorer could not be updated.  Try refreshing Object Explorer manually.".  I right clicked on the database and clicked on refresh.  I also tried to run the following:  ALTER DATABASE [ldm_carepoints] SET HADR RESUME;  I also restarted the services.

Is there anything that I can do to fix this without removing the database from the high availability group and readding it?  Or is that the only solution?

Also, is it better to run the scripts when the database is not a part of the high availability group and is in simple mode or is it ok to run the scripts when the database is a part of the high availability group and is in full mode.  I want to give the individual a good reason why it is best to take the database off of the availability group and place the database in simple mode.

lcerni

↧

Issue setting up my File Share witness

July 18, 2013, 7:47 am
$
0
0

I am in the process of setting up a SQL Failover cluster over two availability zones in AWS.  My issue I am having is my File share witness is throwing me an error when trying to set this part up.  

set-clusterquorum -NodeAndFileShareMajority "\\EPMMNSDC1\Witness"

Gives me this error:

set-clusterquorum : There was an error configuring the file share witness '\\EPMMNSDC1\Witness'.
    Unable to save property changes for 'File Share Witness'.
    The parameter is incorrect
At line:1 char:1
+ set-clusterquorum -NodeAndFileShareMajority "\\EPMMNSDC1\Witness"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Set-ClusterQuorum], ClusterCmdletException
    + FullyQualifiedErrorId : InvalidParameter,Microsoft.FailoverClusters.PowerShell.SetClusterQuorumCommand

I have both my nodes as read/write on the share.  I am able to browse to the share from both nodes.

I try to run it through the GUI and i get this error:

An error was encountered while modifying the quorum settings.
Your cluster quorum settings have not been changed.

There was an error configuring the file share witness '\\EPMMNSDC1\Witness'.

Unable to save property changes for 'File Share Witness'.

The parameter is incorrect



↧

Cluster disk offline issue- SQL Active Passive cluster

September 23, 2016, 12:10 am
$
0
0

Hi ,

We have PRODUCTION SQL Server (STD Edition) Active/Passive Clustering at  DR server. There are two cluster disk used by SQL Server Services one for System databases and other for only User database at DR.

This two disk are dependent on SQL Services i.e disk is added in the dependent of SQL Server Services of Fail-over Management Cluster. If second cluster disk(user database) goes offline then will SQL Service stop working or there will be no affect on SQL Services at DR Active/Passive Clustering.

My doubt is if second disk goes offline for some times then  SQL Services will stop or  not till the 2nd cluster disk comes online 

Regards,
Nikhil Desai 





↧

Backups during rolling update

September 22, 2016, 7:26 am
$
0
0

When doing a rolling update (SQL 2012 SP3 in my case),  https://goo.gl/2uI8hm states "Backups cannot occur on a database that is in the process of being upgraded". Does this mean that they will fail if you try to run them, or that you shouldn't even try to run them because it could cause the update to fail?

My setup is SQL 2012 Always On, one availability group, one async secondary replica (for DR), and an FCI as the primary.

Chuck


↧
↧

SQL Azure upgrading pricing tier for geo replicated databases

September 23, 2016, 8:48 am
$
0
0

I have several SQL Azure databases on the basic pricing tier. These databases are geo-replicated to a different region for DR purposes.

I am trying to upgrade these basic DB's to the Standard pricing tier so that I can add them to an Elastic Pool with my other Standard tier databases. However, in order to upgrade the pricing tier for the basic DB's I need to remove geo-replication, as described in the Azure documentation. I have done this for one of the databases so far. I have then upgraded the primary and secondary databases to the standard tier and then attempted to reconnect these databases to enable geo-replication but I can't see how to do this. When I try to re-enable geo-replication it tries to create a new database with the same name rather than linking the existing one, this causes an error.

Am I right in thinking the only way to do this is to delete the secondary database, wait for a set period of time and then attempt to add geo-replication again to the primary database and allow Azure to create a new secondary database with the same name? I am concerned that if I delete the secondary database then I will not be able to create a new secondary database with the same name and geo-replication will be broken.

↧

SQL Server 2016 AlwaysOn Asynchronous 2 node setup - potential for data loss and being able to tell what point data was lost after failover

September 23, 2016, 1:05 pm
$
0
0
New to AlwaysOn.  Looking at setting up AlwaysOn 2 nodes asynchronous commit mode between our two data centers.  What I am wondering with this setup is: what is the potential for data loss, and if I do failover, how do I know how recent my data data is/what was lost so I can convey that to users (aka:  "Anything you did after 11:27am has to be re-entered")?  Thanks!
↧
Search

JNDI Connection Pool does not re-connect after MS SQL Server 2014 restart or post the availbility group server fail over

September 23, 2016, 10:43 pm
$
0
0

Our JNDI connection pool on tomcat (8.0) does not reconnect after MS SQL Server( 2014) restarts. unless, I restart the tomcat , the DB connection pool remains in state of closed connection , even though the SQL server is up. But if I provide DB URL details instead of JNDI, the connection pool restores the connection post a restart of SQL Server, and does not demand and restart of the tomcat.

This happens also when SQL Server failovers in availability cluster , though the secondary becomes active in DB availability cluster.

Please let me know if any property needs to be additionally defined for this work.

Tried with autoReconnect=true, but that doesn't work. Please do help on the what is auto reconnect property to set to JNDI configuration 

The JNDI config is 

auth="Container"
type="javax.sql.DataSource"
initialSize="10"
maxActive="100"
maxIdle="10"
minIdle="0"
maxWait="1000000"
timeBetweenEvictionRunsMillis="1000"
minEvictableIdleTimeMillis="1000"
validationQuery="SELECT 1"
validationInterval="1000"
testWhileIdle="true"
testOnBorrow="true"
testOnReturn="false"
removeAbandoned="true"
removeAbandonedTimeout="3000"
logAbandoned="true"
username="XX"
password="XX"
factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://localhost:1433;authenticationScheme=nativeAuthentication;xopenStates=false;sendTimeAsDatetime=true;trustServerCertificate=false;sendStringParametersAsUnicode=true;selectMethod=direct;responseBuffering=adaptive;packetSize=8000;multiSubnetFailover=true;loginTimeout=10;lockTimeout=-1;lastUpdateCount=true;encrypt=false;disableStatementPooling=true;databaseName=XX;applicationName=Microsoft JDBC Driver for SQL Server;applicationIntent=readwrite;autoReconnect=true;"/>

Below is stack trace :

[SQLErrorCodesFactory] Error while extracting database product name - falling back to empty error codes
org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is com.microsoft.sqlserver.jdbc.SQLServ
erException: The connection is closed.
at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:305)
at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:329)
at org.springframework.jdbc.support.SQLErrorCodesFactory.getErrorCodes(SQLErrorCodesFactory.java:214)
at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.setDataSource(SQLErrorCodeSQLExceptionTranslator.java:134)
at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.(SQLErrorCodeSQLExceptionTranslator.java:97)
at org.springframework.jdbc.support.JdbcAccessor.getExceptionTranslator(JdbcAccessor.java:99)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:660)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:695)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:727)

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.getMetaData(SQLServerConnection.java:2026)
at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)
at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80)
at com.sun.proxy.$Proxy4.getMetaData(Unknown Source)

Thanks,

Nivedita

↧

How is it possible that I can connect from 2 different ports?

September 23, 2016, 1:32 pm
$
0
0

We were doing audit and discovered that our always on listener was configured with port 14333 (yes! extra 3).  We were curious how our applications are able to connect given that their connection string references port 1433. We would have expected 1433 connections to fail since listener is 14333.

This is not a named instance and we do not have the SQLbrowser service running.

Can anyone explain why both ports 1433 & 14333 work?

sqlcmd -S agd-sqlfoo_listener_name,1433     # Connection established

sqlcmd -S agd-sqlfoo_listener_name,14333    # Connection established

sqlcmd -S agd-sqlfoo_listener_name,143     # Connection fail as expected

sqlcmd -S agd-sqlfoo_listener_name,1234    # Connection fail as expected

Queryoutput  from sys.dm_exec_connections

connect_time net_transport protocol_type endpoint_id auth_scheme local_net_address local_tcp_port
2016-09-23 14:24:30.063 TCP TSQL 4 NTLM 172.17.35.16 14333
2016-09-23 13:03:29.317 TCP TSQL 4 NTLM 172.17.35.16 1433
2016-09-23 14:33:57.110 TCP TSQL 4 NTLM 172.17.35.16 1433
2016-09-23 08:48:57.230 TCP TSQL 4 NTLM 172.17.35.16 1433
2016-09-23 08:51:03.353 TCP TSQL 4 NTLM 172.17.35.16 1433



↧
↧

MS DTC clsutered service role With HA-DR as AG

September 24, 2016, 3:15 am
$
0
0

Hi Team,

We are in a process of SQL HA/DR solution wherein we will have 2 node WSFC at primary data center and 3rd node in DR.

We will have multiple SQL named instances (for each workload) in cluster mode at primary and will have standalone SQL with multiple instances in DR data center. We will have Availability Groups between Primary SQL and DR SQL.

I am going through an article for MSDTC Service Role and it seems it is not supported and recommended with AG.

https://blogs.msdn.microsoft.com/alwaysonpro/2014/01/15/msdtc-recommendations-on-sql-failover-cluster

https://blogs.msdn.microsoft.com/alwaysonpro/2014/01/06/not-supported-ags-with-dtccross-database-transactions

Want check what is the current status on this since article published last year and seems some testing was still on at the time of blog/article publish.

Do we have any further findings on MSDTC recommendations with AG in HA/DR Scenarios?

Any pointers will be appreciated.

Regards,

↧

SQL 2012 availability group Listener accessible only from Primary

September 24, 2016, 3:49 pm
$
0
0
sql 2012 AlwaysOn Availability group with 2 nodes. The 2 nodes are in 2 different subnets. xxxxDBList.Domain.com is the Listerner address. The listener works fine from the Node that is currently Primary (either 1 or 2). But when 1 is active and I attempt to connect to Listener via Management studio on Node 2(and vice versa)it  cannot find the DB server. If I connect via IP address or host name from anywhere it connects fine.  Can't Ping Listener by name or IP from Non primary node.   It sounds like DNS but it looks good. xxxxDbList is listed with both subnet's IPs in DNS.  What am I missing?
↧

Tracking when failover happened?

September 25, 2016, 2:23 am
$
0
0

Hi all of you,

I am searching for the concrete text on SQL Error Logs.

In my monthly review I would need to post how many failover happened in my Always On.

As already commented in these forums there are no traces of it in any DMO/DMV and the only solution is just search through Logs.

Thanks for your help,

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