Back up and restore ECS files-Cloud Backup(Cloud Backup)-阿里云帮助中心

This topic provides an overview of ECS File Backup Essential Edition from Cloud Backup, including its introduction, advantages, how it works, procedures, and billing.

Feature overview

ECS File Backup Essential Edition is a basic backup and recovery feature of Cloud Backup designed for ECS files. It is ideal for scenarios where you have basic backup needs for important files on an ECS instance and prefer minimal operational overhead. You can activate it with a single click and no configuration is required. It automatically backs up your data daily, and you can recover files accidentally deleted within 30 days. Billing is based on the total block storage capacity attached to your backed-up ECS instances and includes a free quota. For more information, see Billing.

Key benefits:

Backup lock
Backup points cannot be manually deleted or tampered with by ransomware, ensuring your backup data remains recoverable.
File-level recovery
You can restore individual files for granular recovery.
Cross-instance recovery
You can restore backup data to the original ECS instance or to another one, even if the original instance has been released.

How it works

Cloud Backup uses an automatically deployed client on your ECS instance to back up data. The client relies on Cloud Assistant for installation and management.

Note

In ECS File Backup Essential Edition, the client is deployed automatically and requires no manual management: it is installed when you activate backups, uninstalled when you cancel backups, and retained when you pause backups. The installation directories are as follows:

Linux installation path: /opt/alibabacloud/hbrclient
Windows installation path: C:\Program Files\Aliyun Hybrid Backup Service Client

The backup process uses a forever-incremental mechanism. The first backup is a full backup, and subsequent backups upload only the changed data. A complete backup point is then synthesized in the cloud. The client performs data deduplication and compression to reduce network traffic.

Limits

ECS File Backup Essential Edition is available in the following regions: China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Zhongwei), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hong Kong), Malaysia (Kuala Lumpur), Malaysia (Johor), Philippines (Manila), Indonesia (Jakarta), Thailand (Bangkok), Japan (Tokyo), South Korea (Seoul), Singapore, Germany (Frankfurt), UK (London), Saudi Arabia (Riyadh), UAE (Dubai), US (Virginia), US (Silicon Valley), US (Atlanta), and Mexico (Mexico City).
You can use either ECS File Backup Essential Edition or ECS File Backup Standard Edition to back up files on an ECS instance, but not both at the same time.
ECS instances that use a 32-bit operating system or reside in a classic network are not supported.
Only data on block storage attached to an ECS instance can be backed up. Network-attached storage, such as NAS, ossfs, and GlusterFS, is not supported.
For ECS instances purchased before December 1, 2017, you must manually install the Cloud Assistant Agent.
The first time you use this feature, you must create and authorize the AliyunServiceRoleForHbrEcsBackup service-linked role. Follow the on-screen instructions to complete this step.
You cannot restore data from a backup point to an ECS instance that is in the Stopped state.
By default, Cloud Backup limits the backup speed to avoid consuming excessive ECS instance resources. If the amount of file data on a single ECS instance exceeds the following limits, the backup may not complete within 24 hours. In this case, subsequent backup jobs are skipped to prioritize the completion of the current job.
- High backup priority: 2 TB
- Low backup priority: 600 GB
If your data volume exceeds these limits, you may have fewer than 30 daily backup versions. To ensure that daily backups succeed, contact online technical support.
Backed-up directories: ECS File Backup Essential Edition backs up only user data. System directories and temporary system files are not backed up. The excluded directories vary by operating system:
- Windows: Excludes all directories named Windows\, python27\, Program Files (x86)\, Program Files\, ProgramData\, Boot\, $RECYCLE.BIN\, System Volume Information\, Users\Administrator\NTUSER.DAT, Users\Administrator\ntuser.dat.LOG*, and pagefile.sys, as well as the client installation directory.
- Linux: Excludes the /bin/, /usr/bin/, /sbin/, /usr/sbin/, /srv/, /selinux/, /lib/, /lib32/, /lib64/, /boot/, /run/, /dev/, /proc/, /sys/, and /lost+found/ directories, as well as the client installation directory.
Database file backup: ECS File Backup Essential Edition reads file content by using the file read/write APIs of the file system and then writes the content to the backup vault. Database files are often locked and continuously modified by the main database process, which can cause read operations to fail frequently. Even if a read operation succeeds, the backup of the database file might be inconsistent due to continuous data modification, making the database unrecoverable from the backup. For this reason, we recommend that you use the ECS Database Backup feature.
Special file types: Socket and hard link files cannot be backed up or restored and are skipped during backup and restore jobs.

