Moving to a new SAN

I have a established cluster that I have to move to
another SAN. Any words of wisdom?
Test, test, test. How are performing the move.
Good luck
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"cgunner" <anonymous@.discussions.microsoft.com> wrote in message
news:02d501c4abd3$ecd50890$a301280a@.phx.gbl...
>I have a established cluster that I have to move to
> another SAN. Any words of wisdom?
|||We are going to go by Q269196 but this does not address
the new LUN's that will have to be setup on the new SAN.
I am mostly concerned with the QUORUM drive. I want to
try to keep the cluster in one piece. Do you know any
other KB's to take into account?

>--Original Message--
>Test, test, test. How are performing the move.
>Good luck
>Cheers,
>Rod
>MVP - Windows Server - Clustering
>http://www.nw-america.com - Clustering
>http://msmvps.com/clustering - Blog
>"cgunner" <anonymous@.discussions.microsoft.com> wrote in
message
>news:02d501c4abd3$ecd50890$a301280a@.phx.gbl...
>
>.
>
|||Sure see
http://www.microsoft.com/resources/d...luad_pr_69.asp
to move the Quorum.
Or do it this way http://support.microsoft.com/?id=280353
Or start all over again - http://support.microsoft.com/?id=245762
More on the quorum http://support.microsoft.com/?id=280345
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"cgunner" <anonymous@.discussions.microsoft.com> wrote in message
news:0d6101c4ac8f$a8f53700$a301280a@.phx.gbl...[vbcol=seagreen]
> We are going to go by Q269196 but this does not address
> the new LUN's that will have to be setup on the new SAN.
> I am mostly concerned with the QUORUM drive. I want to
> try to keep the cluster in one piece. Do you know any
> other KB's to take into account?
> message
|||We just did this on an active / active cluster. If you are using EMC SAn,
they have tools to migrate everything, and to make sure the luns are the
same, and properly assigned to your hosts. You can alos get the data
mirrored, and in sync long before you actually cut over to the new SAN. Our
migration went very smoothly.
"Rodney R. Fournier [MVP]" wrote:

> Sure see
> http://www.microsoft.com/resources/d...luad_pr_69.asp
> to move the Quorum.
> Or do it this way http://support.microsoft.com/?id=280353
> Or start all over again - http://support.microsoft.com/?id=245762
> More on the quorum http://support.microsoft.com/?id=280345
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "cgunner" <anonymous@.discussions.microsoft.com> wrote in message
> news:0d6101c4ac8f$a8f53700$a301280a@.phx.gbl...
>
>
sql

Moving SQL to a partition

I need to move an SQL database from the C: partition to
another partition. Is there a way to do it that will not
cause errors?
Is there a way to increase the partition size without a
full re-intall of Windows Server 2000?
Brice
hi Brice,
"Brice Sutliff" <bsutliff@.socfc.org> ha scritto nel messaggio
news:088701c4e465$90d674a0$a301280a@.phx.gbl
> I need to move an SQL database from the C: partition to
> another partition. Is there a way to do it that will not
> cause errors?
> Is there a way to increase the partition size without a
> full re-intall of Windows Server 2000?
> Brice
Partition Magic probably can do the trick, for increase partition sizes...
as long as moving databases, please have a look at
http://support.microsoft.com/?id=314546 and
http://www.support.microsoft.com/?id=224071
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Moving Published db to different server (cannot reinitialize)

When I've talked about nosync initialization, this was
connected with subscribers. When moving the publisher to
another server of a different name I have always scripted
out the publication, edited it to alter the servernames
then run the script on the new publisher and
reinitialized. If the tables are large, you could
compress the BCP files (winzip9.0) with an alternative
snapshot location being used for the subscription, or
DVDs etc. BTW we have a 35GB database, 20GB of which is
snapshotted occasionally and using fileshares the whole
process takes 2 hours or so.
HTH,
Paul Ibison
In article <18a501c4dd44$b0da7d00
$a501280a@.phx.gbl>, Paul.Ibison@.Pygmalion.Com
says...
> When I've talked about nosync initialization, this was
> connected with subscribers. When moving the publisher to
> another server of a different name I have always scripted
> out the publication, edited it to alter the servernames
> then run the script on the new publisher and
> reinitialized. If the tables are large, you could
> compress the BCP files (winzip9.0) with an alternative
> snapshot location being used for the subscription, or
> DVDs etc. BTW we have a 35GB database, 20GB of which is
> snapshotted occasionally and using fileshares the whole
> process takes 2 hours or so.
> HTH,
> Paul Ibison
>
how long does it take to distribute that snapshot
to a wan subscriber?
Ok on the compression part. Basically I've run
into where windows wont compress a bcp file over
2gb. I guess that is why you are saying use
winzip or rar. Do a normal snapshot to an
alternate location. Then compress those bcp
files, send those compressed bcp files over the
wan link to the subscriber. They unzip them and
insert that information. They I would "push the
new subscription" at that point? How do i keep
the distribution agent from trying to push the
original snapshot that was made , and only push
the data that is in the log reader?
I guess I could move the snapshot files so it
will just move on to the data that is in the log
reader?
Thanks for the help on this paul.
-comb