Re: When adding 2nd node, unable to see shared drives

Nope, MSCS is (and remains currently) a "shared-nothing" model...could this
change in the future? Who knows, but for now, you need to make this work as
is...

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

This posting is provided "AS IS" with no warranties, and confers no rights.

"Isaac Story" <IsaacStory@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11E5B3F2-BE79-4F66-91EA-29961CBD0C2E@xxxxxxxxxxxxxxxx
> Is there a way to disable the "shared-nothing" disk protection until I
> have
> clustering up and running? I don't any other way to get this to work.
>
>
> Isaac
>
> "John Toner [MVP]" wrote:
>
>> Have you seen this KB article?
>>
>> http://support.microsoft.com/kb/331801
>>
>> Regards,
>> John
>>
>> "Isaac Story" <IsaacStory@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:D33A2DA4-E1F0-434C-8E52-A7C3164A9D59@xxxxxxxxxxxxxxxx
>> > I am fairly new to clustering and there is an issue I am having when
>> adding
>> > subsequent nodes after the first one while the first node is still up
>> > and
>> > running. Due to the "shared nothing" model that restricts shared
>> > storage
>> > access to one host, when I bring the second node up, the drives I need
>> > on
>> the
>> > SAN show up as unreadable. As a result, adding the second node fails
>> because
>> > it cannot see the shared quorum drive nor the shared data drive. I have
>> seen
>> > several people say this is normal behavior, yet it is preventing me
>> > from
>> > setting up multi-node clustering. Am I missing something here???
>> >
>> > My hardware setup is as follows:
>> >
>> > IBM HS20 Blades connected to a Hitachi 9570V through a Brocade fabric.
>> > All
>> > hosts are running Windows Server 2003 Enterprise.
>>
>>
>>


.

Relevant Pages

  • Re: Printing issues since Windows 2003 Service Pack 1 was applied
    ... > MVP - Windows Server - Clustering ... > "A troubleshooter's best tool is the Event Viewer and understanding the ... Our clients are windows XP SP2. ...
    (microsoft.public.windows.server.clustering)
  • Re: Running a network-accessible scheduled task on a Virtual Server
    ... MVP - Windows Server - Clustering ... "A troubleshooter's best tool is the Event Viewer and understanding the ... >I want to run a script as a daily scheduled task, but it needs to be able ... > What is the most sensible way of achieving this on a 2-node Windows Server ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows Clustering Software
    ... MVP - Windows Server - Clustering ... "A troubleshooter's best tool is the Event Viewer and understanding the ... events and messages contained therein." ...
    (microsoft.public.windows.server.clustering)
  • Re: Clusprep Tool
    ... MVP - Windows Server - Clustering ... "A troubleshooter's best tool is the Event Viewer and understanding the ...
    (microsoft.public.windows.server.clustering)
  • Re: Clusprep Tool
    ... future...I have a question in to the ClusPrep Beta team and will reply here ... MVP - Windows Server - Clustering ... "A troubleshooter's best tool is the Event Viewer and understanding the ...
    (microsoft.public.windows.server.clustering)
Loading