# Downgrade percona backup for MongoDB **URL:** \ **Category:** Percona Backup for MongoDB\ **Created:** [May 15, 2023, 3:10pm UTC](https://forums.percona.com/t/downgrade-percona-backup-for-mongodb/22065 "2023-05-15T15:10:48Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![aranjith0](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/aranjith0/32/13012_2.png) [@aranjith0](https://forums.percona.com/u/aranjith0)\ **Post date:** [May 16, 2023, 12:09pm UTC](https://forums.percona.com/t/downgrade-percona-backup-for-mongodb/22065/3 "2023-05-16T12:09:52Z")
Hi @Ivan_Groenewold , Yes, The issue happens after upgrading the version to **2.1.0.** It is critical and backups are failing most of the times and sometime it works. i don’t face any issue with v1.8.1 There is no solution on below JIRA as well. That’s why i was looking to downgrade the version. > **[Jira](https://perconadev.atlassian.net/browse/PBM-1110)** Also PBM restore got failed with newer versions: > [@PBM Restore failed](https://forums.percona.com/t/pbm-restore-failed/22041): > > Team, PBM restore to a new cluster got failed multiple time with same message. “retryChunk got copy: context deadline exceeded (Client.Timeout or context cancellation while reading body” [mongod@ip-10-80-11-253 ~]$ pbm status Cluster: shard1ReplSet: shard1ReplSet/10.80.11.253:27038 [P]: pbm-agent v2.1.0 OK configReplSet: configReplSet/10.80.11.253:27039 [P]: pbm-agent v2.1.0 OK shard3ReplSet: shard3ReplSet/10.80.10.159:27038 [P]: pbm-agent v2.1.0 OK shard2ReplSet: shard2ReplSet/10.80.10… --- _[View the full topic](https://forums.percona.com/t/downgrade-percona-backup-for-mongodb/22065)._