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

Connection AlwaysOn AG Listener Problem

June 17, 2014, 9:30 am
$
0
0

I'm a newbie for microsoft technologies and I'm having problems in connectivity part for SQL Server 2014. This is probably an easy issue but I'm stuck.

I've 4 servers. One of them is the Active Directory Domain Controller, one is the application server and the others are being used for SQL Servers. Since it's a connectivity issue, IP's for servers are; -AD DC : 10.6.0.100 ( Also the DNS Server ) -APP : 10.6.0.110 -SQL 1 : 10.6.0.120 -SQL 2 : 10.6.0.121

I've successfully created a failover cluster (DBCLUSTER) and set the IP address of the FC as 10.6.0.130( which is not an actual server IP, I really don't get this part.. ).

Later, I've created an AlwaysOn Availability Group for sql servers. I've successfully created the AG without listener. I could connect to servers from each other, database syncs without problem. Then, I've created a listener (AG-LISTENER) and set it's ip as 10.6.0.131 ( which is not an actual server IP, again? ) and set it's port to 5525. It gave no problems.

So I wanted to test connectivity. When I wanted to make connections from APP server to directly SQL 1or SQL 2, I can connect without problem. But when I try to connect to AG-LISTENER, it cannot find it on network. When I check the DNS records. I can see it as it's being hosted on 10.6.0.131.

When I tried to ping to AG-LISTENER from AD-DC, APP, SQL 2 servers, it responds that the destination host is unreachable (it's pinging 10.6.0.131 but the response comes from the IP's of AD-DC, APP and SQL 2 servers). It can connect from SQL 1 server, which is the primary for AG.

I've checked the firewalls, there's no problem. But I think this is an network issue which I have no clue.

PS: Servers are operating on Windows Server 2012 and are not being hosted on Azure.

↧
Search

Adding SQL Server AlwaysOn to existing Failover Clusters

June 17, 2014, 11:48 am
$
0
0

Hello,

We use two seperate ms sql server 2012 clusters. We have two sites. All nodes are in same domain.

In the first site,  NOD1 and NOD2 are in SITE A cluster group. (INSTANCE A) They have a shared SAN storage.

In the second site, NOD3 and NOD3 are SITE B cluster group. (INSTANCE B) They have a shared SAN storage too.

Can we use alwayson  between two sites?  If it is possible , how can we do it?  and documents, web site etc. 

Thank you.


↧
↧

Maintenance Plan does not delete old BAK and TRN files

June 17, 2014, 11:20 am
$
0
0

My Maintenance Plan doesn't delete old BAK and TRN files, despite my efforts to find and apply all I saw in these posts. In more detail:  (1) The Maintenance Plan creates the BAK files with BAK extension but does not delete them, and (2) the MP creates the TRN files but OMITS the TRN extension and does not delete them.  If I could fix (2), I could write TSQL using  master.dbo.xp_delete_file.

Yes, I create "bak" and "trn" in the wizard, not ".bak" and ".trn".

No, I don't use subfolders.

Yes, I wait, but without success.

Yes, I opend the T-SQL button in the wizard and to my limited knowledge I did confirm the instruction included the trn extension.

Yes, I found a good link in the forum, http://social.technet.microsoft.com/Forums/sqlserver/en-US/53a4afff-79ad-4202-8840-67958a3fd334/sql-server-2008-maintenance-plan-will-not-delete-bak-and-trn-files?forum=sqldisasterrecovery. I used its suggestion to test my permissions, and it worked (deleted all backup but no trn files).

--EXECUTE master.dbo.xp_delete_file 0,N'D:\Program Files\...\MSSQL\Backup',N'bak'

Excluding the use of SSIS, what else is there I can do?

↧

Transitioning mirrored DBs to an AlwaysOn Availability Group....same end point?

June 17, 2014, 12:09 pm
$
0
0

I have a SQL 2012 FCI that currently mirrors all of its DBs to a standalone SQL instance for on-site DR purposes, an instant-on server should something catastrophic happen to the main FCI if you will.  Currently these mirrored DBs are configured as synchronous but no automatic failover.  We want to add another SQL instance for off-site DR purposes.  Now obviously I can't mirror DBs to multiple instances without first transitioning to an AlwaysOn Availability Group first.  (The mirroring was initially set up under SQL 2008 and all servers later upgraded to SQL 2012, hence why an AG wasn't implemented from the get-go).  The idea is that we would first migrate the existing mirror server to a new on-site server configured as a secondary in an AG.  Once that is complete and the old mirror server decommissioned, we could then add another availability replica server located at the remote site.  The process sounds easy enough.

