Re: File share should NOT be dependent on the cluster name -WHY??

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: SA (nospam_at_nospam.nospam)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 10:35:50 -0400

Greg,
Thanks for the reply. I do have SCSI Powervault backend with 14 disks and 2
Win 2003 nodes. I am trying to setup a file share resource and right now I
have only one group with:
1) My cluster name
2) My Cluster IP address
3) Quorum disk
4) Disk 1
5) Disk 2

The only network name resource available is the cluster name. I am just
wondering what my next step should be, create the another group as a virtual
server OR just create a network name within the existing group and map the
file share resource to the new network name and cluster IP address.

Also what needs to be in DNS for network mapping - the virtual server name
or the network name? Really confused just about now.

-SA.

"Greg Page" <gpage@nospam.microsoft.com> wrote in message
news:UUSFUQiLEHA.308@cpmsftngxa10.phx.gbl...
> you don't want to do that for cluster management reasons. if you only have
> one disk as well (sounds like it since you only have one group) you also
> never want to put anything other than the qorum on the quorum disks.
>
> Basically, you want to split all your resources out by functions. The
> defatul name, IP and quorum disk are there for cluster management and
> that's waht they should be used for. I cannot tell you how many customers
> use these resources for other things and later find that when they want to
> change things in their cluster, they are pretty much screwed because all
> their resources use the same name and IP.
>
> This message is provided as is and does not imply any warranty or
gaurantee
> of support of any kind. Microsoft, the person providing the advice, nor
any
> of Microsoft's and posters subsidiaries, friends, pets, children or
> acquaintenances will be held in any way liable for following any advice
> contained herein.
> --------------------
> >From: "SA" <nospam@nospam.nospam>
> >Subject: File share should NOT be dependent on the cluster name -WHY??
> >Date: Thu, 29 Apr 2004 12:00:38 -0400
> >Lines: 22
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> >Message-ID: <OQt7dMgLEHA.2396@TK2MSFTNGP12.phx.gbl>
> >Newsgroups: microsoft.public.windows.server.clustering
> >NNTP-Posting-Host: 192.107.108.230
> >Path:
>
cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
> phx.gbl
> >Xref: cpmsftngxa10.phx.gbl
microsoft.public.windows.server.clustering:3607
> >X-Tomcat-NG: microsoft.public.windows.server.clustering
> >
> >Hi,
> >I am really new to the clustering world and while creating a clustered
file
> >share (following KB 224967) on one of the drives, I came across this:
> >
> >You never want a file share resource to be dependent on the "Cluster
Name"
> >resource.
> >
> >I wanted to know why this is. I only have one group and only one network
> >name resource which is the cluster name resource. I am trying to figure
> out
> >what to do now.
> >
> >I tried to create a Virtual server with a new network name resource and
IP
> >address resource and a file share resource. Do I need to have the
physical
> >disk recource in tehre too??
> >
> >If all this sounds like rambling please ask me to be more specific but
> right
> >now I just want to know what to do to create a clustered file share .
> >Thanks,
> >
> >SA.
> >
> >
> >
>

Relevant Pages

  • Phisical disk resource
    ... I'm setting up a 2 node cluster under 2003 ent. ... is working but I am not able to bring the shared disk ... INFO FmpPropagateResourceState: resource a94c4968- ... INFO Physical Disk: ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)
  • Re: MSDTC conflicting articles
    ... must depend on a network name and a physical disk. ... Put the MSDTC in the default cluster group (the one that contains ... the quorum disk resource. ...
    (microsoft.public.windows.server.clustering)
  • Re: Unable to start the cluster service when creating a new 2 node
    ... existing cluster and could no form a new cluster. ... node 1 as possible host for resource 6add91be-f8ae-4fb7-b78d-2488c502ad0a. ... FmpAddPossibleNodeToList for restype Physical Disk ... [DiskArb] ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... yeta lot of times it depends on each customer's enviornment and the complexity of the SAN migration. ... 305793 How to Replace a Disk That Is on a Windows 2000 or a Windows 2003 Server ... Windows NT/2000/2003 Cluster Technologies ... >> 4) Create a new Disk Resource for the new disk and have that in the SQL ...
    (microsoft.public.windows.server.clustering)