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

Adding new disks to SQL 2012 AlwaysOn Nodes

$
0
0

I am having a bit of an issue with adding 2 new disks to a 2 node SQL 2012 Always On setup.  I am currently running 2x Windows server 2012 R2 Datacenter VM's with SQL 2012 Enterprise with SP2 installed.  SQL AlwaysOn is already configure and functioning properly (maybe?).

I am trying to add 2 new disks to the existing SQL AlwaysOn Nodes.  I can successfully add disks to Node 1 and assign them drive letters.  But when I go to Node 2 and add the disks, I can't assign the same drive letters as what was assigned on Node 1.  I suspect that Windows Clustering is coming in to play here.  Is there any way to add disks to each node with the same drive letters on each node?

Thanks in advance.


AlwaysOn Availability Group - "backup command failed to complete BACKUP LOG"

$
0
0


Hi,
I have a SQL Server 2012 AlwaysOn Availability Group which uses Veeam 7 for backups. I'm using a 2 node Windows 2012 cluster with a file share witness.

- At 19:00 the primary node is backed up by Veeam using application aware image processing to truncate the logs.
- At 22:00 the secondary node is backed up using Veeam without application aware image processing.

On the primary node, I see application event log error "backup command failed to complete BACKUP LOG" <model/master/tempdb/YourDB> "Check the backup application log for detailed information".

On the secondary node, I see application event log error "The recovery LSN (45:6543:1) was identified with the ID 5.This is an informational message only. No user interaction is required"

Other than the backup related messages, the AlwaysON SQL cluster is fine - cluster validation checks pass as expected, no other errors are logged in the event log and failover works as expected.

I want to backup the active DB on my AAG and truncate the logs - ideally using Veeam, but if not, I'm happy to use an alternative.

Is there a best practice, recommended way of doing this?

Thanks

Transparent Failover SQL Azure database

$
0
0
Is it possible to achieve transparent failover for database in SQL Azure database with active geo replication so that the application knows the failover server as well?

Failover

$
0
0

We have built a web solution based on IIS and SQL Server 2012 technology, installed on one physical server with local disks. Server is not member of a domain.

We now want to build a redundant solution by installing a second physical server with local disks in a remote datacenter.

What is the best way to create a redundant (manual failover is OK) solution for SQL Server?

Is Always on an option? Do I need Active Directory for this solution?

Please advise

Kind regards,

Kenny

How to enable high availability on SQL Server 2005 with Windows Server 2008 Enterprise R2

$
0
0

Dear Folks,

I would like to ask you about this thing. I'm working for IT department for bank in Myanmar. Our bank have up to 96 branches across all of Myanmar including H.O. We are using Microsoft SQL Server 2005 with Windows Server 2008 for our banking information system. My main problem is having to backup and restore the database backup files every time the servers in branches goes down for whatever reasons. I want to deploy this feature of high availability and failover cluster using Windows Server 2008 and SQL Server 2005. Our branches have 2 Servers. One is for Primary and other is for Backup. What I want to do is that, I want to change Backup Server to Primary Server whenever the Primary Server goes down for whatever reasons. All the working data and databases from Primary will immediately replicated into Backup Server along with all the IP information of Primary Server. Please give me step by step guide for this process.

AlwaysOn with a single node possible?

$
0
0

This is a rare situation, but here's a projectplan I am currently evaluating. In my opinion this will not work. However, I can't find an answer. I found some documentation about setting up a single node cluster, but this is about a (traditional) 2008 cluster. This project is about migrating a sql 2008 cluster to a sql2012 alwayson solution. Here are the steps:

  1. break the 2-node 2008 cluster. Production will continue on node 1
  2. reinstall the 2nd node with windows 2012. install / activate clustering
  3. install sql2012 with alwayson for this node only
  4. restore database on 2nd node, test
  5. promote 2nd node to production
  6. reinstall 1st node and add to cluster
  7. alwayson is working

So the question is: will step 3 work? Can you install / configure / run always on with selecting one node?

again failover question...

$
0
0

Hi,

