AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Ndm id11/13/2023 ![]() ![]() Commit : After the source to target data synchronization is complete and all application data has been migrated to the target array, a commit operation is performed.Cutover : A cutover operation moves the target devices out of pass-through mode, initiates data synchronization from the source to the target, and makes the paths to the source array inactive so that all I/Os are being serviced by the target array.The array operating system ensures that all I/Os that are directed to the target by the host are actually serviced by the source array until the cutover. Once this is complete, I/O issued by the application is directed to either the source or the target arrays through the host multipathing software. The target devices are assigned the identity of the source devices and are configured in a pass-through mode that allows the data to be accessed from both the source and target devices.Īfter the create operation completes, the administrator issues a host rescan to allow the host to discover the paths to the newly created devices. Create : Solutions Enabler examines a specific application’s storage on the source array and automatically provisions equivalent storage on the target array.All other storage groups migrating between those arrays will use the same migration environment. The environment setup command is run only once prior to the initial migration between two arrays. This includes ensuring that a usable replication pathway for data migration is available between the source and target arrays. It confirms that both the source and target arrays can support the NDM operations. Environment setup: Setup configures the migration environment that will be required to migrate any application from the source array to the target array. ![]() The entire migration of a storage group can be accomplished with a few clicks in Unisphere or through simple and short Solutions Enabler commands. These migrations are performed at the storage group (SG) level. The migration of an application from the source to the target array is completed using a sequence of user-initiated operations, each which is fully automated. This process uses what is referred to as the three Cs: create, cutover, and commit. Since the initial release of the NDM feature, the cutover feature has been the method by which migrations from an array running 5876.xx.xx code have been undertaken. In addition to the support matrix, reference the appendixes in this document for caveats on specific host-OS and multipathing combinations before attempting a migration. Note: Reference the extensive support matrix when planning to migrate applications using NDM. Pass-through NDM overview (migrating from VMAX with HYPERMAXOS 5876) Metro-based NDM : Source array is a PowerMax, VMAX All Flash, VMAX3 running 5977 or 5978 codeįigure 1.Pass-through NDM : Source array is a VMAX or VMAX2 running 5876 code.From a user standpoint, the process is very similar in terms of interaction, but the architecture is fundamentally different. NDM is available in the following two forms depending on the source array involved in the migration session. It also uses PowerMax/ VMAX auto-provisioning, in combination with Dell PowerPath or a supported host multipathing solution, to manage host access to the data during the migration process. ![]() Non-Disruptive Migration leverages VMAX SRDF replication technologies to move the application data to the new storage array.
0 Comments
Read More
Leave a Reply. |