Hi 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.
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 ?
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!
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 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 RelatedDear Friends,I wanted to configure Failover cluster for SQL Server 2000 on Windows2000 advanced servers.I have only 2 no.s of windows 2000 advanced server m/cs. I dont haveany shared disks and SCSI drives. Can I still configure the Failoverclustering?I would like to know more about the need for the shared disks in theFailover clustering.Please shed some light.RegardsKumar
View 1 Replies View RelatedDoes 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 RelatedI 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?
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!
I 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
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.?
Is 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 RelatedHello,
How do i can configure sql server Cluster in mode Failover Active-Active?
Is possible?
Please help me
Thanks
In a clustered sql server environment having two Nodes, configured as Active/Active or Active/Passive, do I need to create the databases on both the Nodes?
I am not too sure about how to create databases in the clustered environment. Can somebody help..
Hello,
Will removing the built in administrator account from the sql server cluster have any related problem with failover happening. Is it ok if i add the domain account under which sql server runs and add it to the local administrators box of both the nodes. I was thinking of not allowing the built in administrator account to access the sql server. Thought adding only the account under which the sql server service runs is enough which is also a domain account with local administrator privileges on both the nodes of the cluster.
Appreciate any reply back.
Sorry if I had posted it on the wrong forum.
Thanks!
Rock
Hello all,
I have tried to install SQL Server 2005 Standard edition with CLUSTERING. I faced a problem and everything rolls back.
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server Setup was unable add user domain1xyz to local group domain1IT Security Admin-Group.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29512&EvtType=sqlca%5csqlsecurityca.cpp%40Do_sqlGroupMember%40Do_sqlGroupMember%40x6ba
I have refered to PostI=1659185 posted by Fly and it still won't be able to fix my problem.
I have added LOCAL SERVICE into the local group (SQLServer2005MSFTEUser$AAA$MSSQLSERVER), but it still can't work.
Please can someone help me on this. Thank a lot....
Hello,
Can anyone give me a site that shows Clustering on SQL Server 2000 step by step. I am trying to have two or more servers acting as one and to get high-availability without having any impact on the application side.
Say I have 2 servers clustered for SQL. xxxP1 and xxxP2.
Can my SQL virtual server name be xxxP1 or does it have to be something other than the names I called the 2 W2K boxes.
Thanks..
I have recently inherited an active/passive cluster. Sql server agent mail is sending notifications, but I haven't figured out how - yet. The active node is setup to start the mssqlservice with a domain acct. that is a local admin on the machine, but the agent is setup to start with the local system acct. The domain acct. has an exchange profile on the server. It was my understanding that the agent and the sqlserver service had to run under the same id for this to work? Are the ids listed under services on the primary node the ids that actually run the services - or are the services run by a different id? If so, can someone point me in the right direction?
View 3 Replies View RelatedEnvironment:
SQL Server 2000 SP3a on W2K Advanced Server SP4.
1 IBM Server x440 with FastT700 Storage (Fibre Channel)
We need to buy another IBM Server x440 or x445 and we would like to make a cluster.
Question 1:
Once we build the Cluster with the installation of the Cluster Service, making the W2K Cluster, is it possible to upgrade the default instance of SQL Server to a default clusterd instance of SQL Server?
In BOL I have found a note that explain how to do this but I have some doubts.
When I installed SQL Server I placed the system files on the C: drive, the DB files on our SAN on disk E: and the log files on disk F:.
Question 2:
If we would like to use Windows Server 2003 what would be the possibility for an upgrade?
I mean, should I erase all and start with Windows Server 2003 setup or can you suggest to upgrade the OS first, from W2K Advanced Server, and then cluster SQL Server if possible?
Can you advice please?
Any help is really appreciated.
Thank you very much for your time.
Franco
If we have a stateful connection (RDS) and the database fails how will the application reconnect. I do not believe that our application was written using MSCS API. Therefore I don't believe that it caches the user logon and password to log back into the session. So, my question is can the application work with sql server clustering since it uses stateful connections? Any help would be greatly appreciated. Thanks
View 1 Replies View RelatedHi,
Is SAN a mandatory requirement for clustering?
I mean to implement SQL server clustering, do I have to have my dbs on SAN?
Hi,
Would anyone give me some directions on where I could get good information on Windows 2003 and SQL 2005 clustering??
Thanks in advance.