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

Restore Log with Standby Mode on VHDX disk problem - hotfix for SQL 2014 needed

$
0
0

               

Restore Log with Standby Mode on Virtual VHDX disk cause a 9004 error in SQL Server 2014 ( test performed on Web edition and Standard version )

Similar Bug for SQL 2008R2 is already registered with number hotfixKB2987585

Restore operations always fail in Hyper-V R2 Server in situations ( text copied fromKB2987585 page )

  • The primary database has its transaction log file (.ldf) stored on a disk that has "Bytes per Physical Sector" set as 512 bytes.
  • You take the transaction log backups of this database, and then you try to restore it by using the standby option on the secondary database.
  • The secondary database transaction log file (.ldf) is located on a VHDX disk that has "Bytes per Physical Sector" set as 4,096 bytes.

In this scenario, the restore operation fails and returns the following error message:

Error: 9004, Severity: 16, State: 6.
An error occurred while processing the log for database '<databasename>'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.

After this error occurs, the secondary database goes into a suspect state.

So restore from Generation1 to Generation2 machine ( where only VHDX disk is possible ) always fails and database is not accessible.

Please create hotfix for SQL 2014 version


SQL Server AlwaysOn- Service Restart Sequence

$
0
0

Team,

Most of our SQL databases are configured on AlwaysON Availability group. I was looking at best practices in restarting a SQL service. Ex: If we change any port details/windows patching etc.

I am particularly looking at the right sequence in which we restart the services.

All our databases are configured in Synchronous Failover mode. 

Regards,

Sharath

How to find name of Primary instance in Always on cluster?

$
0
0

We have 3 node always on cluster and the queries which I have return if the current node is primary or secondary.  But I need to find out which instance is primary irrespective of where ever(Primary or Secondary) I run the query.  Can someone help me with this?

Thanks


SQL clustered instance outgoing traffic

$
0
0

Hi,

I have an interesting issue I'm trying to solve. Hopefully I'm missing something really simple. Here's a description of our environment, and the issue I'm having.

2 node SQL 2008 R2 SP2 clustered named instance. There are a total of 4 instance names on the cluster.

Node 1 IP is 192.168.1.121

Node 2 IP is 192.168.1.122

Named instance IPs are 192.168.1.123 to 192.168.1.126

Now here's my dilemma. When I connect to a linked server from one of the 4 named instances, instead of the remote server seeing the named instance IP (eg, 192.168.1.126), it's seeing the IP of the node that is hosting that instance (eg, 192.168.1.121). This is causing us an issue, as the remote SQL server is behind a firewall, and we expected it to use the instance IP and not the host IP. I have already tried to force the IP in the Server Configuration Manager for the instance name, but this has not helped.

The server logs for the instance show it listening only on the instance IP (eg. 192.168.1.126 <ipv4> 1433).

All communications to the named instances use the correct IP, and not the node IP. Any help would be greatly appreciated.

Regards,

Hugh McDaid

Listener Configuration for AlwaysOn

$
0
0

Hello,

I am following this tutorial http://msdn.microsoft.com/en-us/library/dn425027.aspx

When I get to this PowerShell script thing start to go wrong

# Define variables$ClusterNetworkName="<ClusterNetworkName>"# the cluster network name$IPResourceName="<IPResourceName>"# the IP Address resource name $CloudServiceIP="X.X.X.X"# IP address of your cloud service Import-Module FailoverClusters Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$CloudServiceIP";"ProbePort"="59999";SubnetMask="255.255.255.255";"Network"="$ClusterNetworkName";"OverrideAddressMatch"=1;"EnableDhcp"=0}

I get this error: Set-ClusterParameter : Unable to save property changes

After some testing it appears the PowerShell script cannot update the probeport, subnet mask, OverrideAddressMatch or EnableDhcp. I could however update the other values.

I then used the following PowerShell command to try and update the values separately.

$res = Get-ClusterResource "Resource Name"
$p1 = New-Object Microsoft.FailoverClusters.PowerShell.ClusterParameter $res,ProbePort,59999
$params = $p1
$params | Set-ClusterParameter

But I get the same error. Does anyone have any idea why I cannot change these values? I have managed to do it on other SQL clusters so not sure why it is not working here. I have checked the event logs and I am not getting any errors.


