Re: Node not behaving in cluster
From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 08/13/04
- Next message: Space is not available in TempDB: "Re: Load balancing"
- Previous message: Mark Larma: "Node not behaving in cluster"
- In reply to: Mark Larma: "Node not behaving in cluster"
- Next in thread: Rand Boyd [MSFT]: "RE: Node not behaving in cluster"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Aug 2004 10:50:21 -0400
Did you follow the instructions in BOL under Maintaining a Failover Cluster
on how to replace a failed node? SQL can be very picky about changes to
underlying hardware. You may need to treat this as a failed node and
remove-replace it in SQL. Since the Cluster itself seems OK, you can
probably pick up and do just the SQL installation changes.
-- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Mark Larma" <Mark Larma@discussions.microsoft.com> wrote in message news:46CFE332-8DCD-43AA-AC9A-90AF481133FA@microsoft.com... > We had to do a system swap on a system -- moved the drives and RAID > controller to a new system (same type) and just hooked it all up and went to > town. Well, this isn't working very well. The drives (data and quorum) fail > over just fine, but NO other resources will. Many of them say that only the > other node is a valid owner and we can't add this system as a possible owner. > Some have both listed, but they won't start. Any ideas? > > Mark
- Next message: Space is not available in TempDB: "Re: Load balancing"
- Previous message: Mark Larma: "Node not behaving in cluster"
- In reply to: Mark Larma: "Node not behaving in cluster"
- Next in thread: Rand Boyd [MSFT]: "RE: Node not behaving in cluster"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
