First off, thanks for taking the time to look at this, i've opened a ticket /w MS, but while i wait ...i though i'd pose the question to the forums as well

I have an issue whereby when my link between facilities drops for more than (not entirely sure, not long at all, minutes?) both cluster configurations I have seem to loose quorum and access to the desired "primary" databases is lost.

We are using AlwaysOn as a DR strategy, and I "THINK" my issue is that i need to change the vote level to 0 for anything but the primary SQL servers. 

Regardless if the replicas are online or not, i NEVER want the cluster to put the databases on the primary servers innacessible

I have two seperate Failover Clusters configured...

Cluster 1 = node majority

Server 1   > replicating to Server 3

Server 2   > replicating to server 3

When the wan link between facilities goes down (Server 1 and 2 are in one location, Server 3 is in a remote location) the quorum looses majority and ACCESS to server 1 and server 2's databases seems to go offline while its resolving

Custer 2 = Node and File Share Majority

Server 1 > replicating to server 2

Same scenario, Server 1 and Server 2 are in different facilities, when that link goes down, even with Server 1 and the File share being in the same site, the cluster looses quorum, and access to databases on Server 1 stops

I currently have three traditional FCI SQL 2012 instances within WSFC configured between two physical servers.  I am looking to add AlwaysOn Availability Groups functionality to one of these instances to be used for DR purposes.  The new SQL server will be a virtual node located at a site remote to the current FCIs on the physical nodes.  I am running into something which seem like it would be problematic but may just be making a mountain out of a mole hill.

Obviously the new virtual node needs to be added to the same WSFC containing the two physical nodes that run the three current FCIs.  When I join the virtual node to the WSFC, the virtual node is added as a selected possible owner to most of the resources in the three current FCIs (e.g. SQL Server (INSTANCE), SQL Server Name and IP address, Cluster Name and IP Address, etc.)  The virtual node is also added as an unselected possible owner on the shared disks, unselected obviously because it doesn't have access to the physical storage that presents those disks.  For obvious reasons, this virtual node should never ever own any of the existing FCIs' resources.  I just want the virtual node in the WSFC for AlwaysOn AG purposes.  Should I go through all the existing FCI resources and deselect the virtual node as possible owner, even the Cluster Name and IP Address?  It seems bad that a new node to a WSFC should automatically be added to resources of the existing FCI services when there is no way that the new node could ever own those services.

hello,

I implemented log shipping in our server the process of implementation went fine but when I view job history I found

Message
2014-06-11 12:00:01.53    *** Error: Could not retrieve backup settings for primary ID '99817903-626e-4380-bcf1-c09ca6f48b6d'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2014-06-11 12:00:01.53    *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2014-06-11 12:00:01.53    *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2014-06-11 12:00:01.53    ----- END OF TRANSACTION LOG BACKUP   -----

Exit Status: 1 (Error)

also I check for database ID using select * from msdb..log_shipping_primary_databases

your help is appreciated.

Please Mark it as Answered if it answered your question
OR mark it as Helpful if it help you to solve your problem
Elmozamil Elamir Hamid

MCSE Data Platform
MCITP: SQL Server 2008 Administration/Development
MCSA SQL Server 2012
MCTS: SQL Server Administration/Development

MyBlog

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.

Hello,

I am upgrading from SQL 2008 R2 SE to SQL 2012 SE. I am backing up databases, scripting out logins, linked servers and sql agent jobs. However I plan on detach and attach the databases.

Also, I have a transaction replication setup in sql 2008 r2 with subscriber and publisher and distribution on the same server. How do I move this setup after I upgrade to SQL 2012 SE?

Any steps that I shd follow are highly appreciated.

Thanks a bunch in advance

Hi, We will be upgrading to SQL Server 2012 from SQL Server 2008 R2 pretty soon and want to implement AlwaysOn High Availability. Could you please point me to couple of good resources for starters.

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

Ione

I have AlwaysOn SQL 2012 Enterprise set-up using Windows Failover Clustering Services (not FCI), and have 1 Primary node (P), 1 Synchronous Commit Auto Failover (SC), and 1 Asynchronous Commit Manual Failover (AC) node.  It is set up to prefer secondary, with the highest priority given to AC node.

I am using Ola Hollengren's scripts for Database Maintenance jobs, including a native BACKUP LOG job for the transaction logs of all user databases on a 1 minute schedule.  His scripts already consider AlwaysOn, and although the job is set-up on all 3 nodes, only ever runs on AC node.

The job has been running successfully since initial set-up almost 1 year ago, but suddenly yesterday morning started to fail with the following error, only on 1 of the 13 databases in my availability group:

