# \[ERROR: get backup files: create backupCursor: (Location50917) Oplog rolled over while establishing the backup cursor

**URL:** <https://forums.percona.com/t/error-get-backup-files-create-backupcursor-location50917-oplog-rolled-over-while-establishing-the-backup-cursor/37604>\
**Category:** Percona Server for MongoDB\
**Tags:** pbm\
**Created:** [April 14, 2025, 11:36am UTC](https://forums.percona.com/t/error-get-backup-files-create-backupcursor-location50917-oplog-rolled-over-while-establishing-the-backup-cursor/37604 "2025-04-14T11:36:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sujithtee](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sujithtee/32/18989_2.png) [@sujithtee](https://forums.percona.com/u/sujithtee)\
**Post date:** [April 14, 2025, 11:36am UTC](https://forums.percona.com/t/error-get-backup-files-create-backupcursor-location50917-oplog-rolled-over-while-establishing-the-backup-cursor/37604/1 "2025-04-14T11:36:23Z")

</div>

Hi,

I am facing the below error while starting a physical backup in psmdb 6.0.20-17 and the pbm version is 2.91

[ERROR: get backup files: create backupCursor: (Location50917) Oplog rolled over while establishing the backup cursor.

Also I have enough oplogs

> actual oplog size
> 
> ‘160000 MB’
> 
> configured oplog size
> 
> ‘160000 MB’
> 
> log length start to end
> 
> ‘374871 secs (104.13 hrs)’
> 
> oplog first event time
> 
> ‘Thu Apr 10 2025 04:19:45 GMT+0700 (Western Indonesia Time)’
> 
> oplog last event time
> 
> ‘Mon Apr 14 2025 12:27:36 GMT+0700 (Western Indonesia Time)’
> 
> now
> 
> ‘Mon Apr 14 2025 12:27:39 GMT+0700 (Western Indonesia Time)’

---

<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:** [April 15, 2025, 11:25am UTC](https://forums.percona.com/t/error-get-backup-files-create-backupcursor-location50917-oplog-rolled-over-while-establishing-the-backup-cursor/37604/2 "2025-04-15T11:25:59Z")

</div>

Hi, can you check oplog stats on all members of the replica set. It is possible the server picked by PBM to do the backup has smaller oplog configured? also check pbm agent logs for more clues.

---

<div class="post-metadata">

**Author:** ![radoslaw.szulgo](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/radoslaw.szulgo/32/17315_2.png) [@radoslaw.szulgo](https://forums.percona.com/u/radoslaw.szulgo)\
**Post date:** [October 21, 2025, 8:28pm UTC](https://forums.percona.com/t/error-get-backup-files-create-backupcursor-location50917-oplog-rolled-over-while-establishing-the-backup-cursor/37604/3 "2025-10-21T20:28:42Z")

</div>

We’ve created a bug for this issue: [Jira](https://perconadev.atlassian.net/browse/PBM-1563) It’s initially planned for PBM 2.13.0 - to be released end of this year or early next year.
