Contributors Download PDF of this page
These known limitations identify platforms or features that are not supported.
Cloud Sync is not supported in China.
In addition to China, the Cloud Sync data broker is not supported in the following regions:
AWS GovCloud (US)
Azure US Gov
Azure US DoD
SMB sync behavior due to case-insensitivity limitation
The SMB protocol is case-insensitive, which means uppercase and lowercase letters are treated as being the same. This behavior can result in overwritten files and directory copy errors, if a sync relationship includes an SMB server and data already exists on the target.
For example, let’s say that there’s a file named "a" on the source and a file named "A" on the target. When Cloud Sync copies the file named "a" to the target, file "A" is overwritten by file "a" from the source.
In the case of directories, let’s say that there’s a directory named "b" on the source and a directory named "B" on the target. When Cloud Sync tries to copy the directory named "b" to the target, Cloud Sync receives an error that says the directory already exists. As a result, Cloud Sync always fails to copy the directory named “b.”
The best way to avoid this limitation is to ensure that you sync data to an empty directory.
SMB limitation for hidden directories and files
An SMB limitation affects hidden directories and files when syncing data between SMB servers. If any of the directories or files on the source SMB server were hidden through Windows, the hidden attribute isn’t copied to the target SMB server.