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

Expand/Extend disk in SQL 2014 AAG running on VMware

March 11, 2015, 9:32 am
$
0
0

I created a 2-node AAG in vSphere 5.5 running Windows Server 2012 R2 and SQL 2014 and noticed when I tried to increase the data drive (non-boot volume) the newly allocated VM disk space is reflected differently between compmgmt.msc and Server Manager>Files and Storage Services>Volumes>Disks.

I can extend the disk using compmgmt.msc without problem but Server Manager on the other hand doesn't even recognize that there's new space available to allocate.

So my question is about whether I'm expanding disk the correct way in an AAG setup by using the tried and true Computer Management interface.

↧
Search

Extra Availability Group Or Extra Instance

April 7, 2015, 6:02 am
$
0
0

Hello all,

We've implemented AlwaysOn High availability, an AV Group on three servers. Now we want one server to host sql activity too.

This can be done by creating a second availability group with its primary role on the second server or by creating another instance with its own availability group.

Does anyone have any special things to consider which solution we could choose?

Kind regards,

Fred Koene

↧
↧

SQLWRITER Error

April 7, 2015, 12:38 pm
$
0
0

I found the following error in the event log:

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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file "{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:" 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 10.0
Error message: Processed 0 pages for database 'Net2Archive', file 'Net2Archive_Data' on file 1.

Below is the "Detail":

Log Name:      Application
Source:        SQLWRITER
Date:          4/6/2015 6:03:44 PM
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ***-APP2.Domain.***
Description:
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 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file "{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:" 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 10.0
Error message: Processed 0 pages for database 'Net2Archive', file 'Net2Archive_Data' on file 1.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">24583</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-07T01:03:44.000000000Z" />
    <EventRecordID>123773</EventRecordID>
    <Channel>Application</Channel>
    <Computer>***-APP2.Domain.***</Computer>
    <Security />
  </System>
  <EventData>
    <Data>ICommandText::Execute</Data>
    <Data>0x80040e14</Data>
    <Data>SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file "{FBC0D464-CC27-4C3E-9AC8-BAA99CB09979}5:" 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 10.0
Error message: Processed 0 pages for database 'Net2Archive', file 'Net2Archive_Data' on file 1.
</Data>
    <Binary>53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000</Binary>
  </EventData>
</Event>

This would seem to be something that needs addressing, but what I don't understand is there is no error in the event log or the Windows BackUP system.  Am I on the road to a disaster?

↧

Need a script to create Log-Shipping status reports

November 4, 2014, 2:22 am
$
0
0

Hi All,

In my company log shipping is set up for 5,6 databases i n each server so i need a script that which can generate reports at time for all the databases and i can get the mail about the reports. Is any T-Sql script av liable for this so i can check when ever the backup and restore files are update time of given latency.

↧

Always on network latency between datacenters

October 31, 2014, 6:43 am
$
0
0

When we open Always on dashboard, we see network latency [Estimated Data Loss] on secondary server and our secondary server basically DR server is in different datacenter. Latency causes log file full on primary server. What could be the reason of network latency between servers?

Rahul

↧
↧

The log shipping restore job restores a corrupted transaction log backup to a secondary database

April 7, 2015, 1:15 pm
$
0
0

Dear Sir,

I have primary sql instances in cluster node and it is configured with log shipping for DR system.

The instance fails over before the log shipping backup job finishes. Therefore, a corrupted transaction log backup is generated.how to handle the logshipping without break and how to know this transaction back is damaged.

Cheers,

↧

Issues with AlwaysOn High Availability

February 17, 2015, 2:51 am
$
0
0

I am facing below issues while working with High Availability Group

* While executing PowerShell script as described in below link, getting error

    https://msdn.microsoft.com/en-us/library/hh213078.aspx

System.Data.SqlClient.SqlError: The log in this backup set begins at LSN Which is too recent to apply to the database.

* So i skipped log restoration on seondary server and only restored database, it worked but

          * Now database in Availability Group showing warning sign

           * In Primary server, database is showing Synchronized state and but in Secondary server it is not showing any state, Warning sign may be because of that, but i don't have any idea

It would be great if i can get some clue to get resolution for this issue.

Technical User

↧

3 node cluster with 1 vInstance. vInstance can not to fail-over to one specific node.

April 9, 2015, 12:06 pm
$
0
0

