Planning for Failover ClusteringVersions of Windows SupportedNumber of SQL Server 2000 Instances per Server ClusterName of the SQL Server Virtual ServerNumber of NodesDisksIP Addresses, Ports, and Network Card UsageApplications and Failover ClusteringThird-Party Applications, File Shares, Dependencies, and SQL Server 2000 Failover ClusteringHardware-Assisted Backups and SQL Server 2000 Failover ClusteringService Accounts and SQL Server 2000 Failover ClusteringMemoryCoexistence with Stand-Alone Instances and Other Versions of SQL ServerAnalysis Services and Failover ClusteringSQL Mail and Failover ClusteringExchange and SQL Server on the Same ClusterCluster Group Configuration for Failover ClusteringImplementing SQL Server 2000 Failover ClusteringPrerequisitesInstallation OrderWindows 2000 Advanced Server and Windows 2000 Datacenter ServerWindows Server 2003 Enterprise Edition and Windows Server 2003 Datacenter EditionInstalling a SQL Server Virtual ServerPostinstallation TasksConfiguring Antivirus SoftwareAdding Drives for SQL Server UseVerifying the Drive ConfigurationDisabling Unnecessary ServicesAssigning a Static Port NumberEnabling Advanced SecurityIPSecKerberosSSL CertificatesConfiguring SQL Server ResourcesSetting Preferred OwnersFailing Back to the Preferred Owner, Thresholds, and Other ParametersResource Group FailbackConfiguring Resource ParametersCluster Group ThresholdsVerifying Your Failover Cluster InstallationVerifying Connectivity and Name ResolutionVerifying Connectivity and Name Resolution from a Server NodeVerifying Connectivity and Name Resolution from a ClientValidating FailoverVerifying the SQL Server Service Account and Node ParticipationVerifying the Application with FailoverAdministering SQL Server Virtual ServersEnsuring a Virtual Server Will Not Fail Due to Other Service FailuresAdding or Removing a Cluster Node from the Virtual Server Definition and Adding, Changing, or Updating a TCP/IP AddressRenaming a SQL Server 2000 Virtual ServerUninstalling a SQL Server Virtual ServerManually Removing Failover ClusteringManually Removing Clustered Instances of SQL ServerChanging SQL Server Service AccountsSQL Server Service AccountSQL Server Agent Service AccountChanging DomainsTroubleshooting SQL Server 2000 Failover ClustersBarriers for Failover ClusteringSupport for Failover ClusteringThe Troubleshooting ProcessWhere to Look for ProblemsMicrosoft Product Support Reporting ToolCommon Troubleshooting IssuesInstallation ProblemsConnectivityFull-Text Search SetupDisaster Recovery for Failover ClusteringScenario 1: Quorum Disk FailureScenario 2: Cluster Database Corruption on a NodeScenario 3: Quorum CorruptionScenario 4: Checkpoint Files Lost or CorruptScenario 5: Cluster Node FailureSingle Node FailureMultiple Node FailureAll Nodes FailedScenario 6: A Cluster Disk Is Corrupt or NonfunctionalIf You Do Not Have BackupsProblems on One or More Cluster NodesBad Quorum Disk, Intact Cluster NodesCorrupt Cluster Database on One NodeCorrupt QuorumCorrupt or Missing Checkpoint FilesCorrupt or Bad Cluster DiskSummary