Here is a list of known constraints that you may encounter while using Cloud services via SyncBackPro V7:
Cloud services do occasionally fail. Check to make sure the cloud service is running correctly: http://support.2brightsparks.com/knowledgebase/articles/451450-cloud-service-status
All Cloud Services
If SyncBackPro displays the message Cloud service is throttling requests" then it means the cloud service is asking SyncBackPro to slow down. This is a protection mechanism for cloud services so they do not become overloaded with requests. SyncBackPro will then pause a short while and continue. If SyncBackPro does not slow down then the cloud service will simply fail to provide the services to SyncBackPro.
Some users have reported experiencing slow transfer speeds (usually during uploads) with some Cloud services, even though their Internet bandwidth can go much higher than that. Please note that we've not included any speed throttling in our program code. The throughput speed is going as fast as it could and there is no configuration settings in SyncBackPro to adjust in order to 'make it go faster'.
Bear in mind that the transfer speed will depend on several factors, including the REST API component we rely on to communicate with the Cloud service, how fast the receiving server can accept and process incoming data, the routing path between your geographical location and the physical location where the Cloud server is hosted, etc. In times of high usage it's entirely possible that the cloud providers will give preference to their own software before 3rd party software like SyncBackPro.
Can't set the modification date/time stamp of files uploaded to Dropbox to match the Source - Dropbox's REST API does not allow the setting of modification date/time stamps of uploaded files to it. This means the Last Modified date/time stamp of files on your Source will never match those files on Dropbox as the cloud will set a stamp of the date & time the file was copied to it instead. The Dropbox desktop app does not have this issue, but it is existent in the REST API.
For more info visit the following:
Note - This article applies to SyncBackPro V7 and/or later only.