Hi
I know there was a previous thread on setting up DB Mirroring and Clustering where DB Mirroring would failover first because its faster than clustering. But is there a way to set up servers to allow clustering to failover first and then use DB Mirroring failover if the cluster node fails.
thanks
P
Guys, I really need a help . I have one database (1TB) on two servers in different location( About 1200 miles distance). SO which options will be good:
Clustering or Database Mirroring
I am totally confused . As i read from SQl-server- performance , Clustering doesn't protect data. It is server level.
Can any expert throw a light on me?
clustering sounds expensive and arcane. Is it ever a better choice than mirroring for high availability? Perhaps when the size of the db copy is too prohibitive under the mirroring option?
View 1 Replies View Related I am developing an enterprise class solution using SQL Server 2005 and MS .NET v2 and am tying determine if SQL Server 2005 (which edition and if so how) would be adequate for my proposed solution. Any feedback, tips, comments would be greatly appreciated.
As a background the solution I am developing will be web services based and used by multiple offices around the globe by over 500 users. I have already developed a prototype using a single SQL Server 2005 instance but as this solution is going to be used by offices around the world I want to have an IIS Server and SQL Server 2005 server instance in each office with "links" back to the primary SQL Server 2005 cluster in Australia.
One of my thoughts was to set up replication between the offices that would happen at midnight remote office local time and then set up triggers to update the primary cluster when assoociated data was changed on the remote sites or on the primary cluster. Does anyone know or can anyone suggest alternatives to this strategy?
I effectively need some sort of inter site caching functionality with store and foreward capabilities ...
Thanks
Andrew
Up to now we have gotten by without having any local DR copies of servers (if a sql server goes down we are usually able to get it back in less than 3 hours). But I want more now. I want to trim the "down" window to no more than 5 or 10 minutes. (Immedate failover would be nice but is not an essential requirement. The essential requirement is to loose no data!)
I have a spec of knowledge in these areas:
SQL 2005 Clustering (requires approved hardware, quorum disk, etc. involved)
SQL 2005 Replicaiton
SQL 2005 Log Shipping.
SQL 2005 Database mirroring. ( needs three servers)
Which approach do you think is the most straightforward, sparing of hardware, yet reliable way to get us back up and running after a sql server failure.
TIA,
barkingdog
Hello.
I am confuse and cant decide on how to setup high availability on our SQL 2005. Here's what on my mind and on resources list:
I plan to have mirroring on my SQL1 to SQL2 with the help of SQL3 as witness. So this would be automatic failover. My idea on mirroring is when SQL1 goes down, SQL3 would tell SQL2 to run and be the primary. It will automatically failover to SQL2. Right? My questions are:
1) How can I revert back to SQL1 once it is ready?
2) I read in one of the post that it is impossible to write in a mirrored DB, is this true? I mean, what's the use of failing over to the next node when it's not possible to write and update data/records?
3) If number 2 is false (i hope so), how would the data be synchronize from SQL2 back to SQL1. Those transaction that were made while SQL1 is down.
4) How about the connection string from the web applications? Would it be automatically point to SQL2? We have load balancing setup in place, would this help web application connection to automatically point to SQL2?
Another setup:
We have SAN in place (not yet used, but is planning to use for this SQL thing), EMC to be specific. My question would be:
1) For SAN setup, the data storage would be centralize. So would that mean that SQL1 and SQL2 services will use the same data and log file from the SAN storage?
2) How would you call this setup then? Can this be clustering type of high availability? Will clustering work under load balancing setup? I believe mirroring is not possible here? Right?
3) How can I setup my 3 SQL servers with the same theory in mind: when SQL1 goes down, SQL2 will take over. Data will be synchronize when SQL1 is up and running again. With automatic failover and reverting back to primary.
I read so much topics about this, but the more I research, the more I get confuse.
Any suggestions, comments, advice is greatly appreciated!
We have 2 env. : Testing and Production, both are running Windows 2003 Enterprise Server with SQL Server 2005. The difference is Testing is NOT running Windows cluster but Production do so, what is the best way to transfer a database from testing to production?
We have another systems that both testing and production are running on NON-cluster and we use backup/restore to transfer the database, can it apply in this case.
And I found that there are a tools called DTC, which can transfer all DB objects from one DB to another, is it a best way to transfer between non-cluster and cluster env.?
Server A = primary SQL DBs (mirroring origination)
Server B = failover SQL DBs (mirroring destination)
For database mirroring a witness is required.
Can the witness live in another instance of SQL on server B?
Using SQL Server 2008, we would like propose mirroring between two servers of a critical database. Since we initiate, may require to clarify on its purpose and also required changes from application end.Any changes required from OS Level? (I believe both servers IP or Host name should be added in host entries. Mirroring ports should be allowed/open including Principal and mirror server IP Addresses): Windows Team.Any changes required from Application? (Instance name, authentication: user name and its password should be added in web config files): Application Team.Any changes required from Network Team?Also for mirroring both the principal and mirror servers should be with same version, does it only mean SQL Server 2008 versions are enough or does it also mean to say build numbers 10.00.4000 should also be same.URL....
View 5 Replies View RelatedI need to set up asyncronous data replication across two clustered instances of SQL 2012 across 2 Datacenters. Both the datacenters have a common domain however the vlans are different. There are only 3 small databases on the primary instance.
any issue in setting up mirroring in this case as vlans are different.
Operating system is Windows 2012.
What is clustering?Why is it done?
Any suggestion appreciated.
Cheers!
I need to cluster two NT Enterrpise Servers with SQL 7 running on them. I have been looking all over the Net for info but not much luck. I need to have some specifics. Can you help me with some good sites or books or both? I have tried Microsoft and they had some info but not much.
Please help!
thanks
We are in the process of consolidating all our SQL6.5 and SQL7 databases to a single SQL 7 server - once completed we want to setup a 2 node SQL7/2000 cluster on either NT4 Enterprise or W2k Advanced Server. I would therefore appreciate any advice in choosing between the two platforms based on cost, ease of setup & configuration and ongoing reliabilty & uptime etc - we currently have no NT4 Enterprise Servers so would have to purchase these licenses anyway. Correct me if I am wrong but I also understand that setting up a cluster on NT4 Enterprise is considerabely more complicated and time consuming than on W2K Advanced Server? Any advice would be greatly appreciated..
regards
Marcfw
I have a job interview and I need to know what type of questions can be asked about working in a cluster environment, I don't have much experience in clustering, can someone please give me an idea?
Thanks in advance!!
Can I implement failover clustering between SQL Server 2000 & SQL Server 7.0? Or do they both need to be the same version of SQL Server.
View 3 Replies View RelatedI have a question relating more to documentation and support. I'm trying to find documentation on clustering.
I remember quite some time ago I found a white paper that literally walked you through every step involved in setting up a SQL Server failover cluster. I had also found a white paper that walked you through setting up an Active/Active cluster.
I've been going through Microsoft's site, but all I've found are little bits and pieces.
If anyone can point me in the right direction, or even provide a link, etc. as to where to find some good solid documentation, that would be awesome.
Thanks!!
Anthony
If i have an activepassive cluster for SQL Server, under what circumstances would it prompt to automatic changeover to the passive cluster ? Failure of the SQL Server, or let's say 1 user database out of 25 becomes suspect?
View 1 Replies View RelatedIs this possible with Express Edition.
We have two servers both running SQL 2005 express. Is there anyway that any changes on one could be replicated on the other?
Thanks
HiI would like to know if it's possible to make a basic SQL cluster withwindows 2003 server and SQL 2000 standard edtition. It has to be abasic cluster, I dont need it to be very quick, I can have minutes ofservers down and it's ok.In case the answer is Yes, can you recommend some links to build itup, please?Thanks in advance!!Ignacio
View 2 Replies View Relatedwhat is clustering tell me in detail
We currently have a cluster configuration that is running as failover with one shared SAN storage solution. Two servers running Windows Server 2003 Enterprise and SQL 2005 Enterprise. We have two nodes right now running in failover and we will be purchasing a third.
Everything is working now, but we would like to move to an N+1 configuration with two active nodes hosting a separate SQL instance each with one failover node. I've seen N+1 mentioned on about a dozen Microsoft websites, but I cant find any documentation on how to setup or configure this clustering method. Has anyone ever set up a configuration like this or seen any documentation on how to do it? Is it possible to run failover with three nodes, two of them being active?
Any insight would be greatly appreciated.
Hi,
Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?
Thanks
Hi All,
Is anyone can tell me the difference between log shipping and clustering? I look at it and I think that this is the same thing as they use two different servers.
TIA
Does anyone know the answers to either of these, given that we are talking about an active/passive cluster using MSCS, and we use Groupwise for mail (don't ask!)?
1) How do I configure Agent Mail on the cluster under this setup?
2) How do I set up linked servers from this setup to other (non-clustered) SQL servers - I can set up the cluster virtual server as a linked server from the others OK, but the other way around doesn't work - perhaps not surprisingly, but is there a way around it?
Thanks
Martin
I need some documentation on how to trouble shoot clustering SQL7EE. I have setup the cluster and looks like it is working but I missed somthing. When I test a failover by pulling the Network cable to the main network not the heartbeat network both boxes lock up. I can failover by powering down one box and using the MSCluster Admin. I am using NT40 6a on Dell PowerEdge 2400 and PowerValut 211s
View 3 Replies View RelatedIs any doing any using Microsoft's Clustering technology as a failover
system with NT/SQL Server ?
Those of you who are using MS Clustering, what are some advantages vs. a third party product such as "Double-Take" ? If you have used "Doube-Take" I would be extremely interested in your thought of the product.
Is it relatively easy to setup and configure with and environment
that's using all the standard products of BACKOFFICE (SQL Server 7.0 Standard Edition, NT 4.0 Standard Edition etc...)
Any hints, tips, etc... would be also GREATLY appreciated.
Thanks in advance.
I have a question about database clustering. I am loking for the solution for the databse scalability, performance and zero downtime especially for MS SQL Server. As my understanding (correct if I am wrong), only Oracle provides 2 DB Servers (parallel server) or NT clustering for two sql servers. The drawback for these solution is only one server is working and another one is standing by. It is not efficent (which only 50%). Is any way that I could built the DB server farm which every DB server is working, if one failed, throw it away, rest of them still working; if I need more power, just add another db server box.How to solve the data sync problem ? Replication is not good for more than 4 or 5 db servers in the farm. Disk mirror is not good since if the server is down, there is no way to access the disks. DO you have any good idea ?
View 2 Replies View RelatedHi Guys,
I am installing sqlserver 7.0 in cluster server.
When I start with Installing the MSDTC and give the IP Address
of the Virtual server, It is giving message:
IP Address is in use.
I couldn't able to continue the installation further
Kindly advice me asap.
Thanks in advance,
Anu
2 Clustering Questions for you.
1. If I cluster 2 SQL servers in an active/active configuration and want to have a seperate disk array to house the data, do I need to have 2 disk arrays, one per server, or can I have one disk array?
2. When installing an application's database on the first(primary) sql server in an active/active configuration, do I need to install it on the second(secondary) server also? The second server will pick up the processes if the first fails.
Hello,
How do i can configure sql server Cluster in mode Failover Active-Active?
Is possible?
Please help me
Thanks
For SQL 2000, what are the licensing requirements for a clustered environment? I thought you needed datacenter for the OS, is there a clustered version of sql server, or do you need 2 copies of enterprise edition. Also, if you cluster can you license sql cals for clients, or do you have to do by processor?
View 4 Replies View RelatedWe are going to implement a SQL 2000 cluster in an active/passive setup. We are going to use multiple instances. What I am confused about is the naming of the virtual server and instances. In the microsoft documentation it states that all instance/virtual names must be unique across all nodes in the cluster. But the client always specifies the same virtual server name when connecting so how can the names be unique across all nodes??
I would have thought that if there was an instance created called inst1 on node A then during the installation that instance name would be replicated to the failover node B. When installing another instance on Node A do you have to specify a different virtual server and instance name on the failover node B??
Please help!!!!!!!