I've searched a little while but couldn't find a good answer, just the Standard how to build, but never "how it operates"...

I have built a Default SQL FCI Cluster based on Windows 2012R2 and SQL 2012 Enterprise, this is working as ususal no worries from my side.

Then I wanted to extend the Cluster with the Desaster recovery Feature from availability Groups and added a 3rd node to the WSFC, built my availability Group with async commit and the listener for it.

Anyway my actual question is:

When performing Manual (for maintenance) or automatic Failover of the FCI instance I use the Failover Cluster Manager and when performing the Manual Failover to the Desaster node I use the SSMS, correct?

I worried because when performing the FCI instance Failover the AG listener Fails, clear why, but it just feels awkward. I didn't see a way to give the FCI instance a dependency to the listener so it would take it offline instead of failing it...

anyone has a tipp or operating experience for me with this?

Thanks in advance,

alex

History on Always On

$
0
0

I am using SQL 2012 with Always On.

I would like to get historical information when DB was not synch. Is there any DMV or log where I can get this information. I was hoping to get this info from “AlwaysOn Health Events” but it seems “AlwaysOn Health Events” doesn’t log this kind of information. Am looking into wrong place?


Logshipping.

$
0
0

An Obsolette Db was deleted while its log-shippin was still enabled. After the deletion of DB, SQL Server is not allowing me to delete the Backup, Copy and Restore jobs. Worst is the LS_Alert job keeps buzzing for this deleted DB. The entry of logshipping is still present in the msdb.dbo.log_shipping_primary_databases.

I have also tried to delete the entry with help of the SP as below query. but no luck. Please help.

EXEC

master.dbo.sp_delete_log_shipping_primary_secondary


@primary_database

=N'xxxx',


@secondary_server

=N'xxxxx',


@secondary_database

=N'xxxxx'

Database Ownership gets messed up with SQL Server 2014 AlwaysON

$
0
0

Hi All,

I am trying to build a nightly refresh process for SQL Server DB from on premise to Azure Cloud (IAAS). The Azure infrastructure is configured as 2 node always on. Every Day a new DB get created with retention period of 7 days. (Another script which deletes old DB)

Nightly Build Process as Below:
1)DB Backup get copied to Azure Blob Storage 
2)Restore DB on primary Server on Azure
3)Change DB owner to appropriate login on primary Server
4)Backup DB/Log from primary Server and restore it on Secondary Server.
5)Add DB to alwayson temp Group.
6)Failover temp Group and change DB owner to appropriate login. (Application Dependency to have login ID as the owner of the DB).
7)Failback and remove DB from temp group and add it to appropriate group.

During this process somehow the DB ownership gets messed up randomly either on primary or Secondary. 

I can handle the primary server ownership mess-up by adding piece of code to set the ownership in the end, but for secondary I can't change the ownership as the DB is in readonly mode, resulting, when failover happens the application fails to open default DB.

Any lead on the solution would be appreciated.

Thanks,
Viral Shah


Thanks - Viral

availability replica is disconected

$
0
0

Hello Everyone

we have a cluster with 3 servers GA04 GA05 and OH02, GA04 and GA05 are configured to failover and be the same database server, if one is down the other is up (this have a database instance called SQLSRV_A), and OH02 is configured as a replica by AlwaysOn (with database instance called SQLSRV_B), today we had a failover between GA05 and GA04, this changed the primary node of insance A (from GA05 to GA04), this caused Availability replica on server OH02 down, but OH02 server never was down.

i have read a lot of information about Always on config but i cant find why this happend, i cant fix it neither, and i cant reconfigure replication on AlwaysOn from Zero, i checked ports and Endpoint URL and everithing looks ok, i restarted server OH02 and nothing.

i only have left to restart Primary server (both servers to avoid failover again) i think the issue was caused by failover, but im not sure, anyone have been in this situation?

thanks a lot.

SQL Server Cluster Public/Private Network

$
0
0

HI All,

I have some doubt in Window server fail-over cluster...Please advise..

