Re: cluster group



Do I need to add another ip and cluster name for the group 0 in order to
failover correctly?

"anoni" wrote:

> Currently config
> Cluster group: Cluster IP Address
> Cluster Name
> Disk Q: (quorum).
> Group 0: disk s: physical disk
> Data file Share
>
> I need group 0 to be able to failover along with the cluster group when I
> disconnected the pub nic cables.
>
> When I move the group 0 resources to cluster group, it failed over just
> fine. But not when I place the resources in the group 0, it won’t failover
> with the cluster group.
>
> Thanks.
>
>
>
>
> "Chuck Timon [MSFT]" wrote:
>
> > All networks designated for cluster use on the node where the disk is online
> > would have to fail so a regroup could be initiated and another node in the
> > cluster could arbitrate for the resource and bring it online.
> >
> > I'm a little confused as to why a group would contain a single disk resource
> > and nothing else. We used to do this with the quorum drive in NT 4. Now we
> > do it with the full expectation the lone disks will be either moved into
> > another group, or will be joined by other resources that can be used to
> > access the data that is stored on it (e.g. IP address, Network Name, File
> > Share Resource, Print Spooler, SQL, Exchange, etc...)
> >
> > --
> > Chuck Timon, Jr.
> > Microsoft Corporation
> > CCS Beta Engineer
> > This posting is provided "AS IS" with no
> > warranties, and confers no rights.
> > "anoni" <anoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:4DA93058-C334-4B46-875C-B33D04DA795F@xxxxxxxxxxxxxxxx
> > > Is there anyway to make the 'lone' disk failed over with the cluster group
> > > when the network connectivity stopped?
> > > According MS doc, it should. it did not mention anything as all network
> > > connectivity need to be failed which include private
> > >
> > > Thanks.
> > >
> > > "Chuck Timon [MSFT]" wrote:
> > >
> > >> If the heartbeat network is still connected the group with the disk will
> > >> not
> > >> failover. The cluster group fails over because the IP address fails when
> > >> the public network connectivity goes away. A physical disk resource will
> > >> continue to stay online if it is the only resource in the group. It will
> > >> take all network connectivity, in this case, to get the 'lone' disk in
> > >> the
> > >> group to fail over.
> > >>
> > >> --
> > >> Chuck Timon, Jr.
> > >> Microsoft Corporation
> > >> CCS Beta Engineer
> > >> This posting is provided "AS IS" with no
> > >> warranties, and confers no rights.
> > >> "anoni" <anoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > >> news:6DF329ED-01F3-4621-A9A8-E9D71BCEABF6@xxxxxxxxxxxxxxxx
> > >> > When I'm testing my clustered servers by breaking network connectivity
> > >> > (unplug the pub cables. I am using teamed nic), the cluster group
> > >> > failover
> > >> > the secondary server, but not group 0 which contain the shared disk.
> > >> > When
> > >> > I
> > >> > move the shared disk from group 0 to cluster group, the shared disk (or
> > >> > drive) will failover just fine, any reasons?
> > >> >
> > >> > I did a few other tests, all of them failed over ok.
> > >> >
> > >> > Thanks.
> > >> >
> > >> > "Rodney R. Fournier [MVP]" wrote:
> > >> >
> > >> >> You can always rename a group (though I would not rename the cluster
> > >> >> group).
> > >> >>
> > >> >> Keep the cluster group as it is. Move your Group 1 disk to Group 0 if
> > >> >> you
> > >> >> like and use them from that Group.
> > >> >>
> > >> >> Cheers,
> > >> >>
> > >> >> Rod
> > >> >>
> > >> >> MVP - Windows Server - Clustering
> > >> >> http://www.nw-america.com - Clustering Website
> > >> >> http://www.msmvps.com/clustering - Blog
> > >> >> http://www.clusterhelp.com - Cluster Training
> > >> >>
> > >> >>
> > >> >> "anoni" <anoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > >> >> news:118A71A7-286D-44AA-B75F-F6537C638132@xxxxxxxxxxxxxxxx
> > >> >> > will the cluster services stop working if I move the disk1 to
> > >> >> > cluster
> > >> >> > group?
> > >> >> > I assume I can rename group 0 to a more meaningful name. right?
> > >> >> >
> > >> >> > "Rodney R. Fournier [MVP]" wrote:
> > >> >> >
> > >> >> >> That is the way they programmed it. First disk = group 0, then
> > >> >> >> second
> > >> >> >> in
> > >> >> >> group 1, etc.
> > >> >> >>
> > >> >> >> Cheers,
> > >> >> >>
> > >> >> >> Rod
> > >> >> >>
> > >> >> >> MVP - Windows Server - Clustering
> > >> >> >> http://www.nw-america.com - Clustering Website
> > >> >> >> http://www.msmvps.com/clustering - Blog
> > >> >> >> http://www.clusterhelp.com - Cluster Training
> > >> >> >>
> > >> >> >>
> > >> >> >> "anoni" <anoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > >> >> >> news:97DDE189-7C16-4368-8F85-5334EB138E83@xxxxxxxxxxxxxxxx
> > >> >> >> > By default, the quorum disk is in the default group, and the
> > >> >> >> > shared
> > >> >> >> > data
> > >> >> >> > disk
> > >> >> >> > in the group 0, any reasons?
> > >> >> >> >
> > >> >> >> > Thanks
> > >> >> >> >
> > >> >> >> > "Rodney R. Fournier [MVP]" wrote:
> > >> >> >> >
> > >> >> >> >> Best practice is to leave the cluster group alone, don't mess
> > >> >> >> >> with
> > >> >> >> >> it.
> > >> >> >> >> To
> > >> >> >> >> keep your system highly available the group needs to be left
> > >> >> >> >> alone.
> > >> >> >> >>
> > >> >> >> >> If you see another drive in the cluster group, its a mistake and
> > >> >> >> >> should
> > >> >> >> >> be
> > >> >> >> >> fixed :)
> > >> >> >> >>
> > >> >> >> >> Clustering does not understand or carry about partitions, only
> > >> >> >> >> what
> > >> >> >> >> it
> > >> >> >> >> sees
> > >> >> >> >> as physical disks.
> > >> >> >> >>
> > >> >> >> >> Can you actually restore a 2TB disk in a timely fashion?
> > >> >> >> >>
> > >> >> >> >> Cheers,
> > >> >> >> >>
> > >> >> >> >> Rod
> > >> >> >> >>
> > >> >> >> >> MVP - Windows Server - Clustering
> > >> >> >> >> http://www.nw-america.com - Clustering Website
> > >> >> >> >> http://www.msmvps.com/clustering - Blog
> > >> >> >> >> http://www.clusterhelp.com - Cluster Training
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >> >> "anoni" <anoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > >> >> >> >> news:1D6261DF-E175-4393-8AE5-031E76D33161@xxxxxxxxxxxxxxxx
> > >> >> >> >> >I have a quorum drive and shared data drive, are there any
> > >> >> >> >> >benefit
> > >> >> >> >> >to
> > >> >> >> >> >put
> > >> >> >> >> > them in differ groups when I configure cluster services? by
> > >> >> >> >> > defaut,
> > >> >> >> >> > is
> > >> >> >> >> > it
> > >> >> >> >> > in
> > >> >> >> >> > cluster group? Is there anyway I can have the shared drive
> > >> >> >> >> > more
> > >> >> >> >> > than
> > >> >> >> >> > 2tb
> > >> >> >> >> > on
> > >> >> >> >> > one partition?
> > >> >> >> >> >
> > >> >> >> >> > Thanks
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> > >>
> >
> >
> >
.



Relevant Pages

  • RE: Unable to failover when public network cables are removed
    ... "Unable to failover" wrote: ... > for Network redundancy. ... > initially, that is, server1 is able to failover to server2. ... The Cluster IP address and Cluster ...
    (microsoft.public.windows.server.clustering)
  • Re: Unable to failover when public network cables are removed
    ... determining node failure and subsequent resource failover. ... > Can you provide a little more information here......Is the Public Network ... There is only 1 standard cluster group. ... There is no other resources. ...
    (microsoft.public.windows.server.clustering)
  • Re: Failover on public network failiure?
    ... There are a number of ways the cluster service checks the state of the ... If the network interface is determined to be failed then any ... the IP address on the current node the groupwill failover to another ...
    (microsoft.public.windows.server.clustering)
  • Re: Network cluster problems
    ... >connection, ... W2K will no long failover if you lose network ... the IP resources ... >in the cluster will fail taking down any network names ...
    (microsoft.public.windows.server.clustering)
  • Re: Network cluster problems
    ... it is recommended to disable media sense on the "heartbeat" network ... connection, ... when you lose network connectivity the IP resources ... You're trying to connect to the cluster ...
    (microsoft.public.windows.server.clustering)