Cloud Backup:Overview

To synchronize data in the Cloud Backup console, perform the following steps:

1. Activate Cloud Backup

   You are not charged for activating Cloud Backup. You are not charged for using the data synchronization feature of Cloud Backup. You are charged for using NAS to read files over the Internet and store files. You are charged for using OSS to store files. For more information, see Billing overview of NAS and Billing overview of OSS.

2. Install the Cloud Backup client

   Before you synchronize data from HDFS file systems, on-premises NAS file systems, S3-Compatible Storage buckets, CPFS file systems, OSS buckets, and OSS-Compatible Storage buckets, you must install a Cloud Backup client on the servers where the data sources are located. The client is used to establish data connections and manage services with Cloud Backup.

3. Add data sources

   In the Cloud Backup console, add data sources such as HDFS file systems, on-premises NAS file systems, S3-Compatible Storage buckets, CPFS file systems, OSS buckets, and OSS-Compatible Storage buckets.

4. Create a synchronization plan

   Create a data synchronization plan. Cloud Backup runs the plan and continuously synchronizes data based on the plan.

Limits

• The Cloud Backup client for Windows does not support mounting of Network File System (NFS) file systems. If NFS files systems exist on the source or destination, select the Cloud Backup client for Linux when you create a synchronization plan.

• Neither OSS nor S3-Compatible Storage supports synchronization of Archive objects. Only data of objects (including the objects to which symbolic links point) is replicated. Metadata information, such as the read and write permissions on the objects, is not supported.

• For NAS data synchronization, the maximum length of a file name is 248 bytes. If the length of a file name exceeds 248 bytes, the file fails to be synchronized or the synchronization job is partially completed.

Incremental file list (ChangeList)

Cloud Backup synchronizes data based on an incremental file list. You do not need to perform a full scan. This reduces the file scanning cost and improves synchronization efficiency. When you create a synchronization plan, if the selected data source is an OSS bucket or an S3-Compatible Storage bucket, you can use the custom incremental file list for synchronization.

1. An incremental file list is a CSV table that contains the information about the files to be synchronized on the data source. Each row in the table represents a file. The Name field indicates a path relative to the synchronization path of a data source. The following figure shows a changeList1.csv table. The Name field is a required column that records the files to be synchronized. Other columns are not supported.

   

   Note

   • The values in the Name column must be unique. If the same file name is used, files with the same name overwrite each other during data synchronization.

   • The value of the Name field cannot be a directory and must be a file.

2. When you create a synchronization plan, enter the path where the incremental file list is located. When a data synchronization job starts, Cloud Backup reads all CSV files in the path on the source, parses the files, and transfers the files to be synchronized to the destination.

   Note

   For example, when you create a plan for synchronization from OSS to NAS, you can use an incremental file list to specify the files to be synchronized. If the incremental file lists changeList1.csv and changeList2.csv are stored in the path /changelist on the source, the value of the path for the incremental file lists is /changelist.

3. After the files in each CSV table are processed, the CSV table is moved to the /Completed level of the directory.

   Directory of the CSV table before processing	Directory of the CSV table after processing
   /changelist/changeList1.csv /changelist/changeList2.csv	/changelist/Completed/changeList1.csv /changelist/Completed/changeList2.csv