Which if any of the numbers seem ballpark OK, e.g. according to Duplicati Home screen, and left side near bottom of https://onedrive.live.com/ where it says what’s used and what total available space is?
Sounds like there might be some prior backups. Was there a problem leading to the need to reinstall?
You possibly don’t have a log for the backup that raised the error, but if you got one, what does it say?
Does this message reoccur if you backup again? I think the quota testing runs before next backup too.
Free Space: 22.90 GB
Total Space: 25.00 GB
It takes an empty folder which you point to with a URL similar to what Export As Command-line has.
For a shorter test, you can give it something like --reruns=1 to get it to get to the quota a little faster.
Although this is still Duplicati code, it’s a simpler environment than the full program, so it might differ.
If macOS won’t run the .exe directly, you can probabably run it by adding mono before the command.
There are probably some third-party programs that can get the quota, but one would have to search.
If the problem is actually OneDrive returning it wrong (not proven yet), it will be hard to work around.
The backup Destination is now Storage typeMicrosoft OneDrive v2, not Local folder, right?
Using a file sync protocol sort of works, but would be a completely different exercise in quota debug.
I did have MS Office 365 with 1TB Onedrive storage but I discontinued it and now have a 100GB plan.
I was not able to run the Tester command from the Mac terminal. I think because it doesn’t like .exe with or without mono or mono. in the front. I tried to look for Total Quota for Onedrive but don’t know how to get it. I can try through MS support or try to find a third party option.
Edit: After I’d posted this I created another backup on Google Drive and it also had the same error as with Onedrive. It says it ran successfully but it gave the same error and the log looked the same as with the Onedrive backup.
This morning the Onedrive and Google Drive backups ran successfully but both received the same error about the Quota being exceeded. Their error logs looked the same for TotalQuotaSpace, FreeQuotaSpace and Retries.
The backup to Box Drive succedded without error.
I then did a successful restore from Onedrive but it also gave the Quota exceeded error:
2020-04-06 10:43:02 -05 - [Error-Duplicati.Library.Main.Operation.FilelistProcessor-BackendQuotaExceeded]: Backend quota has been exceeded: Using 2.01 GB of 233.47 GB (0 bytes available)
The restored files all seem to be good so it looks like things are working even with the errors.
The job of mono is to run the .exe and .dll files which in this case are portable code, not Windows code. Application Deployment explains. If you can run mono at all, run mono --version. You need at least 5.
If mono can’t find the .exe, it’s possibly because I forgot to tell you you should either cd or use full path.
It turned out to be quite hard for me (without a Mac) to figure out where things are, but here’s one view. Yours (seen through the ps command, maybe something like ps -auxf | grep mono) may be similar. You can see there how mono is launched, and given a .exe to run. Other .exe files are in the folder too.
I’m also still trying to confirm that you’re going directly to OneDrive, and that your Destination looks like:
I’m still also looking for space history from jobs before the problem rose, to see how it looked back then. Suddenly seeing different results without Duplicati changes would suggest that OneDrive changed then. Possibly this also matches when you changed your size to 100 GB. I don’t know why 999995129856 is still being reported by OneDrive, and I doubt Duplicati made it up – it’s an odd value. How far back is it?
I’m glad you got it going. I don’t know what’s up with missing files. In theory, anything Duplicati does to the local filesystem should eventually get synced to the remote, but one loses the better tracking done by Duplicati. One can even get files uploaded in unknown order chosen by the sync software. This can leave who-knows-what on the remote to restore from if the local drive breaks before finishing the sync.
Knowing you were pointing to a local folder means this is possibly a seeming bug in mono described at