Dear Friends,
I wanted to configure Failover cluster for SQL Server 2000 on Windows
2000 advanced servers.
I have only 2 no.s of windows 2000 advanced server m/cs. I dont have
any shared disks and SCSI drives. Can I still configure the Failover
clustering?
I would like to know more about the need for the shared disks in the
Failover clustering.
Please shed some light.
Regards
Kumar
I have a 2 node Microsoft 2000 cluster with a shared storage device. Iwant to create automatic failover for MS SQL 2000 server. I can dothat wit the following options:1. Active/Pasive (one instance installed)2. Active/Active (More then one instance/virtual sql serversinstalled)I have a question about option 2.Is it possible to have more then one instance/virtual SQL server,service only one database for example loadbalancing. ?, or when youcreate multiple instances/virtual SQL servers, does that mean you havemultiple databases ? If not why does a Virtual SQL server has to betaken over by a cluster node that didnt fail. Then you can actuallyuse option 1. Please advise!The documentation is not very clear on this issues.Regards,Nico de Groot
View 1 Replies View RelatedHi all,
We are the studying the possibilty of implementing SQL - Clustering for
Failover server.
Are there any third party tools readily available.
Any suggestion or checklist ??
Any suggestions or comments will be appreciated.
Thanks and have a great day.
Does anyone know how to obtain the physical server name that a SQL failover cluster instance is running on through the system tables or other database commands? Thanks in advance.
View 3 Replies View RelatedI have two SQL 7.0 SP1 (WinNT 4.0 SP 6.2) Servers using Clustering.
Problem: When SQLBox1 goes down, the Failover sends it to SQLBox2. When
SQLBox1 comes back up, the node stays on SQLBox2, instead of going back to
SQLBox1. This happens over 50% of the time, but not every time. Sometimes
it works fine.
I have done 3 hours of research, and can not find anything on this problem,
can any one a tleast point me in the right direction. I can hardly find any
troubleshooting on this issue. I do have January 2000 of the MSDN Library
installed on my machine if that helps, but there was not much on it in there
either (at least not that I found).
:confused:
In evaluating/comparing MS Clustering vs Hardware Failover Blades, has anyone come across any disadvantages/concerns for a Hardware Failover Blades.
Why would you install MS SQL 2000 Clustering when you can use a Hardware Failover Blade and use a SQL 2000 standard edition. e.g In an event a hardware failure occurs the admin manager brings over a standby hardware blade and reassigns it to the SAN (on which OS and SQL 2000) is installed and you are up and running.
Would appreciate any comments and suggestions to compare these solutions.
Thanks
how to configure email in SQL server failover clustering. I need to configure email to send when node switches from one node to another. best way to configure email in fail over clustering?
View 1 Replies View RelatedI tested the failover clustering for SQL 2008R2.When I stop the SQL server services manully, the failover did not fail to another resource. At the Faiolover cluster manager, SQl server(MSSQLSERVER) only show the status for offline. I think it should be move to another owner intead of just show as offline.
View 3 Replies View Related
I have 2 Windows 2003 r2 servers with a SQL failover cluster installed across the 2 node. Generally I have been running off node1 with node2 as the failover partner. I have purchased the correct licensing for noe1 and from the following I do not need to purchase a license for node2:
Failover clustering is a process where the operating system and SQL Server 2005 work together to provide availability in the event of an application failure, hardware failure, or operating-system error. Failover clustering provides hardware redundancy through a configuration in which critical resources are transferred automatically from a failing machine to an equally configured server to help ensure continuity of service.
When doing failover support, a server is designated as the passive server. The purpose of the passive server is to absorb the data and information held in another server that fails. A passive server does not need a license if the number of processors in the passive server is equal to or less than the number of processors in the active server. The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly
http://www.microsoft.com/sql/howtobuy/activepassive.mspx
My questions are:
1) If I switch my cluster instace to point to node2 for testing node2 in case of a failover, would I need to purchase another licence ? This means I am not doing the repointing because of an 'event of an application failure, hardware failure, or operating-system error' ? Can you please provide information from MS ?
2) How are SQL Licences bound to the windows install in a SQL Server failover cluster configuration ? For instance if node1 legitimately fails due to an 'event of an application failure, hardware failure, or operating-system error' and you failover to node2. Then you think, stuff (forget about) node1 as I have 1 set of licences for SQL Enterprise already and therefore can run with a legitimate licence on node2. Can you please clarify ?
3) I have heard that only one server needs a license in a failover cluster. Then how does this fit in with any of the questions from above:
'The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly' ?
In the event of a legitimate failure, node2 would be running off the license purchased. So why are MS restricting the use of it for 30 days ?
I am looking in to using Microsoft Clustering supported in NT Server Enterprise to provide failover support for 2 database servers running SQL Server 7. I was wondering if anyone had any experience with it--good or bad. I read the white paper and it sounds good, but I'd like to get some real
world application experience.
Thanks for any info.
Bob
Could I implement a failover cluster solution on the two DBs which are based in two different cities?
Possible?
Hi All,
We're planning to install a Server 2005 Failover Cluster and I'd like to find more information about licensing, etc.
Basic questions:
- What is the best O.S. to run? Win 2003 or the new 2008? And what version (datacenter, enterprise)?
- Since I'm going to use 2 machines, will I have to pay for 2 licenses (sql and windows - two lic. each)? Or just 1 license, since just 1 machine will be the active server?
This is for some web applications, so, web environment.
Any help?
Thank you!
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 want to use sql 2005 failover clustering feature, so that upgrade sql 2000 is necessary. But some of the stored procedures built in 2000 are not working directly in 2005, set the compatibility level to 80 could make them work. In this case, can somebody here tell me if down grade the database level will affect failover clustering running properly? e.g. will data still be synchronized properly? Thanks in advance.
View 3 Replies View RelatedI am setting up my first sql node on a 2 node cluster and runing into this
The disks are already added into the failover cluster manager
Ok, got an assignment from my boss.. Need shared storage for a 2 node cluster, with main focus on MSSQL DB Failover. We won't be storing alot of data, speed it not really an issue, just availability..
As far as I know I need 2 SCSI cards, 1 for each node. Node1 has to have ID7 and Node2 ID6 (for example)
this is it.. what's next? what's the best way to configure all this? Do I need a special box for all hard drives to be with certain controller?
I was thinking to link up like this
terminator
|
Node1
|
|
Disk
|
|
Node2
|
terminator
But I wanted to run some sort of RAID on disk, mirroring is fine.. Anyone can suggest me what parts I should get for this setup? my servers don't have 64bit PCI too
I have a guy who wants me to move his databases to an external drive. Hardware is my major weakness and I usually think I am McGyver when I can swap out a RAM board in my home PC. Whenever guys in the office start talking hardware, I go hide in the bathroom.
I know I have read that this is a very bad idea in some book and a few message board threads. This guy is going to use SCSI and it is going to be attached to the same controller as his other disks. I know he should have a battery backup for the drive especially if it employs write caching and that it should be formatted to NTFS and not FAT32.
I googled echnettedBOLedMSDNed this for 2 hours yesterday because I remember reading something about disc controllers and external drives and SQL Server being a recipe for disaster but I could not find anything to back me up.
Any words of wisdom or advice?
1. Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.
2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.
3. after fail over done to 2nd secondary node what mode in production(readonly or read write).
4. how to rollback to production primary ,will change data in secondary will get updated in primary.
We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.
However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.
The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.
Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.
The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.
Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.
Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.
We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?
Are we missing a service pack on the client?
Thanks,
Kimball
1. In alwaysON fail over cluster, Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.
2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.
3. After fail over done to 2nd secondary node what mode in production(readonly or read write).
4. How to rollback to production primary ,will change data in secondary will get updated in primary.
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.?
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