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

Pages on a full recovery model database corrupted, need to ensure data loss is minimal for restore operation

$
0
0

Pages on a full recovery model database corrupted, need to ensure data loss is minimal for restore operation

I am thinking about restoring the latest full backup.

However, the suggested answer is

>>

Perform a page restore

<<

Why?


Enabling TDE on databases which are used for log-shipping.

$
0
0
Hi All,

I have log shipping enabled on databases(primary and secondary) and works fine. I need to implement TDE on the database. I have experience on implementing TDE on databases which are not used for log-shipping.

Can anyone please help me out to the steps needed to setup TDE which are involved with log-shipping.

Thanks in Advance.

Log Shipping : MSG 927 Database cannot be opened It is Restoring state -- Getting this Error in STANDBY/READONLY Mode

$
0
0

 we have setup a log shipping For one database. we configured secondary server as STANDBY/READONLY mode.

When we are trying to run a select query in secondary server is giving me error message as 

  MSG 927 Database cannot be opened . It is in middle of restore

But the state of database as per SSMS object explorer it is STANDBY/READONLY (Even after refreshing the database).

so can any one tell me the reasons behind this Error caused

Transaction Log LUN was deleted

$
0
0

Hello all,

My problem is pretty much what is in the title. Transaction Log LUN was deleted.

Just here to ask whats the best practice to recover this. 

Is there any MSFT official Document on the procedure to recover from this?

What is the best procedure?

First point SQL Server Log file destination to a new Drive and then Backup current data file, detach and attach without specifying log?

 Regards,

 

What might cause a SQL log backup to throw this error??

$
0
0

DESCRIPTION:    The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'DeleteFile' on '\\mls-storage1\backup\sql4_backup\SQL4\UNI_MOUN1309\LOG\SQL4_UNI_MOUN1309_LOG_20110705_210005.trn' at 'storage.cpp'(875).

I use Ola Hallengren's backup scripts; he suggested I inquire to the forums. I am particularly puzzled why the 'storage.cpp' mention since the log backup script is a SQL script.


Thank you, Tom

always on availability groups in sql server 2012 standard edition

$
0
0
Can we set up always on availability groups in <g class="gr_ gr_31 gr-alert gr_spell ContextualSpelling ins-del multiReplace" data-gr-id="31" id="31">sql</g> server 2012 standard edition.

Implications of lease & healthcheck timeout in SQL Server 2014 AlwaysOn AG environment

$
0
0

Issue Background

We have recently migrated to a production environment running on SQL Server 2014 Ent. Ed. & have faced an Availability Group (AG) outage issue as of last week.

 

The AG instance is having 1 Primary & 1 Sync Sec replica. The two replicas are on separate servers & hosted within the same datacenter / LAN network. For reasons of easier explanation, will refer to original Primary replica asA& Secondary replica asB.

 

The sequence of events started with an auto failover fromA to B. This didn’t create any issue as all workloads were running fine till this point. Do note, with this failover,B is now primary & A secondary.

Issue startedsoon after that, when the AG failed over again within a few minutes of the first failover. At this time, DBs in A (Secondary) were not in sync & thus the failover was not successful. Consequently the AG group went into resolving state on both B (primary)& A (secondary) instances.

To come out of this resolving state, we did a manual fail-over toB, after which A went out of AG. But, it was still part of Windows cluster & was reachable physically.

Diagnosis

Went through SQL Server error logs & saw the following line which triggered sequence of events as mentioned above:

The lease between availability group 'AG_Name' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster.

Searching on this, lead us to multiple possible reasons why this might happen.

In our case, there were a couple of queries which were taking 100% CPU. While these queries were running, the lease check process was not receiving any response from invocation ofsp_server_diagnostics, within the timeout period of 30 secs. This resulted in lease timeout & subsequent failover. 

With some more digging & testing, we re-configured MaxDOP (earlier it was set to 0), CTP & also lease timeout from 30 to 100 secs. Its been 6 days since this issue had occurred & it has not happened thereafter. However it raises some queries & doubts.

Queries

  1. Why did A replica went out of AG? We had to manually add it to AG & include the DBs back.
  2. Have understood the working of lease timeout & its frequency of running. However, what has not been clear is the exact difference between lease timeout & health check timeout? Moreover, if both these processes result in AG health monitoring & failover, if required, why are the 2 checks separately needed.
  3. What should be the ideal range of values for lease & health check timeout? Because a higher timeout value will only result in delayed failover when an actual issue happens.

