# Cannot get PITR backup restore to work

**URL:** <https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792>\
**Category:** Percona Operator for MySQL\
**Created:** [November 5, 2024, 2:39pm UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792 "2024-11-05T14:39:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bulwark\_shades](https://avatars.discourse-cdn.com/v4/letter/b/e79b87/32.png) [@bulwark\_shades](https://forums.percona.com/u/bulwark_shades)\
**Post date:** [November 5, 2024, 2:39pm UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792/1 "2024-11-05T14:39:42Z")

</div>

## Description:

I have 2 clusters managed by the same operator: pxc-db and pxc-db-backup-restore. I cannot restore a backup from the pxc-db cluster to the pxc-db-backup-restore cluster using pitr.

## Steps to Reproduce:

to restore a PITR backup to a new Percona XtraDB cluster I create the PerconaXtraDBClusterRestore resource as follows:

```auto
kind: PerconaXtraDBClusterRestore
apiVersion: pxc.percona.com/v1
metadata:
    name: restore-test-2024-11-05
    namespace: pxc-db-backup-restore
spec:
    pxcCluster: pxc-db-backup-restore
    backupSource:
        destination: azure://pxc-db/pxc-db-2024-11-05-11:05:20-full
        azure:
            container: pxc-db
            credentialsSecret: azure-secret
    pitr:
        type: latest
        backupSource:
            destination: azure://pxc-db/pitr
            azure:
                container: pxc-db/pitr
                credentialsSecret: azure-secret

```

My Azure storage account has all backups directly in a container named _pxc-db_ and all binlogs are stored in a folder named _pitr_ within the same container. The restoration procedure works fine until the _pitr-job_ pod fails within the first few seconds with the following output:

```auto
2024/11/05 14:17:49 ERROR: new recoverer controller: get start GTID: no info files in sst dir

```

It retries a few times, but all retried pods fail with the same message.  
Please note that restoring a backup without any pitr works fine.

## Version:

Operator: 1.15.1  
Percona XtraDB Cluster: 8.0.36-28.1

## Logs:

```auto
2024/11/05 14:17:49 ERROR: new recoverer controller: get start GTID: no info files in sst dir

```

## Expected Result:

Success

## Actual Result:

Pod Failed

## Additional Information:

n/a

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [November 16, 2024, 12:13am UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792/2 "2024-11-16T00:13:24Z")

</div>

hey @bulwark_shades - let me spend some time on it on Monday and try to reproduce. If you have any additional details that might help - please let me know.

---

<div class="post-metadata">

**Author:** ![Frederic\_Coelho1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/frederic_coelho1/32/12460_2.png) [@Frederic\_Coelho1](https://forums.percona.com/u/Frederic_Coelho1)\
**Post date:** [December 12, 2024, 12:23pm UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792/3 "2024-12-12T12:23:37Z")

</div>

Hello,

i have the same issue.

Regards,

---

<div class="post-metadata">

**Author:** ![Frederic\_Coelho1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/frederic_coelho1/32/12460_2.png) [@Frederic\_Coelho1](https://forums.percona.com/u/Frederic_Coelho1)\
**Post date:** [December 12, 2024, 3:35pm UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792/4 "2024-12-12T15:35:51Z")

</div>

ok found the issue closed : [Restore fails using Azure storage with message "no info files in sst dir" · Issue #1812 · percona/percona-xtradb-cluster-operator · GitHub](https://github.com/percona/percona-xtradb-cluster-operator/issues/1812)  
i’m afraid by the label 1.17 !!! can we have a patch 1.15.2 ?

---

<div class="post-metadata">

**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:53am UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792/5 "2024-12-17T11:53:32Z")

</div>

This fix was included in PXCO 1.16.0. We will have a release in two days. We do not have a plan to release 1.15.2 patch release.

---

<div class="post-metadata">

**Author:** ![Frederic\_Coelho1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/frederic_coelho1/32/12460_2.png) [@Frederic\_Coelho1](https://forums.percona.com/u/Frederic_Coelho1)\
**Post date:** [December 17, 2024, 11:55am UTC](https://forums.percona.com/t/cannot-get-pitr-backup-restore-to-work/34792/6 "2024-12-17T11:55:47Z")

</div>

Ok thanks for the update