Brian Jones

Log shipping secondary database created in the wrong location (2008 r2)

$
0
0

Primary SQL Server 2008 r2
Secondary SQL Server 2008 r2
Secondary Database Default locations;
Data: D:\SQLData
Log: L:\SQLLogs

From the primary server I'm setting up log shipping to a secondary server (letting the wizard create secondary database), for some reason the secondary database files (MDF & LDF)  are created in D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA even though the default Data & Log location says to create them in another location.

Does anyone know why this happens? or how to tell sql to use the default data & log locations?

I know the work around is to manually create the secondary database prior to setting up the log shipping (or move the databases after the fact).  I'm worried that this step might be forgotten when a new database is added to the primary and needs to be log shipped to the secondary.  

SQL Always On Query

$
0
0

Hi All,

I have been tasked with configuring a high availability SQL installation for a client app that will connect to the database externally. 

I will have no control over the client machines to make changes to DNS/IP's etc.

The SQL connection string for the clients is an external DNS name.

I will be using AlwaysOn to achieve this.

My main query is what happens if there is a loss of connectivity to site A (internet down) and I need to fail over to site B, meaning the DNS name now needs to point to the site B IP. Changes to DNS obviously take too much time to replicate and the changes need to be immediate.

What would be the best solution to get round this?

Thanks!

Building_a_HA_and_DR_Solution_using_AlwaysON_SQL_FCIs_and_AGs

$
0
0

primary site

2 SQL server 2012

DR Site

1 SQL Server 2012 

I want FCI for primary site and AOHA for DR site

How i will configure DR site (SQL)?

Please help me step by step with snap shot


Is it ok to run AwlaysOn non shared disk with different patch levels?

$
0
0

Hi experts,

  I have a non shared disk AlwaysOn like this and I would like to update SQL server 2012 on each instance on different schedules. Is it ok?

ex:

10/5 update SQL server 2012 from SP1 CU8 to SP2 CU2 on server A

10/12 update SQL server 2012 from SP1 CU8 to SP2 CU2  on server B

Server AServer B

primary(DB1)secondary(DB1)

secondary(DB2)primary(DB2)

Question about SQL Server 2008 Disaster Recovery Plan

$
0
0
Hello, we have 2 sites in the USA. We also have 2 Dell SANs replicating to each other. Our servers are running Server 2008 r2 and we are using SQL server 2008. Current DR plan: site a Server name:USServerA Server 2008R2 Ent SQL Server 2008 D:\Logs, E:\backup, F:\DB are all stored on the SAN. Also they are being replicated to SAN at site b. site b Server name: USServerB Server 2008R2 Ent SQL Server 2008 Has a dummy database and is the using the same drive layout as USServerA D:\Logs, E:\backup, F:\DB Both servers have exactly the same updates to the O.S and SQL software. also the DB instances are also named the same (prosuctiondb1). The plan is just to replace the dummy DB and logs with the SAN replicated data when needed. Then refresh DNS. Is this possible? Or do I have to configure something in the database since this has a different host name? Thanks.

SQL SERVER - Always on

$
0
0

Hi All,

 

I have 4 physical servers, 2 are in one DC and 2 are in different DC.

 

I have to provide the DB availablity (No downtime ) using Alwayson, How do we proceed with this.

 

Please provide your Suggestion to configure the same.

 

Thanks in advance.

 

Regards,

Dhanapal

 

 

 

 

Is MSDTC is needed?

$
0
0

Hi all,

We will install two nodes of Windows server 2012 cluster and install SQL server 2012 cluster on top of them with database engine as well as analysis services installed, do we need to have MSDTC installed on the cluster as well?

Configure view state validation

$
0
0
How to Configure view state validation for scaled out sql 2012 reporting services deployment of two server ? 

Question on Quorum : Windows Server 2012 R2 + SQL 2014 AlwaysOn AG

$
0
0

OS on all nodes : Windows Server 2012 R2

SQL on all nodes : SQL Server 2014 CU2

2 cluster nodes in primary data center and AlwaysOn AG doing Sync Transfer between these nodes with auto failover.

