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

Cross Domain Log Shipping

May 12, 2015, 11:12 pm
$
0
0

I have a question on a scenario and would appreciate your inputs. 

Lets say I have a single instance SQL Server on a 2 node cluster with node namesServer X and Server Y. These are part of Domain A.

SQL Agent Account runs under service account - DomainA\SQLAct.

Now I have Server Z which is a standalone SQL Instance on Domain B and there is no trust between domain A and B, not even one way trust.

Even though I dont have trust, I need to configure log shipping for the SQL Instance which is clustered under Domain A to a standalone box in Domain B.

Microsoft recommends Local Account(SQL Agent) to be used for Cross Domain Log Shipping. Also when there is no trust, MSFT recommends to use the same login name and password, however as my setup includes a cluster and cluster cannot have local account I'm not sure what will be the best strategy to follow here.

Any suggestion is greatly appreciated.

Thank you,

Anup

↧
Search

TempDB Full

May 13, 2015, 11:30 am
$
0
0

Hi

Today Morning @ 11.40 AM. Got error like ,

Message
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Message
Error: 9002, Severity: 17, State: 4.

Then immediately we expanded the space issue got resolved. It is Prod server.

Now i want to check  @2.30 PM why tempdb got full.

How to check because after 12.10 PM not alerts. Currently server is working fine. But i want to submit RooT Cause Analysis to management.

↧
↧

CIFS share as file share witness

May 14, 2015, 3:09 pm
$
0
0

 We're trying to use a CIFs share as a file share witness nad getting an error message:

 "the account used is a computer account use your global user or local user account"

Are CIFs supported asa  file share witness? Any ideas as to how to fix this?

thanks

↧

AlwaysOn Routing Problem When Connecting with ReadOnly Parameter

May 14, 2015, 5:40 pm
$
0
0

Hi All,

I've AlwaysOn structure with 2 nodes of SQL 2012 on virtual machines that are in same LAN and different hosts. Another vm is working as witness and file share machine. Each server is able to ping each other, all the firewall settings are in off state.

Primary node ip = 10.0.0.223 "Tcp://cls1.domain.ed:5022"

Secondary node ip = 10.0.0.224 "Tcp://cls2.domain.ed:5022"

Listener ip = 10.0.0.230

Cluster ip = 10.0.0.226

Endpoint = Hadr_endpoint

Everthing works well except readonly routing with listener. When i try to connect from SSMS with listener and open a query pane on each server, "select @@servername" returns 10.0.0.223 which is primary. But when i try to connect listener with ApplicationIntent=READONLY parameter and then open query, it's waiting for a while to connect and then returns error message "A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (.Net SqlClient Data Provider)(Microsoft SQL Server, Error:10054)" on SSMS. When I look at error logs, i see that the corresponding message is "Error: 9642, Severity: 16, State: 3." and "An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')".

Is there anybody to guide me accurately?

Best Regards

↧

Problem in failover with concurrent access with TABLOCK query

May 15, 2015, 6:24 am
$
0
0
We have a solution to the AlwaysOn feature. The problem is that if it gets failover and during this failover there is concurrent accesses a database of the group. These Views using the TABLOCK. From that moment, after failover this table that had concurrent access in failover with tablock crashes the TABLOCK. Doing that after this table as failover to be accessed concurrently by all connections acessom key simultaneously even with the tablock command.
↧
↧

SQL Server 2014 AlwaysOn Availability Group requirements

May 16, 2015, 1:56 am
$
0
0
We are currently using a SQL Server 2008 Failover Cluster, running on a Win2008 WSFC with 2 nodes, with a shared SAN drive.

Now we are evaluating the possibility of switching to use an AlwaysOn Availability Group with 2 nodes.
1 primary replica for read-write, and 1 secondary replica for read-only.
SQL Server 2014 running on Win2012R2 WSFC should be used.
We would like to know the hardware and network requirements for such setup.

I read some info about this:
https://msdn.microsoft.com/en-us/ff929171.aspx
https://msdn.microsoft.com/en-us/library/cc645993.aspx
https://msdn.microsoft.com/en-us/library/ff878487.aspx

