Support

It all depends on the speed with which your host can transfer data to the cloud service you use (be it DropBox, Amazon S3 or any other service which is going to be implemented in the future). As mentioned in the documentation:

Before you begin, you should know the limitations. DropBox does not allow appending to files, so the archive has to be transferred in a single step. PHP has a time limit restriction we can't overlook. The time required to upload a file to DropBox equals the size of the file divided by the available bandwidth. We want to time to upload a file to be less than PHP's time limit restriction so as to avoid timing out. Since the available bandwidth is finite and constant, the only thing we can reduce in order to avoid timeouts is the file size. To this end, you have to produce split archives, by setting the part size for archive splitting in ZIP's or JPA's engine configuration pane. The suggested values are between 10Mb and 20Mb. Most servers have a bandwidth cap of 20Mbits, which equals to roughly 2Mb/sec (1 byte is 8 bits, plus there's some traffic overhead, lost packets, etc). With a time limit of 10 seconds, we can upload at most 2 Mb/sec * 10 sec = 20Mb without timing out. If you get timeouts during post-processing lower the part size.

If you are on shared hosting, there is an additional limitation. The bandwidth allocated to the shared server is finite and equally shared among all sites hosted on it. During peak hours, where many sites are active, it is shared among many sites and things may get extremely slow. During the second run you posted on the other thread the speed was roughly 400Kb/second which is quite good. During the first run it was about 100Kb/sec and dropping, which is too slow for all practical intents and purposes - unless you have a split archive size of 500Kb to 1Mb. The best approach is to do some trial and error to determine the off peak hours of your server and CRON-schedule your backup to happen during that timeframe.

You're welcome! We're here to help :)