Hi 

I am trying to configure AlwaysOn and having issues enabling in SQL Server configuration manager

OS : Windows Server 2012 R2

SQL : SQL Server 2014 Standard Edition

Here is what i see in config manager : 

The AlwaysOn Availability Groups feature requires the x86(non-Wow) or x64 Enterprise Edition of SQL Server 2012 (or later version) running on Windows Server 2008 (or later version) with WSFC hotfix KB 2494036 installed. This SQL Server edition and/or Windows Server system do not meet one or more of these requirements.

I patched both the nodes and ran the cluster validation as well which didn't report any missing patches. Couldn't find any documentation/solution for this. 

Can someone please help me with this ???

I know this seems to have been covered a million different places, but I can't find a site that lists the pros/cons in a simple way.  

It appears that yes, you can do it, but it comes with some caveats.  According to this (http://www.vmware.com/files/pdf/solutions/SQL_Server_on_VMware-Availability_and_Recovery_Options.pdf, page 12) you cannot use vMotion if you are using FC: vSphere vMotion cannot be used for Microsoft failover cluster nodes running on a host’s Fibre Channel storage network.  I am sure there are likely other issues as well, since lots of reputable people seem to say that although you can do it, its not a good idea (http://www.brentozar.com/archive/2012/09/why-your-sql-server-cluster-shouldnt-be-virtualized/)

So I guess what I am looking for is a site that shows in a concise manner, what the pros and cons are for running a SQL cluster in VMware.  

Team,

There is a requirement to move the current DBs from existing SAN to new IBM SAN disks. I have outlined the below steps. Request you to please add your inputs/challenges/risks.

This is in Always ON and We have 3 Nodes. 

Server A , Server B and Server C

A and B are Synchronous

C is hosting Async replica.

Note: The SQL binaries are installed on E: drive which is a SAN drive. Whether is this going to be impacted based on my steps below?

1. Present the new SAN of same size  on all the nodes in the Availability Cluster.
2. Break the secondary replica. On Secondary replica, Migrate the data by physically moving the DB files from old SAN to new SAN.
3. Rename the new SANs back to the original filenames as it was present earlier. Bring up the services and join to Availability Group. Check whether the DBs are Synchronized with Primary.
4. Now, Failover the Primary to Secondary replica- This will be a short outage.
5. Follow the same steps on Primary as mentioned in Steps 1-3.
6. Check the Synchronization of the DBs and perform all the sanity checks.

Thanks!

Sharath

Best Regards, Sharath

Getting below error while working on Microsoft Virtual Lab:

https://technet.microsoft.com/en-us/virtuallabs

System Name : SQL Two

"unable to save the alwayson high availability settings return code 0x80070046"

Getting above error while enabling Always on Availability group from SQL Server Configuration Manager.

We have setup Hi Availability group on SQL 2012.

As usual i have created backup maintenance plan in Primary and secondary server with 2 tasks i.e

• Backup maintenance Task
• Maintenance cleanup task

Then i have created Job and selected given maintenance plan.

After many days when i again looked up, i saw that jobs are failing from many days on these servers. sometimes it says about file not found with xp_delete_file().

I am not sure whether continuing backup strategy as i was doing in  SQL2008 is right way or not when working with High Availability group

One thing which i noticed is that backup is running fine when it became secondary server, but i still need to confirm that.

Any suggestions/views

Technical User

Hi there I was wondering if someone may have a best recommendation for the following requirement I have with regards setting up a third database server for reporting?

Current Setup

SQL Server 2012 Enterprise setup at two sites (Site A & Site B).

Configured to use AlwaysOn Availability groups for HA and DR.

Installed on Windows 2012 Servers.

This is all working and failover works fine and no issues. So…

Requirement

A third server needs to be added for the purpose of reporting, to be located on another site (Site C) possibly in another domain. This server needs to have a replicated read only copy of the live database from site A or Site B, whichever is in use. The Site C reporting database should be as up-to-date to the Site A or Site B database as possible – preferably within a few seconds anyway….

Solution - What I believe are available to me

1.       I believe I can use AlwaysOn and create a ReadOnly replica for the Site C. If so do I assume Site C needs to have the Enterprise version of SQL server i.e. to match Site A & Site B?
2.       Using log shipping which if I am correct means the Site C does not need to be an Enterprise version.

Any help on the best solution for this would be greatly appreciated.

Thanks, Steve

Hi,  I have 2 SQL 2012 servers in my DMZ and I have assigned SQL to run on a static TCP Port.  I would like to setup Always On availability groups on the servers but I cannot get the failover to work with the static TCP port.  It works fine with dynamic ports.

When the failover is initiated it attempts to connect to the secondary replica with out using the static port,  can someone tell me how to setup the availability group using static tcp ports.

Thanks,

Hello,

There is SQL server database on client side in production environment with huge transaction logs.

Requirement :

1. Take database backup

2. Transaction log backup is not required. - so it is set to Simple recovery model.

I am aware that, Simple Recovery model also increases the transaction logs same as in Full Recovery model as given on below link.

http://realsqlguy.com/origins-no-simple-mode-doesnt-disable-the-transaction-log/

Last week, this transaction log became of 1TB size and blocked everything on the database server.

How to over come with this situation?

PS :  There are huge bulk uploads to the database tables.

Current Configuration :

1. Simple Recovery model

2. Target Recovery time : 3 Sec

3. Recovery interval : 0

4. No SQL Agent job schedule to shrink database.

5. No other checkpoints created except automatic ones.

Can anyone please guide me to have correct configuration on SQL server for client's production environment?

Please let me know if any other details required from server.

Thank you,

Mittal.

Gokhan Varol

On primary Prod node suddenly we are seeing AlwaysOn Lease Timeout issue
Error: AlwaysOn: The local replica of availability group <AG> is going offline because either the lease expired or lease renewal failed.
Going to this blog http://blogs.msdn.com/…/how-it-works-sql-server-alwayson-le…
But still trying to understand why it’s happening and how to mitigate

Rahul

Hi All,
Right now am testing in AG, I have a scenario where I created AG without enabling service broker, As per experts Service broker should be enabled first before AOAG since I did not, I remove the DB from AG enabled back service broker and the add back the DB it worked fine also as a point to make when i remove the DB I did not perform any backups in primary DB.
I have 2 questions ->

1) Is this above method correct
2) Will removing and add a DB will affect the AG setup (though no backup will be performed)

