With the growth of your business, there is a good chance that your storage environment will not be as good. Data migration projects in a SAN environment are labor intensive and complex. But with good planning and the checklist set out in this article, your project will not exceed the time and budget.
In general, data migration is simply moving data from an old storage array to a new one. But this is ultimately wrong. Moving data is only a small part of data migration and usually the easiest part.
The migration process consists of a series of manual and intensive tasks. SANpulse Technologies, a storage migration company, identifies 43 distinct tasks. Only six of these tasks are semi-automatable and 37 of them require a lot of human work. They range from pre-planning analysis to migration execution, disabling existing systems, migration validation, data integrity verification, and final cleanup and recovery. documentation
Many of these tasks are repetitive actions. For example, consider discovering and collecting data from physical and virtual servers. All processes must be repeated for each server. But it’s server remediation – make sure it starts, is up-to-date, has the right drivers, microcode, and storage adapters, that it works with the new SAN, that it has the right directories, etc. – which requires a lot of time and effort. And such remediation must be done for each physical and virtual server. This represents many steps for a single task.
The following is a list of 43 tasks that SANpulse has developed to perform a complete SAN data migration . These tasks are divided into six steps to facilitate organization and planning. All tasks are listed below.
Step 1: Collect data before migration
The first step in a data migration is to collect and correlate all host and array data needed for the migration.
The tasks to be performed in this context are:
Identify hosts for migration
Collect data from the migration host (host audit);
Collect data from the storage array (bay audit);
Group information about areas and masks;
Correlate all the data.
Step 2: Establish the remediation rules
There is a need to assess storage remediation and repository requirements before beginning data migration. This process minimizes errors while putting in place procedures to handle the correct patches.
The three tasks to be performed are:
Analyze the migration and sanitation of the target;
Remediation of the host;
Document versions and compatibility of source software and target storage arrays, and correct any incompatibilities.
Step 3: Preparation Phase
This step consists of preparing hosts and source and target storage systems for migration. The 18 tasks involved are:
Configure the source and the target storage array for ease of migration;
Create the link between the source and the target bay
Collect all host storage configuration information, including installed operating system, cluster status, and disaster recovery system
Collect the configuration of each array, including the RAID, the Front-end (FA) port, and the status of each local and remote replication;
Collect SAN configuration, including managers, switches, and gateways
Plan the layout of the storage space on the target bays;
Create configuration scripts for migrating and matching source and target arrays;
Create configuration scripts for FA port mapping and LUN assignment in target arrays;
Create the LUN masking scripts for the target arrays;
Creation of the definition scripts for device aliases;
Prepare the SAN zoning host ;
Group host migrations in cooperation with the operational units;
Update all backup and restore scripts;
Run all host audits before the migration;
Create and execute the relationship matching scripts R1 to R2;
Create and execute the mapping and masking scripts for the target arrays;
Apply all host zoning configurations;
Confirm host connections to the target storage array.
Step 4: Start the migration process
All of the following tasks are required to migrate the data to a new storage array. They range from backup or data protection to stopping applications, stopping hosts, and creating scripts to link to the new array. Once the migration is complete, the tasks are reversed. This will restart the host applications. Specific tasks to follow are:
Start of data migration to the new array
Capture, replicate, or back up all old host configurations;
Sleep (shutdown) the applications, and then shut down the hosts;
Create and execute the scripts that will distribute the new relationships between bays 1 and 2 as soon as the data has been synchronized;
Verify and validate data from host backups
Restart the applications;
Obtaining a validation of business departments so that data migration is considered complete.
Step 5: Validation, restart and cleaning
Validate the migration, re-enable all applications on the new target storage, and disable the old storage system. Research, correct, clean up errors. To do this, you must perform the following tasks:
Check if there were activities on the old bays;
Create and execute the link deletion scripts between Bay 1 and Bay 2;
Create and execute scripts to remove all devices from FAs on the source array;
Create and execute scripts to clear meta-configurations on source arrays;
Create and execute scripts to unmask the source devices of migrated hosts;
Restart the hosts and confirm the visibility of the new target devices;
Clean areas and remove all unused areas;
Check the final connection table on the old bays;
Update device groups, if any.
Step 6: Final Documentation
Complete, document and validate the migration
Create reports and update them by documenting all the processes performed.