by LimeLight Technology Solutions on 20/08/12 at 9:12 am
Data migrations can be the bane of an IT professionals career. However, starting with a solid data migration plan will help you avoid the common pitfalls in getting your data from point A to point B.
- Be sure to understand what systems and software will be affected by your migration. A common source of cost and timeline overruns is failure to account for interoperability.
- Pick the right project methodology. (Hint: the right methodology is iterative.)
- If your migration is between two virtual servers, be sure you understand the risks. Below are some helpful tips for you to use when building out your data migration project plan.
Upgrade More than Your Data Systems
Large data migration projects are generally linked to hardware upgrades. That being the case, when building out your data migration project plan, you need to be aware of what other systems are touching your new hardware. Often times IT managers are caught off guard when they learn their hot new hardware won’t play nice with the OS or firmware they’re using. A significant portion of your project plan needs to include interoperability analysis. Remember, incorporating new software or peripheral gear is costly, in time and money.
Use Iterative Project Management Techniques
If you plan on using a traditional “waterfall” project management methodology, think again. A typical data migration approach involves analyzing, extracting, transforming, validating, and loading — simple linear process right?
Not at all!
Regardless how thorough you are, your analysis will miss certain key constraints. Moreover, you will find that incorrect assumptions and “surprises” uncovered along the way will cause you to constantly be looping back for more analysis. Projects that involve looping are exactly the type that iterative methodologies — such as agile, RUP and adaptive — are suited for.
Don’t Jump Straight to V-2-V Solutions
IT shops using cloud technology — which are fast becoming more common than the contrary – likely have their data virtualized. Generally, virtual-to-virtual (V-2-V) solutions simplify data migration. However, there are some additional factors that need to be considered when building out your project plan.
Be sure your data migration project plan accounts for:
- Immediate post-transfer testing and validation. Typically, the node that previously held your data gets shut down post-transfer, so you will want to be absolutely sure there were no mistakes.
- V-2-V transfer speeds are slower than traditional transfers. Know the speeds you will be operating at and account for it in your plan.
- In line with transfer speeds, are capacity issues. If you have more than one V-2-V to transfer, be mindful of the size of the data you are moving. A couple hundred gigs at a time may go smoothly; however, a more than one large V-2-V transferring concurrently will likely cause problems.
With proper planning and attention to detail, you’ll get through your data migration fine. Remember to pick the right project planning methodology and uncover as many of the project landmines as possible, before you begin.
About The Author: Limelight Technology Solutions is a leading provider of services and applications for data migration projects.