The financial firm represented here had two data centers, both with the need to retire older-generation NetApp HA storage, to be replaced with new EMC VNX-5000’s. Since the environment contained multiple client hosts on different OS platforms (Windows, Linux and VMware) running demanding financial applications on Oracle and SQL, host-side copying of data to the new storage was deemed impossible due to the amount of downtime that would have been required.
The Cirrus Data Solutions’ Cirrus Migrate On-Premises (CMO) was brought in to provide live migration of the data from NetApp to EMC storage without requiring any changes to the existing FC SAN, thereby avoiding any zoning changes, host-side driver installation, or storage LUN masking changes. Using TDI technology, CMO was inserted one path at a time into the live FC data stream, and avoided the risks usually associated with block-level migration. Live I/O was paused for just a few seconds on each path, and activity resumed automatically moments after insertion. CMO then automatically discovered all the source LUNs and hosts for migration.
The entire process was transparent to the database applications and caused no impact to production. At cut-over, the database owner simply unmounted the database from the old storage and remounted on the new device in a few short minutes.
CMO then performed a secure, 4-pass erasure to the old storage LUNs, ensuring that the retired storage could be re-purposed or returned.
The customer was very impressed with how simple it was to deploy the CMO appliances, and how the entire existing SAN environment was discovered and displayed graphically with no user input. All the customer needed to do was to identify and label each of the discovered source LUNs and pair them with the new destination LUNs, a process that could be accomplished with a single batch command. Given the ability to throttle the CMO migration process based on measured impact to production traffic, the customer was also able to set the desired level of aggressiveness so that throughout the entire migration project, the database owners were not aware of any performance impact to their systems.