Re: Moving to a New SAN

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Pat Hall (PatHall_at_discussions.microsoft.com)
Date: 03/24/05 

Date: Thu, 24 Mar 2005 10:35:02 -0800

We have to increase the size of the Quorum disk? I don't understand why when
we use the EMC SAN a 16.5 GB is large enough but on an IBM SAN we need a much
larger Quorum (500 MB).

"Russ Kaufmann" wrote:

> "Pat Hall" <PatHall@discussions.microsoft.com> wrote in message
> news:A861D454-65E9-4788-B59B-A1FAAEE38E3C@microsoft.com...
> > We are planning on moving our SQL Cluster (Win2k3 active/passive) using
> > MSCS
> > from an EMC SAN to an IBM SAN (FastT). 2 questions:
> > 1) Can the Quorum disk
> > stay
> > at 16.5 MB like it is on the EMC SAN or do we need to increase the size to
> > the 500 MB as recommended? The only thing on that drive is the cluster
> > info.
>
> I would recommend changing it on the new SAN.
>
> > 2) Have looked a sever posts and am concerned that our
> > plans
> > may not work like we think. We are going to:
> > a) Make sure the nightly
> > backup
> > ran for each server
> > b) Shut down the servers and install an extra HBA in each
>
> It may be easier to just add the new switches for the new SAN into the
> fabric rather than adding a new HBA. With both SAN devices in the same
> fabric, it won't require cracking the server cases.
>
> > c) Bring the servers up and verify that they can see the
> > correct LUNs
>
> If you add the SAN to the fabric, all you will need to do is rescan for
> drives in disk management, assuming the proper WWNs are added to make the
> new LUNs visible to the nodes.
>
> > d) Shut down the services on each machines
>
> No need to do this unless you are talking about services that are locking
> files.
>
> > e) Copy the files from their current EMC LUN to the IBM LUN (I'd like to
> > do
> > a mirror and then break, we will see which works best, robocopy is our
> > fallback).
>
> I have done both. I like the Mirror and break solution.
>
> > f) Break mirrors (if we do it via mirroring)
> > g) Change drive letters so the IBM LUN now has the one previously used by
> > the EMC drive
> > h) Bring up the services and make sure that everything comes up properly.
> >
> > Are we going to have problems?
>
> The quorum is easiest to move by using the GUI and changing from the drive
> on the EMC to the IBM. If yuo are trying to get to the letter Q (EMC has
> Q:), then I would use one of the LUNs on the IBM as a temp home for the
> quorum and move it there, remove the disk resource for the Q: and then
> reletter it in the OS, and then create a new Q: disk resource on the IBM and
> move from the temporary home to the new Q:.
>
>
>

Relevant Pages

  • Re: Boot AIVX from EMC Clariion
    ... > We have several p670's that are SAN Attached to an EMC Clariion. ... SAN disk before attempting the installation. ...
    (comp.unix.aix)
  • Re: MSCS DR
    ... advice I am getting from EMC at this moment in time!!!!! ... One more thing if the geocluster we were planning is on the HCL would I ... have to dump the disk signatures as suggested earlier by Mark to get ... SAN array. ...
    (microsoft.public.windows.server.clustering)
  • Re: SAN Booting p-Series from EMC storage
    ... We looked at doing this (not with EMC but with IBM Shark). ... disks that are on the SAN. ... Even though you mirror from one disk to the other... ... > Our standard has been 4 internal drives per system. ...
    (comp.unix.aix)
  • Re: MSCS DR
    ... The kit is on the Windows HCL (EMC Clariion and Brocade) Is there a Geo ... Cluster HCL, can you point me to it? ... if you run dumpcfg.exe to document the current Disk signatures, ... SAN array. ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster Disk re-config
    ... Once you create a new physical disk resource in the cluster admin you can change your quorum drive. ... You're going to be doing a similar process to move the quorum even though you are on the same SAN: ...
    (microsoft.public.windows.server.clustering)