vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/ecs/umn/en-us_topic_0133365988.html
Hasko, Vladimir dc74b9cf93 pushing latest changes 
Reviewed-by: gtema <artem.goncharov@gmail.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
2022-09-06 15:22:18 +00:00

3.6 KiB
Raw Permalink Blame History

Migrating an ECS

Scenarios

ECSs can be migrated between DeHs and public resource pools.

  • An ECS created on a DeH can be migrated to another DeH.
  • An ECS created on a DeH can be migrated to a public resource pool.
  • An ECS deployed in a public resource pool can be migrated to a DeH.

Notes

  • Only a stopped ECS can be migrated.
  • CBR and CSBS backups are not affected by cold migrations.
  • ECS IDs remain unchanged after a cold migration.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select your region and project.
  3. Under Computing, click Elastic Cloud Server.
  4. On the Elastic Cloud Server page, select the target ECS.
  5. Click Migrate ECS in the Operation column.
  6. In the Migrate ECS dialog box, migrate the ECS as prompted.
    • If you want to migrate the ECS to a DeH, select a DeH from the list.
    • If you want to migrate the ECS to another DeH, select Migrated To another DeH.
    • If you want to migrate the ECS from a DeH to a public resource pool, select Migrated Out of DeH.
  7. Click OK.

    The ECS is migrated as required.

Parent topic: Instances