BAckup failing with error 422

[Eysenor]

I have a backup running for a folder with photos that is around 400GB and I'm backing it up to Drime cloud. The initial backup often get stuck when around half or 2/3 of the files are uploaded but eventually it worked. Then it worked daily for some week until recently I'm getting a lot of these errors and the backup marked as failed.

Error: rclone: 2026/05/05 10:21:47 ERROR : data/6c/6c2eabe855b6fde453c17bc87377af3d91152be0fd3147b86b9d0a3b6ea73d3d: Post request put error: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {"message":"","errors":{"name":"Folder with same name already exists."}}"

The info about the backup shows that new files were added as well as some modified. I'm not sure if that is really accurate since I get some day 400+ new files even though I do not add that many pictures. Maybe it refers to something else.

Does anyone know where there error come from and how to solve it? I can see that there is a problem with existing folders but I do not know how to solve it.

[towfiqi]

@Eysenor Could be a bit rot. Open your Backup Plan, click the 3 dots, and then click "Check Integrity" and share what the output.

[Eysenor]

I get a lot of errors like "pack 38eb32e2cd4a312a59a0754558dbe276d350ab90797ecbd1636eef2c8336d453: does not exist".

I deleted the failed backups before to see if that would help but maybe it did worse. I can also delete the whole plan and make a new one. Hopefully it can properly upload the whole folder and not get stuck. That, I feel, might be an issue with the cloud provider and rsync.

EDIT: I checked a backup plan that did not have failed backups and still I get the same error when checking the integrity of it. So could this actually be a problem with the cloud provider?

[towfiqi]

Try creating a backup plan and select a storage that's around a few hundred megabytes. After the backup is complete, check the integrity and see if that issue is still happening.

Also, if you have any other cloud storage, other than Drime, try creating a backup plan with it and see if it has the same issue.

[Eysenor]

I tried a smaller backup of 1.8 GB on both Drime and Koofr clouds and that worked fine. The integrity check passes for both. I'm now trying again the old, bigger backups to see if they work.
But every time I try again to backup a bigger folder (400GB) it gets stuck around 75% of the uploaded files. I'm not sure if there is something with the files or the connection to the server is not good. All the folder is set to read and write.

[towfiqi]

@Eysenor, this is actually caused by a breaking API change in Drime's API that rclone uses to upload the files. Rclone already made their Drime integration compatible with the API change in the latest version (v1.74.0), released 5 days ago.
https://www.reddit.com/r/Drime/comments/1svf0da/rclone_issues/

I will shortly release a new version of Pluton, which will bundle the latest rclone, and the issue should be fixed.

[Eysenor]

Thanks a lot for the fast response, looking forward to the update to test it again!

[towfiqi]

Fixed in v0.15.2. Give it a try.

[Eysenor]

This seems to have solved the issue. I rerun all the backups and then the integrity check was good. I'm remaking the backups from scratch now just to be sure and they are uploading with no issue.

There is one weird thing that I noticed now. One of the backups targets my "server backups" share where I save different backups. One of the folders looks empty when I navigate to it from Pluton, it is not empty, it is set to read-write and duplicati sees it correctly in the same share. Any idea why this is happening?

And thanks a lot for the quick help!