Date and time: 2014-06-08 09:36:11
Command: BACKUP LOG [my_db] TO DISK = N'E:\MSSQL\\Transaction Dumps\my_db\MySQLCL$MySQLAG_my_db_20140608_093610_U_LOG.trn' WITH CHECKSUM, COMPRESSION
Msg 35250, Level 16, State 11, Server AC, Line 1
The connection to the primary replica is not active.  The command cannot be processed.
Msg 3013, Level 16, State 1, Server AC, Line 1
BACKUP LOG is terminating abnormally.
Outcome: Failed
Duration: 00:01:00

The other 12 databases continued to backup successfully.

Checking the Availability Group dashboard, windows event logs, and SQL Server error logs, including Failover Cluster events showed no issues.

However, monitoring software (Idera SQLdm) showed blocked sessions on P node.  When I ran sp_who2, it showed that a background process was being blocked by another background process with an HADR BACKUP LOCK.

Since both processes were background processes, I was unable to kill either process.  I temporarily disabled the transaction log backup job, but the blocked process was still active.

I ran DBCC CHECKDB (my_db) WITH all_errormsgs, no_infomsgs, data_purity on both P and AC nodes, with no errors.  However, on AC node, it also showed 1 transaction rolled forward and 0 transactions rolled back.  This also had the effect of releasing the blocked background process, but another background process was now blocking with the same HADR BACKUP LOCK.

I tried to restart SQL Server Agent on AC node, which did not immediately seem to work.  However, after a few minutes, I noticed that the block had disappeared.  I re-enabled the transaction log backup job on AC and it started working normally again.  The error has not occurred again, but I am at a loss as to what happened, and how to prevent it from happening again.

Any help would be greatly appreciated.

Diane

We are observing the below error after every fail over  in the cluster environment .Is this normal error.

Event Id:324

Soruce:SQLSERVERAGENT

Error:OpenCluster (reason: 5).

Initially there was an error for .NetFX3.5. Although installation successful with some error because .NetFX3.5 was not installed. After installing .NetFX3.5 I was trying to install SQL but below error comes and does not allow to proceed.

Please help.

Hello All !

On a Production site, I have a SQL Server 2008 R2 for a fat application. On a DRP site, I have the same SQL Server 2008 R2 fat application.

The production and DRP sites are interconnected with a physical SAN storage (synchrone replication). SAN LUNs are synchronous replicated (Data + logs).

In this case, is it necessary to keep logshipping beetween the 2 sites or the LUNs replication is sufficient ?

Does SQL Server 2014 support Group Managed Service Accounts for an AlwaysOn Availability Group?

Hi  All

In Logshipping  Primary  server we are  planing to add  one more NDF  file in this case  we  have added  in  principal server what  happened in  secondary  server.

My plan is stop all three  jobs after  then we have to  add  NDF  File once done  we have to  start the  again all three jobs.

Request to  you everybody  anything wrong please correct me

subu

Hello,

I'm trying to build storage(LUN) based replication DR site for SAP ECC with MSSQL 2008R2. Please let me know how to  taken care of below -

1. "SAP License" as it is based on hostname? Need to keep DC & DR servers with same host name??

2. How to manage automatic switch over in case of primary site failure??

3. Can we do reverse replication if primary DC is down & comes up after day or two??

Regards,

Pradeep.

                   I had my disk die with the only copy of my wife’s medical “Question and Answer” (Q_And_A)  database on it. She thought it was safe and sound on my computer, and I thought we had an “Off site” backup of the data on hers and hadn’t set up backup for it.

1.)  The bad things are, only the .mdf file was intact.

2.)  All of the permissions based on the old copy of Windows 7 and SQL 2005 or 2008 ( I am not sure which the .mdf was created in.) have gone the way of the dodo.

       Bought a new disk. Reloaded windows 7 64 bit. Loaded SQL 2014 (Thought now was a good time to upgrade.) Problem… so far I have not been able to attach and recreate the log file …

          Just to finish up the data I have, the database was closed properly and is NOT in a read only state according to file properties. That said, I still don’t have a solution.

 So far I tried these three sets of commands:

CREATE DATABASEQ_And_AON
(FILENAME=N'E:\Mikes 128GB\SQL2014\MSSQL12.SQL2014\MSSQL\DATA\Q_And_A.mdf')
FORATTACH_REBUILD_LOG
GO

And this set of commands:

