Support

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

I have set up the confiuration to upload my backup files to my OneDrive account. However, I keep getting an error message that "Invalid JSON data received" (see below)

DEBUG |170515 14:23:09|Akeeba\Engine\Postproc\Onedrive::Akeeba\Engine\Postproc\Onedrive::initialiseConnector - Validating the OneDrive tokens
DEBUG |170515 14:23:09|Akeeba\Engine\Postproc\Onedrive::Akeeba\Engine\Postproc\Onedrive::processPart - Using chunked upload, part size 10485760
DEBUG |170515 14:23:09|Akeeba\Engine\Postproc\Onedrive::Akeeba\Engine\Postproc\Onedrive::processPart - Uploading chunked part
DEBUG |170515 14:23:09|Akeeba\Engine\Postproc\Onedrive::Akeeba\Engine\Postproc\Onedrive::processPart - Got uploadPart Exception 500: Invalid JSON data received
DEBUG |170515 14:23:09|Akeeba\Engine\Postproc\Onedrive::Akeeba\Engine\Postproc\Onedrive::processPart - Maximum number of retries exceeded. The upload has failed

How can I fix this??

Please zip and post the entire backup log. It is helpful to see the context of the error and the other data in the log.

Here's the zipped file.

That's a BIG backup archive. I have been thinking in terms of a host limit, but we may be running into a limit on the Microsoft end. Microsoft says they have throttling limits in place but won't disclose them https://social.msdn.microsoft.com/Forums/en-US/c4aaa90c-dc75-441f-9b30-f5c45e402ac4/limitation-on-api-requestfile-size-limitationresume-upload?forum=onedriveapi. If you really want to back up this volume of data you should look at business-grade file hosting (Amazon S3, RackSpace CloudFiles, Microsoft Azure etc) instead of consumer-grade file hosting (OneDrive, Google Drive etc). Consumer grade file storage solutions always have limits to prevent abuse. No customer is expected to move so much data at once.

Another option is to look for static data on your site, data that does not change frequently. You can manually copy that data to one or more safe locations, then exclude it from your backup. You get a smaller, faster backup and the archive size may miss the limits we're hitting now. The disadvantage is that your restore becomes a two step process. First you restore your backup archive, then you need to copy your static data back to your site.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.