There are several options, but depending on the application, this may or may not require downtime.
Some examples:
- If you're using VMware and have a license tier with storage vMotion, the easiest option is to just use this to hot-move the VMs from the msa to new Compellent volumes
- Hyper-V offers similar options
- If you're using the storage for Exchange, you can just present new (Compellent) storage to the server and have Exchange move the mailboxes (on the fly)
If you can afford the downtime, or there is no way with your application/OS to live migrate the data from the host side, Compellent can attach to your msa and pull the data in (assuming there is a protocol that they share (FC, iSCSI, SAS)). This article has an example of how that person did it to migrate from an HP EVA to their Compellent:
Dev Mgr
6 Operator
•
9308 Posts
•
3 Points
1156
0
Posted January 31st, 2014 06:00
There are several options, but depending on the application, this may or may not require downtime.
Some examples:
- If you're using VMware and have a license tier with storage vMotion, the easiest option is to just use this to hot-move the VMs from the msa to new Compellent volumes
- Hyper-V offers similar options
- If you're using the storage for Exchange, you can just present new (Compellent) storage to the server and have Exchange move the mailboxes (on the fly)
If you can afford the downtime, or there is no way with your application/OS to live migrate the data from the host side, Compellent can attach to your msa and pull the data in (assuming there is a protocol that they share (FC, iSCSI, SAS)). This article has an example of how that person did it to migrate from an HP EVA to their Compellent:
workinghardinit.wordpress.com/.../migration-luns-to-your-compellent-san