- Notes, cautions, and warnings
- Overview of Unisphere
- Functionality supported by each OS type
- Capacity information
- Understanding resource usage
- Login authentication
- Understanding the system health score
- Manage jobs
- Unisphere for PowerMax alert monitoring recommendations
- Alerts
- Server alerts
- Understanding licenses
- Understanding user authorization
- Individual and group roles
- Roles
- User IDs
- Roles and associated permissions
- Roles for performing local and remote replication actions
- RBAC roles for SRDF local and remote replication actions
- RBAC roles for TimeFinder SnapVX local and remote replication actions
- Storage Management
- Understanding storage groups
- Understanding data reduction
- Understanding service levels
- Performance Impact
- Understanding storage templates
- Understanding Storage Resource Pools
- Understanding volumes
- Understanding disk groups
- Host Management
- Understanding hosts
- Understanding masking views
- Understanding port groups
- Understanding initiators
- Understanding PowerPath hosts
- Understanding mainframe management
- Data protection management
- Understanding Snapshot policy
- Understanding SRDF/Metro Smart DR
- Manage remote replication sessions
- Understanding SRDF groups
- Understanding migration
- Understanding Virtual Witness
- Understanding Open Replicator
- Open Replicator session options
- Understanding device groups
- Understanding TimeFinder/Mirror sessions
- Understanding TimeFinder SnapVX
- Understanding Performance Management
- Understanding Unisphere support for VMware
- Understanding eNAS
- Understanding iSCSI
- Understanding NVMe/TCP
- Understanding PowerMax File for storage systems
- Understanding serviceability
- Understanding PowerMax software system profiles and compliance
- Unisphere for PowerMax localized for Japanese market
- Where to get help
Dell Unisphere for PowerMax 10.0.1 Product Guide
Understanding migration
Unisphere supports a migration application to provide a method for migrating data from a source storage system to a target storage system.
Non-Disruptive Migration (NDM) provides a method for migrating data from a source storage system to a target storage system without application host downtime. NDM enables you to migrate storage group (application) data (the storage groups must have masking views) in a non-disruptive manner with no downtime.
Minimally disruptive migration enables migrations on the same supported platforms as non-disruptive migration it but requires a short application outage. The outage is because that the non-disruptive nature of migration is heavily dependent on the behavior of multi-pathing software to detect or enable or disable paths and is not in the control of Dell (except for PowerPath).
PowerMax data mobility is a migration tool (leveraging the NDM interface) that streamlines data mobility from VMAX, PowerMax and competitive arrays to arrays running PowerMaxOS 10 (6079).
Additional migration information is available in the Solutions Enabler Array Controls and Management CLI User Guide and the Non-Disruptive Migration Best Practices and Operational Guide. Source side service levels are automatically mapped to target side service levels.
Non-Disruptive Migration applies to open systems or FBA devices only.
Non-Disruptive Migration supports the ability to reduce data on all-flash storage systems while migrating.
A Non-Disruptive Migration session can be created on a storage group containing session target volumes (R2s) where the SRDF mode is synchronous. The target volumes of a Non-Disruptive Migration session may also have a SRDF/Synchronous session that is added after the Non-Disruptive Migration session is in the cutover sync state.
Suggested best practices
- Try to migrate during slow processing times; QoS can be used to throttle copy rate.
- Use more SRDF links, if possible, to minimize impact:
- Two is minimum number of SRDF links allowed; Non-Disruptive Migration can use up to eight SRDF links.
- More links = more IOPS, lower response time.
- Use dedicated links as they yield more predictable performance than shared links.
You can migrate masked storage groups where the devices can also be in other storage groups. Examples of overlapping storage devices include:
- Storage groups with the exact same devices, for example, SG-A has devices X, Y, Z; SG-B has devices X, Y, Z.
- Devices that overlap, for example, SG-A has devices X, Y, Z ; SG-B has devices X, Y.
- Storage groups where there is overlap with one other migrated SG, for example, SG-A has devices X, Y, Z ; SG-B has devices W, X, Y; SG-C has devices U, V, W.
The following migration tasks can be performed from Unisphere:
- Setting up a migration environment—Configures source and target storage system infrastructure for the migration process.
- Viewing migration environments
- Creating a Migration session—Duplicates the application storage environment from source storage system to target array.
- Viewing Migration sessions
- Viewing Migration session details
- Cutting over a Migration session—Switches the application data access form the source storage system to the target storage system and duplicates the application data on the source storage system to the target storage system.
- Optional: Stop synchronizing data after Migration cutover and Start synchronizing data after Migration cutover—stop or start the synchronization of writes to the target storage system back to source array. When stopped, the application runs on the target storage system only.
- Canceling a Migration session—cancels a migration that has not yet been committed
- Committing a Migration session—Removes application resources from the source storage system and releases the resources that are used for migration. The application permanently runs on the target array.
- Recovering a Migration session—Recovers a migration process following an error.
- Removing a migration environment—Removes the migration infrastructure.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\