Microsoft Windows Cluster Migration by using EMC PowerPath Migration Enabler (PPME)

In previous post we learnt how to migrate data on Microsoft Windows by using PowerPath Migration Enabler (PPME). In this post, I will show you how to perform the data migration on Microsoft Windows Cluster by using PPME. The physical system diagram as below.


SQL Cluster Node1 – Microsoft Windows 2008 R2 SP1 + SQL Server 2008 R2 SP2 and installed EMC PowerPath 6.0 SP2
SQL Cluster Node2 – Microsoft Windows 2008 R2 SP1 + SQL Server 2008 R2 SP2 and installed EMC PowerPath 6.0 SP2
Source Array – EMC CLARiiON CX4-120c (FLARE 30)
Target Array – EMC VNX5200 (Block, VNX OE 32)
Brocade 300B (FOS 6.2) x 2

The following is the migration procedure by using PowerPath Migration Enabler,
1. Firstly assign one target LUN (equal or larger capacity with source LUN) which is shared to each SQL Cluster Node.
2. Note the names of your source and target devices.
3. List Cluster resource groups and configure one of your cluster resources group for migration
4. Setup the cluster migration session by PowerPath Migration Enabler.
5. Starts the cluster migration session.
6. After the cluster migration is successfully completed and commit the LUN swapping.
7. Cleanup the host copy session.
8. Remove the source LUN in SQL server.

You can see the Cluster Disk is Volume S in Failover Cluster Manager.



Assign one target LUN which is shared to each SQL Cluster Node, Disk 2 is the target location.



Executes the PowerPath command “powermt display dev=all”, you can see Pseduo name in the output result. harddisk1 is the source LUN, harddisk2 is the target LUN.



Executes PowerPath command “powermigcl display -all” to list out Cluster resource groups.

NOTE: For help, you can execute command “powermig help”


Configure one of SQL cluster resources group for data migration, then list out Cluster resource groups again. You can see the Status of SQL Server (MMSQLC) is Configured.


Now you will notice that new cluster resource is added named PPME <Disk_resource_name>  into configured cluster resource group.


And each Cluster Disk is dependent on the PPME resource.



Now setup the migration handles c5 for the cluster disks in cluster resource group SQL Server. Executes the PPME command to setup the migration session, “powermig setup -src <source_pseudo> -tgt <target_pseudo> -techType hostcopy -cluster -no”



Start the migration c5



When the migration is successfully completed, you can see the state in sourceSelected.


NOTE : Since we are migrating physical disks in a MSCS environment there is no need to use the “SelectTarget” option with powermigcl migrations.We can commit the migrations immediately once the sun is 100% complete

Now you can commit the migration session.



NOTE: You cannot fallback after commit the migration session.

The SQL service is still running and non-disruptive during commit the migration.


In this moment, you can execute PowerPath command again “powermt display dev=all”, you can see the harddisk1 change to be target LUN, harddisk2 change to be source LUN.



Then you can cleanup the migration session, powermig cleanup -handle <id>


After cleanup the session, the PPME cluster resource also is removed in Cluster resources group.


Optional – SQL Cluster failover test

You can move the SQL service to Node 2. The SQL service can successfully failover to Node 2.



Finally you can remove the source LUN in SQL server, the data migration is completed.

If you have questions about PowerPath Migration Enabler Administration, you can look up the information material at


About Victor Wu

My name is Victor. I hope to be your friend.
This entry was posted in EMC. Bookmark the permalink.

2 Responses to Microsoft Windows Cluster Migration by using EMC PowerPath Migration Enabler (PPME)

  1. Ian Grace says:

    Hi. You have forgotten to document the final step which is to unconfigure (powermigcl unconfig) the cluster group/s. The PPME Cluster Disk resource/s only disappear after this step and not as suggested from the powermig cleanup command (which applies to the individual disk handle operations only.) Otherwise a great article which gave me enough insight and confidence to tackle a 6TB cluster. Thanks!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s