# Query on the backup time using PBM - MongoDB

**URL:** <https://forums.percona.com/t/query-on-the-backup-time-using-pbm-mongodb/24265>\
**Category:** Percona Backup for MongoDB\
**Tags:** percona, mongodb, pbm\
**Created:** [August 7, 2023, 10:49am UTC](https://forums.percona.com/t/query-on-the-backup-time-using-pbm-mongodb/24265 "2023-08-07T10:49:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirangelli](https://avatars.discourse-cdn.com/v4/letter/k/eb8c5e/32.png) [@kirangelli](https://forums.percona.com/u/kirangelli)\
**Post date:** [August 7, 2023, 10:49am UTC](https://forums.percona.com/t/query-on-the-backup-time-using-pbm-mongodb/24265/1 "2023-08-07T10:49:12Z")

</div>

Hi Team,

We are using PBM version 2.2.1 for taking backups on our Percona MongoDB 4.4 environment.  
We have a Replicaset which has a data directory of 2.0 TB in size.

The backup time when using gzip compression mechanism took 30 hours to complete and the backup size is 880GB.

Is there a way where we can reduce the backup time? Do you suggest any other compression mechanism?  
Please advise.

Thanks  
Kiran

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [August 7, 2023, 12:01pm UTC](https://forums.percona.com/t/query-on-the-backup-time-using-pbm-mongodb/24265/2 "2023-08-07T12:01:46Z")

</div>

Hi, 2 TB is quite a lot for the logical backup strategy. I suggest you migrate to Percona MongoDB and take a look at physical backup option. It is a drop-in replacement in case you are wondering: [Migration of MongoDB Enterprise/Community Edition to Percona Server for MongoDB](https://www.percona.com/blog/migration-of-mongodb-enterprise-community-edition-to-percona-server-for-mongodb/)