Backup fail due to 'Exceeded total allowed configured MaxUploadParts' error
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:
Jakub Vecera 2 days ago
I was trying to replicate this, and see if the maxUploadParts
are being honored from the config. From my testing, all seems ok. Not sure if the migration to v2 did any changes. Could I ask for some help? Thanks!

Rama Mekala December 11, 2024 at 5:58 PM
Thank you for your help.

Rama Mekala December 11, 2024 at 5:58 PM
Looks good now. I have successful backups. we moved some of collection data to different shards.

Sandra Romanchenko November 23, 2024 at 1:30 PM
Option uploadPartSize should be set in bytes, so for 20MB it should be 20971520, please try with this value.

Rama Mekala November 22, 2024 at 6:42 PM
Hello - as per your suggestion, I tried the backup again with a part size of 20MB (which will give max allowed file size 195 GB). Because the below collection size is 95GB. I still got the same error.
PBM CONFIG & LOG:
LOG:
Details
Details
Assignee
Reporter

Labels
Needs QA
Yes
Sprint
Fix versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created November 8, 2024 at 7:06 PM
Updated 2 days ago
backups are failing even though I set it maxUploadParts: 30000.
Here is the config:
I attenpted to take backups couple of times. still failing at this place.
Here is the pbm logs: