Migration between Regions

Objective

This guide explains how to use Migration between Regions 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.

within the scope of accessenvironment regionsThe location selection selected at the start of a project can be easily changed. Using the migration option (Obviously, you have access to multiple environment regions.) This represents a powerful tool that can help you gain both cost and performance benefits. For example, you can choose cheaper hardware for the development/test phase. Then move production-ready applications to hardware with the best parameters for release.

Note:Availability of data migration options Including permissions for each environment region depends on the hosting provider's settings.

Therefore moving the existing environment to another hardware region. This can be done by:

• Click on the buttonSettingsnext to the desired enviornment and select an option.Migration

Note:
Pricing policies in different regions It may vary according to the parameters and will be applied automatically after the relocation is complete. Therefore, it is recommended to view the cost details - the cost information for each region can be viewed by clicking onPricinglink belowSelect a Region

The Live Migration tab can be toggled ON/OFF depending on the target region selected. Here you can specify which migration type should be used. (from two types provided):

• live migration- Available only in regions marked with LM in the list. (depending on the physical hardware location of the region)
  
• offline migration- Can be used in all environment regions

Specify all required conditions and click the button.Verify & Migrateat the bottom to move the location. There will then be a pop-up to confirm the action.

When the migration is complete, a message will appear on the dashboard and the region tag next to the environment will change. You will also receive a notification email with the details of the migration (such as the duration for all containers and any changes to parameters made through the process).

Below, the two Migration modes are described in detail.

Live Migration

Within the Target region list selector, you will see an LM label displayed next to the region - this is used to mark live migration as available.

When selecting a live migration region, an ON toggle will appear below. (It is enabled by default)

If this type of migration is selected, Environment will be executed by default. That is, there is no need to restart the container and no additional configuration required. So your app will not experience any interruption.

More:In case of high load (many incoming requests) it will stop working temporarily.downtime(about 10 seconds) showing error 502 - environment stopped. However, once the data transfer is successful, it will automatically resume.

If offline mode is required for some reason - just turn off the corresponding switch.

In such cases, the environment with all containers in it will be unavailable for the entire migration process and will resume normal operation. There is no need to make additional manual adjustments.

Offline Migration

When live migration is not available If the environment is moved to another data center (due to moving the environment to another data center) or if it is manually disabled, offline mode will be used. During such relocation the environment will be turned off.shut downuntil the end of this process

Additionally, if there is only one migration type, some environment settings such as nodes' IP addresses and configured domain names will be changed. Therefore, after the migration is completed, some manual configuration may be required to restore the functionality of the moved application - all necessary information will be additionally sent to you by e-mail.

Obviously that Based on the pros and cons mentioned above, live migration is the better choice (if any).