# \[pitr\] oplog slicer is paused for lock **URL:** \ **Category:** MongoDB\ **Tags:** percona, mongodb\ **Created:** [December 3, 2025, 10:27am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826 "2025-12-03T10:27:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![karam\_alhalabi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/karam_alhalabi/32/22724_2.png) [@karam\_alhalabi](https://forums.percona.com/u/karam_alhalabi)\ **Post date:** [December 3, 2025, 10:27am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826/1 "2025-12-03T10:27:51Z")
[pitr] oplog slicer is paused for lock [Snapshot backup, opid: 692902205e216c21fa537eaf] The oplog slicer remains paused indefinitely, preventing the backup from completing and affecting point-in-time recovery capabilities. **Steps to Reproduce:** 1. Deploy Percona MongoDB cluster in Kubernetes 2. Create a backup schedule/trigger manual backup 3. Monitor backup agent logs 4. Observe the “oplog slicer is paused for lock” message i run operator 1.21.1 ---
**Author:** ![yunus.uyanik](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus.uyanik/32/19250_2.png) [@yunus.uyanik](https://forums.percona.com/u/yunus.uyanik)\ **Post date:** [December 10, 2025, 5:55am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826/2 "2025-12-10T05:55:03Z")
> [@karam\_alhalabi](#): > > oplog slicer is paused for lock The ` oplog slicer is paused for lock` is not an error, and the cause of this is that PBM stops saving PITR chunks when a logical backup is running. For example, if you have 1TB of data, it’s expected that the backup will take a long time to complete. Isn’t it ever continuing in your case? Have you ever had a successful backup? ---
**Author:** ![karam\_alhalabi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/karam_alhalabi/32/22724_2.png) [@karam\_alhalabi](https://forums.percona.com/u/karam_alhalabi)\ **Post date:** [December 14, 2025, 6:53am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826/3 "2025-12-14T06:53:37Z")
I have some backup ready and some backup fails due the same reason oplog slicer is paused for lock ![Screenshot from 2025-12-14 09-50-47](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/5/a/5afdaef15069b7c3ce82cf5bc97bb894f3144c20.png) ---
**Author:** ![karam\_alhalabi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/karam_alhalabi/32/22724_2.png) [@karam\_alhalabi](https://forums.percona.com/u/karam_alhalabi)\ **Post date:** [December 15, 2025, 6:41am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826/4 "2025-12-15T06:41:52Z")
after see the logs on another node of backup-agent mark RS as error `dump: dump namespaces: pay_687dsfsd851393.filemanager_logs: close: upload: "pay_687dsfsd851393.filemanager_logs": save during split-merge mw: upload to S3: operation error S3: PutObject, exceeded maximum number of attempts, 6, https response error StatusCode: 504, RequestID: N/A, HostID: N/A, api error GatewayTimeout: The server did not respond in time.`: can you help? ---
**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:** [December 15, 2025, 10:54am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826/5 "2025-12-15T10:54:48Z")
as per the log above you are getting timeouts talking to the storage. The problem is either the network or the remote storage then. ---
**Author:** ![karam\_alhalabi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/karam_alhalabi/32/22724_2.png) [@karam\_alhalabi](https://forums.percona.com/u/karam_alhalabi)\ **Post date:** [December 16, 2025, 7:39am UTC](https://forums.percona.com/t/pitr-oplog-slicer-is-paused-for-lock/39826/6 "2025-12-16T07:39:22Z")
> [@Ivan\_Groenewold](#): > > e log above you are getting timeouts talking to the storage. The problem is either the network or the remote storage then **Manual backups execute successfully, however, the automated cron-based backups are failing with an error. this my config** —————————- backup: enabled: true image: perconalab/percona-server-mongodb-operator:main-backup ``` storages: NBG1: type: s3 s3: bucket: test-bk-test region: NBG1 credentialsSecret: mongodb-prod-1-backup-s3 endpointUrl: https://nbdc.your-objectstorage.com retryer: numMaxRetries: 5 minRetryDelay: 30ms maxRetryDelay: 10m prefix: "" uploadPartSize: 20971520 maxUploadParts: 10000 pitr: enabled: true oplogOnly: false ``` # oplogSpanMin: 10 ``` compressionType: gzip compressionLevel: 6 tasks: # ============= # DAILY BACKUP at 12PM UTC 0 # ============= - name: mongodb-prod-1-backup-daily enabled: true retention: count: 3 # keep 1 backup each day, 3 days max type: count deleteFromStorage: true type: logical # best for storage, slower schedule: 0 2 \* \* \* # daily at 2 AM UTC 0 storageName: NBG1 # ============= # WEEKLY BACKUP at SATURDAY 12AM UTC 0 # ============= - name: mongodb-prod-1-backup-weekly enabled: true retention: count: 2 # keep 1 backup each week, 2 weeks max type: count deleteFromStorage: true type: logical # best for storage, slower schedule: 0 0 \* \* 5 # weekly at 12AM UTC 0 friday storageName: NBG1 # ============= # MONTHLY BACKUP at SATURDAY 12AM UTC 0 # ============= - name: mongodb-prod-1-backup-MONTHLY enabled: true retention: count: 3 # keep 1 backup each month, 3 months max type: count deleteFromStorage: true type: logical # best for storage, slower schedule: 0 4 1 \* \* # 1st day of every month at 4 AM storageName: NBG1 ```