Re: Moving Cluster to new SAN

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: MC (MC_at_discussions.microsoft.com)
Date: 03/07/05 

Date: Mon, 7 Mar 2005 08:23:04 -0800

John:

Thanks for the response. I researched this after my post and I now see the
importance of the signature manipulation. Would you recommend doing this
via the ClusterRecovery or any other particular tool?

"John Toner [MVP]" wrote:

> Your plan (as written) will not work. MSCS is highly dependent upon the disk
> signatures and you will not get MSCS back up again without reinstalling from
> scratch if you cannot restore the signatures.
>
> If this were my cluster, I would:
>
> 1) Change the IP addresses of the cluster NICs/resources (if necessary).
> Follow directions in the following KB article for details:
> http://support.microsoft.com/kb/230356
> 2) Disable cluster disk driver on both nodes.
> 3) Move the servers to the new location...alter zoning, masking, etc.
> 4) Power up one node and restore the disk signatures to the new SAN volumes.
> I would reboot after making these changes.
> 5) Verify drive letter assignments are correct for the disks on BOTH nodes.
> (power down Node1 when verifying on Node2).
> 6) Restore data to the new cluster volumes
> 7) Re-enable cluster disk driver and reboot.
>
> No need to evict nodes IMO.
>
> Hope this helps.
>
> Regards,
> John
>
> "MC" <MC@discussions.microsoft.com> wrote in message
> news:0CD53D6C-21C5-42BC-B1A2-8B1D66D38D67@microsoft.com...
> > I need to move a Netbackup Master server on a WIN2K3 2-node cluster to a
> new
> > SAN in a physically different location. I will not have dual SAN/array
> > connectivity for the move.
> >
> > My plan is to:
> >
> > 1) Evict the idle node, and thus run the cluster as a single-node cluster
> > 2) Disable cluster services on each node
> > 3) Physically relocate the cluster servers, change IP addresses (hostnames
> > will remain the same) perform SAN zoning, lun-masking, etc., for the new
> > Quorum LUN and other shared disk resources
> > 4) Restart cluster services on single node, and bring the cluster up as a
> > single-node cluster
> > 5) Re-join the evicted node to the cluster
> >
> > Will I need to preserve the quorum db, and disk signatures under this
> > scenario? Or, should the cluster come back up with new logs, db, etc.
> > provided it sees the quorum drive as before ("Q: Drive)? Also, is there a
> > better way to do this?
> >
> > Thanks in advance for any assistance.
>
>
>

Relevant Pages

  • SUMMARY: restore a crashed test cluster
    ... I have a 5.1B cluster with dupatch 3. ... the quorum disk. ... and restore the following ... I then go to the boot prompt again, and try to start the first member by ...
    (Tru64-UNIX-Managers)
  • Re: Cannot delete file in the virtual disk.
    ... > it did lose all attributes when i did a Legato restore. ... >> mentioned that you have restarted the cluster, I am assuming this is NOT ... Ceck to make sure thar the disk is properly inserted, ... >>> that you are connected to the internet or your network, ...
    (microsoft.public.windows.server.clustering)
  • RE: Cannot delete file in the virtual disk.
    ... No processes is using it, and this is a Production system, I had a few hours ... I have tryed to do a restore again, but the file is "not accessable" though ... I'm not in mood to rebuild the cluster just because of this file, ... > NTFS) disk to your quorum ...
    (microsoft.public.windows.server.clustering)
  • Re: Moving Cluster to new SAN
    ... MSCS is highly dependent upon the disk ... scratch if you cannot restore the signatures. ... Change the IP addresses of the cluster NICs/resources. ... Disable cluster disk driver on both nodes. ...
    (microsoft.public.windows.server.clustering)
  • RE: Restoring cluster node to standalone server with no shared storage
    ... have everything setup but your disk signatures are not correct. ... service in conjuction with the cluster disk driver identifies which disks are ... in the cluster based on disk signatures or. ... > can restore the filesystem and System State, but the Cluster service fails to ...
    (microsoft.public.windows.server.clustering)