- Notes, cautions, and warnings
- Preface
- Introducing metro node
- Metro node use cases
- Features in metro node
- Integrity and resiliency
- Software and upgrade
Use metro node to move data between data centers, relocate a data center or consolidate data, without disrupting host application access to the data.
The source and target arrays can be in the same data center (metro node Local) or in different data centers separated by up to 10ms (metro node Metro). The source and target arrays can be heterogeneous.
When you use metro node to move data, the data retains its original metro node volume identifier during and after the mobility operation. No change in volume identifiers eliminates application cut over. The application continues to use the same data, though the data has been moved to a different storage array.
There are many types and reasons to move data:
With metro node, you no longer need to spend significant time and resources preparing to move data and applications. You do not have to plan for an application downtime or restart the applications as part of the data movement activity. Instead, a move can be made instantly between sites, over distance, and the data remains online and available during the move without any outage or downtime. Considerations before moving the data include the business impact, type of data to be moved, site locations, total amount of data, and schedules.
The data mobility feature of metro node is useful for disaster avoidance, planned upgrade, or physical movement of facilities. The mobility jobs in metro node are as follows:
Device | Moves data from one device to another device (within a cluster and across clusters). |
Batch | Moves data using a migration plan file. Create batch migrations to automate routine tasks.
|