Have searched on the above queries, esp. 2 & 3 but have not found any reasonable clarity.

Will really appreciate if these are adequately answered.

Thanking in advance,

Subho


What's-On














Error raised during log shipping when nothing seems wrong

$
0
0
I have log shipping configured to leave the secondary database in Recovering mode, with log shipping set at 15 minute intervals.  If I run profiler, I see the error below for every database that is being log-shipped every 15 minutes:

Application name: "SQL Server Log Shipping"
Error: 927
Database name: "master"
messsage: "Database 'name_of_database' cannot be opened. It is in the middle of a restore."

"SELECT * FROM msdb.dbo.log_shipping_monitor_error_detail" returns nothing
"SELECT * FROM msdb.dbo.log_shipping_monitor_history_detail" returns many rows that show all restores succeeded

So the question is, why is the error occurring if there is no other evidence that anything is failing?

Move database files that are in an Availability Group.

$
0
0

Greetings. I need to move files for a lot of databases that are all part of an AG. I've used the method at the bottom of this link with success on a small test DB, and wanted to see if anyone else has done this? Any pitfalls?

Thanks!


Thanks in advance! ChrisRDBA

SQL 2008 Ent Licensing..

$
0
0

I heard from one of my friend that,  there are two clauses in SQL2008 Ent license. One with SA(Software Assurance) and one with out SA.

Do we  require to buy license for passive node in case if we buy SQL 2008 Ent license without SA?

Also Let me know what is meant by Software Assurance license for SQL 2008 Ent

Peter.K

09486110789

High Availabilty for SCCM 2012 SP1

$
0
0

Hi Experts,

There was a need for setting up High Availability for SCCM 2012 SP1 database instance. However what I understand is that AlwaysOn/Mirroring/Logshipping is not supported for SCCM 2012 SP1 database instance. Can you please confirm if missing out something and any reason for the same.

Thanks

Is there any diagnostics tools for I/O Subsystem and Memory chip

$
0
0
I would like to know if there is tools out there in the market to Diagnostics I/O Subsystem and memory chip in SQL Server?

SQL HA Availability Groups in MS Azure IaaS

$
0
0

I have a SQL 2012 R2 HA configured in Azure Iaas VMs, using Availability groups. it has 2 SQL nodes & 1 Listener server (in ILB) under same cloud service. Currently I have only one SQL named instance.

There is a customer requirement that, they wanted multiple SQL named instances in those two SQL nodes, and they need to be in Availability groups.

It is already known that 'Only one availability group listener is supported per cloud service' . Now If I create new named instance & create a new Availability group - how to attach the listener there ?

If Azure doesn't support multiple listeners per cloud service - how to deploy this kind of requirement & what are best possible options ? is there any roadmap to support this ?

if Client wants to stick to the options of multiple named instances on these nodes  (like on-premise) - what is best option here ? Deploying them on different set of servers will increase the cost.

Thanks for your suggestion here.

AlwaysOn Availability and TRUSTWORTHY Property

$
0
0

Hello All,

We have a SQLServer 2012 Always-On Availability (AAG) Primary and Secondary Node installation/environments. On the Primary node, we have some databases that have the TRUSTWORTHY option enabled (Set to ON). But when the databases are synched/added to the AAG the databases loose the TRUSTWORTHY property and are reset to OFF on the Secondary Node.

Because of this,When the instance fails over to the Secondary Node the applications that were working don’t work anymore.

Is there a workaround for this issue?

Thanks,

rgn

Backup file size after implementing AOAG

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


We recently implemented a High Availability Group. We have been doing file group backups of our main production database for about a year. We do a full backup once a week on Sunday, we do differentials every night except Sunday and we do regular transaction log backups.

The odd thing is that once we moved the database to the AOAG, the size of the backup files exploded for no apparent reason. We first noticed this with the differential backups, but it's also the full backups.

For example, we have one file group that is just under 42 GB. Prior to the AOAG, the size of the full backup for this file group tended to be around 10 GB and the differentials ranged between 200 MB to 1 GB. After AOAG the backup sizes exploded so that the full backup files are 16 GB but the differentials really exploded to 14 GB!

A bunch of the differential backup files even for our smaller file groups are around that same 14 GB size which is several times the size of the data files in some cases. All total our full backups went from taking about 425 GB now they are over 800 GB. Our differentials went from taking about 9 GB the day after the fulls to taking over 700 GB! 