Thanks

Best Regards Moug

Hello,

Log shipping (Stand by)stopped working after changing the network path location of log backup to new share location.Am getting error like An entry for primary server , primary database Open fire does not exist on this secondary. Register the primary first.

Later I re configured log shipping and it is started working.

Is there any best solution for without breaking log shipping we can achieve.

I Execute this command in primary server but no luck.
exec master.dbo.sp_change_log_shipping_secondary_primary 
@primary_server = ***,
@primary_database = DB,
@file_retention_period =14020

Cheers,

--ALways ON : sql server 2012 SP2  stand alone servers on win 2012 servers.

Version: SQL Server 2012 SP2 on windows 2012

Test Scenario:
Node1:
  TestDB
Node2:
TestDB
NOde3:
Other databases
Notes:
Always on configured from Node1 to Node3 on TestDB database.
NOde1,NOde2 and Node3 are standalone servers, not shared storage.

**Question:**
For autmoatic fail over purpose,can we use Node3 as Node majarity in Cluster Quorum configuration for configuring the always ON NOde1 to NOde2?
(We tried using Fileshare and working fine,but want to use 3rd server(node3--sql server intalled) as NOde majority)
i.e, NOde3 does it requred TestDB database or not not ?

thanks

Hi All,

I removed a node from the cluster and ran, cluster node <computername> /forcecleanup, to cleanup all the registery entries.

Now I am trying to create a new windows cluster and am getting the below error

Beginning to configure the cluster ********.
Initializing Cluster ********.
Validating cluster state on node ********.com.
Find a suitable domain controller for node ********.com.
Searching the domain for computer object '********'.
Bind to domain controller \\********com.
Check whether the computer object ******** for node ********.com exists in the domain. Domain controller \\********com.
Computer object for node ********.com exists in the domain.
Verifying computer object '********' in the domain.
Checking for account information for the computer object in the 'UserAccountControl' flag for CN=********,CN=Computers,DC=********,DC=com.
Enable computer object ******** on domain controller \\********.com.
Configuring computer object '******** in organizational unit CN=Computers,DC=********,DC=com' as cluster name object.
Get GUID of computer object with FQDN: CN=********,CN=Computers,DC=********,DC=com
Validating installation of the Network FT Driver on node ********.com.
Validating installation of the Cluster Disk Driver on node ********.com.
Configuring Cluster Service on node ********.com.
Waiting for notification that Cluster service on node ********com has started.
Forming cluster '********'.
Adding cluster common properties to ********.
Creating resource types on cluster ********.
Creating resource group 'Cluster Group'.
Creating IP Address resource 'Cluster IP Address'.
Creating Network Name resource '********'.
Searching the domain for computer object '********'.
Bind to domain controller \\********.com.
Check whether the computer object ******** for node exists in the domain. Domain controller \\********com.
Computer object for node exists in the domain.
Verifying computer object '********' in the domain.
Checking for account information for the computer object in the 'UserAccountControl' flag for CN=********,CN=Computers,DC=********,DC=com.
Set password on ********.
Configuring computer object '******** in organizational unit CN=Computers,DC=********,DC=com' as cluster name object.
Get GUID of computer object with FQDN: CN=********,CN=Computers,DC=********,DC=com
Provide permissions to protect object from accidental deletion.
Write service principal name list to the computer object CN=********,CN=Computers,DC=********,DC=com.
Set operating system and version in Active Directory Domain Services.
Set supported encryption types in Active Directory Domain Services.
Unable to successfully cleanup.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.
An error occurred while creating the cluster.
An error occurred creating cluster '********'.

Access is denied

To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.

I can manually run clear-clusternode without any issues, verified all the permissions, exists.

I am stumped. Any help appreciated. Thank You.

-Kranp.

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.

