Initiate and control migration (ttmtm3520m000)

Use this session to control the migration process. In a tenant environment, the migration process starts by changing the operational status of the tenant to Admin Only. This prevents other users to change the database during the creation of the backup.

This session creates a backup of the production database. After the migration, if the migration was accepted, the migration database is copied to the production database.

After the first "Start Migration", the tenant mode is switched to "Migration Mode". As long as the tenant is in Migration Mode, application upgrades are not allowed and blocked.

The landlord can verify this mode in a tenant overview list. Tenants in migration mode require special resources, for example a migration server and database. These services are not free of charge and the tenant must change the status in time to avoid extra costs.

The tenant can change the mode with several form commands:

Finalize Migration

Switches the tenant mode back from "Migration" to "Operational".

Migration running
With this command the tenant receives a status that indicates that the tenant is in migration mode.

Actions

These options are available:

Admin Only
Changes the operational status of the tenant to Admin Only.

Like in case of installing upgrades and patches (ttmtm3500m000), 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.
Start Migration
Starts the migration process by copying the production database to the migration database.

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 are using 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, then 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.

Accept Migration
Use this command to accept the migration process. The actual migration is done by the Loader Dashboard (ttmig5600m000) 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.
Abort Migration

Abort the migration process. The actual migration is done by the Loader Dashboard (ttmig5600m000) 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".
Migration Running
With this command the tenant receives a status that indicates that the tenant is in migration mode.
Sensitivity Label

The sensitivity label that is displayed to the users during the migration.

This field is read-only.

Default value

“Warning: Migration Environment.”

If the field is empty, the sensitivity labeling is not set.