I have a 3 node cluster all running Windows Server 2008 R2. Roughly once a month I see my vInstance become degraded and attempt to fail-over. Everything is good as long as it fail-over to SQL01 or SQL02. However if it attempts to fail-over to SQL03, it does not come online

Quick resolution is to move it manually to SQL01 or SQL02. What could be causing it to fail every time on SQL03.

A couple points:

I did not build the environment.

I am not a DBA.

I only have general knowledge of SQL clustering.

I always get two EVENT ID's: 1069

Cluster resource 'SQL Server (VSQL04)' in clustered service or application 'SQL Server (VSQL04)' failed.

and then

EVENT ID 1205

The Cluster service failed to bring clustered service or application 'SQL Server (VSQL04)' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Where should I begin to look for issues?

↧
Search

Where to place witness server for SQL mirroring using high-safety and auto-failover, 2 sites (protected and DR)

April 9, 2015, 3:39 pm
$
0
0

We have 2 data centers, site 1 and site 2.  Site 1 is generally our primary, and site 2 is our Disaster Recovery (DR) site.  I want to setup a SQL instance to have extremely high availability.  Therefore I was looking at using DB mirroring, with synchronous data writing, high-safety and auto-failover.  This requires the usage of a witness server.  

Where is the best place to put the witness server?  This link seems to indicate the primary site (site 1 in my example): https://social.technet.microsoft.com/Forums/office/en-US/27611fa8-e1f2-4ecf-a8a6-456278943b5b/help-with-placing-servers-to-use-database-mirroring-for-dr-when-only-two-locations-are-available?forum=sqldisasterrecovery

My problem with this setup, is that if the witness and principal are both at site 1, if site 1 goes away (power failure, asteroid impact, lol, anything else that would be a *true* DR scenario), then there is no failover to the mirror server at site 2.   However, if you put the witness at site 2, anytime the WAN link between site 1 and site 2 has an issue, the DB will auto-failover to site 2.  Is the reason for the recommendation of the witness being at the primary site because the thinking is that WAN link failure is likely more common than a *true* DR scenario that takes out all of site 1?

↧
↧

SQL Cluster + high-safety, synchronous mirroring?

April 9, 2015, 3:42 pm
$
0
0

Very simple question.  Is it possible to have a SQL cluster at site 1, another SQL cluster at site 2 (for DR) and have the 2 sites synchronously replicate to one another using high-safety mirroring?  

If the answer is that its technically yes, I have a follow-up answer of: is it even worthwhile doing this?

 
↧

SQL 2005 Cluster

April 9, 2015, 6:24 am
$
0
0

Hi,

I have 2 SQL 2005 database servers setup in a cluster and they both have the following:
SQL Server Management Studio 9.00.3042.00 and .Net Framework 2.0.50727.42, I am planning to update the .Net Framework on one of these servers with SP2 and was wondering this would break the cluster as I affect the database if I perform a failover. I know that it is best practise to keep the config on both cluster node the same.

↧

DataBase unavailable and Mirrored Db role has chnaged.

April 10, 2015, 1:05 am
$
0
0

Hello All,

We got below errors in our principal and Mirror db servers.

1) The mirroring connection to "TCP://servername.domain.com:5022" has timed out for database "Db name" after 10 seconds without a response.  Check the service and network connections.(Mirror Server).

2) Database mirroring is inactive for database 'DB Name'. This is an informational message only. No user action is required.(Pricipal)

2) The command failed because the database mirror is busy. Reissue the command later. .(Pricipal)

3) The mirrored database "Db" is changing roles from "PRINCIPAL" to "MIRROR" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. .(Pricipal)

Before the first error we got an alert that db is unavailable. After 1 min of this alert the issue has started.

After a successful fail-over of that particular db to mirror again it was rolled back to principle automatically. After that I can see a server shut down with below errors.and mirroring failed on all the dbs.

Database mirroring connection error 4 'The connection was closed by the remote end, or an error occurred while receiving data: 55(The specified network name is no longer available.)'' for 'TCP://Server Name.Domain.com:5022'.(Mirror)

Database mirroring connection error 4 'An error occurred while receiving data: '1054(An existing connection was forcibly closed by the remote host.)'.' 'TCP://Server Name.Domain.com:5022'. .(Mirror)

SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. (Pricipal)

The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required. (Pricipal)

SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: IP. (Pricipal)

I am very confused that why this db unavailable before the issue. I don’t have any information about this.

