# Pitr backup having error with kubernetes v1.28 **URL:** \ **Category:** Percona Operator for MySQL\ **Created:** [December 12, 2024, 3:14am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620 "2024-12-12T03:14:14Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kllmkadx](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@kllmkadx](https://forums.percona.com/u/kllmkadx)\ **Post date:** [December 12, 2024, 3:14am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/1 "2024-12-12T03:14:14Z")
## [root@k8s-master-prod mysql]# kubectl logs -f cluster1-pitr-64dd8b9b4-nm7b6 Defaulted container “pitr” out of: pitr, pitr-init (init) 2024/12/12 03:01:41 run binlog collector 2024/12/12 03:01:42 ERROR: get binlog time get binlog list for host cluster1-pxc-0.cluster1-pxc.default.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3 2024/12/12 03:01:42 ERROR: get binlog time get binlog list for host cluster1-pxc-1.cluster1-pxc.default.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3 2024/12/12 03:01:42 ERROR: get binlog time get binlog list for host cluster1-pxc-2.cluster1-pxc.default.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3 2024/12/12 03:01:42 ERROR: get binlog time get binlog list for host cluster1-pxc-3.cluster1-pxc.default.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3 2024/12/12 03:01:42 ERROR: new db connection: get host: can’t find host ``` Last Transition Time: 2024-12-12T02:48:30Z Message: update binlog collector deployment 'cluster1-pitr': resource name may not be empty Reason: ErrorReconcile Status: True Type: error Last Transition Time: 2024-12-12T02:48:36Z Status: True Type: ready Last Transition Time: 2024-12-12T02:48:39Z Message: check binlog gaps in pod cluster1-pitr-64dd8b9b4-sw5dg: unable to upgrade connection: container not found ("pitr") Reason: ErrorReconcile Status: True Type: error ``` Haproxy: Label Selector Path: [app.kubernetes.io/component=haproxy,app.kubernetes.io/instance=cluster1,app.kubernetes.io/managed-by=percona-xtradb-cluster-operator,app.kubernetes.io/name=percona-xtradb-cluster,app.kubernetes.io/part-of=percona-xtradb-cluster](http://app.kubernetes.io/component=haproxy,app.kubernetes.io/instance=cluster1,app.kubernetes.io/managed-by=percona-xtradb-cluster-operator,app.kubernetes.io/name=percona-xtradb-cluster,app.kubernetes.io/part-of=percona-xtradb-cluster) Ready: 2 Size: 2 Status: ready Host: cluster1-haproxy.default Logcollector: Message: Error: check binlog gaps in pod cluster1-pitr-64dd8b9b4-sw5dg: unable to upgrade connection: container not found (“pitr”) Observed Generation: 23 Pmm: Proxysql: Pxc: Image: percona-xtradb-cluster-operator:main-pxc5.7 Label Selector Path: [app.kubernetes.io/component=pxc,app.kubernetes.io/instance=cluster1,app.kubernetes.io/managed-by=percona-xtradb-cluster-operator,app.kubernetes.io/name=percona-xtradb-cluster,app.kubernetes.io/part-of=percona-xtradb-cluster](http://app.kubernetes.io/component=pxc,app.kubernetes.io/instance=cluster1,app.kubernetes.io/managed-by=percona-xtradb-cluster-operator,app.kubernetes.io/name=percona-xtradb-cluster,app.kubernetes.io/part-of=percona-xtradb-cluster) Ready: 4 Size: 4 Status: ready Version: 5.7.44-48-57 Ready: 6 Size: 6 State: error Events: How can i do ---
**Author:** ![eleonora.zinchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/eleonora.zinchenko/32/19132_2.png) [@eleonora.zinchenko](https://forums.percona.com/u/eleonora.zinchenko)\ **Post date:** [December 12, 2024, 8:43am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/2 "2024-12-12T08:43:05Z")
Hi! As I can see you are running MySQL 5.7. PITR is supported in 8.0 for now as per [Store binary logs for point-in-time recovery - Percona Operator for MySQL](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-pitr.html) : > Point-in-time recovery is off by default and is supported by the Operator only with Percona XtraDB Cluster versions starting from 8.0.21-12.1. An additional note: I have noticed that you are using `percona-xtradb-cluster-operator:main-pxc5.7` image from `perconalab` repository. This image is not recommended for production usage as is our testing one and is build from main branch in development. Consider using one of [Percona certified images - Percona Operator for MySQL](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html?h=images) . ---
**Author:** ![kllmkadx](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@kllmkadx](https://forums.percona.com/u/kllmkadx)\ **Post date:** [December 12, 2024, 10:29am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/3 "2024-12-12T10:29:54Z")
But I want to restore all data in 5.7 cluster,so just to add two more cronjob doing binlog backup and restore binlog sql is best? ---
**Author:** ![kllmkadx](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@kllmkadx](https://forums.percona.com/u/kllmkadx)\ **Post date:** [December 16, 2024, 1:23am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/4 "2024-12-16T01:23:27Z")
But I want to restore all data in 5.7 cluster,so just to add two more cronjob doing binlog backup and restore binlog sql is best? Mean is keep binlog want to save an safe way(other storages and so on) ---
**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\ **Post date:** [December 17, 2024, 11:48am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/5 "2024-12-17T11:48:54Z")
Hi @kllmkadx, as @eleonora.zinchenko mentioned, the PXC operator supports PITR only for PXC 8.0. You can implement something custom for PXC 5.7, but we can’t guarantee that it will work correctly. ---
**Author:** ![kllmkadx](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@kllmkadx](https://forums.percona.com/u/kllmkadx)\ **Post date:** [December 24, 2024, 2:34am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/7 "2024-12-24T02:34:19Z")
I know that,just want to using other way to backup binlog for pxc 5.7,not using PITR,so do you have other good idea to backup this one man? ---
**Author:** ![kllmkadx](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@kllmkadx](https://forums.percona.com/u/kllmkadx)\ **Post date:** [January 9, 2025, 7:09am UTC](https://forums.percona.com/t/pitr-backup-having-error-with-kubernetes-v1-28/35620/8 "2025-01-09T07:09:40Z")
Also did you have good idea to backup binlog likes backup Pitr lady?