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
go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||
You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.
Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.
If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.
|||adminup, did the article help?|||Thanks It helped.
Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?
|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||
Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.
setup failed to start on the remote machine. Check the task scheduler event log on the reote machine
Why I am getting this error
|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.
I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.
Any ideas?
Anup
|||sql setup log might give some clues as why it fails.|||As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?
|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).
No comments:
Post a Comment