Ezine

This article can also be found in the Premium Editorial Download "Storage magazine: Who owns storage in your organization?."

Download it now to read this article plus other related content.

Data migration checklist

    Requires Free Membership to View

    Login

Before starting any type of data migration, follow these steps to ensure a successful migration:
PRE-MIGRATION
Determine the classes of storage that will be used in your environment.
Identify which data belongs on which class of storage.
Run an analyzer to determine how many files will be migrated and how long it will take.
How many volumes need to be migrated?
How large are the volumes?
Do they need to be grouped? If so, how many need to be migrated together?
How much time is available to complete the migration?
Is the hardware configured correctly?
Are there sufficient resources available in the server (host-based)?
Verify that the high-availability options in place on the source arrays are also in place on the target arrays.
Is sufficient network bandwidth available?
Has all of the needed software been identified, purchased and licensed?
Does all of the data need to be migrated at once, or can it be staggered?
MIGRATION
Monitor and adjust performance and migration rate.
Monitor application performance.
PRE-MIGRATION
Determine the type of application cutover--is it automatic or manual?
Decide how long to keep old data.
Validate the performance on the new storage.
Recover resources from which data was migrated.
Moving data is a constant struggle for most storage departments. Sluggish applications need to move to faster disks for better performance. Rarely accessed data needs to move in the other direction--to less-expensive ATA disks, CD-ROM or tape. If not handled judiciously, data migrations can cause application outages and server reboots, resulting in 2:00 a.m. work sessions.

There are many methods at different price points to move data. Some organizations may be able to simply use the move command that comes with every operating system. Others may need standalone utilities and network- and host-based approaches to get data from point A to point B. What's the best way to move data? To determine which method suits your needs, consider the following:

  • Type of application and data
  • Impact on application performance
  • Storage infrastructure
  • Network throughput
  • CPU and memory consumption
  • Affected users
Once you document your storage environment against this list (see "Data migration checklist"), pick a migration tool. Migration utilities operate at the host, network and array level. Each approach comes with its own set of advantages and disadvantages. For example, host-based commands like move should only be used for files not in use. Third-party, host-based utilities like NSI Software's Double-Take can help users measure and forecast the impact, time and I/O wait times of a data migration before moving the file. Without interrupting the application, EMC Corp.'s Symmetrix Optimizer utility automates load balancing and data placement within the array to improve application performance.

While some applications allow outages, many times it's simply not practical to shut down an application to perform the migration. The utility you choose should be able to monitor the application, increase and decrease the speed of the data migration or even stop the data migration if the application becomes exceptionally busy. This will allow server resources such as CPU and memory to be diverted from the data migration utility to the application.

A specialized migration tool isn't necessarily more effective in moving data. Host-based software such as Veritas Software Corp.'s Volume Replicator is often used to avoid vendor lock-in. However, host-based software can be costly and difficult to manage, depending on the number of servers, operating systems and arrays involved.

Array-based utilities such as EMC's Symmetrix Remote Data Facility (SRDF) and IBM's Peer-to-Peer Remote Copy (PPRC) tie users to a specific vendor's hardware, but can be administrated by a smaller, well-trained staff with minimal intervention required at the server level during the migration process.

Click here for a data replication software table (PDF).

This was first published in May 2004

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top