# Pitr restore with latest xtradb cluster with operator on k8s no consistent **URL:** \ **Category:** Percona XtraDB Cluster 8.x\ **Created:** [December 26, 2025, 2:27pm UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943 "2025-12-26T14:27:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 26, 2025, 2:27pm UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943/1 "2025-12-26T14:27:45Z")
Hello Members, This is my first time experience with percona xtradb cluster. I enabled storing binary logs on s3 minio storage. looks like cluster running ok(ready) ,backup going ok. I disable pitr before restore. but when i restoring with pitr , i miss some or all rows , that i added after backup. even pitr type=latest. ---
**Author:** ![Yunus](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus/32/6430_2.png) [@Yunus](https://forums.percona.com/u/Yunus)\ **Post date:** [December 27, 2025, 7:23am UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943/2 "2025-12-27T07:23:21Z")
Can you explain “some or all rows” in details? Hope that your binlogs does not have gaps. > **[Binlog gaps - Percona Operator for MySQL - On the same cluster](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-restore.html#binlog-gaps)** > > You can restore from a backup as follows: please share restore logs as well if there are any failures. ---
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 27, 2025, 8:08am UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943/3 "2025-12-27T08:08:48Z")
Thanks @Yunus for response. I had mysql table with 4 rows. Pitr enable. I did backup. after backup i inserted 2 rows in the same table. I saw updated “Latest Restorable Time” of the backup. I disable Pitr. I did restore with pitr, and i saw only 4 rows in the table. no errors in the restore pods,not in restore itself, not in restore pitr. Ok, last of many attempts of restore was successful. after restore, i enabled pitr,did backup. question, is it must make backup after restore with pitr? Now i have another problem. after enabled pitr , i inserted some data in the table , i see in the logs of pitr pod “no binlogs to upload” . restart of pod not helped. Also not exist “Latest Restorable Time” of last backup , even after 50 minutes. ---
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 28, 2025, 5:46am UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943/4 "2025-12-28T05:46:15Z")
I installed operator v 1.18 with pxc ver 8.0.42-33.1 on k8s ver 1.27 . may be some compatibility issues with this version? ---
**Author:** ![Abhinav\_Gupta](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/abhinav_gupta/32/6262_2.png) [@Abhinav\_Gupta](https://forums.percona.com/u/Abhinav_Gupta)\ **Post date:** [December 28, 2025, 1:07pm UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943/5 "2025-12-28T13:07:45Z")
Please share the output of below. ```auto kubectl get all | grep -i pitr kubectl exec -it -- sh -c "ps" kubectl log | grep -i "successfully wrote binlog file" | tail -n 5 ``` ---
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 28, 2025, 4:10pm UTC](https://forums.percona.com/t/pitr-restore-with-latest-xtradb-cluster-with-operator-on-k8s-no-consistent/39943/6 "2025-12-28T16:10:54Z")
> [@Abhinav\_Gupta](#): > > `kubectl get all | grep -i pitr` ```auto kubectl get all | grep -i pitr pod/cluster1-pitr-68d7bbc68b-g74j9 1/1 Running 0 9h pod/pitr-job-restore1-cluster1-nfrt4 0/1 Completed 0 2d3h pod/pitr-job-restore31-cluster1-dzbrf 0/1 Completed 0 2d2h pod/pitr-job-restore32-cluster1-nbnbv 0/1 Completed 0 2d2h pod/pitr-job-restore34-cluster1-z6d8j 0/1 Completed 0 47h pod/pitr-job-restore35-cluster1-kds7t 0/1 Completed 0 47h pod/pitr-job-restore36-cluster1-p5xmq 0/1 Completed 0 47h pod/pitr-job-restore37-cluster1-m8rwp 0/1 Completed 0 46h pod/pitr-job-restore38-cluster1-sgzk9 0/1 Completed 0 46h pod/pitr-job-restore39-cluster1-sbpxq 0/1 Completed 0 32h pod/pitr-job-restore40-cluster1-lvnzv 0/1 Completed 0 10h service/cluster1-pitr ClusterIP 10.99.101.219 8080/TCP 9h deployment.apps/cluster1-pitr 1/1 1 1 9h replicaset.apps/cluster1-pitr-68d7bbc68b 1 1 1 9h job.batch/pitr-job-restore1-cluster1 1/1 17s 2d3h job.batch/pitr-job-restore31-cluster1 1/1 11s 2d2h job.batch/pitr-job-restore32-cluster1 1/1 12s 2d2h job.batch/pitr-job-restore34-cluster1 1/1 14s 47h job.batch/pitr-job-restore35-cluster1 1/1 12s 47h job.batch/pitr-job-restore36-cluster1 1/1 13s 47h job.batch/pitr-job-restore37-cluster1 1/1 13s 46h job.batch/pitr-job-restore38-cluster1 1/1 12s 46h job.batch/pitr-job-restore39-cluster1 1/1 13s 32h job.batch/pitr-job-restore40-cluster1 ``` ```auto kubectl exec -it cluster1-pitr-68d7bbc68b-g74j9 -- sh -c "ps" Defaulted container "pitr" out of: pitr, pitr-init (init) PID TTY TIME CMD 136793 pts/0 00:00:00 ps ``` ```auto kubectl logs cluster1-pitr-68d7bbc68b-g74j9 | grep -i "successfully wrote binlog file" | tail -n 5 Defaulted container "pitr" out of: pitr, pitr-init (init) ```