Can some body help me to find out the root cause why this unexpected fail over and sql shutdown.

↧

DR Solution Using FCI with SIOS DataKeeper

April 9, 2015, 1:13 pm
$
0
0

I've already seen a few discussions touching on this topic of DR solution using DataKeeper to perform block level replication to a DR site hundreds of miles away from the primary data center. Even though they have been helpful, I have a few questions I'm not sure I've found the answer to. So here's the situation: we have an 2-node Active/Active cluster with 2 SQL Server 2008 R2 FCIs on each node, so a total of 4 instances, with SAN storage. We have 200+ databases between these instances ranging from as little as 50MB to as large as 150GB. We have a DR datacenter 650 miles away with a stand alone server for SQL Server DR databases and need to replicate/mirror the data in the primary cluster to the DR server. All three servers (2 nodes in cluster and DR server) are identical: 32-core CPU, 384GB RAM, however, like I mentioned, the DR server is not a node in the cluster. I was looking at Database Mirroring for a solution to have the data replicated to the DR site but there are worker threads limitations that would limit the number of databases to mirror, especially on the mirror server. Also, DB Mirroring only works at the database level and anything outside (server logins, agent jobs, etc) would have to be kept synchronized manually. But the showstopper for me was not being able to mirror all the databases. Then we started looking for other options and SIOS DataKeeper kept coming up as a great and more complete solution as it would mirror EVERYTHING on the drives and do away with the mirrored-databases limit, and I believe would also be easier to administer/maintain.

Question: Do we need to use FusionIO drives for DataKeeper to do it's job? Can we replicate from the SAN currently holding the data to the DR site? I believe it is required if you're setting up a SANless cluster but is it required when you already have a SAN and you just want to replicate that data?

Question: Does the DR server need to be part of the primary failover cluster or can the data be replicated to an independent server?Should the DR server be a part of the cluster for best practices? Why?

Question: Which edition of SIOS DataKeeper would be appropriate for this setup?

I believe I had some other questions but can't remember right now. I will update this post when it comes back! I appreciate your feedback. Thank you!

Edit: I remembered another question. Could I use DataKeeper to replicate data for stand alone instances to the DR server? We do have a handful of 2008 R2 instances that host databases which are either not cluster compatible or need their own server.

Leroy G. Brown


↧
↧

Uninterrupted availability of data in SQL Server

April 10, 2015, 10:52 am
$
0
0
I'm trying to solve a problem my company has in its data warehouse of data availability. We have dozens of transactional databases in production from which we pull data to create a cache of data that we make available to reports for both internal and external customers.

The problem I'm trying to solve is I want all of the people using the data to still be able to access the previous version of the data (maybe data from an hour ago) while the new data is being refreshed. I have looked at a lot of ways this is possible. From the very manual, the built in solutions, or a custom drive cloning solution but I'd like to hear from the community what people think is the best way to go about this. The server version is SQL Server 2008, but we could install 2012 in time for this need.

Right now I'm leaning towards AlwaysOn Availability Groups but if there's something better I'd love to know about it.
↧

Always-on High Availability issue

April 10, 2015, 5:55 am
$
0
0

Hi,

I have configured Always-on high availability on Windows Cluster server and it is working fine on both cluster the nodes.

But while Connecting to SQL Server from third machine within a domain using listener name listener is connecting to secondary server where databases are in Read-only mode instead of connecting to primary.

Please Someone help me.

↧
Search

logshippin backup job failed

November 22, 2012, 7:07 am
$
0
0

Hi team,

Logshipping backups jobs failed ERROR :

2012-11-22 05:40:21.52 *** Error: Could not retrieve backup settings for primary ID '92dcbd1e-2cd5-4307-ba43-eb8e3185370e'.(Microsoft.SqlServer.Management.LogShipping) ***
2012-11-22 05:40:21.52 *** Error: Failed to connect to server IP-0A7653F2.(Microsoft.SqlServer.ConnectionInfo) ***
2012-11-22 05:40:21.52 *** Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(.Net SqlClient Data Provider) ***
2012-11-22 05:40:21.53 ----- END OF TRANSACTION LOG BACKUP   -----

Please suggest us.

Tx

subu

↧

ERROR "An exception has been raised that is likely due to a transient failure. ..." when connecting to Always on Availability Group Listener with ApplicationIntent=ReadOnly

April 12, 2015, 5:40 am
$
0
0

