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

Question about adding drives to a SQL cluster as a dependency

August 31, 2016, 4:39 pm
$
0
0

Recently we added new drives to our 2008 R2 64 bit SQL cluster to replace old ones.  The process went well and we were able to bring everything back online fairly quickly using the new drives.  However, one thing  that we noticed that when we try and do a manual backup using use the SQL Server Management Studio (SSMS), when it came time to select a backup destination, which in this case, would be one of the newly added drives, we get the following error:

Locate Database Files - [SQLSERVERNAME]

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

V:\BACKUPS

Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists. 

If you know that the service account can access a specific file, type in the full path for the file in the File Name control in the Locate dialog box.

We did some Googling and came across this article that states that when you add drives to a SQL cluster you need to add them as a dependency  which is something we did not do:

               http://www.sqlcoffee.com/troubleshooting069.htm

This article describes a 2005 SQL Cluster, but we suspect that this is the cause of our issue as well. Also, please note that the SQL instance service account has full effective rights to the drives in question. 

So my question is, should the new drives have been added to the cluster as a dependency or not?  Could this be an explanation to the error we are seeing?



↧
Search

AlwaysOn and Witness

September 1, 2016, 8:20 am
$
0
0

We currently have a three-node cluster used by AlwaysOn.

We plan on decreasing from three-nodes to two-nodes.

Should a disk witness be configured for the cluster in case of one of the nodes is down?

We are using Windows Server 2012 R2 and SQL Server 2014.

Thanks

↧
↧

Adding new drives

September 1, 2016, 12:21 pm
$
0
0

Hello,

I am using SQL 2012 SE using a 2 node cluster and are in the process of upgrading to a new SAN from existing ones. I have the backed up the databases and scripted out logins and agent jobs and saved them.

New SAN has Luns carved out and I am able to add the storage to the cluster with non existing drive letters on the server. The cluster is able to identify the disks however from the SQL Server instance I am not able to see the drives. Is there a feature or something that I am missing here?

Thanks

Edit: On the disk folder in the failover cluster manager on right side I clicked on Add disk and added all disks. I also added went to roles right click mssqlserver click on add storage and selected all drives and click ok. I didnt mention this earlier so I am adding it now.


↧

AlwyasOn Automatic Failover

September 2, 2016, 7:24 am
$
0
0

Does sql server 2016 support more than 2 automatic failvoer targets in alwayson?

I knew that SQL 2012/2014 maximum support 2.

↧

SCHEDULING DIFFERENT BACKUPS

September 2, 2016, 12:21 am
$
0
0

Hi,

I would like to plan a disaster recovery method, apart from scheduling full both full\differential backups will taking T-LOG backups help me with this?

This is the schedule that I would like to have:

Full DB backup at 8AM

T-LOG backup every 2 hrs (till 8PM)

Differential backup at 8PM

T-LOG backup every 2 hrs(till 8AM)

Is is possible to schedule all this with the T-LOG itself or do I have to schedule each backup separately? Also may I have the steps to configuring each backup method as I am new and haven't got much idea about it, any help will be much appreciated.


↧
↧

SQL Server 2012 slow Cluster

September 3, 2016, 7:02 am
$
0
0

Hello,

I am using SQL Server 2012 SE and we just upgraded the SAN from SAS to SSD. The migration was smooth but we are noticing

failover time has increased drastically (from less than 30 seconds with SAS to 15 minutes SSD). When failover is performed disks are available immediately to the previously passive node which want to become active and also the cluster comes up instantly but it takes very long time for the sql server service and sqlserver agent service to start. There are in total 10 databases and the biggest log file is close to 3GB. The VLF count per database is as show:

dbnamevlfcount
DB1179
distribution4
master3
model26
msdb55
DB2275
DB3307
DB459
DB547
DB629
DB7319
DB832
DB9331
DB1032
tempdb67
 

The biggest database size is 5GB. Considering they are not that bad. I performed failover multiple times and whats interesting is the quickest time was 5mins and the slowest was 16 mins for a failover and it never timed out. This is confusing and I was not able find anything in the cluster log or windows eventvwr or cluster eventvwr or sqlserver error log.

How do I know why is it taking so long? Experts need your valuable inputs.


↧

Database is Not Synchronizing/Suspect on the secondary server

September 3, 2016, 6:39 pm
$
0
0


I am running scripts to partition two tables.  The database is a part of a high availability group.  Normally I would remove the database from the high availability group, change the recovery mode to simple, and run the scripts.  However, the individual that I report to wants me to run the scripts with the database still in the high availability group.  I think because they don't want to take the databasse down in production.

I am currently running a test in development and the scripts ran find but I discovered that the database is Not Synchronizing/Suspect on the secondary server.

I tried to resume data movement but it fails.  I get an error message "A timeout occurred while waiting for the operation to complete.  Object Explorer could not be updated.  Try refreshing Object Explorer manually.".  I right clicked on the database and clicked on refresh.  I also tried to run the following:  ALTER DATABASE [ldm_carepoints] SET HADR RESUME;  I also restarted the services.