However, since these are mission-critical DBs, management doesn't want to lose the instant-on on-site mirror server without a replacement.  Obviously a DB can't be added to an AG if it is already being mirrored so something has to give.  Since mirroring is done on a per-DB basis, the mirroring can be removed from one database at a time and once gone, the DB can then be added to an AG.  I was stepping through this process and noticed that the AG wizard picks up the same endpoint already configured for mirroring (5022).  Can the same endpoint be used for both mirroring and availability groups at the same time?  It doesn't appear that you can add a new end point via the New AG wizard which would lead me to believe both mirroring and availability groups can co-exist on the same end point.  You couldn't have multiple mirroring end points in previous versions of SQL so I think its the same in 2012.  I was looking around and can't seem to find a definitive answer on this.  Can anyone confirm?

↧

the cluster resource could not be brought online due to an error bringing the dependency resource

June 17, 2014, 2:55 pm
$
0
0

hello

i am tring to install sql 2012 sp1 clyutering on Windows server 2012. every thing is fine until a get this error

The cluster resource 'SQL Server (SQLCLUSTER)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name (ST-SQLCluster)' online.  Refer to the Cluster Events in the Failover Cluster Manager for more information. i don,t have permision issue.

any help for this please

Kamel

KAMEL

↧
↧

Backup Maintenance Plan on SQL AlwaysOn Availability Group Secondary Read-Only node

June 8, 2014, 2:27 pm
$
0
0

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.

The backup job within SQL Maintenance plan is failing with the following error:

Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"

Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

↧

LogShipping Alert Job on Secondary server is failing with no backup msg.

June 18, 2014, 4:40 am
$
0
0

Hi,

The Log shipping alert job on secondary server is getting failed and giving the error below.

'The log shipping primary database --------- has backup threshold of 60 minutes and has not performed a backup log operation for 166653 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420).  The step failed.'

When I have a look at the table log_shipping_monitor_primary from two different servers, the records on primary server
are showing the last_backup_date as the recent one but from the secondary server, the last_backup_date is about 4 months back.
And hence the error shows 'has not performed a backup log operation for 166653 minutes'.

What can be the possible reason for the error in the 'LogShipping Alert Job on Secondary server' and how to resolve?

Thanks

↧

Transaction cross 2 Always on availability groups with asynchronize mode

June 18, 2014, 4:05 am
$
0
0

We have 2 AG each with on DB in it. the mode of the synchronization of those AG is Asynchronize.

What will happen in a case where a transaction crosses the boundary of a database.

Example SP on DB A deletes account records from DB B and inserts account records into DB A– in a single transaction.

what happens in a case of disaster to the copies in the DR site, will they be as it was before the begining of the transaction, or it could be that one DB will have half a trasaction commited on it?

↧
Search

Removing SQL 2012 AAG after virtualisation

June 18, 2014, 8:32 am
$
0
0

HI There

We have an SQL 2012, 2 node AAG Cluster running in a Server 2012 WFC environment. We have now virtualised the SQL estate and no longer require the AAG functionality. We want therefore to remove (drop) the AAG. The AAG is used for a SharePoint Farm.

If we do this i believe the AAG listener is also removed? This will therefore disconnect the client from the databases. I cannot find any documentation on removing an AAG (other than just right click the AAG on the Primary node and select delete ) and then re-establishing connections.

Can someone tell me the correct procedure to remove the AAG (and subsequent WFC node) whilst maintaining connectivity to our SPS Farm (client connectivity to database)?

thanks

Steve 

↧
↧

Transaction log is full

June 17, 2014, 6:12 pm
$
0
0

Hi,

What is going to be happen if transaction log is full?

↧

Always On power loss caused entire availability group to fail

June 18, 2014, 9:20 am
$
0
0
I have a 2 node availability group on SQL Server 2014. Each node is in a different row of the data center. The row with the primary node lost power and the secondary node did NOT come online. The secondary node went into a "recovery pending" state. The cluster was no longer accessible from the Failover Cluster Manager. Once the primary came back online we were once again able to use the availability group as well as see the group in the Failover Cluster Manager.

When we just unplugged the server to simulate the power loss we had the exact same result. We also got the same result but unplugging the network cables from the primary node.  This lack of failover during a network or power outage is very troubling and we are worried that either we missed something in setup of the high availability group or perhaps AlwaysOn does not achieve the HA we were hoping for.

Is there a step we missed to allow the HA Group to fail over from one node to the other during a network/power outage?
↧

Clustered role 'SQL Server ' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made

June 17, 2014, 10:06 pm
$
0
0
Clustered role 'SQL Server ' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made

KAMEL

↧

SQL Server 2005 High Availability and Disaster Recovery options

June 18, 2014, 8:50 am
$
0
0

Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how do we test the failover is working?

Thanks in advance.........

Ione

↧
↧