Scenario :- I have 8 node cluster, with node and disk majority , with two networks (public and private). Case 1. If Public network gets down then what would happen...Will a failover initiated or not? Case 2. If active node is not able to communicate to the public network but other nodes could communicate to the public network...what would happen..

Thanks In Advance


Thanks

Alter IP address of SQL Server AlwaysOn Failover clustering Iistener

$
0
0

Hi,

Is there a possibility to change the IP address of SQL Server AlwaysOn Failover clustering Listener IP address without deleting the exiting one and also retaining the same DNS name.

NOTE: Only the IP address needs to be altered rest all (DNS, port) should remain the same.

Regards

Vijay

How to do the secured data transfer between Databases Servers to Application Server

$
0
0

Hello,

I got a question from my Management “How to do the secured data transfer between Databases Servers to Application Server”.It would be really helpful if someone can provide some tips.

Thanks

Karthick

Are you using AlwaysOn or replication for scale?

$
0
0

One of the attractions of the current "big data" fad is scalability - you can throw ten or a hundred servers at the problem of persisting data and then (mostly) selecting from it.

Seems to me that we could do that with SQL Server - have a single (cluster) host where data is inserted and updated, and have multiple read-only copies to support scalability to thousands of simultaneous select/SP transactions.

But I haven't seen it done.  This may or may not involve sharding, where a copy contains only a part of the data, and may or may not - but mostly not - involve letting the clients do any data modification.

"Scaling out" and sharding were somewhat more popular ten years and more ago, before SQL Server and Wintel got so good at multiple processors per server.  Anybody doing any of that now?

Outside of log shipping to DR and replication to a report server, I haven't seen any recently.

Shipping data from an OLTP system to a data warehouse or data mart via an operational data store does not count, that's changing the shape of the data as it moves and not using the destinations homogenously.

Thanks,

Josh


Clustering failover issue

$
0
0
Hi All,

During scheduled re-boot when the sql resources of cluster are moved from primary Node to seconday it is taking long time for the databases to get online in secondary node . But this is not the same when the resources are moved from secondary to primary node . Please let me know if any settings to be changed in Maximum failures in the specified period andPeriod (hours) ?

Thanks

Operating system error 1450(Insufficient system resources exist to complete the requested service.).

$
0
0

Hi,

We have a windows server 2003 32 bit SQL server with SQL 2008 installed on it. The Log shipping backup jobs are failing with following msg.The server has 32 gb of memory and SQL instance is set to have 20gb max memory.

We implemented http://support2.microsoft.com/default.aspx?scid=kb;en-us;304101 but still the backup jobs are failing.

Is there any fix(OS Updates) for this OS issue?

BackupIoRequest::ReportIoError: write failure on backup device . Operating system error 1450(Insufficient system resources exist to complete the requested service.).

Regards,

V


vamsi chaitanya

Unable to connect SCOM 2012 console to SQLAlways listener

$
0
0

Hi Friends,

I built SCOM 2012 Infrastructure with SQL Alwayson 2012 cluster in backend.

But when I do manual failover of SQl server and try to connect with SCOM server is unable to connect with SQL listener on Node2 of MS SQL wher it works fine on

Node1.SCOM console freezes and unable to ping sqllistener IP.And I see dashboard all synchronization is healthy.

How I built:

MS1

MS2

SQL1(1 and 2 are replicating with Alwayson)

SQL2 

Any ideas on this are appreciated.

Thanks

Ameen


Mohammad Ameenuddin

Minimum number of Servers needed for an SQL Availability Group

$
0
0

I have looked and I cannot find a definitive answer on this.  What is the minimum number of SQL servers required to create an always on availability group?

We would like to create an Availability Group with two SQL servers with a file share witness on a third server like we have with Exchange but I can find nowhere that specifically says if this is possible or not.

Any help would be appreciated.

AlwaysOn

$
0
0
What happens if secondary replica unavailable in synchronus-commit mode in SQL 2012 AlwaysOn?
Will the transaction is going to be success at Primary?
Viewing all 4689 articles
Browse latest View live


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