Video tutorial

This video demonstrates how to use ECS File Backup Essential Edition to back up files on an ECS instance.

Backup overview

Go to the Cloud Backup console and select a region at the top of the page. You can view the Backed-up ECS, Backed-up block storage capacity, and Un-backed-up ECS in the current region. You can also view the total number of backed-up ECS instances and the total backed-up block storage capacity across all regions. The total backed-up block storage capacity across all regions is the sum of the free quota and billable capacity. The progress bar shows the used free quota and used billable capacity separately. The billable portion is the basis for your charges.

The following table describes the metrics.

Metric	Description	Example
Backed-up ECS	The total number of ECS instances that have backup versions. This includes released instances that still have backup versions but does not include instances where backup is activated but no backup versions exist yet.	You have 12 running ECS instances in the current region. Of these, 5 have ECS File Backup Essential Edition activated and have backup versions, 3 have it activated but do not have backup versions yet, and 4 do not have it activated. You will see: Backed-up ECS: 5 Un-backed-up ECS: 7 The 3 instances that are activated but do not have backup versions yet are counted as un-backed-up ECS instances. After backup versions are generated, they are automatically counted as backed-up ECS instances. You will then see: Backed-up ECS: 8 Un-backed-up ECS: 4 If you have released ECS instances that still have backup versions for recovery, these instances are also counted as backed-up ECS instances, and their corresponding block storage capacity is included in the backed-up block storage capacity.
Backed-up block storage capacity	The total capacity of block storage attached to the backed-up ECS instances. If no activated ECS instances have backup versions, this value is 0. In the all-regions view, the backed-up block storage capacity shows the used free quota and remaining free quota separately. The capacity that exceeds the free quota is displayed as billable capacity.
Un-backed-up ECS	The total number of existing ECS instances that do not have backup versions. Only unreleased instances are counted. This includes instances where backup is activated but no backup versions have been generated yet (for example, the feature was just activated, backups are consistently failing, or backup versions expired due to paused backups).

Backup and restore

Create an ECS file backup

Before you begin, activate the Cloud Backup service and make sure your ECS instance meets the requirements. For more information, see Limits. The procedure involves selecting an instance, configuring backup parameters, and starting an automatic backup job.

Important

If you attach or detach a disk during a backup job, the inclusion of that disk's data in the backup version depends on when the action occurred during the job.

Go to the Cloud Backup console. At the top of the page, select the region of the ECS instance that you want to back up.
Click Add ECS with No Backup and configure the following parameters.
- ECS to Be Backed-up: Select the ECS instance to back up.
- Start Time: By default, a time point between 00:00 and 06:00 is automatically selected. To specify a time, select Specified Time and set a time point.
- Advanced Settings: By default, Cloud Backup performs low-priority backups and the Keep At Least One Backup Version feature is enabled. Modify these settings as needed.
  - Backup Priority: Select Low (maximum backup throughput of 10 MB/s, uses 1 vCPU core) or High (maximum backup throughput of 30 MB/s, uses up to 2 vCPU cores).
  - Keep At Least One Backup Version: This feature is enabled by default to ensure that at least one backup version is always retained and not automatically deleted. For more information, see Modify backup settings.
Click OK.

The system automatically backs up the ECS instance files daily based on your settings. You can view the backup progress on the View Details > Backup Jobs tab for the target instance in the Cloud Backup console. When the Job Status changes to Complete, the backup is complete and a backup version is created.

Note

