- make use of the Microsoft Cluster Resource Center. There is a tremendous amount of well organized material on this site that will help avoid both operational issues and technical issues. http://www.microsoft.com/windowsserver2003/technologies/clustering/resources.mspx#ENH
- The servers need to be identical prior to clustering the servers. I'm a big fan of unattended build processes, but not every IT organization uses unattended builds. Keep in mind the more manual interaction you have with a build, the less likely they are to identical. Servers shouldn't be like snowflakes.
- In addition to being current on all current MS hotfixes, apply any applicable updates from this knowledge base article: http://support.microsoft.com/kb/935640 That article applies to SP2, fixes for SP1 and base install are linked at the bottom of that document.
- When installing hotfixes pay close attention to failures prior to continuing with hotfix deployment. If you apply a hotfix that supersedes an existing hotfix you will be unable to return to install the original, and the servers will appear to have inconsistent patches, despite having the same end result.
- Check your network configuration: http://support.microsoft.com/kb/258750
- Make use of the ClusPrep tool. If you need to check an x64 server, you will need to host the file on a 32bit server. My understanding is it is back ported from the 2008 clusprep tool, and therefore there will not be any further updates to the tool. http://www.microsoft.com/downloads/details.aspx?FamilyID=bf9eb3a7-fb91-4691-9c16-553604265c31&DisplayLang=en
In part two, I'll discuss some of the common operational readiness steps that are crucial to successful clustering.
No comments:
Post a Comment