What actions do you need to take, if any? Will
the applications work as expected? Logical failover planning is just as important.
Physical Failover
After installing SQL Server on a cluster, check to be sure that you haven??™t created any
unexpected resource dependencies. Every resource can have a dependency, and many
have dependencies immediately after the install. For example, SQL Agent is dependent
on the SQL Server instance running, as shown in Figure 7-5. If the instance fails, SQL
Agent won??™t be able to access the MSDB database, so naturally it will fail as well.
SQL Server 2005 is much better about putting only minimal logical dependencies in
place. The instance depends on both the clustered disk resource and a network name.
The network name depends on having an IP address. Every dependency probably needs
to be in place, but it??™s still a good idea to check them over.
You may want to create your own dependencies as well. If your application depends
on full-text search capabilities, you may want to configure resources to have some sort of
dependency on the full-text search service or on the drive that holds the full-text catalog.
Pages:
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365