Initiate and control migration (ttmtm3520m000)

Migration safety time and planned downtime

If the transition to or from migration mode cannot be completed before a scheduled maintenance window begins, the tenant may risk corruption. To prevent this, a resource called migration_safety_time is available. By default, migration_safety_time is set to 24 hours, but this value can be changed by the Infor Cloud team.

This session considers the value of the migration_safety_time resource and the planned downtimes registered in the Planned Downtime (ttaad5530m000) session.

If you attempt to initiate or accept a migration and the time remaining until the next planned downtime is less than the value set for migration_safety_time, a message is displayed and the action is not performed.

Example:

With migration_safety_time set to 24 hours and the next planned downtime occurring in 23 hours, attempting to start the migration displays the following message and prevents the process from proceeding:

In less than 24 hours a maintenance window will start. Process cannot be started.

Options

These options are available:

Admin Only

Changes the operational status of the tenant to Admin Only .

As with installing upgrades and patches in the Install Upgrades and Patches (ttmtm3500m000) session, other users should not be able to make changes to the database in these situations:

• When the database is copied to the migration database.
• When the migrated data is copied back to the production database.

Bring Online

Changes the operational status of the tenant to Online .

Launch Migration Instance

Launches the migration instance on which the migration process is based. This step prepares the migration infrastructure, which saves time after starting the migration process. When you click Start Migration , the creation of a migration instance is skipped if a migration instance is already running.

Start Migration

Starts the migration process by copying the production database to the migration database and creating a migration instance.

These steps are performed:

• A backup of the current production database is created.
• The copy of the production database is copied to the migration database.
• The tenant config is changed so that the users of the tenant use the migration database instead of the production database.
• If a text for the sensitivity label is specified and sensitivity level 1 does not exist, then the sensitivity labeling is set for all sessions in the migration environment. The label is created with level 1.

Note: If you set the sensitivity labeling, also all users of the tenant are dumped to runtime. After this, the tenant admin must restart to change the database to the migration database.

If you click this button while the number of hours until the next planned downtime is less than the migration_safety_time, a message is displayed and the action is not performed. See Migration safety time and planned downtime.

Accept Migration

Use this command to accept the migration process. The actual migration is done by the session. After verification of the migration, you must decide whether to accept or abort the migration.

These steps are performed:

• A new backup of the current production database is created.
• On the migration database, the sensitivity labeling is reset to the settings before the start of the migration.
• A backup of the migration database is created.
• The backup of the migration database is copied to the production database.
• The tenant config file is changed so that the users of the tenant use the production database again.

Note: 

If you click this button while the number of hours until the next planned downtime is less than the migration_safety_time, a message is displayed and the action is not performed. See Migration safety time and planned downtime.

Abort Migration

Aborts the migration process. The actual migration is done by the session. After verification of the migration, you must decide whether to accept or abort the migration.

This step is performed:

The tenant config file is changed so that the users of the tenant use the production database again.

Note: The database that is used for the migration still exists on the migration server. This database must be removed by the Infor Cloud team.

Finalize Migration

Switches the tenant mode back from Migration to Operational. The migration infrastructure is removed.

Terminate Migration Instance

Terminates the launched migration instance.

Migration running

Sends a status to the tenant indicating that the tenant is in migration mode.