A backup version is a collection of multiple backup points from a specific time. For example, if an ECS instance has two partitions, C and D, a backup of the ECS instance generates one backup version that contains two backup points: one for partition C and one for partition D. To restore files, you must select a specific backup point (represented by a green dot in the backup history) for either partition C or D to perform file-level or folder-level recovery.

Backup running status

After you activate backups, you can view the current status of each instance in the Backup running status column on the ECS File Backup Essential Edition page. The following table describes each status.

Status	Description
Not Activated	ECS File Backup Essential Edition is not activated for this ECS instance.
Preparing	ECS File Backup Essential Edition is activated for this ECS instance. The backup client is being installed. This process typically takes about 5 minutes.
Preparation Failed	The backup client failed to install. For more information, view the error details in the console.
Ready	The backup client is installed. The system is waiting for the first backup job to start.
Running	The backup status is normal. The system is waiting for the next backup job to run.
Running (Backing Up)	The backup status is normal, and a backup job is in progress.
Backup Failed	The backup job failed. Common causes include an offline client, Cloud Assistant unavailability, or insufficient disk space. View the error details in the console and see ECS File Backup Essential Edition issues for troubleshooting.
Paused	The backup job is paused.
Stopped	The ECS instance cannot be found, and the backup job has been automatically stopped.

Note

In the Paused and Stopped states, backup data is retained and expires automatically after the 30-day retention period. You can still use the existing backup versions for restores.

Restore ECS files

You can restore files from a historical backup point to a specified path on the original instance or another ECS instance. You can choose to restore all files or filter for specific files.

Go to the Cloud Backup console. In the View Details column of the target ECS instance, click View Details.
On the Backup History tab, find the row that contains the target backup point and click Restore in the Actions column. Alternatively, switch to the timeline view by clicking the icon on the right, click a backup point, and then click Restore.
Configure the following restore parameters.
- Restore Destination: By default, the Original ECS is selected. You can also select another ECS instance that is not in the Stopped state in the same region as the restore destination.
- Destination Path: By default, files are restored to the Original Path. If you select Other Path, ensure the destination path exists on the destination instance. Otherwise, the restore job will fail.
- File Conflict Policy: By default, Skip This File is selected. You can also select Overwrite The File. This action permanently overwrites the original file content. Use this option with caution.
- Restore Items: By default, All is selected. You can also select Include Files to restore only selected files, or Exclude Files to restore all files except for those selected.
  Note
  If a directory specified for restoration is empty in the backup point, Cloud Backup creates a restore job but does not restore any files.
Click OK to start the restore.
The system performs the restore job based on your settings. You can view the progress on the View Details > Restore Jobs tab for the target instance in the Cloud Backup console. When the Job Status is Complete, the restore is complete.

Browse backup files

View the list of backed-up files in a specific backup point.

Go to the Cloud Backup console and click View Details in the View Details column of the target ECS instance.
On the Backup History tab, find the row that contains the target backup point and click Browse in the Actions column to view the backed-up files.
Click the list view icon to the right of the Backup History section to switch to a list view and view backup records.

Cancel backup and restore jobs

To cancel a backup or restore job, perform the following steps in the Cloud Backup console.

Cancel a single backup job

At the top of the page, select the region where the target ECS instance resides.
In the Actions column, click View Details and go to the Backup Jobs tab.
For a running job, click Cancel. In the dialog box that appears, click OK.

Cancel a single restore job

At the top of the page, select the region where the target ECS instance resides.
In the Actions column, click View Details and go to the Restore Jobs tab.
For a running job, click Cancel. In the dialog box that appears, click OK.

Modify backup settings

To modify backup settings, perform the following steps in the Cloud Backup console.

