# Backups via PMM are failing with \`xtrabackup is not compatible with mysql version\`
**URL:** https://forums.percona.com/t/backups-via-pmm-are-failing-with-xtrabackup-is-not-compatible-with-mysql-version/40277
**Category:** Percona XtraBackup
**Created:** [February 23, 2026, 11:42pm UTC](https://forums.percona.com/t/backups-via-pmm-are-failing-with-xtrabackup-is-not-compatible-with-mysql-version/40277 "2026-02-23T23:42:59Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Marko\_Todoric](https://forums.percona.com/u/Marko_Todoric)
#### Post date: [February 23, 2026, 11:42pm UTC](https://forums.percona.com/t/backups-via-pmm-are-failing-with-xtrabackup-is-not-compatible-with-mysql-version/40277/1 "2026-02-23T23:42:59Z")
Hello team,
as the title states, when attempting to run backups via PMM (Version 3.6.0) i get an error:
```auto
xtrabackup version "8.0.35-35" is not compatible with mysql version "8.0.44-35.1": incompatible xtrabackup
```
However, this message does not come from xtrabackup as running `xtrabackup --backup` manually works like a charm - so i believe it comes from PMM Server. I have the latest available xtrabackup version for 8.0.
Attempting to use xtrabackup 8.4 would fail:
```auto
This version of Percona XtraBackup can only perform backups and restores against MySQL and Percona Server '8.4
```
Are there any workarounds that allows me to use PMM Server to schedule upgrades? Seems like a silly limitation to enforce version checks on server when xtrabackup has it’s own version checks.
I can see the version check happens in `services/backup/compatibility_helpers.go` file of PMM server.
---
### Author:  [@Marko\_Todoric](https://forums.percona.com/u/Marko_Todoric)
#### Post date: [February 23, 2026, 11:44pm UTC](https://forums.percona.com/t/backups-via-pmm-are-failing-with-xtrabackup-is-not-compatible-with-mysql-version/40277/2 "2026-02-23T23:44:57Z")
I have just found a github issue from 2024 regarding same problem:
>
>
> \### Description
>
> While attempting to back up, I am getting the following error a…s shown in screenshot
> !\[Screenshot from 2024-03-20 15-44-29\](https://github.com/percona/pmm/assets/1525027/f73f2a1f-95e1-4009-a0e8-e8f68c67183b)
> the
>
> \### Expected Results
>
> Backup works correctly while running as a command in the terminal.
> So it should ideally I should be able to backup
>
> \### Actual Results
>
> Please see screen shot
> !\[Screenshot from 2024-03-20 15-44-29\](https://github.com/percona/pmm/assets/1525027/6f2575c0-7d6c-484e-bea5-7cb9e0226b76)
>
>
> \### Version
>
> PMM server latest
> ProjectName: pmm-admin
> Version: 2.41.1
> PMMVersion: 2.41.1
> Timestamp: 2024-01-30 13:27:05 (UTC)
> FullCommit: f4004eac5c03e97327ae235dbf40f91e31ba2208
>
>
> \### Steps to reproduce
>
> try to create full backup with latest PMM client and server
>
> \### Relevant logs
>
> \_No response\_
>
> \### Code of Conduct
>
> \- \[X\] I agree to follow Percona Community Code of Conduct
Can we get some traction on this problem?
---
### Author:  [@jrivera](https://forums.percona.com/u/jrivera)
#### Post date: [February 24, 2026, 6:10am UTC](https://forums.percona.com/t/backups-via-pmm-are-failing-with-xtrabackup-is-not-compatible-with-mysql-version/40277/3 "2026-02-24T06:10:13Z")
Hi Marko,
I believe this is related to [Jira](https://perconadev.atlassian.net/browse/PMM-14594) . Kindly add your comment there. You may follow the bug report to get the latest updates.
---
### Author:  [@Marko\_Todoric](https://forums.percona.com/u/Marko_Todoric)
#### Post date: [February 24, 2026, 10:14am UTC](https://forums.percona.com/t/backups-via-pmm-are-failing-with-xtrabackup-is-not-compatible-with-mysql-version/40277/4 "2026-02-24T10:14:41Z")
Seems like i cannot add comments to that Jira ticket. However i did make a [pull request](https://github.com/percona/pmm/pull/5069) in hope to fix this issue. At least for 8.0.x release.
It’s a shame that the GitHub issue was opened in 2024, Jira ticket since 2025 from what it seems - and yet no fix is available.