Use sync backup to synchronize folders between Cloud Drive for Enterprises (CDE) and local devices in real time. Choose bidirectional synchronization or one-way upload for collaboration, backup, and multi-device access, and maintain eventual consistency across devices.
Prerequisites
Use the PC client to log on to CDE client version 1.4.0 or later. For the latest version, see Client download.
Enable the history version feature.
Provide the enterprise code and contact us to enable sync backup.
Enable sync backup
For first-time use, complete the on-screen installation steps to enable sync backup. 

Choose a sync mode
Choose the sync mode based on your synchronization requirements before creating a task.
Mode | Recommended scenarios | Key behavior |
Bidirectional synchronization | Collaboration and multi-device editing, where local and cloud data must stay consistent. | Changes on either side are synchronized to the other side. |
One-way upload | Backup scenarios where local changes are synchronized to the cloud and cloud-side changes do not affect local files. | Local changes are uploaded. Cloud-side changes do not affect local files. |
Set mode options in the task
Select bidirectional synchronization or one-way upload
In Synchronization type, select bidirectional synchronization or one-way upload for folders in team space, personal space, or received shares.
Then select the cloud folder that you want to synchronize.


Advanced settings
Bidirectional synchronization
Keep local and cloud file data consistent. Changes on one side are synchronized to the other side.
One-way upload
Synchronize local folder changes to the cloud, except delete operations. Changes to cloud files do not affect local files.
The delete rule can be set in Advanced > Other Settings > Delete local files in one-way upload mode.


Configure sync backup in the client
After sync backup is enabled, complete the following steps in the client to create and manage sync backup tasks.
Open sync backup
On the Synchronized Backup page, click Creating Synchronized Backups. 
Create a sync backup task
On the Creating Synchronized Backups page, complete the required fields Select local folder, Select cloud folder, and Synchronization type (default: bi-directional synchronization).

On the Advanced page, configure sync filtering, sync throttling, local file deletion handling in one-way upload mode, and whether to enable automatic synchronization.

Sync details
Sync details include Synchronized completion, Synchronizing, and Synchronization failed.

Sort sync tasks by Cloud Name or Creation Time.
Filter sync tasks by synchronization status, type, and space.

Manage sync tasks: pause, cancel, or configure synchronization, and view local or cloud synchronized files.

Mode behavior reference
Use this section as a detailed reference after you choose a mode and create a task.
Bidirectional synchronization
In bidirectional synchronization mode, the local directory will be completely consistent with the cloud. File operations on one end will be reflected on the other end. There are differences when performing delete operations:
When a file is deleted locally, the corresponding file in the cloud will be moved to the recycle bin.
When a file is deleted in the cloud, the Windows system will move the local file to the recycle bin, while the Mac system will directly delete the file (currently does not support moving to the trash).
One-way upload
In one-way upload mode, the local directory will be backed up to the cloud. File operations in the cloud directory will not affect local files. This mode is mainly suitable for backup scenarios.
When different file operations are performed locally, the corresponding behavior in the cloud is as follows:
File operation performed locally
Cloud behavior
Create a file
Create a file
Delete a file/move to recycle bin
No operation by default
(If the deletion configuration is enabled, the cloud file will be moved to the recycle bin)
Move a file
Move a file
(Due to operating system limitations, moving A-->B/A may eventually result in creating A under B in the cloud, with the original A file remaining; the same applies to renaming files)
Rename a file
Rename a file
Modify file content
Create a new version
Copy a file
Create a new file
When different file operations are performed in the cloud, the corresponding behavior locally is as follows:
File operation performed in the cloud
Local behavior
Create a file
No operation
Delete a file/move to recycle bin
If the file is uploaded locally: re-upload the original file to the cloud
(To delete a file backed up locally in the cloud, you need to enable the delete switch first, delete the corresponding local file, and the cloud will automatically move the file to the recycle bin.)
If the file is not uploaded locally: no operation
Move a file
Rename a file
Modify file content
No operation
(If the cloud modifies a file backed up locally, the file version successfully backed up locally will exist in the cloud file history version. However, due to the limitation of the number of history versions and the impact of automatic merge policies, the file version successfully backed up may be cleared. You need to set an appropriate version merge/cleanup policy based on specific usage scenarios or try not to edit files uploaded from local backups in the cloud.)
Copy a file
No operation
Permissions
If you encounter issues during Authorization Management, refer to Permission Description.
Synchronizer permission
Users with the Synchronizer permission can perform bidirectional synchronization or one-way upload on folders in team space and received shares. 
Backer permission
Users with the Backer permission can perform one-way upload on folders in team space and received shares. 
No Synchronizer or Backer permission
Users without Backer or Synchronizer permissions can perform bidirectional synchronization or one-way upload only on folders in personal space and received transfers.
Usage notes
Sync backup consumes storage space on both local devices and the cloud. Ensure that enough storage is available on both sides.
To synchronize local files to the cloud in time, keep the client running in the background and maintain a stable network connection.
After sync backup is enabled, if the sync backup entry does not appear in the user interface, log on again and check.
This feature is a value-added service. It is free during public preview. If charges are introduced later, we will notify you in advance.
During the creation of sync backup, if there are files or folders with the same name in the same path locally and in the cloud, the following automatic processing will occur:
If files exist on both ends, the local file will be uploaded to the cloud as a new version, and the original cloud file will be saved in the history version.
If one end is a file and the other end is a folder, one of them will be automatically renamed.
Limitations
Supported operating systems and versions |
Linux and NAS are not supported |
Supported file systems |
|
Local directories not allowed to create sync backup |
|
Number of sync directories | A single user on a single terminal is allowed to create up to 10 sync directories. |
Number of sync files | A single terminal is allowed to sync up to 1 million files. |
File path length | Windows does not support syncing files with a full path length exceeding 260 characters (system default limit). |