Is there anything that I can do to fix this without removing the database from the high availability group and readding it?  Or is that the only solution?

Also, is it better to run the scripts when the database is not a part of the high availability group and is in simple mode or is it ok to run the scripts when the database is a part of the high availability group and is in full mode.  I want to give the individual a good reason why it is best to take the database off of the availability group and place the database in simple mode.

lcerni

↧

Cluster IP address resource ‘Cluster IP Address’ cannot be brought online because the cluster network ‘Cluster Network 1’ is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the c

September 4, 2016, 10:32 pm
$
0
0

HI All,

We are getting the below issue when fail over from one node to another node . what may cause.

Cluster IP address resource ‘Cluster IP Address’ cannot be brought online because the cluster network ‘Cluster Network 1’ is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.

↧
Search

SQL SERVER CLUSTER INSTANCE ISSUE

September 4, 2016, 10:29 pm
$
0
0
WE ARE ABLE TO CONNECT SQL SERVER cluster INSTANCE LOCALLY BUT NOT REMOTELY WHAT IS ISSUE .Could you please help.
↧
↧

Listener port for AG for DR

September 5, 2016, 11:37 am
$
0
0

Hi Team,

I have WSFC cluster in main site and DR . We have SQL Cluster in Main site and individual/standalone SQL in DR (windows node is part of WSFC). SQL Servers multiple instances to support different workloads.

I have few queries related to SQL AG and looking for some inputs.

1. Since i have multiple SQL instances, we are planning to have static port for each instance. Can we use the same SQL instance port for listener as well? suppose instance A is using 1440 , instance B is using 1441 , can i use Listener port for AG as 1440 and 1441? will there be any conflict? or else what should be the recommended approach choosing static port for AG listener and what need to keep in view from registering it with DNS or when Workload need to connect to DR?

Using 1433 need to be avoided since its a default port.

2. Once AG is configured between Primary and DR, How to redirect any application server (if particular instance is down for some workload in primary) or workload to DR SQL DB replicated as part of AG assuming other workloads are running and using the primary SQL only. What should be the process followed? and once instance is back in primary how to replicate the DB bck to primary and redirect the workload also to use primary DB now?

Any pointers will be highly appreciated.

Regards.

↧

How to prevent automatic failover with active-active nodes when cluster heartbeat lost communication

September 5, 2016, 9:30 pm
$
0
0

Hi All,

We have 2 nodes windows 2008 cluster, both nodes are active, 3 SQL 2005 instances were running on Node1 and 2 SQL 2005 instances were running on Node2, and both nodes can do failover automatically. Our network team will do some maintenances next week, so the heartbeat between 2 nodes will be lost about 1 min. We just want all SQL instances to be run on their original nodes during the maintenance. My question is, how can we prevent sql failover when the nodes lose communication. We do not want them to failover automatically. I did checked cluster configuration, Under each cluster SQL service, it has server name,disk drivers and other resources (SQL server instance and SQL server agent). I can right click each of them, choose property->advanced policies, then I can see possible owners (both nodes were ticked). If I choose SQL service 1 which is running on node1. Can I clear the check box for a Node (for example Node2), so this resource won't failover to the node (node 2). But I have to change all items under the cluster sql service (server name,disk drivers and other resources (SQL server instance and SQL server agent)).

Does anybody have any other recommendation?

Thanks

David

↧

Mount points vs CSV disks in SQL clusters

August 18, 2016, 2:15 pm
$
0
0

Hello

I am trying to overcome the 26 character limitation when trying to place multiple SQL Instances in a Windows cluster.

I know mount points is the solution for this, and have few questions:

Will mount points work in clustered environment?

Is CSV just a another name for mount points in a clustered environment? Or is that different from mount points?

↧

SQL Server 2008 R2 Cluster/Integration Services

September 6, 2016, 11:44 am
$
0
0
Hi. I have a 2-node SQL 2008 R2 cluster on W2K12 R2 -- CLNODEA and CLNODEB.  It's been a while since I set up Integration Services -- as I recall, I simply installed SSIS on both nodes.  My question is, if the server that currently owns the cluster is CLNODEA, and I import SSIS packages from a stand-alone SQL Server SERVERX to CLNODEA, is the imported SSIS package now available on CLNODEB in case of failover?  Or do I need to import packages separately to both CLNODE A and B?  Thanks.
↧
↧

AOAG across subnets

September 6, 2016, 4:39 pm
$
0
0

So, I understand the concepts of the AOAG, and I have it configured as

DC1: Primary / Replica 1 Sync automatic Failover

DC2: Replica 2 - Async Manual Failover 

DC3: File share witness.

I added both IPs for the 2 subnets to the Listener. So here are the issues I am having

1. Logged in using the service account which is SysAdmin on all instances, I try to force failover from Primary to Replica 1 and I receive the error Availability group DDL operations are permitted only when you are using the master database (error 35208). I checked around and it says to make sure master is the default database for the login which it is on all instances. If I login with 'sa' and fail it over it works fine. 