And below are my understanding. Can anyone correct me if I am wrong, and enlighten me on the points that I still don't know?

If there are any other requirements or constraints,  I would also like to know.

SQL Server 2014 Edition?
Enterprise Edition only.

Witness server? Or any 3rd server other than the 2 nodes?

Not required.

Shared storage (SAN, network drive, any kind of shared storage)?

Not required.

Quorum drive? (In our existing Win2008 WSFC, the shared SAN drive contains a volume specifically for quorum. Is this still required in Win2012R2 WSFC?)

??

Dedicated network card for heartbeat?

Recommended

Dedicated private network for heartbeat?
??

LAN network speed between the nodes? (1Gb? 10Gb?)
??
↧

Do not see SSAS cube on Secondary Replica

May 18, 2015, 10:57 am
$
0
0

Hello

I have set up Always on availability functionality in SQL 2012. It is working as expected for Database engine.

But recently, I created SSAS cube and deployed on SQL server. In SSAS cube, Datasource connection was for Listener.

I can view SSAS cube on SQL1(Primary replica) and Listener, but when I login to SQL2(Secondary Replica) , I don't see SSAS cube in management studio.

Do I need to do anything additional to view SSAS cube on SQL2(Secondary replica)?

Thanks

↧

Recommended practices when using a Shared/FTP Drive on the servers containing the Primary and Secondary Availibility Groups?

May 5, 2015, 11:10 am
$
0
0

Hello, we are currently using 2, 2014 SQL Server Enterprise Servers that contain our AlwaysOn High Availability groups. 

Server One is the primary replica ,

Server 2 is the secondary replica, not being used for read-only. 

In the event of a failover, what is the best recommended practices to automate the secondary server's connection to a Shared/FTP drive that is used daily by the Primary Server?

I apologize in advance if this is the wrong forum for this question.  I realize it is Windows Explorer related as well, however, I was assuming some of the users of AlwaysOn High Availability Groups may already have a solution in place that works. 

Thanks.

↧
Search

SQL Alert

May 18, 2015, 7:01 am
$
0
0

 alert fires, but the responsible operator does not receive notification.

We area using this alert from past few months. But last week got an TempDB full and we found the error in SQL server 2012 error log. But we didn't get notification to email.

But the email id is working fine because we are using same email id for all other alerts.

Please help me.

Date of last Alert:Wednesday, May 13, 2015 12:00:45 PM

Date of last Response:Wednesday, May 13, 2015 12:00:45 PM

But we didn't get email.




↧
↧

Failed to change listening port of SQL Server 2014 Failover Cluster

May 17, 2015, 10:54 pm
$
0
0

Want to check anyone had successfully changed the listening port of SQL Server 2014 Failover Cluster?

I used following steps but kept failing to startup SQL Server cluster again:

1. Use Get-ClusterResource -Name "SQLCLSTNM" | Remove-ClusterCheckpoint -CryptoCheckpoint

2. Change port number through SQL Server Configuration Manager on each node

3. Use Get-ClusterResource -Name "SQLCLSTNM" | Add-ClusterCheckpoint -CryptoCheckpointName "Microsoft Enhanced Cryptographic Provider v1.0" -CryptoCheckpointType 1 -CryptoCheckpointKey "......"

I even tried to stop the SQL Server cluster role before I tried step 1. The SQL Server cluster always stopped after several minutes waiting for SQL Server service come online. During the startup, I have checked SQL Server service status. It was actually already started. After several minutes, SQL Server failover cluster role will fail. And the SQL Server service was also terminated without any message in the ERROR log, not even any informational message.

The cluster runs perfectly fine once I revert it back to use 1433 port.

This is a three nodes cluster, SQL Server 2014 SP1 running on Windows Server 2012 R2, cross two different subnets.

↧

Disaster recovery option for a Principal+Replica nodes

May 20, 2015, 4:21 am
$
0
0

Good day.

My problem is really quite simple, I hope to explain it in a easy way :)

We have 2 SQL servers (STD 2012) at the moment in production, one is principal, and one is a "replica" server, using replication of Logs, that our apps use only for reading.

