Virtual LUN migration rules with Clones

Something which came up recently was a question around using virtual LUN migration when Snaps or Clones are involved.

 When migrating a LUN using Clariions virtual LUN migration the following applys :

If migrating a LUN to a destination LUN of the same size, Source LUNs for Snaps are Clones can be migrated without issue.

However if migrating to a larger destination LUN, any Snapview sessions must be destroyed, Clone groups must be destroyed and re-configured after the migration.

Also, its worth noting, that snapview reserve LUNs or Clone private LUNs cannot be migrated.

More info on the attached EMC document.



About interestingevan

I work as a Technical Architect for a Storage and Virtualisation distributor in the UK called Magirus. The goal of this blog is simply to be a resource for people the want to learn about or go and Sell storage. I'm a qualified EMC Clariion Technical architect, Commvault Engineer and Cisco Unified computing specialist. I have also worked with the rest of the EMC portfolio for a good few years. This Blog will provide information on how specific technologies work, what questions need to be asked in order to spec certain products, competative info and my two pence on some of these technologies. Please feel free to provide feedback as to the content on this blog and some bits you'd like to see. View all posts by interestingevan

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

%d bloggers like this: