Quantcast
Channel: Blog | Dell
Viewing all articles
Browse latest Browse all 8970

4 Questions to Ask Before Starting a Data Migration

$
0
0
EMC logo

Data migrations are a pain. There I said it. They’re messy and they keep storage admins up at night.

But, they’re also a necessary part of business operations. To realize the value, the performance, the promises of modernized new infrastructure, you need to onboard your existing data and processes.

Because of this, data migration will always be a part of storage tech refreshes. But, it no longer has to be tedious, time-consuming, error prone, or painful. The key to turning that corner is in asking the right questions before you get started and choosing the right vendor to engage with.

Let’s focus on your people and partners — the most crucial component to success or failure. When it comes to migrations, you want proven industry experts who are well versed in moving data. So how can you distinguish the amateurs from the pros? Here are some questions to consider to help you make that decision.

  • Are you working with a company that has the capabilities to perform platform- and vendor-agnostic migrations?

This is a big deal when you take into account that most data centers are sprawling, multi-generational, complex environments and the tier 2 and tier 3 storage that you’ll find in there are likely heterogeneous and the disks are outdated.

  • What is the company’s track record for dealing with complex environments and do they have a track record that demonstrates a commitment to customer collaboration and service excellence?

Every environment is different and every business has its own tolerances and requirements. Migrations are a cooperative exercise, so you’ll want to make sure that a strong desire to collaborate is in place.

  • How standard and proven is the migration methodology?

How thorough is your prospective vendor with pre-work asset mapping?  Is their remediation strategy proactive or reactive? In other words, do they start with a low-cost base rate, move over what they can, and fix whatever remains after the fact? This should give you an idea of potential hidden costs, anticipated business disruption and the level of automation that the vendor has developed to make its migration successful.

  • What underlying data migration technology does the vendor use?

This can make a huge difference in choice and convenience. If migration capabilities are embedded into the product, you can go with a DIY approach. Even if you would never actually do it yourself, embedded technology simplifies and reduces the level of effort for the data movement. That would result in a significantly lower cost for migration, even if you decide to leverage outside expertise to do the job for you.

Dell EMC moves massive amounts of data (over an exabyte each year and more than 200 petabytes of that comes from non-Dell EMC arrays) so we’ve seen many different scenarios. What we’ve learned is change is good, questions are good, and it’s always worth exploring better options. One particular customer that comes to mind had 500+ TB of data and for the last 15 years refreshed their storage annually — a process that took nine months to complete each time. With Dell EMC’s proven and standardized methodology, we were able to complete that same migration 75% faster. For the customer that meant 7 months of data migration work eliminated, $400,000 in maintenance costs saved and a reduction in TCO by $60,000/month.

DEW Twitter Image IIf you’ll be at Dell EMC World this year, come hear me talk in detail about Intelligent Data Mobility, our better, faster and easier way to migrate data.

Dell EMC World Breakout Session: Data Migration: Cheaper, Faster, Easier…and Now at Scale!

  • Tue 8:30 AM – 9:30 AM, Palazzo L
  • Wed 3:00 PM – 4:00 PM, Palazzo J

The post 4 Questions to Ask Before Starting a Data Migration appeared first on InFocus Blog | Dell EMC Services.


Viewing all articles
Browse latest Browse all 8970

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>