检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Deleting snapshots Deletion failed An error occurs when you try to delete a snapshot. Deleting snapshots Rolling back The snapshot is being used to roll back data. NOTE: When you roll back data from a snapshot, you can only roll back data to the source EVS disk.
Snapshot retention policy The system does not automatically delete snapshots. Snapshots are deleted in the following scenarios: You delete snapshots. You delete EVS disks. Then, the legacy snapshots of the disks are automatically deleted.
When you delete a disk whose standard snapshots have Instant Snapshot Restore enabled, the snapshots will not be deleted, but Instant Snapshot Restore will be disabled automatically.
Contact customer service. 400 EVS.1046 volume status must be available, error, error_extending, error_restoring, error_rollbacking when delete volume! Failed to delete the disk because the disk status is incorrect.
Run the following command to back up the configdriver partition: dd if=/dev/sdf4 of=/root/configdriver.img Information similar to the following is displayed: Run the following command and delete the configdriver partition: fdisk /dev/sdf Run the partprobe command to update the partition
User A can delete the unaccepted disk transfer. For details, see Deleting an EVS Disk Transfer. User B accepts transfer_id and auth_key. User B accepts the transfer through transfer_id and auth_key. For details, see Accepting an EVS Disk Transfer.
You are advised to periodically delete snapshots that are no longer used. This helps you avoid unnecessary billing on the snapshots. For details, see Deleting an EVS Snapshot. Parent Topic: Using EVS Snapshots
If you no longer need a disk, delete or unsubscribe from it in a timely manner. Constraints After a system disk is detached, some operations cannot be performed on the original server and the system disk.
Recycle bin When deleting an EVS disk, you can choose not to delete the disk immediately and move it to the recycle bin. This prevents data loss caused by accidental deletions.
To modify the setting, delete the task, restart the SMS-Agent, and configure the target server again. (Optional) Configure volume groups. If the source server uses LVM, you can resize logical and physical volumes. If the source server does not use LVM, skip this step.
The following is an example of a deny policy: { "Version": "1.1", "Statement": [ { "Effect": "Deny", "Action": [ "evs:volumes:delete" ]
After a disk is moved to the recycle bin, you can either recover the disk from the recycle bin or delete it permanently. EVS recycle bin is disabled by default. You need to enable it before using it.
Delete the source disk after the snapshot is created. You can add a maximum of 20 tags to a snapshot. Tag keys of the same snapshot must be unique.
Deleting Deletion failed An error occurs when you try to delete the EVS disk. None Expansion failed An error occurs when you try to expand the capacity of the EVS disk. Deleting Restoration failed An error occurs when you try to restore the EVS disk from a backup.
Initializing a disk does not delete the snapshots created for the disk, so you can still use snapshots to roll back data to the source disk after the disk is initialized.
You can delete some snapshots and then perform the change. In rare cases, the disk type may fail to be changed due to a background resource issue. If this happens, submit a service ticket. A disk protected by SDRS cannot have its disk type changed.
Delete the existing partition. In this example, delete the partition whose partition number is 1. rm 1 Re-create a primary partition.
Initializing a disk does not delete the snapshots created for the disk, so you can still use snapshots to roll back data to the source disk after the disk is initialized.
Except for tagging the disk during disk creation, you can also add, modify, or delete tags for existing disks. For more information about tags, see Managing EVS Tags. Enterprise Project default When creating EVS disks, you can add the disks to an existing enterprise project.
Initializing a disk does not delete the snapshots created for the disk, so you can still use snapshots to roll back data to the source disk after the disk is initialized.