Migrating using assisted save and restore

When assisted save and restore is used, IBM i Migrate While Active uses Db2 Mirror for i, along with save and restore to migrate the source node.

Introduction to migrating using assisted save and restore
IBM i Migrate While Active can use assisted save and restore technology to migrate SYSBAS from the source node to the copy node.
Concepts
This section contains an explanation of the fundamental pieces of IBM i Migrate While Active when using assisted save and restore.
System migration stage
The system migration stage for assisted save and restore consists of the steps required to set up the IBM i Migrate While Active environment. This includes configuring migration settings, saving the source node, transferring the save, and then restoring the save onto the copy node. At the end of the system migration stage, the environment is ready for data synchronization to begin.
Data synchronization stage
Once the system migration to the copy node has completed, IBM i Migrate While Active using assisted save and restore will enter what is known as the data synchronization stage. During this stage, changes to objects within SYSBAS are tracked using the integrated file system and library tracking lists. These tracking lists are used by Migrate While Active to understand which objects need to be migrated to the copy node.
Cutover stage
The cutover stage is the point where the migration to the copy node is finalized, and the relationship between the source and copy node is severed. When the cutover stage is complete, the source node will no longer interact with the copy node and the copy node is fully capable of being used as an independent instance of an IBM i.
Managing and monitoring IBM i Migrate While Active
Managing and monitoring Migrate While Active when using assisted save and restore varies greatly depending upon the migration stage.

Parent topic: IBM i Migrate While Active