Hi everybody,

Once SQL lives its life, I get the OS Error 170 (often on the LOG file but It happened on a datafile too when I charged the system with hammerDb.

I've tried all I could to find out what is the problem here and I don't get any clue.. I hope one of you could help.

Hi All

I'm after some help please, as I think I may have discovered a bug with SQL Log Shipping to a server that is also running SQL Reporting Services.

To try and help keep things clear, I have 4 servers, ServerA, ServerB, ServerC and ServerDR. ServerA, B and C are all within the same domain, whilst ServerDR is in a data centre offsite.

I have setup to logship several databases from ServerA (11.0.3000 - 2 node SQL cluster) to ServerDR (11.0.3128), this is working as it should and the databases are in a Standby / Read Only mode. I then setup to logship to ServerB (11.0.3128), from ServerA. This initially worked, but at certain times over night the log shipping would fail and leave the databases on ServerB in a restoring state, rather than Standby / Read Only state. I deleted logshipping and re-created the job. This runs fine through the day, but as soon as the evening comes it fails again. It seems that when the transaction backup doesn't have any data changes to apply, this is when it fails.

Log shipping is setup to restore into Standby / Read Only mode and disconnect the users.

I then tested log shipping from ServerA to ServerC and this has worked without fault over night. The only difference between ServerC and ServerDR, is that ServerB is running Reporting Services.

The logs from ServerB when the log restore fails is:

2013-12-27 15:16:05.82 * Error: Could not apply log backup file 'F:\Logshipped Files\xxxxx_20131224171511.trn' to secondary database 'Logship_xxxxx'.(Microsoft.SqlServer.Management.LogShipping) 2013-12-27 15:16:05.82 Error: An error occurred while processing the log for database 'Logship_xxxxx'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. An error occurred during recovery, preventing the database 'Logship_xxxxx' (27:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support. RESTORE LOG is terminating abnormally. Processed 0 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1. Processed 1 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1.(.Net SqlClient Data Provider) 2013-12-27 15:16:05.82 Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) 2013-12-27 15:16:05.82 Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) * 2013-12-27 15:16:05.82 Skipping log backup file 'F:\Logshipped Files\xxxxx_20131224173011.trn' for secondary database 'Logship_xxxxx' because the file could not be verified. 2013-12-27 15:16:05.82 * Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) 2013-12-27 15:16:05.82 Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) 2013-12-27 15:16:05.82 Error: Could not apply log backup file 'F:\Logshipped Files\xxxxx_20131224174511.trn' to secondary database 'Logship_xxxxx'.(Microsoft.SqlServer.Management.LogShipping)This is a snippet and it repeats itself

I then have run Restore VerifyOnly from disk = 'D:\.....' to check the integrity of the log file it has copied. This returnsThe backup set on file 1 is valid.

If I manually apply this log with:

RESTORE LOG Logship_xxxxx

FROM DISK='F:\Logshipped Files\xxxxx_20131223193011.trn'

WITH STANDBY='F:\Logshipped Files\UNDO\UNDO_xxxxx_ARCHIVE.DAT'

This fails with the:

Processed 0 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1. Processed 1 pages for database 'Logship_xxxxx', file 'xxxxx_log' on file 1. Msg 9004, Level 16, State 6, Line 1 An error occurred while processing the log for database 'Logship_xxxxx'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally. Msg 3414, Level 21, State 1, Line 1 An error occurred during recovery, preventing the database 'Logship_xxxxx' (27:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

It will then allow me to move onto the next log, which will generate the same error, but then when I hit a log with some slight data change, this applies successfully and puts the database back into Standby / Read Only.

I have also checked the SQL jobs that are running on ServerB to see if there is anything that is causing an issue and nothing coincides with the timings of the restores.

Apologies if I have missed anything, but any ideas would help a lot.

Thank you.

Hello,

I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)

Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.

Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?

Thanks for your help,
Luca

Hey all. I am totally stuck here. Using SQL Server 2008 ver 10.0.6000

I have a database we are trying to run DBCC CHECKDB Repair_Rebuild on but continue to get message:

Repair (rebuild) failed: Repair statement not processed. One or more files in the database are read-only and must be made writeable in order to run repair.

I have:

1. restored from backup

2. detached/attached 

3. created a new database and pumped the data from the original database into the new one.

All with the same results. I can successfully run just the DBCC CHECKDB command w/o error.

There is nothing noted in the SQL Server logs to indicate a problem. The actual results are not even posted?!

Where do I go from here? Bear in mind I am no DBA and know just enough about SQL commands to be dangerous.... 

Thank you for any assistance you can offer..

Dave

I just changed out a server, which I use for my SQL backups and it contains both transaction and data logs and the data. The backup use to be fast but now it is very slow. I left the server name alone so I would not have to change the jobs. The backups work, however, the time it takes to do the backup has increased from 40 minutes to 2 1/2 to almost 3 hours. What I find particularly strange is if I run the backup on the SQL server and save it locally and then copy the same files over from the SQL server to the backup server it only takes 25 minutes. I am not sure what else to do so any suggestions are much appreciated.