# Upgradin Percona Components

**URL:** <https://forums.percona.com/t/upgradin-percona-components/40046>\
**Category:** MySQL & MariaDB\
**Created:** [January 14, 2026, 10:22am UTC](https://forums.percona.com/t/upgradin-percona-components/40046 "2026-01-14T10:22:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![acelayir](https://avatars.discourse-cdn.com/v4/letter/a/e68b1a/32.png) [@acelayir](https://forums.percona.com/u/acelayir)\
**Post date:** [January 14, 2026, 10:22am UTC](https://forums.percona.com/t/upgradin-percona-components/40046/1 "2026-01-14T10:22:12Z")

</div>

Hi

We have percona xtradb cluster in following version

backup: tpercona-xtradb-cluster-operator:1.13.0-pxc8.0-backup-pxb8.0.32  
pxc: percona-xtradb-cluster:8.0.32-24.2  
operator: percona-xtradb-cluster-operator:1.13.0

and we want to upgrade them to following version

backup: [docker.io/percona/percona-xtradb-cluster-operator:1.17.0-pxc8.0-backup-pxb8.0.35](http://docker.io/percona/percona-xtradb-cluster-operator:1.17.0-pxc8.0-backup-pxb8.0.35)  
pxc: [docker.io/percona/percona-xtradb-cluster:8.0.41-32.1](http://docker.io/percona/percona-xtradb-cluster:8.0.41-32.1)  
operator:docker.io/perconalab/percona-xtradb-cluster-operator:1.17.0

What is the best way to do it?

Our first approach;

-take backup of mysql from old env

-uninstall existing env and install new env with new version

-restore backup to new env

1- Is this approach work or not?

2- This approach takes downtime, is there anyway to upgrade new env without downtime or limited downtime

3- Can the replication be used for this upgrade

Regards

---

<div class="post-metadata">

**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:** [January 14, 2026, 3:28pm UTC](https://forums.percona.com/t/upgradin-percona-components/40046/2 "2026-01-14T15:28:34Z")

</div>

Here, you can check if you can utilize the cross-site cluster replication to achieve your goal.

> **[Percona Operator for MySQL - Multi-cluster and multi-region deployment](https://docs.percona.com/percona-operator-for-mysql/pxc/replication.html)**
>
> The cross-site replication involves configuring one Percona XtraDB Cluster as Source, and another Percona XtraDB Cluster as Replica to allow asynchronous replication between them:

---

<div class="post-metadata">

**Author:** ![acelayir](https://avatars.discourse-cdn.com/v4/letter/a/e68b1a/32.png) [@acelayir](https://forums.percona.com/u/acelayir)\
**Post date:** [January 15, 2026, 12:52pm UTC](https://forums.percona.com/t/upgradin-percona-components/40046/3 "2026-01-15T12:52:25Z")

</div>

Hi @Abhinav_Gupta

actually i am asking which method i should use? i hope to get feedback from someone who has experience on it

Regards

---

<div class="post-metadata">

**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:** [January 17, 2026, 4:29am UTC](https://forums.percona.com/t/upgradin-percona-components/40046/4 "2026-01-17T04:29:28Z")

</div>

Hello @acelayir

> [@acelayir](#):
>
> Our first approach;

If you are talking about taking a backup, uninstalling, installing a new version and then restoring. This will take a significant amount of time, depending on the database size and available resources.

> [@acelayir](#):
>
> 3- Can the replication be used for this upgrade

Yes as my colleague mentioned, you can create a replication, upgrade the new environment and cutover. This will require only the limited downtime during cutover.

You can also use the operator-recommended upgrade in our documentation,

> **[Percona Operator for MySQL - About upgrades](https://docs.percona.com/percona-operator-for-mysql/pxc/update.html)**
>
> You can upgrade Percona Operator for MySQL based on Percona XtraDB Cluster to newer versions

We suggest you to go through this document as the upgrade is quite a long jump from 1.13.0 to 1.17.0

Also, you should plan for 1.18.0 as it is the latest version