Cisco Cisco Data Mobility Manager 정보 가이드

Q&A

Page 2 of 4

bandwidth resources. Application performance can deteriorate by as much as 50 percent

when administrative traffic such as that needed for the migration task competes for CPU

and I/O bus bandwidth. In addition to this significant problem, in a host-based approach the

storage administrator is dependent on the server and system administrators to complete

the migration task. This dependency invariably results in a larger coordination effort and

more time and resources than is optimal spent on the migration task.

●

Array-based solutions are typically limited to homogeneous environments. Because the

migration is delivered using the same tools as for disaster recovery, such a migration task

typically requires considerable human involvement because storage administrators are

dependent on array vendor services to configure the migration task, meaning that more

coordination and time is needed to complete the migration task. Such a solution is

acceptable when the customer needs to migrate data only infrequently, but the inability to

complete a migration task without depending on others can be a very big problem for

storage teams that must migrate data on a regular basis.

●

Appliance-based solutions are typically used to move data across heterogeneous vendor

arrays when the coordination needed by host-based solutions is considered unacceptable.

Appliance-based solutions require two outages, so such outages must be acceptable in an

environment that uses this approach.

Although some of these solutions work for some customers in some scenarios, no one solution

works for all customers all the time. Cisco DMM, however, addresses the different limitations of all

these approaches and so is a best-fit solution for most application scenarios.

What are the main features of Cisco DMM?

Main features of Cisco DMM are as follows:

●

Cisco DMM integrates into the existing environment completely transparently, so that

neither the host server nor the storage array have to be reconfigured when Cisco DMM is

introduced into the user environment, nor is any zoning configuration required. The storage

administrator thus can complete the migration task without needing to inform the server,

system, or database administrator that a migration is being planned.

●

Cisco DMM can move data over long distances where the copy operation must be

completed asynchronously with write I/O operations.

●

Cisco DMM can securely erase the data from the existing storage so that this step can be

completed before the array leaves the customer data center.

●

Other features include capabilities to pace the data migration job, schedule the start and

cutover times, and view the effect on the SAN of the extra traffic generated by the data

movement. A configuration wizard simplifies setup and use, and a command-line interface

(CLI) allows advanced users to complete their migration tasks using scripts.

What Cisco DMM configurations are supported?

From a SAN switch perspective, mixed switch vendor environments are possible, but use of

such a configuration is discouraged for the initial release of Cisco DMM, until the mixed switch

vendor environments have been thoroughly tested. Thus, initially, Cisco DMM is assumed to

be employed in an environment that uses exclusively Cisco MDS 9000 family switches.

In addition, existing and new storage must be connected to Cisco MDS 9000 family switches that

are running Cisco MDS 9000 SAN-OS Software Version 3.2(1) or later. In the optimal

configuration, existing and new storage is connected to the same switch. Also, while the Cisco