CLI Tutorial: Environment Migration

Objective

This guide explains how to use CLI Tutorial: Environment Migration on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

Sometimes you may need to move your applications toRegionothers with better conditions or positions Or for exampleCloningmultiple environment combinations between different hardware for greater availability Remote operations require you to perform data migration methods.migrateCLI through your terminal So let's take a look in more detail:

1. The first step is to view the list of regions available on the platform using the commandgetregionsYou can use appropriate search filters to reduce the output and make it easier to understand:

~/jelastic/environment/control/getregions | sed -rne '/(uniqueName|isEnabled|displayName)/{/Name/,/isEnabled/p}'

You will see a list of available environment regions for your account (where“isEnabled”Specified astrue) with name on the dashboard (displayName) and a unique identifier (uniqueName) Here you need to remember the last parameter.

Note:The first shows global information on the data center, while the parameters of the region you want to recover for further operations. It will show the level below. (That line will be shifted to the right.) ValueuniqueNamecircled at the top

2. You should check the possibility of data migration before proceeding with the migration using the method. CheckMigrationPossibility CLI with the following command:

~/jelastic/environment/control/checkmigrationpossibility --envName {env_name} --hardwareNodeGroup {region_id}

where:

• {env_name}- The name of the environment into which you want to move the new region.
• {region_id}- unique identifier of the environment region from the previous step

3. You now have all the necessary information to complete the migration process.

~/jelastic/environment/control/migrate --envName {env_name} --hardwareNodeGroup {region_id} --isOnline {true/false}

A new parameter here is the isOnline parameter, which can be set to {true/false} to use live or offline migration mode respectively.

Wait a moment (migration time depends on the contents of your environment). The operation will complete and the application will be migrated successfully.