dbTalk Databases Forums  

Moving the quorum to another LUN on the SAN

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Moving the quorum to another LUN on the SAN in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mark Broadbent
 
Posts: n/a

Default Moving the quorum to another LUN on the SAN - 02-06-2009 , 08:41 AM






anyone got any useful documents or tips on this? Need to move the Quorum on
a 4 node 64 bit cluster.

Thanks,

Mark.



Reply With Quote
  #2  
Old   
John Toner [MVP]
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-06-2009 , 03:45 PM






Easiest way would be to just add the new LUN to the cluster and then use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote

Quote:
anyone got any useful documents or tips on this? Need to move the Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.





Reply With Quote
  #3  
Old   
Mark Broadbent
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-07-2009 , 12:52 AM



thanks john, I had stumbled on that one and yes it does look incredibly
easy. Worked a treat on my test system too.
One problem that i have is that my quorum drive also has msdtc using it, so
that procedure looks a bit of a mare (so I am going to have to do a two
phase process in order to retain original drive letter for that).

Thanks for your help.

Regards,

Mark.
"John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote

Quote:
Easiest way would be to just add the new LUN to the cluster and then use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:O%234IGkGiJHA.1780 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
anyone got any useful documents or tips on this? Need to move the Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.







Reply With Quote
  #4  
Old   
Geoff N. Hiten
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-08-2009 , 05:58 PM



I would break, uninstall, then reinstall MSTDC rahter than play the drive
letter rename game. Of course, that depends on the maintenance window you
have.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote

Quote:
thanks john, I had stumbled on that one and yes it does look incredibly
easy. Worked a treat on my test system too.
One problem that i have is that my quorum drive also has msdtc using it,
so that procedure looks a bit of a mare (so I am going to have to do a two
phase process in order to retain original drive letter for that).

Thanks for your help.

Regards,

Mark.
"John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message
news:OVjU7QKiJHA.3904 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
Easiest way would be to just add the new LUN to the cluster and then use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:O%234IGkGiJHA.1780 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
anyone got any useful documents or tips on this? Need to move the Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.








Reply With Quote
  #5  
Old   
Jasen
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-09-2009 , 08:41 AM



We just upgraded our SAN and I have been doing exactly what you are trying on
all my SQL clusters. Goeff is right on about the MSDTC, I have always placed
it into its own cluster group; the easiest way to move it was break,
uninstall, reinstall using the new LUN. The quorum was easy as well, but you
have to do the process twice is you want to keep the same drive letter; that
is easy enough with cluadmin though (note your dependency structure so you
can rebuild them). We use Veritas SFW5.1, if you are interested in the exact
steps let me know and I can help with documentation.

"Geoff N. Hiten" wrote:

Quote:
I would break, uninstall, then reinstall MSTDC rahter than play the drive
letter rename game. Of course, that depends on the maintenance window you
have.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:up3goCPiJHA.500 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
thanks john, I had stumbled on that one and yes it does look incredibly
easy. Worked a treat on my test system too.
One problem that i have is that my quorum drive also has msdtc using it,
so that procedure looks a bit of a mare (so I am going to have to do a two
phase process in order to retain original drive letter for that).

Thanks for your help.

Regards,

Mark.
"John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message
news:OVjU7QKiJHA.3904 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
Easiest way would be to just add the new LUN to the cluster and then use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:O%234IGkGiJHA.1780 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
anyone got any useful documents or tips on this? Need to move the Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.









Reply With Quote
  #6  
Old   
Mark Broadbent
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-10-2009 , 02:55 PM



yeah I agree with both of you.In the end I did the two phase approach last
Saturday.

What I did was:-
offlined dtc
added in new disk resource across cluster
moved quorum to another existing disk resource
changed drive letter of old quorum/ dtc drive
changed drive letter of new disk resource to what old quorum letter was
did a robocopy of dtc directory with permissions to new resource.
offlined old disk resource
brought online dtc
moved quorum to new disk resource
failover testing/ tidied up

....not too bad really to be honest. Yes Geoff I'm sure I've attempted to
move DTC in the past to a lot of fustration and decided that it isnt worth
the aggrovation.
Jasen your point about the seperate cluster group is probably a good idea
(something which I have thought about before in fact) but this time was
easier to do a like for like swap.

Thanks for your comments.

"Jasen" <Jasen (AT) discussions (DOT) microsoft.com> wrote

Quote:
We just upgraded our SAN and I have been doing exactly what you are trying
on
all my SQL clusters. Goeff is right on about the MSDTC, I have always
placed
it into its own cluster group; the easiest way to move it was break,
uninstall, reinstall using the new LUN. The quorum was easy as well, but
you
have to do the process twice is you want to keep the same drive letter;
that
is easy enough with cluadmin though (note your dependency structure so you
can rebuild them). We use Veritas SFW5.1, if you are interested in the
exact
steps let me know and I can help with documentation.

"Geoff N. Hiten" wrote:

I would break, uninstall, then reinstall MSTDC rahter than play the drive
letter rename game. Of course, that depends on the maintenance window
you
have.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:up3goCPiJHA.500 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
thanks john, I had stumbled on that one and yes it does look incredibly
easy. Worked a treat on my test system too.
One problem that i have is that my quorum drive also has msdtc using
it,
so that procedure looks a bit of a mare (so I am going to have to do a
two
phase process in order to retain original drive letter for that).

Thanks for your help.

Regards,

Mark.
"John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message
news:OVjU7QKiJHA.3904 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
Easiest way would be to just add the new LUN to the cluster and then
use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:O%234IGkGiJHA.1780 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
anyone got any useful documents or tips on this? Need to move the
Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.











