The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Data migration is the process of copying data from an existing storage device to a new storage device. Data migration is required for storage array upgrades and for consolidation or replacement of existing storage arrays. Traditional methods of migrating data can be complex and can cause service disruptions.
Cisco MDS Data Mobility Manager (DMM) for the Cisco MDS 9000 Family switches provides capabilities and features that simplify data migration and minimize service disruptions.
This chapter includes the following sections:
Traditional data migration methods can be complex and disruptive, often requiring extensive rewiring and reconfiguration of the SAN infrastructure. Configuration changes to servers and storage subsystems require coordination among different IT groups and storage vendor service representatives. Server downtime requires advanced scheduling with potentially long lead times.
Cisco MDS DMM is an intelligent software application that runs on the Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4) or the MDS 9222i switch or the MDS 9250i switch. With Cisco MDS DMM, no rewiring or reconfiguration is required for the server, the existing storage, or the SAN fabric. The MSM-18/4 module, MDS 9222i switch or MDS 9250i switch can be located anywhere in the fabric, as Cisco MDS DMM operates across the SAN. Data migrations are enabled and disabled by software control from the Cisco Fabric Manager.
Cisco MDS DMM provides a graphical user interface (GUI) (integrated into Fabric Manager) for configuring and executing data migrations. There is also a command-line interface (CLI), which is suitable for creating scripts.
Cisco MDS DMM can be used in SANs that have only Cisco MDS 9000 switches as well as those containing a heterogeneous mixture of Cisco and other vendor switches.
Application downtime is a critical factor in data migration, as prolonged periods of downtime are difficult to schedule. Cisco MDS DMM minimizes application downtime. Existing data is available to the applications while the migration is performed. Cisco MDS DMM uses hardware and software resources on the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch to move data to the new storage. This approach ensures that data migration adds no processing overhead to the servers.
Cisco MDS DMM supports online migration, allowing applications to continue to access the existing storage devices. During data migration, all traffic between the server and storage flows through the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch, (Figure 1 (right side)). The MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch coordinates all server access to the storage and performs the data migration. The migration activity is transparent to the server, which continues to have full access to the data Figure 1 (left side) shows the server’s view of the network during data migration. The server is unaware of the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch, the new storage, and the migration activity.
Cisco MDS DMM performs data migration without any additional layer of virtualization. Cisco MDS DMM requires only the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch configuration to enable the feature and SAN configuration to access the new storage array. Cisco MDS DMM can be enabled (when data needs to be migrated) and disabled (after the migration is completed) without any major SAN or host reconfiguration.
Cisco MDS DMM uses the following concepts and terminology:
The storage that is currently used by the application server. The data contained in the existing storage will be migrated to the new storage.
The storage to which the data will be migrated.
A logical unit number (LUN) is a reference to a unit of storage that you can specify for migration. The LUN is only a unique number in the context of a storage port.
A data migration session migrates the data from one LUN in the existing storage to a LUN in the new storage.
A data migration job defines a set of LUNs to be migrated together. A data migration session is created for each LUN that is to be migrated. The data migration job is the main unit of configuration and management. For example, the migration rate and other attributes are configured for the data migration job. The data migration job (not individual sessions) can be started or stopped.
The DMM node comprises of the MDS modules and switches like the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch that provide intelligent services. The Cisco MDS DMM feature executes on the DMM node.
The MSM-18/4 module, MDS 9222i switch or tare MDS modules and switches that provide intelligent services. The Cisco MDS DMM feature executes on the MDS MSM-18/4 module or the MDS 9222i switches.
In a dual-fabric topology, a data migration job runs on an MSM-18/4 module, MDS 9222i switch or MDS 9250i switch in each fabric. The two MSM-18/4 modules, MDS 9222i switch or the MDS 9250i switch es are peers. The MSM-18/4 modules, MDS 9222i switch or the MDS 9250i switch communicate with their peer MSM-18/4 modules, MDS 9222i switch or the MDS 9250i switches to coordinate the data migration jobs.
Fibre Channel Redirect (FC-Redirect) allows on-demand insertion and removal of the MSM-18/4 module or the MDS 9222i switch intelligent services with minimal disruption to existing traffic. No configuration changes are required on the server or storage devices. Cisco MDS DMM uses the FC Redirect capability to redirect traffic to the DMM node on either an MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch. This redirection is transparent to the host and storage devices.
A virtual target (VT) is a proxy target address for a storage port. During data migration, the FC-Redirect feature redirects traffic from the server to a VT on the MSM-18/4 module or the MDS 9222i switch.
A virtual initiator (VI) is a proxy initiator address for a server host bus access (HBA) port. During data migration, the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch uses a VI to forward redirected traffic to the existing storage port. The MSM-18/4 module or the MDS 9222i switch also uses the VI to forward data migration traffic to the new storage.
The control plane processor (CPP) is the main processor in the MSM-18/4 module or the MDS 9222i switch. DMM runs on the CPP.
The data path processors (DPPs) are a set of resource processors in the MSM-18/4 module or the MDS 9222i switch. The DPP transfers blocks of data across the switch without impacting the CPP. DMM uses a VI on the DPP for migrating data.
The production fabric is a fabric where the host port(s) and existing storage port(s) are connected. The server to storage traffic is carried in the production fabric. The new storage port is not present in the production fabric.
The migration fabric is a fabric dedicated for data migration or remote replication. The existing storage and the new storage are connected to the migration fabric. No server port is present in the migration fabric.
Cisco MDS DMM supports the following features and capabilities:
In server-based migration, the focus is data migration for the storage used by a particular server (or server HBA port). All LUNs accessed by the selected server are available for migration to new storage.
In storage-based migration, the focus is data migration for storage exposed by a particular storage array (or storage array port). All LUNs in the specified storage array are available for migration to new storage.
Cisco MDS DMM is designed to provide online data migration. The existing storage is available to server applications while the MSM-18/4 module, MDS 9222i switch or the MDS 9250i switch performs the data migration. During migration, data reads from the server are directed to the existing storage. DMM ensures that data writes are processed correctly. For example, if the write is to a storage segment already migrated, the write is mirrored to the existing and new storage.
During offline data migration, servers must not initiate reads or writes to the existing storage. Any server application using the existing storage must be quiesced. Offline data migration is faster than online data migration and can be used for noncritical data applications.
For the section of existing storage LUN whose data is already migrated to a new storage LUN, any new SCSI Write I/Os from the server is written to both the existing and new storage LUN before sending a response back to the server. Method 1 is typically used in local data migration.
SCSI Write I/Os from the server to any section of existing storage LUN are written only to the existing storage LUN. The Write I/O changes to the existing storage LUN are marked in the Modified Region Log (MRL) before sending a response back to the server. These changes are then migrated to the New Storage LUN in subsequent iterations. Method 2 is typically used in remote data center migration.
The Cisco MDS DMM GUI is integrated into Fabric Manager. The DMM GUI provides a wizard to guide you through the steps required to configure a data migration job. To minimize customer impact, you can schedule the start time for a data migration and you can configure the rate of data migration. The wizard also prompts you to perform tasks on external entities such as the fabric switch and the storage devices.
The DMM GUI also provides a job status screen, for monitoring and managing data migration jobs and sessions.
Cisco MDS DMM provides a set of CLI commands, which are suitable for creating scripts. These commands are accessed from the MDS switch command console or Telnet session.
To increase the amount of data that an existing server can access, Cisco MDS DMM facilitates migration to a larger LUN. After the migration, expand the file system on the LUN to take advantage of the increased storage space.
Cisco MDS DMM can migrate data between storage devices from different vendors. The supported devices are listed in the Cisco MDS 9000 Family Interoperability Support Matrix, which is available at Interoperability Matrix for Cisco Nexus and MDS 9000 Products:
Cisco MDS DMM supports data migration on SANs that contain third-party vendor switches (such as Brocade). Servers may be connected to the third-party vendor switches, however the existing and new storage devices must be attached to an MDS switch.
Cisco MDS DMM supports post-migration verification of the new storage. The existing storage is offline during the verification.
Cisco MDS DMM supports multiple simultaneous data migration jobs and simultaneous data migration sessions within a job.
Cisco MDS DMM supports data migration for dual fabric topology. In this topology, servers are connected to storage devices across two independent SAN fabrics and the servers are configured for multipathing.
Cisco MDS DMM also supports data migration for single fabric SANs with single-path or multipath configurations.
After the data is copied from the existing storage to the new storage, you can delay the reconfiguration of the server to access the new storage. During this period, all writes are mirrored to the existing storage and the new storage. This description assumes Method 1.
A data migration job typically comprises three major stages. (See Figure 1.)
In the pre-migration stage, create a plan for data migration, configure the new storage, and create the DMM job. In the migration stage, start the data migration job and monitor its progress. In the post-migration phase, prepare the server to use the new storage, delete the data migration job, and remove the old storage.
In the pre-migration stage, create a plan for the migration, configure the new storage, and create the data migration job. Full details about pre-migration activities are covered in Preparing for Data Migration
Create a plan for data migration, identifying external dependencies and activities that need to be scheduled.
Configure the new storage device and any other configuration.
Create and configure the data migration job using the DMM GUI. You can create a job without a schedule or you can specify the day and time for the job to start.
In the migration stage, jobs with a configured schedule jobs start automatically. Manually start unscheduled data migration jobs.
A data migration job comprises one or more data migration sessions. A data migration session performs the migration of one LUN from the existing storage to the new storage.
During migration, the DMM feature ensures the integrity of the storage data by intercepting all traffic from the server and storage ports involved in the migration job.
Cisco MDS DMM directs all server-initiated reads and writes to the existing storage. If the server initiates a write to a region that has already been migrated, the write is mirrored to the new storage for Method 1. For Method 2, if the server initiates a write to a region that is already migrated, the MRL gets updated for that region while the data gets migrated in the background subsequently.
During migration, you can monitor progress of the DMM job by using the job status display for Method 1 in the DMM GUI. For Method 2 jobs, the Est. TOC field determines when to enter the Finish command.
In the post-migration stage, reconfigure the server to use the new storage. The exact post-migration configuration steps vary depending on the operating system of the server.
To configure the post-migration steps for Method 1, follow these steps.
Schedule a time (and the personnel) to reconfigure the server to use the new storage and remove references to the existing storage.
Optionally, verify the data integrity between the existing and new storage after the migration has completed. The existing storage must be offline during the verification.
To delete a data migration job, follow these steps:
To configure the post-migration steps for Method 2, follow these steps.
Schedule
Schedule a time (and the personnel) to reconfigure the server to use the new storage and remove references to the existing storage.
Finish
To complete Method 2 data migration, quiesce server applications select Finish to stop access to the existing storage.
The existing storage LUNs are offline for the servers. Cisco DMM migrates the changed blocks from the existing storage LUNs to the new storage LUNs for the last time.
Verify
Optionally, you can verify the data integrity between existing and new storage after the Finish operation is completed. The existing storage LUNs will be offline during the verification. This optional operation can be performed just before deleting a job.
Delete
To delete a data migration job (in Method 2), follow these steps:
Table 1 lists the supported modules, methods, and releases for Cisco MDS DMM.
Switch Modules |
Method |
Supported Release |
---|---|---|
MDS 9250i switches |
Method 1 |
NX-OS Release 6.2(5) and later |
MDS 9222i switches |
Method 1 |
NX-OS Release 4.1.3a and later |
MDS 9222i switches |
Method 2 |
NX-OS Release 4.1.3a and later |
Multiservice Module (MSM-18/4) |
Method 1 |
NX-OS Release 4.1.1b and later |
Multiservice Module (MSM-18/4) |
Method 2 |
NX-OS Release 4.1.1b and later |
Note | To configure DMM on a switch running NX-OS Release 4.1(1) or later, the Fabric Manager server must be running NX-OS Release 4.1(1) or later. |
Cisco MDS DMM software application executes on the MSM-18/4 module, MDS 9222i or the MDS 9250i switch.
The following switches support the MSM-18/4 modules, MDS 9222i or the MDS 9250i switches:
The storage ports must connect to Cisco MDS switches that support FC-Redirect. All Cisco MDS switches support FC-Redirect, with the following exceptions:
Note | Fibre Channel Redirect (FCR) support is introduced in the Cisco MDS 9710 series switch in Cisco NX-OS Release 6.2(3). The storage ports can be connected to Cisco MDS 9710 series switch running with Cisco NX-OS Release 6.2(3) or later. |
The server HBA ports can be connected to any switch (Cisco or third-party vendor).
The SAN fabric has the following hardware-related requirements:
The Cisco MDS DMM software application has the following configuration limitations:
The Cisco MDS DMM software application has the following restrictions:
If a target switch is configured for FC-redirect, and the switch has ISLs configured on Generation 1 line cards, then external non-FC-Redirect hosts that are accessing the target switch might experience a disruption in traffic to the switch. This disruption occurs only if the host’s FC4-feature type is not registered as scsi-fcp:init.
When adding a Bulk Notification enabled switch to an existing FC-Redirect enabled fabric, a new DMM job must not be configured with any hosts or targets connected to the newly added switch before disabling Bulk notification via CLI command no fcns bulk-notify on the newly added switch. Likewise, previously configured DMM jobs may assume operation only after disabling Bulk Notification on the switch. This is applicable only to Cisco NX-OS release 6.2(7) and onwards.