Years ago, the most common type of migration you'd be likely to see in a data center would be upgrading from one operating system version to another. That process would usually be tied to a server hardware refresh and possibly an application version upgrade. In the process, production data would inevitably be moved from one place to another -- but that migration wasn't the objective.
These days, with ever-growing mountains of data and the increasing popularity of server virtualization, it's much more common to see storage hardware upgrades that have nothing to do with OS upgrades. The act of virtualizing a physical server or providing more storage space has taken a front seat.
Straight-up data migrations look simple enough on paper: Large amounts of data need to get from point A to point B. Simple enough, right? Not exactly -- as with most things in IT, the devil is in the details.
The success (or failure) of these types of data migrations usually revolves around the amount of downtime they require. As such, minimizing that downtime and ensuring that your migration process finishes without complication within the time you have available is a key concern. Here, I'll dig through the most common data migration scenarios and outline some of the pitfalls you'll want to avoid.
To continue reading this article register now