Hi!
We are experiencing random errors when the app searches for old backups to clean up in the Dropbox destination. The task involves around 14 databases performing a full backup at 2:00 AM, followed by a differential backup every hour throughout the day.
Most of the time, the error occurs in only one database, but it is not always the same one. On some occasions, errors appear in multiple databases. Additionally, not every run produces an error. For example, in the last 20 runs, 10 completed without issues, while the other 10 encountered errors (see attached image).
This behavior has become more frequent in the past month. Previously, it occurred only on rare occasions. Below is a snippet of the log showing the error messages:
• 12:06:44 PM : Cleanup of “CSTransporte_TuBus” completed.
• 12:06:44 PM : Cleaning up backups of “CSTransporte_DelSurBus” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:08:16 PM : ERROR: Failed to search on the “Dropbox” destination:
• 12:08:40 PM : Cleanup of “CSTransporte_DelSurBus” completed.
• 12:08:40 PM : Cleaning up backups of “Catedral_LobosBus” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:09:18 PM : Cleanup of “Catedral_LobosBus” completed.
• 12:09:18 PM : Cleaning up backups of “Catedral_DelSurBus” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:09:57 PM : Cleanup of “Catedral_DelSurBus” completed.
• 12:09:57 PM : Cleaning up backups of “Catedral_TuBus” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:10:41 PM : Cleanup of “Catedral_TuBus” completed.
• 12:10:41 PM : Cleaning up backups of “Catedral_SalernoViajes” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:11:30 PM : Cleanup of “Catedral_SalernoViajes” completed.
• 12:11:30 PM : Cleaning up backups of “CSTransporte” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:12:58 PM : ERROR: Failed to search on the “Dropbox” destination:
• 12:13:18 PM : Cleanup of “CSTransporte” completed.
• 12:13:18 PM : Cleaning up backups of “CSTransporte_DelSurBus_Gasoducto” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:13:59 PM : Cleanup of “CSTransporte_DelSurBus_Gasoducto” completed.
• 12:13:59 PM : Cleaning up backups of “CSTransporte_LobosBus_Gasoducto” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:14:37 PM : Cleanup of “CSTransporte_LobosBus_Gasoducto” completed.
• 12:14:37 PM : Cleaning up backups of “CSTransporte_TuBus_Gasoducto” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:15:18 PM : Cleanup of “CSTransporte_TuBus_Gasoducto” completed.
• 12:15:18 PM : Cleaning up backups of “CSTransporte_Web_LobosBus” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:15:56 PM : Cleanup of “CSTransporte_Web_LobosBus” completed.
• 12:15:56 PM : Cleaning up backups of “CSTransporte_LobosBus” database at “Dropbox” destination “Datacenter Lobos Bus”.
• 12:17:27 PM : ERROR: Failed to search on the “Dropbox” destination:
• 12:17:48 PM : Cleanup of “CSTransporte_LobosBus” completed.
• 12:17:49 PM : Cleaning up backups of “CSTransporte_Web_DelSurBus” database at “Google Drive” destination “LobosBus Backups”.
• 12:17:50 PM : Cleaning up “SQL Backups\CSTransporte_Web_DelSurBus” folder.
To investigate the issue futher, we need more information. Could you please, enable the Advanced Log, reproduce the issue, and then send log to our dev team. Here are more details on how to do it How to send Log to developers – SQLBackupAndFTP's blog
Important: Once logging is enabled, please attempt to reproduce the error so that all necessary details are captured in the log. Then, send the log to our developers for analysis.
Please let us know once the log has been sent along with your Application ID (“Help” > “Application ID”).
FYI we’re seeing the same problem. All started 3-4 weeks ago. In my case, it was always the same sub-folder. As a test, I renamed the folder so a brand new folder would be created during the next run. My thinking was maybe the folder had too many files in it (approx 40).
Still go the error with only 5 files in it. Definitely seems like a throttle or api limit on the Dropbox side of the equation
We suspect the issue is related to Dropbox limiting the number of API requests, specifically the API search calls.
Our team is actively working on a solution to resolve this as soon as possible.
As a temporary workaround, if you have multiple backup jobs, we recommend scheduling them at different times to reduce the number of simultaneous requests.
It has to be in the either the Search API request count, or total requests per minute.
Oleg, right now there’s a setting that backs up everything, then uploads everything. Or backup one, upload one, backup one, upload one. Why not enhance that to include the cleanup logic? It’s already a per-database loop anyways. Then users hitting that API limit can switch to the one-one mode until a more definitive fix is possible.
That would at least extend the timing of the API calls in an organic way without a major design change.
We’re planning to release a new version in the coming weeks to address this issue with Dropbox more reliably. We’ll keep you posted once the update is available.
We’ve made improvements to address the issue with Dropbox. Could you please download and install the updated version of SQLBackupAndFTP from the link below?
After installation, please go to your Dropbox destination settings and disable the option: “Verify backup files on the destination after uploading”
(see the screenshot for reference).
Let us know if the issue persists or if you need any further assistance.
