manual failover procedure for patching

,I know the procedure by heart to manually failover my SQL cluster to the
other node, patch, move it back , test, etc. But does someone have a
documented procedure they would like to share that they use in patching so i
can make sure i am not leaving anything out??????

Sounds like you are already on track.

[General doc for maintenance]
How to install service packs in a cluster
http://support.microsoft.com/kb/174799

Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Willy,

Something like this?
http://support.microsoft.com/kb/174799

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> ,I know the procedure by heart to manually failover my SQL cluster to
> the other node, patch, move it back , test, etc. But does someone have
> a documented procedure they would like to share that they use in
> patching so i can make sure i am not leaving anything out??????
>

Actually i have alwasys been doing a initate failure on the SQL instance till
it moves over to the passive member. Then patch the previously active side,
initiate failure till it moves back. if it works great, if not move it back.
and figure out what happened. This is the first i have seen using a move
groups for a SQL cluster. Also i am using a Windows 2003 cluster not 200 or
nt4. so is there a newer procedure????

"Meinolf Weber" wrote:

> Hello Willy,
>
> Something like this?
> http://support.microsoft.com/kb/174799
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > ,I know the procedure by heart to manually failover my SQL cluster to
> > the other node, patch, move it back , test, etc. But does someone have
> > a documented procedure they would like to share that they use in
> > patching so i can make sure i am not leaving anything out??????
> >
>
>
>

You mean other than the procedure in 174799?

I don't think I've ever heard of anyone initiating a failure of a resource
just to perform a move group, other than in a test environment/scenario.
Seems a bit...excessive. I'd stick with the move group as this performs a
clean stop of SQL.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"Willy" <> wrote in message
news:0872C473-E104-4516-A327-...
> Actually i have alwasys been doing a initate failure on the SQL instance
till
> it moves over to the passive member. Then patch the previously active
side,
> initiate failure till it moves back. if it works great, if not move it
back.
> and figure out what happened. This is the first i have seen using a move
> groups for a SQL cluster. Also i am using a Windows 2003 cluster not 200
or
> nt4. so is there a newer procedure????
>
> "Meinolf Weber" wrote:
>
> > Hello Willy,
> >
> > Something like this?
> > http://support.microsoft.com/kb/174799
> >
> > Best regards
> >
> > Meinolf Weber
> > Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
> > no rights.
> > ** Please do NOT email, only reply to Newsgroups
> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >
> >
> > > ,I know the procedure by heart to manually failover my SQL cluster to
> > > the other node, patch, move it back , test, etc. But does someone have
> > > a documented procedure they would like to share that they use in
> > > patching so i can make sure i am not leaving anything out??????
> > >
> >
> >
> >