How to migrate a cluster windows 2003 with EMC OM

Check the guide for 3.9.  I believe the changes between 3.9 and 3.10 were minor enough that they didn't publish a new guide at this time.  However, there are Release Notes for each version which should be reviewd as well.  The 3.12 guide would not be appropriate for OM version 3.10. 

The "Complete Migration" is only available in version 3.12.

Thanks for your replies guys !!, one more question.

Some will have a copy of the manual version 3.9 or 3.10 to do the test in my cluster.

I have only 3.12

Best regards !!

You may find the 3.9 guide by following these menu choices from the main Powerlink page.

Home > Support > Technical Documentation and Advisories > Software ~ J-O ~ Documentation > Open Migrator/LM > General Reference

Hi, after to much tests, at last i know hot migrate a cluster with EMC OM

Thanks to all for your help and answers !!!

best regards

You will find step-by-step instructions in the OM product guide.

In PowerLink go to: Home > Support > Technical Documentation and Advisories > Software ~ J-O ~ Documentation > Open Migrator/LM > Installation/Configuration

It really depends on which version of OM you use. I recommend you use 3.12 since it's more cluster friendly compared to the older versions.

Can you  please let me know the steps to follow for cluster migration using OM. do we have reboot he active . with passive node shut down , after we hit the migration complete in the OM. can you please assist.

hi Talijic,

I followed these below steps with version 3.12 (OM)

Below are the steps that were followed while migration using open migrator for this sql cluster.

Step 1 to 5 was successfully implemented, but as soon as we remove the old San from the host we lost the connectivity to the new volume. Do you see anything I missed in order for the migration to fail?

1. Assign the new san to both the node on the cluster (active/passive)

2. reboot he active node which has the OM install after the filter divers are attached.

3, After the reboot start the migration

4, once the migration is done , complete the migration and shut down the passive node , so the active node can be rebooted,

5. Once the active node comes up the drive letters will be swapped to the new volumes.

6. Then rebuilt the Quorum disk.

Run powermt display dev=all to make sure that the data resides on the new array. If you are testing the failover to another host the quorum drive will be moved as well. You need to move the quorum drive to the new array as well. If the quorum drive is not on the new SAN the cluster will go down once you remove the old array.

Tio migrate the quorum drive go to: http://support.microsoft.com/kb/280353

Did you configure the quorum drive to be on the new array?

If the data definitely lives on the new array, including data and quorum LUNs, removing the old SAN should not cause any issues. Make sure that both hosts, active and passive, are logged in and registered on the new array and see the same LUNs.

Whats the scenario , if we have removed all the data disk and quorum from the old san , with passive node down , do this this will still cause the data be not accesable on the new san we have migrated to on the active node.

what  happens , if i remove the data and quorum disk from old san just on the active cluster , with passive completely shut down. Do this still cause the data not accessible on the active node ( with quorum not yet configured & passive node is down).

No it doesn't. If you are performing those actions while the passive node is down the active node will remain online as long as you verified that all storage has been migrated to the new array.