Actions	Description
Pause or resume backups	At the top of the page, select the region where the target ECS instance resides. In the Actions column, click Suspend Backup or Resume Backup. Alternatively, click View Details, and then click Suspend Backup or Resume Backup next to Backup Running Status. In the dialog box that appears, click OK to pause or resume periodic backups. After you pause backups, subsequent backup jobs do not run. Existing backup versions and points are not affected and expire automatically after the 30-day retention period. If the Keep At Least One Backup Version feature is enabled, the last backup version is not affected. If an ECS instance still has backup versions after you pause backups, billing for that instance continues.
Cancel backups	Warning When you cancel backups for an ECS instance, Cloud Backup deletes all backup points for that instance, stops billing, and removes the instance from the backup list. At the top of the page, select the region where the target ECS instance resides. In the Actions column, click Stop Backup. Alternatively, click View Details and then click Stop Backup next to Backup Running Status. In the dialog box that appears, click OK to cancel the instance backup.
Disable or enable Keep At Least One Backup Version	Important If you disable this option, the backup versions for the ECS instance are automatically deleted after the 30-day retention period expires. You may have no backup versions available for recovery if backups are paused or due to accidental operations. If you disable the Keep At Least One Backup Version feature, the configuration takes effect within one hour. If only the last backup version remains and its retention period has expired, it will be deleted within one hour. If you enable this option, the latest backup version is not deleted due to retention period expiration or accidental operations. This ensures you always have at least one backup version available for recovery. At the top of the page, select the region where the target ECS instance resides. In the Actions column, click ┇ > Disable Keep At Least One Backup Version or ┇ > Enable Keep At Least One Backup Version. Alternatively, click View Details and then enable or disable the Keep At Least One Backup Version feature. In the dialog box that appears, click OK to apply the setting.
Modify backup priority	The configuration change takes effect when the next backup job runs. At the top of the page, select the region where the target ECS instance resides. In the Actions column, click ┇ > Modify Backup Priority. Alternatively, click View Details and then click the modify icon next to Backup Priority. In the dialog box that appears, select a Backup Priority and click OK.
Modify the next backup time	At the top of the page, select the region where the target ECS instance resides. In the Actions column, click ┇ > Modify Next Backup Time. Alternatively, click View Details and then click the modify icon next to Next Backup Time. In the dialog box that appears, set the Next Backup Time and click OK. You can modify only the time of the backup, not the date. If the backup for the current day has not yet run and the modified time is later than the current time, the backup for the current day and all subsequent backups run at the modified time. If the modified time is earlier than the current time (for example, if the backup is scheduled for 05:00 and you change the time to 04:00 at 04:30), the backup for the current day is skipped. Use this option with caution. If the backup for the current day has already run, subsequent backups run at the modified time, regardless of whether the modified time is before or after the current time.

Production best practices

Backup priority: In a production environment, we recommend that you set different priorities for ECS instances based on their purpose. For critical business instances, use low-priority backups to reduce the impact on business performance. For non-critical business instances, use high-priority backups to shorten the backup window and avoid conflicts with peak business hours.
Keep At Least One Backup Version: We recommend that you enable this feature. For more information, see Enable Keep At Least One Backup Version.
Important
If you enable this feature, the instance will always retain at least one backup version, even if backups are paused, and billing will continue.
Canceling backups: This action permanently deletes all historical backup versions. Before you proceed, ensure the data is no longer needed. Before you upgrade to a different backup plan, make sure that the new plan has completed at least one successful backup.
Failure alerts: When a backup fails, the system automatically sends alert SMS messages, emails, and internal messages to the Alibaba Cloud account. Review these alerts promptly and see ECS File Backup Essential Edition issues for troubleshooting information.

Billing

Billing method: You are charged based on the total block storage capacity attached to your backed-up ECS instances (instances with one or more backup versions). The charges are not affected by the actual volume of file data on the instances. The service uses a pay-as-you-go model with daily billing and daily settlement. Billing starts after the first backup version is created. You can purchase resource plans to offset pay-as-you-go fees.
Free quota: The Alibaba Cloud account and its RAM users share a free quota of 100 GiB across all regions. You are charged for usage that exceeds the free quota.
Cost calculation: Your daily fee is calculated based on the total block storage capacity of the ECS instance, as recorded in the latest backup version created before 00:00 (UTC+8) each day. If a daily backup is skipped because the data volume is too large, you are still charged based on the capacity of the latest valid backup version.