# PSMDB 1.15.0 PITR Restore not working **URL:** \ **Category:** Percona Backup for MongoDB\ **Tags:** percona, mongodb\ **Created:** [October 17, 2023, 5:33am UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957 "2023-10-17T05:33:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Swwapnil\_Yadav](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/swwapnil_yadav/32/12998_2.png) [@Swwapnil\_Yadav](https://forums.percona.com/u/Swwapnil_Yadav)\ **Post date:** [October 17, 2023, 5:33am UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957/1 "2023-10-17T05:33:50Z")
Hello Team, I am using PSMDB & Operator for MongoDB version 1.15.0 and trying to store and restore the PITR backups since incremental backup is not yet supported. I have mentioned all the details related to issue on below thread. > [@No support for Incremental Backup in 1.15.0 version?](https://forums.percona.com/t/no-support-for-incremental-backup-in-1-15-0-version/25834/4): > > Hello @Parag_Bhayani , PITR backup is getting stored on the same bucket where i am copying the physical backup. Now, when it comes to restore it using the timestamp I am executing the below restore file, apiVersion: psmdb.percona.com/v1 kind: PerconaServerMongoDBRestore metadata: name: restore-pitr spec: clusterName: mongodb-psmdb-db backupName: cron-mongodb-psmdb-db-20231012104500-p7xjr pitr: type: date date: 2023-10-12 09:55:39 # date: YYYY-MM-DD hh:mm:ss But i see its st… Any inputs would help me to move ahead and stick to the decision of choosing Percona. Regards, Swwapnil Yadav ---
**Author:** ![kyeongjun.me](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kyeongjun.me/32/14426_2.png) [@kyeongjun.me](https://forums.percona.com/u/kyeongjun.me)\ **Post date:** [January 2, 2024, 5:54am UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957/2 "2024-01-02T05:54:48Z")
Same to me… 1. config server, replicaset pod restarted without backup-agent sidecar (backup-agent logs is below. just shut down) ```auto 2024-01-02T05:38:48.000+0000 D [backup/2024-01-02T05:38:46Z] skip after nomination, probably started by another node 2024-01-02T05:38:52.000+0000 I [pitr] created chunk 2024-01-02T05:34:28 - 2024-01-02T05:38:42 2024-01-02T05:38:52.000+0000 I [pitr] pausing/stopping with last_ts 2024-01-02 05:38:42 +0000 UTC 2024-01-02T05:39:14.000+0000 D [pitr] start_catchup [oplog only] 2024-01-02T05:39:14.000+0000 D [pitr] lastTS set to {1704173922 2} 2024-01-02T05:38:42 2024-01-02T05:39:14.000+0000 I [pitr] streaming started from 2024-01-02 05:38:42 +0000 UTC / 1704173922 2024-01-02T05:39:14.000+0000 D [pitr] start_ok 2024-01-02T05:43:59.000+0000 I [pitr] got done signal, stopping 2024-01-02T05:44:01.000+0000 I [pitr] created chunk 2024-01-02T05:38:42 - 2024-01-02T05:43:52 2024-01-02T05:44:01.000+0000 I [pitr] pausing/stopping with last_ts 2024-01-02 05:43:52 +0000 UTC 2024/01/02 05:47:23 [entrypoint] got terminated, shutting down 2024/01/02 05:47:23 [entrypoint] kill `pbm-agent` (185): ``` 1. operator do : statefulset status check → run pbm config → fail (full log is below) ```auto 2024-01-02T05:48:35.258Z INFO Checking if replset is ready for physical restore {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "2641eb55-4335-452c-9c5b-aace25c49d64", "replset": "cfg"} 2024-01-02T05:48:36.848Z INFO Replset is ready for physical restore {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "2641eb55-4335-452c-9c5b-aace25c49d64", "replset": "cfg", "primary": "mongodb-test-psmdb-db-cfg-0"} 2024-01-02T05:48:36.848Z INFO Set PBM configuration {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "2641eb55-4335-452c-9c5b-aace25c49d64", "command": ["/opt/percona/pbm", "config", "--file", "/etc/pbm/pbm_config.yaml"], "pod": "mongodb-test-psmdb-db-rs0-0"} 2024-01-02T05:48:42.284Z INFO Starting restore {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "2641eb55-4335-452c-9c5b-aace25c49d64", "command": ["/opt/percona/pbm", "restore", "--base-snapshot", "2024-01-02T05:12:10Z", "--time", "2024-01-02T05:24:28", "--out", "json"], "pod": "mongodb-test-psmdb-db-rs0-0"} 2024-01-02T05:48:42.493Z INFO Restore started {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "2641eb55-4335-452c-9c5b-aace25c49d64", "pod": "mongodb-test-psmdb-db-rs0-0"} 2024-01-02T05:48:42.493Z INFO Restore state changed {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "2641eb55-4335-452c-9c5b-aace25c49d64", "previous": "waiting", "current": "requested"} 2024-01-02T05:48:48.186Z INFO Restore state changed {"controller": "psmdbrestore-controller", "object": {"name":"restore1","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "restore1", "reconcileID": "a344ba03-f440-458c-bdc8-d8ddc39bfac3", "previous": "requested", "current": "error"} 2024-01-02T05:50:14.085Z INFO balancer enabled {"controller": "psmdb-controller", "object": {"name":"mongodb-test-psmdb-db","namespace":"mongodb-test"}, "namespace": "mongodb-test", "name": "mongodb-test-psmdb-db", "reconcileID": "969f2414-3230-4cee-92e1-664a5d01b9fe"} ``` ---
**Author:** ![kyeongjun.me](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kyeongjun.me/32/14426_2.png) [@kyeongjun.me](https://forums.percona.com/u/kyeongjun.me)\ **Post date:** [January 3, 2024, 1:03am UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957/3 "2024-01-03T01:03:18Z")
It works to me now… Do you have arbiter member in cluster? And what os and image version? (server, backup agent) ---
**Author:** ![dxzio](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@dxzio](https://forums.percona.com/u/dxzio)\ **Post date:** [January 24, 2024, 8:03pm UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957/4 "2024-01-24T20:03:33Z")
Hi @kyeongjun.me I am interested in your config because i cannot get restore of a pitr physical backup working. I tried to restore to a new kubernetes mongodb cluster without success. Any hints are appreciated. ---
**Author:** ![kyeongjun.me](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kyeongjun.me/32/14426_2.png) [@kyeongjun.me](https://forums.percona.com/u/kyeongjun.me)\ **Post date:** [January 25, 2024, 2:21am UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957/5 "2024-01-25T02:21:37Z")
@dxzio Hi Same to me… Restoring in new kubernetes cluster is not working for me. My topic is here([link](https://forums.percona.com/t/pitr-restore-working-different-way-in-two-ways/27655/3)) Uinsg cr `backupName` is working. but this case is that restoring in same kubernetes cluster. Using `backupSource`(in aws s3 bucket) in new kubernetes cluster is not working. You can see specific configure my upper topic If I success, I will notice you 🙂 Good luck for you. ---
**Author:** ![dxzio](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@dxzio](https://forums.percona.com/u/dxzio)\ **Post date:** [January 27, 2024, 7:06pm UTC](https://forums.percona.com/t/psmdb-1-15-0-pitr-restore-not-working/25957/6 "2024-01-27T19:06:10Z")
@kyeongjun.me Thank you for reply. I am wondering if the documentation [Restore backup to a new Kubernetes-based environment - Percona Operator for MongoDB](https://docs.percona.com/percona-operator-for-mongodb/backups-restore-to-new-cluster.html) is working at all. And if yes with which percona mongodb operator version ? Maybe with the upcoming 1.16.0 ? Is there any bug ticket existing ?