# Unexpected backup failure - convergeCluster lost shard? **URL:** \ **Category:** Percona Backup for MongoDB\ **Created:** [January 5, 2021, 10:16pm UTC](https://forums.percona.com/t/unexpected-backup-failure-convergecluster-lost-shard/8642 "2021-01-05T22:16:11Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Nathan\_Neulinger](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nathan_neulinger/32/176_2.png) [@Nathan\_Neulinger](https://forums.percona.com/u/Nathan_Neulinger)\ **Post date:** [January 7, 2021, 2:35am UTC](https://forums.percona.com/t/unexpected-backup-failure-convergecluster-lost-shard/8642/2 "2021-01-07T02:35:10Z")
Interesting, on at least one these, when I started testing for a different issue (desire for throttling) > [@Feature request - throttling support for s3 backups](https://forums.percona.com/t/feature-request-throttling-support-for-s3-backups/8664): > > Currently, I have pbm in an environment where the bandwidth to the storage (s3 equivalent) is essentially limited solely by the network bandwidth of my host. Under typical circumstances this would be great. The problem is that right now, this results in an extreme network spike when the full backup kicks off - multiple gigabit spike for a short period, which is being felt in other apps/servers. It would be really nice if there were at least limited support for a throttling of s3 requests. At … after applying that throttling, it was able to complete the initial backups. Wonder if there is some sort of race condition? --- _[View the full topic](https://forums.percona.com/t/unexpected-backup-failure-convergecluster-lost-shard/8642)._