If you have an ECS with applications deployed, you can use the ECS to create a private image and then use the image to create identical ECSs. In this way, you do not need to deploy applications repeatedly.
You can create up to 100 private images under an account in a region.
No. You can create an image from a running ECS. But the data that was written into the ECS during the image creation will not be included in the image.
Log in to the management console. Choose Computing > Image Management Service and click the Private Images tab. Check the image creation progress in the Status column.
Creating an image may take a period of time because it requires to install KVM drivers, load the OS kernel, and configure GRUB boot. In addition, the network speed, image file type, and disk size all have impacts on how long the entire process takes.
Yes.
Private images created by an IAM user are visible to the account that the IAM user belongs to as well as all other IAM users (if any) under this account.
In addition, private images created by an account are visible to IAM users under this account.
A full-ECS image contains the OS, applications, and service data of an ECS. Generally, a full-ECS image is used to migrate all data of an ECS. For example:
When creating a full-ECS image from a CBR backup, you must select a vault. The vault is where your image and backup are stored. You need to pay for the vault.
So, no matter which backup type you select, you need to pay for the storage. Selecting a vault does not mean that you need to pay extra fees.
To check data disk details, you need to go to the CBR console. That is because only system disk information (Disk Capacity) is displayed in the image list and image details after a full-ECS image is created.
The following describes how to view the data disk details in CBR:
Image details are displayed.
The CBR backup details page is displayed.