Re: Moving to a New SAN

From: Russ Kaufmann (russ_at_exchangemct.com)
Date: 03/23/05


Date: Wed, 23 Mar 2005 16:12:23 -0700


"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: Exchange 2007 LUNs on a SAN
    ... This means that all drives in the OS are really striped across all the ... disks on our SAN. ... separate all the LUNs? ... Putting a single database on a single LUN is generally a good idea due ...
    (microsoft.public.exchange.setup)
  • Re: How to verify/fix High Disk Read Latencies in Exch2003 ?
    ... Do they all map LUNs to your SAN? ... > wondering how the disk could be highly utilized if I have no users ... >> following formulats for the RAID type of each LUN: ...
    (microsoft.public.exchange.admin)
  • Re: Im giving up computers if this is the future.
    ... > Intel 80x86 family, so it doesn't change my complaints with the Intel ... Commadore aimed straight for the mass market from the beginning)... ... TX-0 that the MIT Tech Model Railroad club worked on and that IBM old ... average PC only can handle a limited number of drives? ...
    (comp.os.vms)
  • Re: Western Digital hard drives are garbage
    ... The 75GXP series IBM drives used a glass platter instead of the ... they don't use the same technology and materials now. ... The whole reason they tried the glass platters in the first place was to ...
    (comp.os.linux.hardware)
  • Re: ingres locations and SAN
    ... Companies will often take the largest disk drives possible for the SAN ... System Administrators will typically make everything RAID 5 ... to get the faster drives for the Ingres configuration and won. ...
    (comp.databases.ingres)