We want to have the possibility of a Disaster recovery option, so here's my question...

What will be the easiest and cheapest way to have one server in other region CPD in High Availability? We discard raising to Enterprise (too much money).

thanks

↧

SQL2012 AG Network

May 20, 2015, 4:12 pm
$
0
0

I have setup two node SQL 2012 Always ON cluster with file share witness. I have configured two networks, one for heartbeat and second for public.

My question is do I need a third network/ subnet for AG Listener?

Which network does the SQL user databases in the AG group use to replicate between the replica servers?

When I do the SQL backups, do I need to backup primary and secondary replicas or just backup the databases in the secondary replica?

Please advise.

↧

Change password for CLIUSR account.

May 20, 2015, 1:23 pm
$
0
0

Hello,

I am running Windows Server 2012 R2 with MS SQL Server 2012. This system has account and password tracking requirements for all local accounts. Regarding the account created upon instancing a multi-node cluster, CLIUSR, how would I safely change the password for that account, to ensure that it never exceeds a required maximum age threshold (180 days)?

Thank you

↧
↧

!!!Urgent !!!!!Cannot recovery database without log files (SQL 2008)

December 30, 2008, 8:56 pm
$
0
0
I only have single mdf file, the transaction log file was corrupted. When I was trying to attatch the mdf file, I received the following error message. Can someone give me a help..... it's really urgent!


TITLE: Microsoft SQL Server Management Studio
------------------------------