2. If I failover to DC2/Replica 2 it works, but I noticed the other nodes become paused and I have to manually start the old primary, but when I start the secondary I again get the (35208 error)

In the old mirroring setups if you failover it immediately goes to synchronizing with no issues.

All systems appear to be able to see each other from Windows, but under the replicas folder on either secondary it doesn't show the status of the other secondary. Is that normal?

John M. Couch

↧

Availability Groups - Migrating Secondary to a new server without taking another full backup/restore

September 6, 2016, 5:35 am
$
0
0

Hello,

I have to migrate my DR server to a bigger box so I already installed the server on the remote datacenter and now I have to add it into the AG. this server will replace the old secondary.

Is there any way to move the secondary without having to take a new full backup and copying the BAK files from the primary ? Is there any way to accomplish this task moving the files from the existing secondary? 

I am asking because moving the BAK files from the WAN connection will take me several days due to the BAK files sizes and the network bandwidth

Thanks

Regards,

Javier Villegas

DBA // MCTS // MCP

Blog:http://sql-javier-villegas.blogspot.com.ar/ Twitter:https://twitter.com/javier_vill  / LinkedIn:https://www.linkedin.com/in/javiervillegas/ 

Note: Posts are provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

↧
Search

Differential Backup fails in SQL Server Failover Cluster Enviornment

September 7, 2016, 3:28 am
$
0
0

Hello,

I have setup Failover cluster on SQL Server 2014 which working fine. Then I implement backup strategy. It is also working fine.

But after failover only last differential backup (which is occurred at 12 AM) started failing. From below query I find out that DB snapshot is occurred on 8:30 PM everyday on this node.

select backup_finish_date,is_snapshot,database_name from msdb.dbo.backupset where is_snapshot = 1

We don't implement any snapshot for database.

After failback it is working fine again.Then again I execute above query; And I am surprised now DB snapshot is not happening.

Can you please explain why the differential backup is failed from only one node and not from second? If snapshot is happening how can I get all information regarding snapshot? (e.g. where is it store? from where is it taken? why snapshot happening from only one node if I have implemented failover clustering? ) 

Full DB Backup: everyday 2AM

Differential Backup:  Every 8 hour between 8:00 AM and 7:59:59 AM

↧

Mirroring problem with Principal @ 2014 and Mirror @ 2016

September 7, 2016, 8:38 am
$
0
0

If I haven't changed the code...not 100% sure ... this process used to work, but it is not working now.

Perhaps a SQL Server SP update code might have changed the restore process.

Here is the summary:

Totally from script .... I was doing mirroring from 2014 Server to 2016.

Create Mirroring Endpoint, assign it a port number on Principal Server, etc.

Then take a Full DB Backup and the Logs backup on the 2014 Principal Server 

Copy the Bak files to the destination Mirror server and restore the DB on the Mirror server

After that Grant Connect to Endpoints, and then set partner properties, etc.

The new problem is that the during the restore process on the 2016 Mirror gets stuck on Restoring status and not switching to Recovering as it used to do.

When I tried the restore from the code just one isolated Restore command on the 2016 Mirror .... it started to "upgrade" the restored database to 2016 version.

Is there a way, at least restoring the 2014 DB into a 2016 DB with the older Compatibility Level 2014 without upgrading on the fly.

Thank you....

 

↧
↧

Restore log with norecovery always reporting "processed 0 pages"

September 7, 2016, 9:25 am
$
0
0

Hi,

I'm restoring a database on a SQL Server 2008 R2 Enterprise Edition using a full backup and several log backups. There are a total of 46 files in the database: the primary data file, 44 secondary data files, and 1 log file.

When the restore of the full backup was performed, all files were moved and renamed. I've restored some of the log backups, adding the norecovery option and all the 'move ... to ...' clauses, and the restore completes successfully. However, the progress information always reports "processed 0 pages of" for all the data files (the log file reports a different number of pages on each restore as expected). I can't bring it online because tomorrow I'll be receiving the last log backups I need to restore before making the database available to the users.

Is this the expected result when you use the norecovery option? If I had messed up the file "mapping" I guess there would have been an error, but it ended successfully.

Thank you

↧

SQL Server 2014 on a New Failover Cluster

September 8, 2016, 6:06 am
$
0
0

Hi All,

We have to perform sql 2014 installation on two node cluster environment. After installation we have to configure SQL Alwayson.

My question is:

During installation (in below wizard), we have to mention unique IP address. Can we use same IP address that we are using for AlwaysOn AG listener configuration? OR Do we need separate IP's for AG listener and below cluster NW configuration?

Our DBA shared below required IP information with us. 

2 IP's for 2 DB servers

1 IP for Windows Cluster

1 IP for AG listener


↧

2way data flow solution

September 8, 2016, 6:54 am
$
0
0

I need both read/write operation from primary and secondary server.

apart from transaction replication with updatable subscription, do we have any other option available. is there any solution which can be created here...

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