{"id":41857,"date":"2024-05-22T08:27:59","date_gmt":"2024-05-22T08:27:59","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=41857"},"modified":"2026-02-19T05:16:34","modified_gmt":"2026-02-19T05:16:34","slug":"cli-environment-migration","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/cli-environment-migration","title":{"rendered":"CLI Tutorial: Environment Migration"},"content":{"rendered":"

CLI Tutorial: Environment Migration<\/h2>\n

Sometimes, it is necessary to shift your application to a different environment that offers improved conditions or is in a better location. Alternatively, you may need to replicate your environment across various hardware setups to enhance availability. To do this remotely, you must run a specific migration<\/strong> command line method using your terminal. Let’s delve into this further.<\/p>\n

1. First off, you’ll need to grab the list of regions offered on the platform. To do this, use the “getregions<\/strong>” command, but make sure to apply the right search filter. By doing this, the output will be reduced and it will be easier to understand.<\/p>\n

\r\n~\/jelastic\/environment\/control\/getregions | sed -rne '\/(uniqueName|isEnabled|displayName)\/{\/Name\/,\/isEnabled\/p}'<\/code><\/pre>\n
\"Linked<\/a><\/p>\n
On your dashboard, you’ll find a list of environmental regions linked to your account, each marked as ‘isEnabled’ (meaning it’s active). They’re identified by their display names and unique identifiers. Remember, the crucial detail here is the unique identifier.<\/p>\n
Note:<\/strong> The top-tier list provides an overview of general information regarding data centers. However, the specific parameters for each region, which you’ll need for additional tasks, are displayed in a lower tier (these lines are indented to the right).<\/div>\n
<\/div>\n
To clarify further, the distinct ‘uniqueName<\/strong>‘ values are highlighted within the image provided.<\/p>\n
2. Before initiating the operation, it’s wise to assess whether migration is feasible. Utilize the CheckMigrationPossibility<\/strong> CLI method tailored for this purpose.<\/p>\n
\r\n~\/jelastic\/environment\/control\/checkmigrationpossibility --envName {env_name} --hardwareNodeGroup {region_id}<\/code><\/pre>\n
Here are the details you need:<\/strong><\/p>\n