Ok, I solved the issue, however I'm unsure to what caused it.
Turns out I had a file with the exact same name (name + type) on the root folder in S3. This file was not present in the Left side, and should have been deleted as configured.
I manually went ahead and nuked it out of S3 and rerun the ...
Search found 2 matches
- Mon Mar 22, 2021 11:28 pm
- Forum: Windows Topics
- Topic: Failing after exception: File too big for renaming
- Replies: 2
- Views: 4102
- Mon Mar 22, 2021 11:19 pm
- Forum: Windows Topics
- Topic: Failing after exception: File too big for renaming
- Replies: 2
- Views: 4102
Failing after exception: File too big for renaming
Hi!
I'm running Syncovery to snapshot the files inside a Shared Drive on Google Drive onto an S3 Bucket, however I'm running into an error when a specific new file is to be uploaded.
Failing after exception: File too big for renaming, Retry Number: 0
19:07:24.211 Error renaming S3://<REDACTED ...
I'm running Syncovery to snapshot the files inside a Shared Drive on Google Drive onto an S3 Bucket, however I'm running into an error when a specific new file is to be uploaded.
Failing after exception: File too big for renaming, Retry Number: 0
19:07:24.211 Error renaming S3://<REDACTED ...