HP MPX200 Multifunction Router - Manual (Page 30)

Table 5 Data migration size
Minimum Required DML Capacity Number of Remote Migration Jobs per MPX200
100 GB 64
164 GB 128
292 GB 256
548 GB 512
For more information on working with DMLs, refer to “Creating and removing a DML” (page 69)
and “Command line interface” (page 76) .
Remote peers
A remote peer identifies the remote router used at a remote site. The remote router establishes
native IP connectivity to perform remote data migration operations.
“Using remote peers” (page
51) provides procedures for adding and removing remote peers.
Online remote migration
Remote data migration with the MPX200 uses either Native IP connectivity or FCIP. Because the
MPX200 uses an asynchronous replication method to migrate data online to a remote location,
the router requires a DML, see
“Creating and removing a DML” (page 69) . The MPX200 uses the
DML to record all the changes during the remote migration process. The DML must be allocated
from any storage array in a local SAN. For DML allocation guidelines, refer to the previous section,
“DML” (page 29) .
NOTE: For details about the WAN link between the local and remote sites, refer to the HP
MPX200 Multifunction Router Command Line Interface User Guide. The WAN link test command
helps identify possible WAN issues such as packet drops, jitter, available bandwidth, and so on,
and enables the migration user to adjust the WAN accordingly.
Deploy the MPX200 for data migration at a local location where the source data resides. Before
configuring any remote data migration job, allocate the DML to the MPX200 system from the local
site (source location). To add or delete a DML, see the procedures in
“Creating and removing a
DML” (page 69) 1. Use one of the following methods to perform remote migration.
Method 1: Using Native IP
Online remote data migration with Native IP has the following objectives:
•
To reduce and simplify the configuration steps required for implementing a remote data
migration.
•
To improve the performance of remote migration using compression.
Configuring the Router and Chassis
Follow these procedures to configure the remote and local routers and chassis for online remote
data migration with Native IP.
To configure the remote router and chassis:
1.
Present the LUNs to be used as part of the migration from the destination array to the remote
router and blade VPGs.
2. If the destination array has been moved from the local site to this remote site, add the remote
router and blade VPGs in the same host group as the local router and blade VPGs. This step
ensures that LUNs are visible to the remote router at the same LUN IDs.
3. Zone in the destination array ports with the appropriate VPGs.
4. Ensure that the targets and LUNs are visible on the remote router.
30 Data migration objects