This is a huge problem for us. I've double checked and we are still using compression. Interestingly the transaction log backups are about the same size as before.

Any ideas on what's going on? 


SQL HA in Azure IaaS

$
0
0
     

I have a SQL 2012 R2 HA configured in Azure Iaas VMs, using Availability groups. it has 2 SQL nodes & 1 Listener server (in ILB) under same cloud service. Currently I have only one SQL named instance.

There is a customer requirement that, they wanted multiple SQL named instances in those two SQL nodes, and they need to be in Availability groups.

It is already known that 'Only one availability group listener is supported per cloud service' . Now If I create new named instance & create a new Availability group - how to attach the listener there ?

If Azure doesn't support multiple listeners per cloud service - how to deploy this kind of requirement & what are best possible options ? is there any roadmap to support this ?

if Client wants to stick to the options of multiple named instances on these nodes  (like on-premise) - what is best option here ? Deploying them on different set of servers will increase the cost.

Thanks for your suggestion here

AG databases went into 'Synchronizing/In recovery' after upgrading to 2014

$
0
0
We have 3 replica AG setup. 2 replicas are in sync/automatic failover, the other(DR Server, different subnet) in asynchronous/manual mode…All these replicas were on sql server 2012, Recently we upgraded DR server to 2014. Since then we have a problem, the AG databases in 2014 instance went into ‘Synchronizing/ in recovery’ state…The SQL server error log has message, the recovery couldn’t start for the database ‘XYZ’…We tried to create a new database and add it to AG , it works for fine for other two 2012 replicas, but on 2014 we see the same issue…Is there any workout to fix it or upgrading other replicas to 2014 is the only available solution..Quick help would greatly be appreciated

Slow performance in SQL Server 2012 when we run a command on a spatial data type of a large table

$
0
0

Hi friends,

the  following is the culprit for poor performance. cpu spike always high(avg-97-100)

-cpu busy count-74687537

SELECT top(1)@location=isnull(location,'No Location Found.'),@lat=Lat,@lon=lon 
 FROM [IndiaLocation].[dbo].[IndiaLocation] WITH(INDEX(idxGeom))
 WHERE geom.STDistance(@g) is not null and geom.STDistance(@g) < 2000
 ORDER BY geom.STDistance(@g);

any idea how to stable it and how degrade the cpu resources...

Best way to copy large database to another and keep them synchronized?

$
0
0

Hi all,

We have a situation that requires converting all INT columns from source database to BIGINT in destination.

By ‘copying’ term, I consider any operation like insert-select, merge, asynchronous replication or any other that will get all data synchronized until some moment in time, i.e. 2015-12-31 10:00 PST when downtime is planned. Before that moment it isn’t important if data in source and destination DB are in sync.

Copying process starts early enough to allow appliance of any technique/technology – there’s enough time to find best solution.

Requirements:

1\ Destination database is superset of source, having all tables and all columns plus few more columns in few tables. Additional columns have default NULL or they are computed. INT columns in source are BIGINT in destination.

2\ If source and destination are not in sync at the moment downtime begins, it is allowed to have few minutes to wait for synchronization. For instance, if transaction logs from last hour or so need to be shipped, that would be ok. If large table need to be synchronized by comparing row-by-row, it’s not ok.

3\ Source database performance must not be compromised by any copying if it’s done before scheduled downtime

There are couple of options I have in mind involving MERGE command but its appliance might be limited by current DB design. Additionally, based on business logic, I cannot be absolutely sure if some row, created while ago, wasn’t changed meanwhile. For some large tables, there is no indicator at all when any row has changed – I cannot rely on IDs nor there is column like ‘[date last changed] DATETIME’

I have been reading about various kinds of replication, i.e. log shipping but I’m not clear if any of these is applicable. Key points, if there is replication involved, are copying process must start from empty destination database plus synchronization must not compromise source DB performance

So, any ideas how to do this using any kind of replication? Any other ideas?

SQL server Always On

$
0
0

Hi,

I have 2014 always on setup on a database in my infra.

When ever i add a data or log file in my primary database,  always on sync is abending on secondary with below error,

Not able to add a data or log file in database, because the location does not exist.

My questions are below,

1. Do we need a same directory structure on all the always on nodes ?

2. Do we have any other option to enable , where data or log files get created on existing(default) location ?

3. Do we have an option to not seek for new files on the always on database ?

Thanks,


Vinodh Selvaraj

Viewing all 4532 articles
Browse latest View live


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