CREATE DATABASEQ_And_AON
(FILENAME=N'E:\Mikes 128GB\SQL2014\MSSQL12.SQL2014\MSSQL\DATA\Q_And_A.mdf')
FORATTACH
GO

EXECsp_attach_single_file_db@dbname='Q_And_A', @physname=N'E:\Mikes 128GB\SQL2014\MSSQL12.SQL2014\MSSQL\DATA\Q_And_A.mdf'

GO

         So far this is the computer’s reply to everything I have thrown at it. I haven’t told my wife that 600 hours of her work is inaccessible, and I would really rather not do so. Anything anyone can offer would be great.

File activation failure. The physical file name "E:\Mikes 128GB\SQL2014\MSSQL12.SQL2014\MSSQL\DATA\Q_And_A_log.ldf" may be incorrect.

The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure.

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'Q_And_A'. CREATE DATABASE is aborted.

          Is there anything else anyone out there can offer as help? My wife has often said that she doesn’t believe in divorce. But murder she will consider. If she loses 600 hours of her data this could be my last post. I am joking … I think … That said, any help is extremely welcome. Thanks in advance.

Initially there was an error for .NetFX3.5. Although installation successful with some error because .NetFX3.5 was not installed. After installing .NetFX3.5 I was trying to install SQL but below error comes and does not allow to proceed.

Please help.

Hi all,

I had configured SQL Server always on availability groups on windows server 2012 and it was successful.

I’ve installed and successfully configured our SQL Server 2012 AlwaysOn 2-node windows cluster servers. I've gotten AlwaysOn working great, and our Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. As we know “we must manually find, select, back-up and then add those new databases individually to get them into AlwaysOn."

But wait; that can be quite a task, constantly checking the SQL Server back-end servers to see what databases were created, then having to add them into AlwaysOn, 7/24!

Im looking for an automated script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then add those databases to Always On, all automatically.

Requirements:

1. Every time the newly created or added databases should be full backed up once in the shared location with automated script.
2. Newly created database should be added into always on group and should be added to available replica automatically with the TSQL script

Regards,

SQL LOVER.

Hello all,

My company finally grew a brain this weekend and let me set up the AlwaysOn cluster I've been telling them we needed for months.  It's in Azure (which wasn't easy), but it works flawlessly. 

I really like the Data Collector of SQL Server and usually have it running on a continuous basis in the background.  Makes troubleshooting way easier.  It's worked well in the previous single-server design we were running.  But while I've used both Data Collector and AlwaysOn before, I've never tried to run both at the same time.  I expect that I will need to stand up non-synchronized databases on each node of the cluster and configure the MDW separately, as failing over the MDW seems unwieldy, and I can't imagine how I would get data from both the primary and the read-intent secondaries to all flow into one location.

To add a bit of complexity to the mix, the cluster is comprised of VM's in an Azure datacenter.  We're running SQL 2012 on Windows Server 2012 on all boxes except the domain controller (which doesn't have SQL server).

So my question is this: is there any documentation on pitfalls to avoid when setting up the MDW on an AlwaysOn cluster in Azure?  Or are there some recommended best practices?

Thanks in advance!

When you create a listener the IP address and port number combination always has to be unique for every listener.

I created two SQL Server 2012 EE instances on one Windows 2012 server. They both have the same IP address and node name (because it is the same server). They are not using the same port numbers. The first instance is using port 1433 and the second instance is using port 1435. That is working fine.

I created an availability group with one listener. The listener has a unique name and is using port 1433. That is also working fine.

I created a second availability group with one listener. The listener has a unique name and is using port 1433. That generates the following error message: “Create failed for Availability Group Listener ‘ag-list02’. (Microsoft.SqlServer.Smo) …  The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL Server failed to listen on the specified port [ag-list02:1433]. This TCP port is already in use. Reconfigure the availability group listener, specifying an available TCP port. For information about altering an availability group listener, see the “ALTER AVAILABILITY GROUP (Transact-SQL)” topic in SQL Server Books Online. (Microsoft SQL Server,  Error: 19486)”

I wanted to create the following listeners:

Name                   IP address           TCP Port          Description

SQLServ1            10.1.1.10             1433                 Listener of Instance 1

SQLServ1            10.1.1.10             1435                 Listener of Instance 2

Ag-list01             10.1.1.11             1433                 Listener of Availability Group 1

Ag-list02             10.1.1.12             1433                 Listener of Availability Group 2

Every listener is using a unique IP address and port number combination.

Why is this not working?

Is there something special about availability groups and listeners? Does the general rule that you can use the same port number on different IP addresses not apply for availability groups?

Can I only use a port number once per fail-over cluster?