Re: Move cluster data drives to new cluster

All of the answers depend on how you are copying the data from your old SAN
to the new SAN. If the disk signatures are being copied, you pretty much do
not need to do anything at the cluster level other than take things offline
while the SAN swap is occurring.

Assuming you're doing some sort of backup/restore operation, you'd need to
add the new SAN disks in as new cluster disk resources.

I'd recommend reviewing Russ's blog for more details on this:

http://msmvps.com/blogs/clusterhelp/archive/2005/08/05/moving-a-cluster-to-a-new-san-original-posted-jul-22-2005.aspx


Regards,
John

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

"Mike O." <MikeO@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:157A9841-092E-4B64-9281-A18D80ED8C5E@xxxxxxxxxxxxxxxx
What I'm looking for is what I should do on the Windows side before
removing
them from the cluster group on the SAN. I assume I need to take the
physical
disk resource off line, but shoud I delete the resource from the existing
cluster before moving it at the SAN level?

Then once I add it to the new cluster group on the SAN, do I just add it
as
cluster resources using the steps in KB555312? That article is the steps
I
use when I add a new disk to a cluster, but I wasn't sure if that's the
same
process to add a drive that already has data.

Will the transferred drive automatically pick up the same drive letter, or
do I need to re-assign the letter in disk admin after presenting it to the
new cluster?


Mike O.

"John Toner [MVP]" wrote:

There shouldn't be any issues doing this. Just unmask the storage from
the
old cluster and present the disks to the new cluster nodes. Once the
storage
is presented, you should just be able to add these disks as cluster disk
resources.

Regards,
John

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

"Mike O." <MikeO@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA60143C-45E3-49E4-AA3E-139E022B9D92@xxxxxxxxxxxxxxxx
We currently have a two node Windows 2003 R2 32 bit cluster. There
are
about 6 data "drives" in it, running on our EMC SAN.

We're wanting to replace the cluster with newer hardware. I've set up
a
new
2003 R2 x64 two node cluster, and I want to move the data drives from
the
existing cluster to the new one. I'm just wanting to move the data
drives, I
have a new quorum drive on the new cluster.

The total of all the drives is about 4TB, so I a backup/restore isn't
really
an option , I just want to move the SAN resources from the old cluster
to
the
one.

The SAN side of the move isn't an issue, I can move the LUN's from the
old
group to the new one, but I'm looking for some information about having
the
new cluster properly recognized the transferred "drive"

I've done some searching, but most of what I'm finding is moving the
data
from one SAN to another, but keeping the same server hardware.

Any suggestions would be appreciated.





.

Relevant Pages

  • Re: Correcting corrupt $MFT on shared clustered disk.
    ... against a cluster disk. ... handles against the disk. ... After digging into it I figured out I didn't need the extended maintenance mode and figured out the rest of the article. ... If I assign drives for different areas, I figure we'll eventually end up with the same problem we had before: some areas running out of space and others with space to spare. ...
    (microsoft.public.windows.server.clustering)
  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... Our san guy is ... completely forget about is that moving the head on the disk is the slowest ... the drives that were being assigned to the SQL machine. ... I mean the binn folder which contains the sql server executable among ...
    (microsoft.public.sqlserver.setup)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... Also, the problem I'm having is on the smaller basic disk, the GPT one is ... When I do run chkdsk, are there any special issues with the cluster? ... The three drives are a 500MB for the quorum, ...
    (microsoft.public.windows.server.general)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)
  • Re: Clustering Newbie - SAN Advice
    ... You are right to observe that we probably don't want cost of full-blown SAN ... piggy backing them on some sort of shared disk array. ... The disks in the array doesn't need anything special. ... single-instance cluster. ...
    (microsoft.public.sqlserver.clustering)
Quantcast