2 cluster nodes in DR data center(Different subnet) and AlwaysON AG doing an Async Transfer between primary replica and these nodes with manual failover.

As this is a multi sub-net cluster we are giving DR nodes 0 vote. 2 nodes on primary DC has votes and a file share on the primary DC has a vote.

If the primary DC is gone,then should we re-assign node votes to the 2 nodes in DR site and again manually configure a file share witness and give it a vote?

Whats the best strategy here? Any recommendation is highly appreciated.

Thank you,

sql 2005 and sql 2008 cluster

$
0
0
Hi,

What are the major differences between SQL 2005 Cluster and SQL Server 2008 Cluster?

Thank you.

how to upgrade sql 2005 cluster to sql 2008 cluster

$
0
0

Hi,

This question is regarding how to upgrade a sql 2005 2 node cluster to sql 2008 cluster?

What is the best way or what is the procedure to upgrade sql 2005 2 nodes to sql 2008?

Thanks.

LogShipping 2008R2 Primary -> 2014 Secondary

$
0
0

Hello,

I have many servers in SQL Server 2008R2 replicated via Log Shipping to one "Replica concentrator" Instance of SQL 2008R2.

Now i've been asked to upgrade the concentrator server to SQL 2014.

Did someone has and DB replicated from 2008R2 to 2014? I have found some problems with DB versions.

(I can only restore the first TLog backup, because the database is in StandBY mode and and version upgrade is nedeed)

Thank You

Rafa

SQL 2014 Clustered with CSV

$
0
0
I just built up a test two node clustered environment with Server 2012R2. Everything seems to be functioning, however, the default file paths seem inaccessible within SQL tools. Meaning, if I try to specify the backup location to restore, I get an error that I cannot access the specified path on the server (C:\ClusterStorage\Instance\SQL\...) - then then the file structure is empty after I select OK. If I create a database new, the files get put in the default locations fine as well as when I'm on the server, I can access the files fine via the CSV path.

My thought is, the SQL cluster is not communicating properly with the CSV. In my prod 2008 R2 cluster, the disks are a dependency of the SQL service while in Windows 2012 R2, it is not (since it is using CSV).

I followed http://blogs.msdn.com/b/clustering/archive/2014/05/08/10523860.aspx - which really doesn't differ too much than older versions of Failover Clustering.

Any thoughts?

Unable to create a linked server that points to an availability group listener.

$
0
0

I don't even know if this scenarios is supported or not, I can't find any documentation on it.

I have a couple SQL 2012 servers setup using AlwaysOn Availability Groups.  The listener (SQLAG1) is setup and working as expected with applications.   The 2 machines are in different subnets, so we are using the MultiSubnetFailover=True on the connection strings to ensure that failover works. 

From an SQL 2014 box I want to create a linked server that points at the Listener.   I'm able create the linked server, but it appears like sql server is not using the MultiSubnetFailover=True and it fails to connect.  Here is what I used to create the linked server;

EXEC sp_addlinkedserver 
@server = N'SQLAG1', 
@srvproduct = N'SQL2012', 
@provider = N'SQLNCLI11', 
@datasrc = N'SQLAG1', 
@provstr = N'Provider=SQLNCLI11.1;Data Source=SQLAG1;MultiSubNetFailover=True', 
@catalog = NULL
GO

Do anyone know if this is supported?  if so what it proper way to create the linked server?  

Thanks!!!

SQL 2012 HADR failover instance

$
0
0

Greetings all.

Currently here is the setup we have built out.  All are Server 2012 R2 OS

2 node FCI shared storage SQL 2012 servers in production site.  Failover works flawlessly between them. WSFC setup between them

1 node in DR, member of the WSFC with the 2 servers above but not FCI, seperate storage infrastructure but same disk drive letter setups

Availability Groups setup between the 2 that are fully synchronized

We are going to have a planned primary outage in the primary DC.  Nerves are getting the better of me in regard to the setup.  I know the data is there and it can be accessed.  My question is that once i perform the failure of the two nodes in the FCI how are my applications going to know how to reach the HADR server as it is on a seperate instance?  Does SQL aliasing need to be setup in the configuration to make it work properly or am i being overly paranoid at this point?

Viewing all 4532 articles
Browse latest View live


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