Move a 5.1B cluster to a different EMC SAN

From: Mark Schubert (Mark.Schubert_at_COGITA.COM)
Date: 08/10/05

  • Next message: Thomas Edward Kempster: "KZPEA and DS20E" 
    Date: Wed, 10 Aug 2005 15:24:08 +0930
To: tru64-unix-managers@ornl.gov

    Hi,

    We want to move a 5.1B cluster from one EMC SAN to another EMC SAN. Is
    it possible to do this without having to reinstall unix?

    We know we can duplicate the devices on the new SAN and also copy the
    data from the old SAN to the new SAN without using the hosts. The issue
    is how and where do we point unix to the new devices?

    I expect we should be able to change a few pointers to point to the new
    devices and then boot genvmunix and rebuild the kernel.

    Is this possible?

    TIA

    Mark.

  • Next message: Thomas Edward Kempster: "KZPEA and DS20E"

    Relevant Pages

    • Re: SAN attached storage
      ... You need to install the Multi-Path IO feature for Windows 2008 and then the multipath driver (PowerPath if it is an EMC SAN) from the vendor. ... Principal SQL Infrastructure Consultant ... I would like to remove the ghosted disk appearance. ...
      (microsoft.public.sqlserver.clustering)
    • Re: Moving to a new SAN
      ... We just did this on an active / active cluster. ... If you are using EMC SAn, ... >> the new LUN's that will have to be setup on the new SAN. ...
      (microsoft.public.sqlserver.clustering)
    • SAN setup and configuration
      ... My company is going to purchase a emc SAN ... storage and i need to prepare myself to learn the SAN ...
      (SunManagers)
    • Re: Clustering Newbie - SAN Advice
      ... A SAN generally has gigabtes of cache and uses large internal block sizes ... The SAN or Smart array will dictate what internal connection the disks have. ... Senior SQL Infrastructure Consultant ... single-instance cluster. ...
      (microsoft.public.sqlserver.clustering)
    • Re: Correct sequence to present new SAN disks to W2K3 cluster
      ... then SAN? ... single storage group for your cluster you won't be able to do step 3 below ... Delete the resources for the new disks from the cluster, ... I'd move the resources all to a single node and pause the passive node ...
      (microsoft.public.windows.server.clustering)