Application team is receiving the following error message when applications try to connect through the Availablity Group Listener using readonly parameter:

 "An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy."

 Already using latest .net framework. Using the Extended events I can trace the read_only_route_complete event as well. However, they get this message when trying to open the read only database.

If I try to simulate the connection to ReadOnly replica from management studio, it is working successfully. But not from the application:

Note:

-verified firewall is disabled. (this is development environment)

-SQL Server 2012 SP2 is installed.


↧
↧

Fail-over time difference between 2 node active/passive FCI cluster, and high-safety auto-failover mirroring?

April 13, 2015, 9:41 am
$
0
0

I am trying to think of different ways to build a highly available SQL instance, and have been mulling over different options.   How much time difference is there during failover between a pretty standard 2-node active/passive SQL cluster and a database mirroring setup with high-safety and automatic failover?  

The instance is a "nicer" method, as everything follows the failover (SQL agent jobs, etc), but in my experience an instance failover can take 2-3 minutes to actually take place.  Additionally there are some shared single points of failure, with the primary one being the shared storage/SAN.  If I go with a mirrored solution, I *think* the failover will be quicker, resulting in less DB downtime and there isn't the shared single point of failure (since the DB mirror doesn't have to have shared storage), but you lose the SQ agent jobs/etc being moved over after a failover.  I might be missing some other benefits of a FCI that a mirrored option doesn't give you.  The other big one I can think of is that the mirrored site doesn't share a DNS name, so some additional work has to occur after failover for clients to reach the mirrored DB, correct?

The main point of this thread is to understand what the time difference is between the two options.  But I'd be happy to listen to any other factors that you think I have missed. 


↧

Multiple SQL Server Instances and MSDTC / AGs usage

March 24, 2015, 11:16 am
$
0
0

Hello,

 We are in the planning stages of migrating from SQL Server 2008R2 to 2012 to be running on Windows Server 2012, and I have a question about MSDTC, Availability Groups and multiple sql instances on a single box.

 We have a couple of databases that rely on MSDTC so we know they can not participate in Availabilty Groups, but most of the other dbs we use DO NOT need MSDTC so I wondering the following:

1) Can I install two instanaces of SQL Server on a single box and have one using a local DTC, and therefore unable to use AGs, and the other instance on the same box NOT use DTC and therefor CAN use AGs?

2) If I can't do this, I assume each instance would need it's one machine. Is that correct?

Thanks

Eric

↧

T-SQL Code to backup database with multiple files - Syntax error

April 14, 2015, 12:50 pm
$
0
0

Hello,

I'm trying to backup a database into multiple files but I'm getting a syntax error.

Here is the code:

declare @DBName varchar(100)
declare @DBFileName varchar(256)
declare @FolderName varchar(256)
declare @Path varchar(100)

set @Path = '\\Backup-Server\Test\'
set @DBName = 'DayNite'

set @DBFileName = 'DayNite-Full' + '-' + (SELECT CONVERT(char(10), GetDate(),110)) + '-' + 'P'
set @FolderName =(SELECT CONVERT(char(10), GetDate(),110))
set @Path = @Path + @FolderName + '\'


EXEC master.dbo.xp_create_subdir @Path

--Calculate broken files  for BACKUP DATBASE Function
/*declare @dbsize int
set @dbsize = (SELECT ((size*8)/1024)/1000 as SizeGB FROM sys.database_files WHERE file_id = '1')
set @dbsize = @dbsize / 4
print @dbsize*/

EXEC
BACKUP DATABASE [test] TO
DISK = @Path + @DBFileName + '1.bak',
DISK = @Path + @DBFileName + '2.bak',
DISK = @Path + @DBFileName + '3.bak',
DISK = @Path + @DBFileName + '4.bak',
DISK = @Path + @DBFileName + '5.bak',
DISK = @Path + @DBFileName + '6.bak',
DISK = @Path + @DBFileName + '7.bak',
DISK = @Path + @DBFileName + '8.bak',
DISK = @Path + @DBFileName + '9.bak',
DISK = @Path + @DBFileName + '10.bak',
DISK = @Path + @DBFileName + '11.bak',
DISK = @Path + @DBFileName + '12.bak',
DISK = @Path + @DBFileName + '13.bak'
WITH INIT , NOUNLOAD , NAME = 'DayNite Full Backup', NOSKIP , NOFORMAT

↧
Viewing all 4532 articles
Browse latest View live
Search