Reply With Quote
  #7  
Old   
Jasen
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-10-2009 , 04:58 PM



Glad it worked for you! I migrated another one yesterday, works like a charm!

"Mark Broadbent" wrote:

Quote:
yeah I agree with both of you.In the end I did the two phase approach last
Saturday.

What I did was:-
offlined dtc
added in new disk resource across cluster
moved quorum to another existing disk resource
changed drive letter of old quorum/ dtc drive
changed drive letter of new disk resource to what old quorum letter was
did a robocopy of dtc directory with permissions to new resource.
offlined old disk resource
brought online dtc
moved quorum to new disk resource
failover testing/ tidied up

....not too bad really to be honest. Yes Geoff I'm sure I've attempted to
move DTC in the past to a lot of fustration and decided that it isnt worth
the aggrovation.
Jasen your point about the seperate cluster group is probably a good idea
(something which I have thought about before in fact) but this time was
easier to do a like for like swap.

Thanks for your comments.

"Jasen" <Jasen (AT) discussions (DOT) microsoft.com> wrote in message
news:1B1A8178-0CEE-4A33-8215-F2F56734ED0C (AT) microsoft (DOT) com...
We just upgraded our SAN and I have been doing exactly what you are trying
on
all my SQL clusters. Goeff is right on about the MSDTC, I have always
placed
it into its own cluster group; the easiest way to move it was break,
uninstall, reinstall using the new LUN. The quorum was easy as well, but
you
have to do the process twice is you want to keep the same drive letter;
that
is easy enough with cluadmin though (note your dependency structure so you
can rebuild them). We use Veritas SFW5.1, if you are interested in the
exact
steps let me know and I can help with documentation.

"Geoff N. Hiten" wrote:

I would break, uninstall, then reinstall MSTDC rahter than play the drive
letter rename game. Of course, that depends on the maintenance window
you
have.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:up3goCPiJHA.500 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
thanks john, I had stumbled on that one and yes it does look incredibly
easy. Worked a treat on my test system too.
One problem that i have is that my quorum drive also has msdtc using
it,
so that procedure looks a bit of a mare (so I am going to have to do a
two
phase process in order to retain original drive letter for that).

Thanks for your help.

Regards,

Mark.
"John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message
news:OVjU7QKiJHA.3904 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
Easiest way would be to just add the new LUN to the cluster and then
use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:O%234IGkGiJHA.1780 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
anyone got any useful documents or tips on this? Need to move the
Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.











Reply With Quote
  #8  
Old   
Geoff N. Hiten
 
Posts: n/a

Default Re: Moving the quorum to another LUN on the SAN - 02-10-2009 , 08:07 PM



Glad everything worked out.

I don't have to be right, just helpful.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Jasen" <Jasen (AT) discussions (DOT) microsoft.com> wrote

Quote:
Glad it worked for you! I migrated another one yesterday, works like a
charm!

"Mark Broadbent" wrote:

yeah I agree with both of you.In the end I did the two phase approach
last
Saturday.

What I did was:-
offlined dtc
added in new disk resource across cluster
moved quorum to another existing disk resource
changed drive letter of old quorum/ dtc drive
changed drive letter of new disk resource to what old quorum letter was
did a robocopy of dtc directory with permissions to new resource.
offlined old disk resource
brought online dtc
moved quorum to new disk resource
failover testing/ tidied up

....not too bad really to be honest. Yes Geoff I'm sure I've attempted to
move DTC in the past to a lot of fustration and decided that it isnt
worth
the aggrovation.
Jasen your point about the seperate cluster group is probably a good idea
(something which I have thought about before in fact) but this time was
easier to do a like for like swap.

Thanks for your comments.

"Jasen" <Jasen (AT) discussions (DOT) microsoft.com> wrote in message
news:1B1A8178-0CEE-4A33-8215-F2F56734ED0C (AT) microsoft (DOT) com...
We just upgraded our SAN and I have been doing exactly what you are
trying
on
all my SQL clusters. Goeff is right on about the MSDTC, I have always
placed
it into its own cluster group; the easiest way to move it was break,
uninstall, reinstall using the new LUN. The quorum was easy as well,
but
you
have to do the process twice is you want to keep the same drive letter;
that
is easy enough with cluadmin though (note your dependency structure so
you
can rebuild them). We use Veritas SFW5.1, if you are interested in the
exact
steps let me know and I can help with documentation.

"Geoff N. Hiten" wrote:

I would break, uninstall, then reinstall MSTDC rahter than play the
drive
letter rename game. Of course, that depends on the maintenance window
you
have.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:up3goCPiJHA.500 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
thanks john, I had stumbled on that one and yes it does look
incredibly
easy. Worked a treat on my test system too.
One problem that i have is that my quorum drive also has msdtc using
it,
so that procedure looks a bit of a mare (so I am going to have to do
a
two
phase process in order to retain original drive letter for that).

Thanks for your help.

Regards,

Mark.
"John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message
news:OVjU7QKiJHA.3904 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
Easiest way would be to just add the new LUN to the cluster and
then
use
MSCS to move the quorum to a new drive. See
http://support.microsoft.com/kb/280353 for more details

Regards,
John

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

"Mark Broadbent" <spam (AT) nospam (DOT) com> wrote in message
news:O%234IGkGiJHA.1780 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
anyone got any useful documents or tips on this? Need to move the
Quorum
on
a 4 node 64 bit cluster.

Thanks,

Mark.












Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.