Reporting from Database Mirroring and Database Snapshots Vs Logshipping.

June 18, 2014, 12:46 am
$
0
0

All SQLSERVER 2008R2 instances with Windows 2008R2. 

Environment:
I have a :
SqlserverProd instance 
SqlserverReport instance in sycn with SqlserverProd using replication. 
SqlserverMirror in sycn with SqlserverProd using Mirroring. 
SqlserverLogShip in sycn with SqlserverProd using Logshipping. 


Descripton:

I am looking at what can be the best option to use as the backup for the SqlserverReport in case the SqlserverReport goes down and I have to carry on reporting. 
At the moment I am using the SqlserverLogShip server for reporting when the SqlserverReport is down by pushing the restore frequency down to 2 hours. This is currently working great for me and I am happy with it. 

Now, that I realized that we can create Snapshots on the SqlserverMirror server and do the reporting from it. 

Question:
I am just wondering what what shall be the gain to do the reporting from the db Snapshots on the SqlserverMirror server over the logshipping database. I understand that we drop the connetions when the log is applied but thats fine we don't have the requirement for any real time reporting. 


↧

Always On availability groups between Windows Azure regions

September 18, 2013, 1:51 am
$
0
0

Hello.

I want to configure SQL Server Always On availability groups between Windows Azure virtual machines in different regions. One machine would be in a data center in Europe and one in Asia. Is that even possible? Cannot seem to find much information about Always On cross-region. I have looked into mirroring instead but I need both databases to be readable.

Thanks!

/Niklas

↧
Search

Not able to create the db and restore the db in cluster environment

June 11, 2014, 10:52 am
$
0
0

Hi

We have created a new sql cluster server.After configuration we have created a db on the server.

After some days we tried to create the db and restore the db.But we are getting the below errors.

While restoring from a drive observed below error.

Error:cannot access the specified path or file on th eserver.verify that you have necessary security privileges and that the path or file exist

While creating new db

cannot use file 'path:*****.mdf' for cluster server.only formatted files on which the cluster resource of the server has a dependency can be used.Either the disk resource containing the file is not present in the cluster group or the cluster resource of the sql doesnot have a dependency on it.
create database failed .some file names listed could not be created.check related errors.(microsoft sql server,error:5184)

On active node c drive and quorum drives are offline.On passive node both are online.Remaining other drives are in online on active node.We have kept the user and sys db  files on other drives.

Is this causing issue.please share if there are any links related to this issue.

↧

AlwaysOn availibility group state is unknown in secondary node

June 20, 2014, 5:21 am
$
0
0

Hi all,

I have configured a alwayson database.

The availibility group state in primary node is okay, but it is unknown in secondary node.

How can I make it to healthy?

Here is the screen capture.

↧
↧

Disk GUID shown at the Failover Cluster Manager instead of the NTFS Mount Volume Name

June 20, 2014, 7:00 am
$
0
0

Dear Team

I have built windows 2012 R2 fail over cluster. The sql server 2012 has been installed in cluster mode. When we add share disk for database it showing like General DBs\\?\Volume{665480bd-12d9-11dd-92ea-001cc442e304}\

Can you Please explain why it is showing in GUID like this. While in 2008 it is showing as O:\Miscellaneous\General DBs .

We need to have this NTFS mount volume name in our win2012 server. Pl reply

Thanks

↧

Atltered table reverts back to it's old form or newly Created table gets dropped after making transaction with database.

June 20, 2014, 5:03 am
$
0
0

I have succeeded in altering a table or creating a new table.

But, all these get dropped from the database I make transaction

with the database. Please , how do I get round this problem?

↧

Failed over to a Aysnc Replica and now previous primary replica(Now Secondary) is in NOT SYNC state

June 20, 2014, 11:44 am
$
0
0

Hello All,

Here is my situation :

3 Nodes in an AG configuration, and its a multi-site cluster. Sync commit between 2 nodes in one DC and Async commit to a node in the DR DC. 

AG is failed over to the Async Replica which is the DR site and all the databases comes up fine and application also can connect using the listener.

When checked the state of secondary databases, its in NOT SYNC mode. Data is suspended automatically.  I can resume data movement to fix the problem, but was curious why this will be in NOT SYNC mode?

Thanks in advance.

Thank you,

Anup

<div> <p>Anup | Database Consultant </p> <p></p> <p>Blog: <a href="www.sqlsailor.com/">www.sqlsailor.com</a> Twitter: <a href="https://twitter.com/#!/AnupWarrier"> Follow me !</a></p> <p></p> <p>Please use <b><i>Mark as Answer</i></b> if my post solved your problem and use <b><i>Vote As Helpful </i></b>if a post was useful. </p> </div>

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