Attach database failed for Server 'DEV8\sqlexpress2008'.  (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.1600.22+((SQL_PreRelease).080709-1414+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Could not open new database 'Smartadmin'. CREATE DATABASE is aborted.
File activation failure. The physical file name "C:\MSSQL\Smartadmin_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. (Microsoft SQL Server, Error: 1813)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.1600&EvtSrc=MSSQLServer&EvtID=1813&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------



Javafun
↧

How can i know how many bandwith I need for a "Log shipping" or "Database Mirroring" Configuration

May 22, 2015, 5:57 am
$
0
0

Good day to all.

In this question we go two excelent options, and for sure we will implement one or another, but thinking about them, we come with the question above.

We asked our 'backup' guys about the 'Log' they copy every hour, but the data shows a big amount of data in the morning (after many jobs) and in the evenig (after the work) this is the table:

Start Time       MB/h
8:00:0460117
9:00:0316,31
10:00:0715,5
11:00:1015,63
12:00:0916,31
13:00:1215,75
14:00:0518,94
15:00:0419,5
16:00:0615,81
17:00:1015,5
18:00:0915,5
19:00:1315,81
20:00:0215,88
21:00:0611931,56
21:45:1258020,94
22:00:13115,19
23:00:1114,88

That table shows some moments with a peak of 60 GB... I think that can be "exactly" real, maybe some "diff" backup or something.

So the question, as I see it is: How can we know the log data growing in a hourly or similar frecuency so we can know if we need more or less bandith in our alternative CDP?

Simple selects that only show the size of registry database didnt work, because they can be transactions already calculated... thanks.

Sorry for my english, If anyone needs more clarification I'll try to improve it.

↧
Search

Error adding Replica to SQL AlwaysOn failover cluster

May 22, 2015, 9:11 am
$
0
0

Hi All -

I'm getting an error adding Replica to SQL AlwaysOn failover cluster in the new availability group wizard.  When I enter the name of the target node (secondary replica) server and press connect, I get the following:   

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

The system cannot fine the file specified

The SQL Browser service is up and running on the target.  I am using an Azure VM for my SQL instance.  This cluster spans geographies from our on-premise site to Azure via a VPN.  This is a multi-subnet cluster. I'm attempting to create a new AG from the primary replica node and the target is a node on Azure called SSASNodeAz03. 

I'm reviewing all the setup docs again, but I'm hoping you have some recommendations.

Many Thanks,

JBP

Screen shots:

http://1drv.ms/1FDrHVb

Full error:

Connect to Server

Cannot connect to ssasnodeaz03

Additional information:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

The system cannot fine the file specified

↧

SQL 2012 Active\Passive cluster with AlwaysOn to DRS

May 22, 2015, 5:39 am
$
0
0

Dear All,

I have Windows 2012 R2 running on three nodes, two at the primary site and one on the Disaster Recovery Site. On the primary site I have an Active\Passive SQL cluster, and on top of it I have AlwaysOn Availability Group enabled to ensure a replica for my DRS site.

The Active\Passive cluster works fine and the replica with AlwaysON as well, however when I try to move ALL Cluster resources at my primary site from one node to the other using Windows Fail-over Cluster console, the SQL and MSDC resource are moved successfully however the Availability group resource fails to move.

I understand that AlwaysOn are managed from SQL Management Console, however in Active \Passive cluster how do i move the AG resource?

The error shows the following:

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

↧
↧

Setting up shared SAN disks in aiming to cluster SQL 2008?

May 22, 2015, 2:26 pm
$
0
0

Hello, currently have 2 nodes (both Windows 2008 r2) in aiming to set up Active-Passive cluster.  These are currently 2 separate identical VMs not clustered (Failover Clustering feature have not been enabled).  Currently I notice Node1 has all of our shared SAN disks configured as Online & labeled but Node2 currently have all of them in Offline.  Does Node2 need to have all of these put into Online & labeled as well first & then enable/configure these 2 nodes to be clustered or cluster these nodes first or something different?  (After successfully clustered will install & cluster SQL Server 2008 on these nodes.)

Thanks in advanced.

↧

SQL Server 2012 AlwaysOn Secondary Operational State Unknown

September 30, 2013, 3:22 pm
$
0
0

I recently configured SQL Server 2012 AlwaysOn Availability group using two nodes - a primary and one secondary read only replica.  The group is residing on a windows 2012 cluster with an smb file share as the quorum.  I am able to successfully failover through SQL and through the windows 2012 cluster.  When I look at the group dashboard on the primary server and view the Operational state of each node I notice an odd value.  The secondary role server is listed as Unknown.  I also noticed that the Availability replicas node icons in object explorer are displaying the same icon on the primary server but on the secondary server, the primary server is shown as a server with a question mark.  Am I missing a permissions setting or is this normal behavior.

For example:

ServerA is the primary

ServerB is the secondary

ServerA  lists the servers in Object Explorer as:

  • ServerA (Primary)
  • ServerB (Secondary)

ServerB  lists the servers in Object Explorer as:

  • ServerA 
  • ServerB (Secondary)

The primary is never listed a primary on the secondary server.  Again failovers are working properly, but I want to be sure I am not missing a setting somewhere. Any help is greatly appreciated.

↧

AvailabilityReplica.Role property is always "Unknown"?

August 6, 2012, 3:54 pm
$
0
0

Whenever I query AvailabilityReplica.Role property it is always “Unknown” for all the replica servers participating in the AAG except for the one that I’m making the call on.
I do not see this problem when I make the call on primary replica server.

Any idea why it behaves like this and how to get the right information? I do not want to make call to each replica server to get the details.

See the output below.

----------------
AAG details:
----------------
AAG name: Lakers_Fluke
AAG Parent: [fluke]
AAG Primary Replica Server Name: LAKERS
AAG State: Existing
AAG Local Replica Role: Secondary
----------------
REPLICA SERVERS FOLLOWS:
----------------

Replica Server 1.

AAG replica name: FLUKE
AAG Parent: [Lakers_Fluke]
AAG State: Existing
AAG replica mode: AsynchronousCommit
AAG SConnection tate: Connected
AAG Operational State: Online
AAG Role: Secondary

Replica Server 2.

AAG replica name: LAKERS
AAG Parent: [Lakers_Fluke]
AAG State: Existing
AAG replica mode: AsynchronousCommit
AAG SConnection tate: Unknown
AAG Operational State: Unknown
AAG Role: Unknown

Replica Server 3.

AAG replica name: WARRIORS
AAG Parent: [Lakers_Fluke]
AAG State: Existing
AAG replica mode: AsynchronousCommit
AAG SConnection tate: Unknown
AAG Operational State: Unknown
AAG Role: Unknown
----------------
↧
Viewing all 4689 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>