|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Where do you set the number of seconds to wait before failover occurs from
one node to another in Windows Server 2003?
Thank you.
--
Mike
|
|
http://support.microsoft.com/kb/815267
To set the value of the ClusSvcHeartbeatTimeout property, run the following
command from a command prompt:
cluster.exe /cluster:clustername /prop clussvcheartbeattimeout=number of
seconds
where clustername is the name of the cluster and number of seconds is the
number of seconds that you want to use in the calculation of the heartbeat.
But, I would not mess with it. What are you trying to accomplish.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com...
[Quoted Text] > Where do you set the number of seconds to wait before failover occurs from
> one node to another in Windows Server 2003?
>
> Thank you.
> --
> Mike
|
|
I want to set a property in Cluster Administrator: number of seconds to wait
before failover occurs from one node to another in Windows Server 2003.
Thank you.
--
Mike
"Rodney R. Fournier [MVP]" wrote:
[Quoted Text] > http://support.microsoft.com/kb/815267> > > To set the value of the ClusSvcHeartbeatTimeout property, run the following > command from a command prompt: > > cluster.exe /cluster:clustername /prop clussvcheartbeattimeout=number of > seconds > > where clustername is the name of the cluster and number of seconds is the > number of seconds that you want to use in the calculation of the heartbeat. > > But, I would not mess with it. What are you trying to accomplish. > > Cheers, > > Rodney R. Fournier > > MVP - Windows Server - Clustering > http://www.nw-america.com - Clustering Website > http://msmvps.com/clustering - Blog > http://www.clusterhelp.com - Cluster Training > ClusterHelp.com is a Microsoft Certified Gold Partner > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... > > Where do you set the number of seconds to wait before failover occurs from > > one node to another in Windows Server 2003? > > > > Thank you. > > -- > > Mike > > > |
|
What is your business need? I understand the technical requirement.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com...
[Quoted Text] >I want to set a property in Cluster Administrator: number of seconds to >wait > before failover occurs from one node to another in Windows Server 2003. > > Thank you. > > -- > Mike > > > "Rodney R. Fournier [MVP]" wrote: > >> http://support.microsoft.com/kb/815267>> >> >> To set the value of the ClusSvcHeartbeatTimeout property, run the >> following >> command from a command prompt: >> >> cluster.exe /cluster:clustername /prop clussvcheartbeattimeout=number of >> seconds >> >> where clustername is the name of the cluster and number of seconds is the >> number of seconds that you want to use in the calculation of the >> heartbeat. >> >> But, I would not mess with it. What are you trying to accomplish. >> >> Cheers, >> >> Rodney R. Fournier >> >> MVP - Windows Server - Clustering >> http://www.nw-america.com - Clustering Website >> http://msmvps.com/clustering - Blog >> http://www.clusterhelp.com - Cluster Training >> ClusterHelp.com is a Microsoft Certified Gold Partner >> >> >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... >> > Where do you set the number of seconds to wait before failover occurs >> > from >> > one node to another in Windows Server 2003? >> > >> > Thank you. >> > -- >> > Mike >> >> >>
|
|
I want to change the number of seconds MSCS failover occurs so it does not
conflict with SAN failover.
Thank you.
--
Mike
"Rodney R. Fournier [MVP]" wrote:
[Quoted Text] > What is your business need? I understand the technical requirement. > > Cheers, > > Rodney R. Fournier > > MVP - Windows Server - Clustering > http://www.nw-america.com - Clustering Website > http://msmvps.com/clustering - Blog > http://www.clusterhelp.com - Cluster Training > ClusterHelp.com is a Microsoft Certified Gold Partner > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... > >I want to set a property in Cluster Administrator: number of seconds to > >wait > > before failover occurs from one node to another in Windows Server 2003. > > > > Thank you. > > > > -- > > Mike > > > > > > "Rodney R. Fournier [MVP]" wrote: > > > >> http://support.microsoft.com/kb/815267> >> > >> > >> To set the value of the ClusSvcHeartbeatTimeout property, run the > >> following > >> command from a command prompt: > >> > >> cluster.exe /cluster:clustername /prop clussvcheartbeattimeout=number of > >> seconds > >> > >> where clustername is the name of the cluster and number of seconds is the > >> number of seconds that you want to use in the calculation of the > >> heartbeat. > >> > >> But, I would not mess with it. What are you trying to accomplish. > >> > >> Cheers, > >> > >> Rodney R. Fournier > >> > >> MVP - Windows Server - Clustering > >> http://www.nw-america.com - Clustering Website > >> http://msmvps.com/clustering - Blog > >> http://www.clusterhelp.com - Cluster Training > >> ClusterHelp.com is a Microsoft Certified Gold Partner > >> > >> > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... > >> > Where do you set the number of seconds to wait before failover occurs > >> > from > >> > one node to another in Windows Server 2003? > >> > > >> > Thank you. > >> > -- > >> > Mike > >> > >> > >> > > > |
|
If you are running a geographically dispersed cluster, what SAN / software
are you using for this ?
"Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com...
[Quoted Text] > I want to change the number of seconds MSCS failover occurs so it does not > conflict with SAN failover. > > Thank you. > > -- > Mike > > > "Rodney R. Fournier [MVP]" wrote: > > > What is your business need? I understand the technical requirement. > > > > Cheers, > > > > Rodney R. Fournier > > > > MVP - Windows Server - Clustering > > http://www.nw-america.com - Clustering Website > > http://msmvps.com/clustering - Blog > > http://www.clusterhelp.com - Cluster Training > > ClusterHelp.com is a Microsoft Certified Gold Partner > > > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... > > >I want to set a property in Cluster Administrator: number of seconds to > > >wait > > > before failover occurs from one node to another in Windows Server
> > >
> > > Thank you.
> > >
> > > --
> > > Mike
> > >
> > >
> > > "Rodney R. Fournier [MVP]" wrote:
> > >
> > >> http://support.microsoft.com/kb/815267
> > >>
> > >>
> > >> To set the value of the ClusSvcHeartbeatTimeout property, run the
> > >> following
> > >> command from a command prompt:
> > >>
> > >> cluster.exe /cluster:clustername /prop clussvcheartbeattimeout=number
of
> > >> seconds
> > >>
> > >> where clustername is the name of the cluster and number of seconds is
the
> > >> number of seconds that you want to use in the calculation of the
> > >> heartbeat.
> > >>
> > >> But, I would not mess with it. What are you trying to accomplish.
> > >>
> > >> Cheers,
> > >>
> > >> Rodney R. Fournier
> > >>
> > >> MVP - Windows Server - Clustering
> > >> http://www.nw-america.com - Clustering Website
> > >> http://msmvps.com/clustering - Blog
> > >> http://www.clusterhelp.com - Cluster Training
> > >> ClusterHelp.com is a Microsoft Certified Gold Partner
> > >>
> > >>
> > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com...
> > >> > Where do you set the number of seconds to wait before failover
occurs
> > >> > from
> > >> > one node to another in Windows Server 2003?
> > >> >
> > >> > Thank you.
> > >> > --
> > >> > Mike
> > >>
> > >>
> > >>
> >
> >
> >
|
|
Guys, all I want to "please" know is where do you set the number of seconds
to wait before failover occurs from one node to another in Windows Server
2003? Is this done in CLuster Administrator? If so, where do I set this
property?
Thank you.
--
Mike
"Edwin vMierlo [MVP]" wrote:
[Quoted Text] > If you are running a geographically dispersed cluster, what SAN / software > are you using for this ? > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com... > > I want to change the number of seconds MSCS failover occurs so it does not > > conflict with SAN failover. > > > > Thank you. > > > > -- > > Mike > > > > > > "Rodney R. Fournier [MVP]" wrote: > > > > > What is your business need? I understand the technical requirement. > > > > > > Cheers, > > > > > > Rodney R. Fournier > > > > > > MVP - Windows Server - Clustering > > > http://www.nw-america.com - Clustering Website > > > http://msmvps.com/clustering - Blog > > > http://www.clusterhelp.com - Cluster Training > > > ClusterHelp.com is a Microsoft Certified Gold Partner > > > > > > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... > > > >I want to set a property in Cluster Administrator: number of seconds to > > > >wait > > > > before failover occurs from one node to another in Windows Server > 2003. > > > > > > > > Thank you. > > > > > > > > -- > > > > Mike > > > > > > > > > > > > "Rodney R. Fournier [MVP]" wrote: > > > > > > > >> http://support.microsoft.com/kb/815267> > > >> > > > >> > > > >> To set the value of the ClusSvcHeartbeatTimeout property, run the > > > >> following > > > >> command from a command prompt: > > > >> > > > >> cluster.exe /cluster:clustername /prop clussvcheartbeattimeout=number > of > > > >> seconds > > > >> > > > >> where clustername is the name of the cluster and number of seconds is > the > > > >> number of seconds that you want to use in the calculation of the > > > >> heartbeat. > > > >> > > > >> But, I would not mess with it. What are you trying to accomplish. > > > >> > > > >> Cheers, > > > >> > > > >> Rodney R. Fournier > > > >> > > > >> MVP - Windows Server - Clustering > > > >> http://www.nw-america.com - Clustering Website > > > >> http://msmvps.com/clustering - Blog > > > >> http://www.clusterhelp.com - Cluster Training > > > >> ClusterHelp.com is a Microsoft Certified Gold Partner > > > >> > > > >> > > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... > > > >> > Where do you set the number of seconds to wait before failover > occurs > > > >> > from > > > >> > one node to another in Windows Server 2003? > > > >> > > > > >> > Thank you. > > > >> > -- > > > >> > Mike > > > >> > > > >> > > > >> > > > > > > > > > > > > |
|
your question was specifically answered in an earlier post.
you do it from the command line.
- NuTs
"Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com...
[Quoted Text] > Guys, all I want to "please" know is where do you set the number of > seconds > to wait before failover occurs from one node to another in Windows Server > 2003? Is this done in CLuster Administrator? If so, where do I set this > property? > > Thank you. > > > > -- > Mike > > > "Edwin vMierlo [MVP]" wrote: > >> If you are running a geographically dispersed cluster, what SAN / >> software >> are you using for this ? >> >> >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com... >> > I want to change the number of seconds MSCS failover occurs so it does >> > not >> > conflict with SAN failover. >> > >> > Thank you. >> > >> > -- >> > Mike >> > >> > >> > "Rodney R. Fournier [MVP]" wrote: >> > >> > > What is your business need? I understand the technical requirement. >> > > >> > > Cheers, >> > > >> > > Rodney R. Fournier >> > > >> > > MVP - Windows Server - Clustering >> > > http://www.nw-america.com - Clustering Website >> > > http://msmvps.com/clustering - Blog >> > > http://www.clusterhelp.com - Cluster Training >> > > ClusterHelp.com is a Microsoft Certified Gold Partner >> > > >> > > >> > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... >> > > >I want to set a property in Cluster Administrator: number of seconds >> > > >to >> > > >wait >> > > > before failover occurs from one node to another in Windows Server >> 2003. >> > > > >> > > > Thank you. >> > > > >> > > > -- >> > > > Mike >> > > > >> > > > >> > > > "Rodney R. Fournier [MVP]" wrote: >> > > > >> > > >> http://support.microsoft.com/kb/815267>> > > >> >> > > >> >> > > >> To set the value of the ClusSvcHeartbeatTimeout property, run the >> > > >> following >> > > >> command from a command prompt: >> > > >> >> > > >> cluster.exe /cluster:clustername /prop >> > > >> clussvcheartbeattimeout=number >> of >> > > >> seconds >> > > >> >> > > >> where clustername is the name of the cluster and number of seconds >> > > >> is >> the >> > > >> number of seconds that you want to use in the calculation of the >> > > >> heartbeat. >> > > >> >> > > >> But, I would not mess with it. What are you trying to accomplish. >> > > >> >> > > >> Cheers, >> > > >> >> > > >> Rodney R. Fournier >> > > >> >> > > >> MVP - Windows Server - Clustering >> > > >> http://www.nw-america.com - Clustering Website >> > > >> http://msmvps.com/clustering - Blog >> > > >> http://www.clusterhelp.com - Cluster Training >> > > >> ClusterHelp.com is a Microsoft Certified Gold Partner >> > > >> >> > > >> >> > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... >> > > >> > Where do you set the number of seconds to wait before failover >> occurs >> > > >> > from >> > > >> > one node to another in Windows Server 2003? >> > > >> > >> > > >> > Thank you. >> > > >> > -- >> > > >> > Mike >> > > >> >> > > >> >> > > >> >> > > >> > > >> > > >> >> >>
|
|
Sorry, I missed it. Thanks guys!
--
Mike
"Nut Cracker" wrote:
[Quoted Text] > your question was specifically answered in an earlier post. > > you do it from the command line. > > - NuTs > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com... > > Guys, all I want to "please" know is where do you set the number of > > seconds > > to wait before failover occurs from one node to another in Windows Server > > 2003? Is this done in CLuster Administrator? If so, where do I set this > > property? > > > > Thank you. > > > > > > > > -- > > Mike > > > > > > "Edwin vMierlo [MVP]" wrote: > > > >> If you are running a geographically dispersed cluster, what SAN / > >> software > >> are you using for this ? > >> > >> > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > >> news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com... > >> > I want to change the number of seconds MSCS failover occurs so it does > >> > not > >> > conflict with SAN failover. > >> > > >> > Thank you. > >> > > >> > -- > >> > Mike > >> > > >> > > >> > "Rodney R. Fournier [MVP]" wrote: > >> > > >> > > What is your business need? I understand the technical requirement. > >> > > > >> > > Cheers, > >> > > > >> > > Rodney R. Fournier > >> > > > >> > > MVP - Windows Server - Clustering > >> > > http://www.nw-america.com - Clustering Website > >> > > http://msmvps.com/clustering - Blog > >> > > http://www.clusterhelp.com - Cluster Training > >> > > ClusterHelp.com is a Microsoft Certified Gold Partner > >> > > > >> > > > >> > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > >> > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... > >> > > >I want to set a property in Cluster Administrator: number of seconds > >> > > >to > >> > > >wait > >> > > > before failover occurs from one node to another in Windows Server > >> 2003. > >> > > > > >> > > > Thank you. > >> > > > > >> > > > -- > >> > > > Mike > >> > > > > >> > > > > >> > > > "Rodney R. Fournier [MVP]" wrote: > >> > > > > >> > > >> http://support.microsoft.com/kb/815267> >> > > >> > >> > > >> > >> > > >> To set the value of the ClusSvcHeartbeatTimeout property, run the > >> > > >> following > >> > > >> command from a command prompt: > >> > > >> > >> > > >> cluster.exe /cluster:clustername /prop > >> > > >> clussvcheartbeattimeout=number > >> of > >> > > >> seconds > >> > > >> > >> > > >> where clustername is the name of the cluster and number of seconds > >> > > >> is > >> the > >> > > >> number of seconds that you want to use in the calculation of the > >> > > >> heartbeat. > >> > > >> > >> > > >> But, I would not mess with it. What are you trying to accomplish. > >> > > >> > >> > > >> Cheers, > >> > > >> > >> > > >> Rodney R. Fournier > >> > > >> > >> > > >> MVP - Windows Server - Clustering > >> > > >> http://www.nw-america.com - Clustering Website > >> > > >> http://msmvps.com/clustering - Blog > >> > > >> http://www.clusterhelp.com - Cluster Training > >> > > >> ClusterHelp.com is a Microsoft Certified Gold Partner > >> > > >> > >> > > >> > >> > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > >> > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... > >> > > >> > Where do you set the number of seconds to wait before failover > >> occurs > >> > > >> > from > >> > > >> > one node to another in Windows Server 2003? > >> > > >> > > >> > > >> > Thank you. > >> > > >> > -- > >> > > >> > Mike > >> > > >> > >> > > >> > >> > > >> > >> > > > >> > > > >> > > > >> > >> > >> > > > |
|
Ok, here is the real answer: you can not.
When a failover starts, it starts. There is no parameter where you can set a
"pause" because of your san disks who need to failover.
What you can do however is to create a "scripted geo-cluster"
1) script your "failover commands"
2) add this script as a resource to your cluster
3) make your disk resources dependent on your script
this way, on failover, your script fires on node 2 first, your disks are not
failed over in the san / still at node 1, but your script takes care of
this, and your disk resources do not come online until your script finishes.
script finish / online --> disks on san are failed over --> physical disk
resources come online properly
and please see this blog (
http://msmvps.com/blogs/jtoner/archive/2007/05.aspx ) from John Toner on
this subject, it details how you do this on an EMC Clariion, but you
probably can apply methods to your specific environment.
Please realize, if you do all this, you are NOT using a qualified solution,
I am afraid you are running a NON-supported solution.
I would never run production applications on such a scripted geo-cluster.
Because I can think of many, many scenarios where your script would not
execute or not pick up the exact conditions to determine the correct action.
Also a scripted geo-cluster will have a risk of a split brain due to not
picking up the correct information, or not having the logic to deal with the
situation/failure.
Testing with this in a test/lab environment, sure ! I have done it, good fun
!
rgds,
Edwin.
"Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com...
[Quoted Text] > Guys, all I want to "please" know is where do you set the number of
seconds
> to wait before failover occurs from one node to another in Windows Server
> 2003? Is this done in CLuster Administrator? If so, where do I set this
> property?
>
> Thank you.
>
>
>
> --
> Mike
>
>
> "Edwin vMierlo [MVP]" wrote:
>
> > If you are running a geographically dispersed cluster, what SAN /
software
> > are you using for this ?
> >
> >
> > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com...
> > > I want to change the number of seconds MSCS failover occurs so it does
not
> > > conflict with SAN failover.
> > >
> > > Thank you.
> > >
> > > --
> > > Mike
> > >
> > >
> > > "Rodney R. Fournier [MVP]" wrote:
> > >
> > > > What is your business need? I understand the technical requirement.
> > > >
> > > > Cheers,
> > > >
> > > > Rodney R. Fournier
> > > >
> > > > MVP - Windows Server - Clustering
> > > > http://www.nw-america.com - Clustering Website
> > > > http://msmvps.com/clustering - Blog
> > > > http://www.clusterhelp.com - Cluster Training
> > > > ClusterHelp.com is a Microsoft Certified Gold Partner
> > > >
> > > >
> > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com...
> > > > >I want to set a property in Cluster Administrator: number of
seconds to
> > > > >wait
> > > > > before failover occurs from one node to another in Windows Server
> > 2003.
> > > > >
> > > > > Thank you.
> > > > >
> > > > > --
> > > > > Mike
> > > > >
> > > > >
> > > > > "Rodney R. Fournier [MVP]" wrote:
> > > > >
> > > > >> http://support.microsoft.com/kb/815267
> > > > >>
> > > > >>
> > > > >> To set the value of the ClusSvcHeartbeatTimeout property, run the
> > > > >> following
> > > > >> command from a command prompt:
> > > > >>
> > > > >> cluster.exe /cluster:clustername /prop
clussvcheartbeattimeout=number
> > of
> > > > >> seconds
> > > > >>
> > > > >> where clustername is the name of the cluster and number of
seconds is
> > the
> > > > >> number of seconds that you want to use in the calculation of the
> > > > >> heartbeat.
> > > > >>
> > > > >> But, I would not mess with it. What are you trying to accomplish.
> > > > >>
> > > > >> Cheers,
> > > > >>
> > > > >> Rodney R. Fournier
> > > > >>
> > > > >> MVP - Windows Server - Clustering
> > > > >> http://www.nw-america.com - Clustering Website
> > > > >> http://msmvps.com/clustering - Blog
> > > > >> http://www.clusterhelp.com - Cluster Training
> > > > >> ClusterHelp.com is a Microsoft Certified Gold Partner
> > > > >>
> > > > >>
> > > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com...
> > > > >> > Where do you set the number of seconds to wait before failover
> > occurs
> > > > >> > from
> > > > >> > one node to another in Windows Server 2003?
> > > > >> >
> > > > >> > Thank you.
> > > > >> > --
> > > > >> > Mike
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
> >
> >
> >
|
|
hmm.. not really that was the heartbeat, and the time it takes to "detect
prior to failover"
the OP wants to "wait / pause" a few seconds when cluster already has made
the decision to failover.
the OP's problem is that "his san disks are not failed over yet" when the
cluster tries to bring the physical disk resources online on another node
at least that is what I understood the problem is.
rgds,
edwin.
"Nut Cracker" <nutcracker[ at ]internationalhacker.org> wrote in message
news:ufl5t4crHHA.532[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > your question was specifically answered in an earlier post.
>
> you do it from the command line.
>
> - NuTs
>
> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com...
> > Guys, all I want to "please" know is where do you set the number of
> > seconds
> > to wait before failover occurs from one node to another in Windows
Server
> > 2003? Is this done in CLuster Administrator? If so, where do I set
this
> > property?
> >
> > Thank you.
> >
> >
> >
> > --
> > Mike
> >
> >
> > "Edwin vMierlo [MVP]" wrote:
> >
> >> If you are running a geographically dispersed cluster, what SAN /
> >> software
> >> are you using for this ?
> >>
> >>
> >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> >> news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com...
> >> > I want to change the number of seconds MSCS failover occurs so it
does
> >> > not
> >> > conflict with SAN failover.
> >> >
> >> > Thank you.
> >> >
> >> > --
> >> > Mike
> >> >
> >> >
> >> > "Rodney R. Fournier [MVP]" wrote:
> >> >
> >> > > What is your business need? I understand the technical requirement.
> >> > >
> >> > > Cheers,
> >> > >
> >> > > Rodney R. Fournier
> >> > >
> >> > > MVP - Windows Server - Clustering
> >> > > http://www.nw-america.com - Clustering Website
> >> > > http://msmvps.com/clustering - Blog
> >> > > http://www.clusterhelp.com - Cluster Training
> >> > > ClusterHelp.com is a Microsoft Certified Gold Partner
> >> > >
> >> > >
> >> > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> >> > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com...
> >> > > >I want to set a property in Cluster Administrator: number of
seconds
> >> > > >to
> >> > > >wait
> >> > > > before failover occurs from one node to another in Windows Server
> >> 2003.
> >> > > >
> >> > > > Thank you.
> >> > > >
> >> > > > --
> >> > > > Mike
> >> > > >
> >> > > >
> >> > > > "Rodney R. Fournier [MVP]" wrote:
> >> > > >
> >> > > >> http://support.microsoft.com/kb/815267
> >> > > >>
> >> > > >>
> >> > > >> To set the value of the ClusSvcHeartbeatTimeout property, run
the
> >> > > >> following
> >> > > >> command from a command prompt:
> >> > > >>
> >> > > >> cluster.exe /cluster:clustername /prop
> >> > > >> clussvcheartbeattimeout=number
> >> of
> >> > > >> seconds
> >> > > >>
> >> > > >> where clustername is the name of the cluster and number of
seconds
> >> > > >> is
> >> the
> >> > > >> number of seconds that you want to use in the calculation of the
> >> > > >> heartbeat.
> >> > > >>
> >> > > >> But, I would not mess with it. What are you trying to
accomplish.
> >> > > >>
> >> > > >> Cheers,
> >> > > >>
> >> > > >> Rodney R. Fournier
> >> > > >>
> >> > > >> MVP - Windows Server - Clustering
> >> > > >> http://www.nw-america.com - Clustering Website
> >> > > >> http://msmvps.com/clustering - Blog
> >> > > >> http://www.clusterhelp.com - Cluster Training
> >> > > >> ClusterHelp.com is a Microsoft Certified Gold Partner
> >> > > >>
> >> > > >>
> >> > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> >> > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com...
> >> > > >> > Where do you set the number of seconds to wait before failover
> >> occurs
> >> > > >> > from
> >> > > >> > one node to another in Windows Server 2003?
> >> > > >> >
> >> > > >> > Thank you.
> >> > > >> > --
> >> > > >> > Mike
> >> > > >>
> >> > > >>
> >> > > >>
> >> > >
> >> > >
> >> > >
> >>
> >>
> >>
>
>
|
|
That's right. Thank you!
--
Mike
"Edwin vMierlo [MVP]" wrote:
[Quoted Text] > hmm.. not really that was the heartbeat, and the time it takes to "detect > prior to failover" > > the OP wants to "wait / pause" a few seconds when cluster already has made > the decision to failover. > the OP's problem is that "his san disks are not failed over yet" when the > cluster tries to bring the physical disk resources online on another node > > at least that is what I understood the problem is. > > rgds, > edwin. > > > > "Nut Cracker" <nutcracker[ at ]internationalhacker.org> wrote in message > news:ufl5t4crHHA.532[ at ]TK2MSFTNGP06.phx.gbl... > > your question was specifically answered in an earlier post. > > > > you do it from the command line. > > > > - NuTs > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com... > > > Guys, all I want to "please" know is where do you set the number of > > > seconds > > > to wait before failover occurs from one node to another in Windows > Server > > > 2003? Is this done in CLuster Administrator? If so, where do I set > this > > > property? > > > > > > Thank you. > > > > > > > > > > > > -- > > > Mike > > > > > > > > > "Edwin vMierlo [MVP]" wrote: > > > > > >> If you are running a geographically dispersed cluster, what SAN / > > >> software > > >> are you using for this ? > > >> > > >> > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > >> news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com... > > >> > I want to change the number of seconds MSCS failover occurs so it > does > > >> > not > > >> > conflict with SAN failover. > > >> > > > >> > Thank you. > > >> > > > >> > -- > > >> > Mike > > >> > > > >> > > > >> > "Rodney R. Fournier [MVP]" wrote: > > >> > > > >> > > What is your business need? I understand the technical requirement. > > >> > > > > >> > > Cheers, > > >> > > > > >> > > Rodney R. Fournier > > >> > > > > >> > > MVP - Windows Server - Clustering > > >> > > http://www.nw-america.com - Clustering Website > > >> > > http://msmvps.com/clustering - Blog > > >> > > http://www.clusterhelp.com - Cluster Training > > >> > > ClusterHelp.com is a Microsoft Certified Gold Partner > > >> > > > > >> > > > > >> > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > >> > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... > > >> > > >I want to set a property in Cluster Administrator: number of > seconds > > >> > > >to > > >> > > >wait > > >> > > > before failover occurs from one node to another in Windows Server > > >> 2003. > > >> > > > > > >> > > > Thank you. > > >> > > > > > >> > > > -- > > >> > > > Mike > > >> > > > > > >> > > > > > >> > > > "Rodney R. Fournier [MVP]" wrote: > > >> > > > > > >> > > >> http://support.microsoft.com/kb/815267> > >> > > >> > > >> > > >> > > >> > > >> To set the value of the ClusSvcHeartbeatTimeout property, run > the > > >> > > >> following > > >> > > >> command from a command prompt: > > >> > > >> > > >> > > >> cluster.exe /cluster:clustername /prop > > >> > > >> clussvcheartbeattimeout=number > > >> of > > >> > > >> seconds > > >> > > >> > > >> > > >> where clustername is the name of the cluster and number of > seconds > > >> > > >> is > > >> the > > >> > > >> number of seconds that you want to use in the calculation of the > > >> > > >> heartbeat. > > >> > > >> > > >> > > >> But, I would not mess with it. What are you trying to > accomplish. > > >> > > >> > > >> > > >> Cheers, > > >> > > >> > > >> > > >> Rodney R. Fournier > > >> > > >> > > >> > > >> MVP - Windows Server - Clustering > > >> > > >> http://www.nw-america.com - Clustering Website > > >> > > >> http://msmvps.com/clustering - Blog > > >> > > >> http://www.clusterhelp.com - Cluster Training > > >> > > >> ClusterHelp.com is a Microsoft Certified Gold Partner > > >> > > >> > > >> > > >> > > >> > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > >> > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... > > >> > > >> > Where do you set the number of seconds to wait before failover > > >> occurs > > >> > > >> > from > > >> > > >> > one node to another in Windows Server 2003? > > >> > > >> > > > >> > > >> > Thank you. > > >> > > >> > -- > > >> > > >> > Mike > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > > > >> > > > > >> > > > > >> > > >> > > >> > > > > > > > |
|
Thanks again!
--
Mike
"Edwin vMierlo [MVP]" wrote:
[Quoted Text] > Ok, here is the real answer: you can not. > > When a failover starts, it starts. There is no parameter where you can set a > "pause" because of your san disks who need to failover. > > What you can do however is to create a "scripted geo-cluster" > > 1) script your "failover commands" > 2) add this script as a resource to your cluster > 3) make your disk resources dependent on your script > > this way, on failover, your script fires on node 2 first, your disks are not > failed over in the san / still at node 1, but your script takes care of > this, and your disk resources do not come online until your script finishes. > > script finish / online --> disks on san are failed over --> physical disk > resources come online properly > > and please see this blog ( > http://msmvps.com/blogs/jtoner/archive/2007/05.aspx ) from John Toner on > this subject, it details how you do this on an EMC Clariion, but you > probably can apply methods to your specific environment. > > Please realize, if you do all this, you are NOT using a qualified solution, > I am afraid you are running a NON-supported solution. > > I would never run production applications on such a scripted geo-cluster. > Because I can think of many, many scenarios where your script would not > execute or not pick up the exact conditions to determine the correct action. > Also a scripted geo-cluster will have a risk of a split brain due to not > picking up the correct information, or not having the logic to deal with the > situation/failure. > > Testing with this in a test/lab environment, sure ! I have done it, good fun > ! > > rgds, > Edwin. > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com... > > Guys, all I want to "please" know is where do you set the number of > seconds > > to wait before failover occurs from one node to another in Windows Server > > 2003? Is this done in CLuster Administrator? If so, where do I set this > > property? > > > > Thank you. > > > > > > > > -- > > Mike > > > > > > "Edwin vMierlo [MVP]" wrote: > > > > > If you are running a geographically dispersed cluster, what SAN / > software > > > are you using for this ? > > > > > > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > > news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com... > > > > I want to change the number of seconds MSCS failover occurs so it does > not > > > > conflict with SAN failover. > > > > > > > > Thank you. > > > > > > > > -- > > > > Mike > > > > > > > > > > > > "Rodney R. Fournier [MVP]" wrote: > > > > > > > > > What is your business need? I understand the technical requirement. > > > > > > > > > > Cheers, > > > > > > > > > > Rodney R. Fournier > > > > > > > > > > MVP - Windows Server - Clustering > > > > > http://www.nw-america.com - Clustering Website > > > > > http://msmvps.com/clustering - Blog > > > > > http://www.clusterhelp.com - Cluster Training > > > > > ClusterHelp.com is a Microsoft Certified Gold Partner > > > > > > > > > > > > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > > > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... > > > > > >I want to set a property in Cluster Administrator: number of > seconds to > > > > > >wait > > > > > > before failover occurs from one node to another in Windows Server > > > 2003. > > > > > > > > > > > > Thank you. > > > > > > > > > > > > -- > > > > > > Mike > > > > > > > > > > > > > > > > > > "Rodney R. Fournier [MVP]" wrote: > > > > > > > > > > > >> http://support.microsoft.com/kb/815267> > > > > >> > > > > > >> > > > > > >> To set the value of the ClusSvcHeartbeatTimeout property, run the > > > > > >> following > > > > > >> command from a command prompt: > > > > > >> > > > > > >> cluster.exe /cluster:clustername /prop > clussvcheartbeattimeout=number > > > of > > > > > >> seconds > > > > > >> > > > > > >> where clustername is the name of the cluster and number of > seconds is > > > the > > > > > >> number of seconds that you want to use in the calculation of the > > > > > >> heartbeat. > > > > > >> > > > > > >> But, I would not mess with it. What are you trying to accomplish. > > > > > >> > > > > > >> Cheers, > > > > > >> > > > > > >> Rodney R. Fournier > > > > > >> > > > > > >> MVP - Windows Server - Clustering > > > > > >> http://www.nw-america.com - Clustering Website > > > > > >> http://msmvps.com/clustering - Blog > > > > > >> http://www.clusterhelp.com - Cluster Training > > > > > >> ClusterHelp.com is a Microsoft Certified Gold Partner > > > > > >> > > > > > >> > > > > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > > > > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... > > > > > >> > Where do you set the number of seconds to wait before failover > > > occurs > > > > > >> > from > > > > > >> > one node to another in Windows Server 2003? > > > > > >> > > > > > > >> > Thank you. > > > > > >> > -- > > > > > >> > Mike > > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > |
|
You can modify the isAlive and looksAlive timeouts, as well as the number of
times to restart a resource, and the interval between restarts via cluadmin.
Right click your disk resource, go to properties, then advanced.
Adjust the looksAlive and isAlive timeouts to suit your needs. You'll
probably have to experiment to find the optimal settings since you don't
want to ignore failed resources.
Good luck!
~kenny
"Edwin vMierlo [MVP]" <EdwinvMierlo[ at ]discussions.microsoft.com> wrote in
message news:e7rtpCdrHHA.1168[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Ok, here is the real answer: you can not. > > When a failover starts, it starts. There is no parameter where you can set > a > "pause" because of your san disks who need to failover. > > What you can do however is to create a "scripted geo-cluster" > > 1) script your "failover commands" > 2) add this script as a resource to your cluster > 3) make your disk resources dependent on your script > > this way, on failover, your script fires on node 2 first, your disks are > not > failed over in the san / still at node 1, but your script takes care of > this, and your disk resources do not come online until your script > finishes. > > script finish / online --> disks on san are failed over --> physical disk > resources come online properly > > and please see this blog ( > http://msmvps.com/blogs/jtoner/archive/2007/05.aspx ) from John Toner on > this subject, it details how you do this on an EMC Clariion, but you > probably can apply methods to your specific environment. > > Please realize, if you do all this, you are NOT using a qualified > solution, > I am afraid you are running a NON-supported solution. > > I would never run production applications on such a scripted geo-cluster. > Because I can think of many, many scenarios where your script would not > execute or not pick up the exact conditions to determine the correct > action. > Also a scripted geo-cluster will have a risk of a split brain due to not > picking up the correct information, or not having the logic to deal with > the > situation/failure. > > Testing with this in a test/lab environment, sure ! I have done it, good > fun > ! > > rgds, > Edwin. > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message > news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com... >> Guys, all I want to "please" know is where do you set the number of > seconds >> to wait before failover occurs from one node to another in Windows Server >> 2003? Is this done in CLuster Administrator? If so, where do I set this >> property? >> >> Thank you. >> >> >> >> -- >> Mike >> >> >> "Edwin vMierlo [MVP]" wrote: >> >> > If you are running a geographically dispersed cluster, what SAN / > software >> > are you using for this ? >> > >> > >> > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> > news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com... >> > > I want to change the number of seconds MSCS failover occurs so it >> > > does > not >> > > conflict with SAN failover. >> > > >> > > Thank you. >> > > >> > > -- >> > > Mike >> > > >> > > >> > > "Rodney R. Fournier [MVP]" wrote: >> > > >> > > > What is your business need? I understand the technical requirement. >> > > > >> > > > Cheers, >> > > > >> > > > Rodney R. Fournier >> > > > >> > > > MVP - Windows Server - Clustering >> > > > http://www.nw-america.com - Clustering Website >> > > > http://msmvps.com/clustering - Blog >> > > > http://www.clusterhelp.com - Cluster Training >> > > > ClusterHelp.com is a Microsoft Certified Gold Partner >> > > > >> > > > >> > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> > > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com... >> > > > >I want to set a property in Cluster Administrator: number of > seconds to >> > > > >wait >> > > > > before failover occurs from one node to another in Windows Server >> > 2003. >> > > > > >> > > > > Thank you. >> > > > > >> > > > > -- >> > > > > Mike >> > > > > >> > > > > >> > > > > "Rodney R. Fournier [MVP]" wrote: >> > > > > >> > > > >> http://support.microsoft.com/kb/815267>> > > > >> >> > > > >> >> > > > >> To set the value of the ClusSvcHeartbeatTimeout property, run >> > > > >> the >> > > > >> following >> > > > >> command from a command prompt: >> > > > >> >> > > > >> cluster.exe /cluster:clustername /prop > clussvcheartbeattimeout=number >> > of >> > > > >> seconds >> > > > >> >> > > > >> where clustername is the name of the cluster and number of > seconds is >> > the >> > > > >> number of seconds that you want to use in the calculation of the >> > > > >> heartbeat. >> > > > >> >> > > > >> But, I would not mess with it. What are you trying to >> > > > >> accomplish. >> > > > >> >> > > > >> Cheers, >> > > > >> >> > > > >> Rodney R. Fournier >> > > > >> >> > > > >> MVP - Windows Server - Clustering >> > > > >> http://www.nw-america.com - Clustering Website >> > > > >> http://msmvps.com/clustering - Blog >> > > > >> http://www.clusterhelp.com - Cluster Training >> > > > >> ClusterHelp.com is a Microsoft Certified Gold Partner >> > > > >> >> > > > >> >> > > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message >> > > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com... >> > > > >> > Where do you set the number of seconds to wait before failover >> > occurs >> > > > >> > from >> > > > >> > one node to another in Windows Server 2003? >> > > > >> > >> > > > >> > Thank you. >> > > > >> > -- >> > > > >> > Mike >> > > > >> >> > > > >> >> > > > >> >> > > > >> > > > >> > > > >> > >> > >> > > >
|
|
"Kenny Speer" <kenny.speer[ at ]gmail.com> wrote in message
news:361B0BCF-79EA-4D5E-BDF7-5FEE32A54FCF[ at ]microsoft.com...
[Quoted Text] > You can modify the isAlive and looksAlive timeouts, as well as the number
of
> times to restart a resource, and the interval between restarts via
cluadmin.
> Right click your disk resource, go to properties, then advanced.
>
> Adjust the looksAlive and isAlive timeouts to suit your needs. You'll
> probably have to experiment to find the optimal settings since you don't
> want to ignore failed resources.
>
Hmm, same as my post in response to tweaking heartbeat parameters: that
(tweaking IsAlive/LooksAlive) influences the time the cluster take *before*
making the decision to failover the resrouce group. The OP was looking for a
method of "pausing / delaying" the failover proces *after* the cluster has
made its decision.
Again, there is no parameter to "pause" or "delay" the actual failover
process.
As well as the OP is running a replicated storage solution where the second
node is connected to the second (replicated) storage. This is an
geographically dispersed cluster, and there are only two options for the OP.
1) buy a qualified geo-disp-cluster solution from the catalog / HW-vendor,
or
2) script it, but this is not qualified, nor is it supported, but can be
done. (not recommended)
Rgds,
Edwin.
|
|
You're right. But his problem is that his storage is not failing over as
quick as the cluster is. So, if he delays the detection time for a failure,
which will give his storage time to complete it's failover, then the cluster
does a failover, it's the same net-net result. My understanding is that
modifying those timeouts is supported by Microsoft, else why are they so
easily accessible?
~kenny
"Edwin vMierlo [MVP]" <EdwinvMierlo[ at ]discussions.microsoft.com> wrote in
message news:e$BQsPJuHHA.1208[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] >
> "Kenny Speer" <kenny.speer[ at ]gmail.com> wrote in message
> news:361B0BCF-79EA-4D5E-BDF7-5FEE32A54FCF[ at ]microsoft.com...
>> You can modify the isAlive and looksAlive timeouts, as well as the number
> of
>> times to restart a resource, and the interval between restarts via
> cluadmin.
>> Right click your disk resource, go to properties, then advanced.
>>
>> Adjust the looksAlive and isAlive timeouts to suit your needs. You'll
>> probably have to experiment to find the optimal settings since you don't
>> want to ignore failed resources.
>>
>
> Hmm, same as my post in response to tweaking heartbeat parameters: that
> (tweaking IsAlive/LooksAlive) influences the time the cluster take
> *before*
> making the decision to failover the resrouce group. The OP was looking for
> a
> method of "pausing / delaying" the failover proces *after* the cluster has
> made its decision.
>
> Again, there is no parameter to "pause" or "delay" the actual failover
> process.
>
> As well as the OP is running a replicated storage solution where the
> second
> node is connected to the second (replicated) storage. This is an
> geographically dispersed cluster, and there are only two options for the
> OP.
> 1) buy a qualified geo-disp-cluster solution from the catalog / HW-vendor,
> or
> 2) script it, but this is not qualified, nor is it supported, but can be
> done. (not recommended)
>
> Rgds,
> Edwin.
>
>
|
|
"Kenny Speer" <kenny.speer[ at ]gmail.com> wrote in message
news:F3A9CEDA-1B7D-4E93-9609-8FACBECE3D9F[ at ]microsoft.com...
[Quoted Text] > You're right. But his problem is that his storage is not failing over as
> quick as the cluster is. So, if he delays the detection time for a
failure,
> which will give his storage time to complete it's failover,
Ah ! I see where you are comming from: only when the failure is on the
storage end, then yes, this *could* work, but only in specific situations. I
can think of many situations where this would not work.
Still... to run this properly, the OP need to buy a geo cluster solution.
> then the cluster
> does a failover, it's the same net-net result. My understanding is that
> modifying those timeouts is supported by Microsoft, else why are they so
> easily accessible?
modify away, but know why and what you modify, as Microsoft will ask
questions when they are changed from default. you need to be able to justify
and explain why things have been changed.
|
|
Just to come back on my previous statement:
A scripted geo-cluster can be fully supported for production processes !
EMC / Microsoft have qualified a scripted cluster recently, please see the
catalog :
http://www.windowsservercatalog.com/item.aspx?idItem=4f28600a-1184-77a3-5768-7091f50227dd
To get more information on how to do this, please contact your storage
vendor (EMC in this case)
rgds,
Edwin.
"Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
news:F76417AE-48B6-4480-AE33-FE51B6150881[ at ]microsoft.com...
[Quoted Text] > Thanks again!
> --
> Mike
>
>
> "Edwin vMierlo [MVP]" wrote:
>
> > Ok, here is the real answer: you can not.
> >
> > When a failover starts, it starts. There is no parameter where you can
set a
> > "pause" because of your san disks who need to failover.
> >
> > What you can do however is to create a "scripted geo-cluster"
> >
> > 1) script your "failover commands"
> > 2) add this script as a resource to your cluster
> > 3) make your disk resources dependent on your script
> >
> > this way, on failover, your script fires on node 2 first, your disks are
not
> > failed over in the san / still at node 1, but your script takes care of
> > this, and your disk resources do not come online until your script
finishes.
> >
> > script finish / online --> disks on san are failed over --> physical
disk
> > resources come online properly
> >
> > and please see this blog (
> > http://msmvps.com/blogs/jtoner/archive/2007/05.aspx ) from John Toner
on
> > this subject, it details how you do this on an EMC Clariion, but you
> > probably can apply methods to your specific environment.
> >
> > Please realize, if you do all this, you are NOT using a qualified
solution,
> > I am afraid you are running a NON-supported solution.
> >
> > I would never run production applications on such a scripted
geo-cluster.
> > Because I can think of many, many scenarios where your script would not
> > execute or not pick up the exact conditions to determine the correct
action.
> > Also a scripted geo-cluster will have a risk of a split brain due to not
> > picking up the correct information, or not having the logic to deal with
the
> > situation/failure.
> >
> > Testing with this in a test/lab environment, sure ! I have done it, good
fun
> > !
> >
> > rgds,
> > Edwin.
> >
> >
> >
> > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > news:80F5ABDB-B401-4256-B998-1501A6ABA929[ at ]microsoft.com...
> > > Guys, all I want to "please" know is where do you set the number of
> > seconds
> > > to wait before failover occurs from one node to another in Windows
Server
> > > 2003? Is this done in CLuster Administrator? If so, where do I set
this
> > > property?
> > >
> > > Thank you.
> > >
> > >
> > >
> > > --
> > > Mike
> > >
> > >
> > > "Edwin vMierlo [MVP]" wrote:
> > >
> > > > If you are running a geographically dispersed cluster, what SAN /
> > software
> > > > are you using for this ?
> > > >
> > > >
> > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > > > news:C9B6F40E-474D-4EB6-AA9C-6AEC335D2C62[ at ]microsoft.com...
> > > > > I want to change the number of seconds MSCS failover occurs so it
does
> > not
> > > > > conflict with SAN failover.
> > > > >
> > > > > Thank you.
> > > > >
> > > > > --
> > > > > Mike
> > > > >
> > > > >
> > > > > "Rodney R. Fournier [MVP]" wrote:
> > > > >
> > > > > > What is your business need? I understand the technical
requirement.
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Rodney R. Fournier
> > > > > >
> > > > > > MVP - Windows Server - Clustering
> > > > > > http://www.nw-america.com - Clustering Website
> > > > > > http://msmvps.com/clustering - Blog
> > > > > > http://www.clusterhelp.com - Cluster Training
> > > > > > ClusterHelp.com is a Microsoft Certified Gold Partner
> > > > > >
> > > > > >
> > > > > > "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > > > > > news:5843AC3C-6B38-4F5F-BF2A-0C22623AD5B4[ at ]microsoft.com...
> > > > > > >I want to set a property in Cluster Administrator: number of
> > seconds to
> > > > > > >wait
> > > > > > > before failover occurs from one node to another in Windows
Server
> > > > 2003.
> > > > > > >
> > > > > > > Thank you.
> > > > > > >
> > > > > > > --
> > > > > > > Mike
> > > > > > >
> > > > > > >
> > > > > > > "Rodney R. Fournier [MVP]" wrote:
> > > > > > >
> > > > > > >> http://support.microsoft.com/kb/815267
> > > > > > >>
> > > > > > >>
> > > > > > >> To set the value of the ClusSvcHeartbeatTimeout property, run
the
> > > > > > >> following
> > > > > > >> command from a command prompt:
> > > > > > >>
> > > > > > >> cluster.exe /cluster:clustername /prop
> > clussvcheartbeattimeout=number
> > > > of
> > > > > > >> seconds
> > > > > > >>
> > > > > > >> where clustername is the name of the cluster and number of
> > seconds is
> > > > the
> > > > > > >> number of seconds that you want to use in the calculation of
the
> > > > > > >> heartbeat.
> > > > > > >>
> > > > > > >> But, I would not mess with it. What are you trying to
accomplish.
> > > > > > >>
> > > > > > >> Cheers,
> > > > > > >>
> > > > > > >> Rodney R. Fournier
> > > > > > >>
> > > > > > >> MVP - Windows Server - Clustering
> > > > > > >> http://www.nw-america.com - Clustering Website
> > > > > > >> http://msmvps.com/clustering - Blog
> > > > > > >> http://www.clusterhelp.com - Cluster Training
> > > > > > >> ClusterHelp.com is a Microsoft Certified Gold Partner
> > > > > > >>
> > > > > > >>
> > > > > > >> "Mike" <Mike[ at ]discussions.microsoft.com> wrote in message
> > > > > > >> news:87BC79B2-217D-4995-92CF-3C2497996173[ at ]microsoft.com...
> > > > > > >> > Where do you set the number of seconds to wait before
failover
> > > > occurs
> > > > > > >> > from
> > > > > > >> > one node to another in Windows Server 2003?
> > > > > > >> >
> > > > > > >> > Thank you.
> > > > > > >> > --
> > > > > > >> > Mike
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
|
|
|