# Restore runs forever

**URL:** <https://forums.percona.com/t/restore-runs-forever/32918>\
**Category:** MySQL & MariaDB\
**Tags:** kubernetes\
**Created:** [September 4, 2024, 5:09pm UTC](https://forums.percona.com/t/restore-runs-forever/32918 "2024-09-04T17:09:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![n7qnm](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/n7qnm/32/16109_2.png) [@n7qnm](https://forums.percona.com/u/n7qnm)\
**Post date:** [September 4, 2024, 5:09pm UTC](https://forums.percona.com/t/restore-runs-forever/32918/1 "2024-09-04T17:09:50Z")

</div>

I have a 3 node kubernetes system running the XtraDB Operator, running in Proxmox/Ceph. The underlying disks got corrupted. I was able to restore the nodes from a backup, but the databases would not come up.

I tried running a restore from the pxc-backups and that has now been running for more than 13 hours.

Help?

clayj@K8S-CTRL:~$ kubectl get pods  
NAME READY STATUS RESTARTS AGE  
percona-xtradb-cluster-operator-7c769dcc6d-bbh79 1/1 Running 31 (63m ago) 25h  
restore-job-restore1-cluster1-kgqpm 0/1 Completed 0 13h  
restore-src-restore1-cluster1 1/1 Running 1 (13h ago) 13h  
restore-src-restore1-cluster1-verify 0/1 Completed 0 13h  
xb-cron-cluster1-fs-pvc-2024930023-372f8-ts57k 0/1 Completed 0 18h

---

<div class="post-metadata">

**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:** [September 16, 2024, 9:14am UTC](https://forums.percona.com/t/restore-runs-forever/32918/2 "2024-09-16T09:14:05Z")

</div>

Hi @n7qnm,

With the given information, we can’t go further. What I can say is, you might take a look at the `kubectl decribe` and the `kubectl log` to get more detailed information about your current process to find which step is hanging, if any.