3 Common (and Dangerous) Data Migration Mistakes

3 Common (and Dangerous) Data Migration Mistakes

We all know that doing a proper data migration is a complicated task — one that is often bogged down by various issues: You don’t have all the resources that you would ideally want; you have a strict timeframe in which to get the migration done; or the approvals you need take way too long from “those above”.

, 3 Common (and Dangerous) Data Migration Mistakes

Of course, even as you wade through these issues, there can be a whole slew of challenges greeting you as soon as you get started. Knowing this, we’ve created a list of the three commonly missed mistakes that usually happen because IT staff are so mired down in handling all the complex details of an important data migration.

By keeping these three mistakes in mind, and watching for them while doing your data migration, you can save yourself a lot of time and frustration — and your company lots of money, which just could lead to them giving some of that saved dough to you, in the form of a raise. (Just sayin’.)

Mistake #1: Trusting That Your Backup Will Be There for You

“I have backups! I have so many backups! We always back-up before we change anything around here!”

We don’t doubt that you back up your data. The problem is that many (too many) IT professionals trust back-ups that turn out to be unreliable or problematic — and they didn’t realize it until it was too late. Cue the hypothetical thought bubble: Do you test those backups?

When was the last time you fully tested your backup system? When was the last time you did a test deployment of your back-up in exactly the same manner as you would have to do it, should you actually lose some data?

Here’s where the mistake hides, like many, in plain sight. Many times, during the crunch of time of a data migration, people are quick to back up, and keep moving. Many times, people have to refer back to those backups, at least to recover some part of their data. Many times the recovery mission fails, and only then do they realize that something was wrong with either the back-up itself or with the recovery system.

Make a copy of your data before migrating it. You want to be able to see everything as it was originally, on its original system, so that you can spot any corruption or anything that looks out of place.

Make sure that you change as little as possible between the “back-up” phase, and the actual migration phase, so that you don’t lose any changes that you might make before the migration.

Oh, yeah, and test your back-up. Run an actual recovery and see what happens.

Mistake #2: Leaving Home Without Roadmap

, 3 Common (and Dangerous) Data Migration MistakesLook, you wouldn’t leave your house and try to fumble your way to some place you have never ever been before, without your GPS. Right? Okay, so why would you start a migration without a detailed report on all your files — where they are and what is connected to what?

Print it out too (yes, on this old-timey stuff called “paper”) and keep it nearby to refer back to. This means that you have something external and physical that maps out your file structure before the migration, so you have something to look back at during the migration itself. Then, if you get lost, you don’t have to stop for directions. (You may still need to make a restroom stop, though.)

A very simple way to do this, for Windows users, is to, of course, generate a report using CommandPrompt. However, this is a very simplistic program that just gives a “broad-strokes” view of your file structures.

Overall, find the tool that works best for you to generate a comprehensive view of your files, including all the links contained within them. (Hint: www.linkreporter.com)

Mistake #3: Lack of Hardware, Software and/or Network Preparation

“Huh? We have a lot of this stuff (particularly hardware) around here!”

Yes, but you are doing a data migration now. The rules change a bit. Consider the following.

Hardware:

, 3 Common (and Dangerous) Data Migration MistakesMake sure that you have the allotted resources for your migration. When you’re doing a migration, you’re usually moving from an outdated or smaller resource to a larger one. Nonetheless, a good “rule of thumb” is to have at least 20% more capacity than what you think you will need.

Secondly, be sure that the hardware you’re migrating to has been tested and passed a benchmark test. Make sure that you’ve thoroughly tested it before the migration, so that you don’t finish up your migration, pat yourself on the back, and then have something break five minutes later.

Software:

During the migration itself, be doubly sure that you’ve shut down any processes or applications on the software you’re using. Having other processes running in the background while you’re trying to do a migration can cause interruptions or complications in your migration.

Tip: If you’re using a Windows machine, check back periodically to be sure no pesky automatic program has started itself up while you weren’t looking. Yeah, these have been known to cause problems surreptitiously. (That means they’re sneaky.) You could spend many hours trying to figure out some weird phenomena, not realizing the source of the problem is something running that you didn’t notice.

Network:

Last, but not least, you want to be absolutely sure you’re working with an open pipe. Make sure your firewall settings aren’t choking you from doing what you need to but aren’t leaving you vulnerable either.

Also, if you’re going to have users on your network while you’re doing your migration, you want to be sure to throttle your own use, so that you’re not slowing down your users.

If you know you’re going to have users on at the time of your migration, plan for it. You can’t kick them out and lock the door (tempting as that may be), so you’ll have to be sure you’re allocating the proper amounts of bandwidth for both you and them, so as to not slow down any work for either of you.

Summary

All of these things might seem obvious, in hindsight, yet are the things that have bitten many an IT pro in the you-know-what. You should pay extra attention to these areas when planning a data migration, no matter how big or small. Making sure you plan for all these things will keep you vigilant, and help make the other aspects of your migration run smoothly (“smoothly” being a relative term).

Ed Clark | Chief Operating Officer | Helping IT, CIO’s and Information Governance avoid losing data due to migrations or errors | LinkMail@LinkTek.com

photo credit: All you need is the plan, the road map, and the courage to press on to your destination. Earl Nightingale via photopin (license)

photo credit: New servers at work via photopin (license)