# Migrating from Percona Server to Aurora with Xtrabackup

**URL:** <https://forums.percona.com/t/migrating-from-percona-server-to-aurora-with-xtrabackup/38500>\
**Category:** Percona XtraBackup\
**Created:** [June 30, 2025, 11:06am UTC](https://forums.percona.com/t/migrating-from-percona-server-to-aurora-with-xtrabackup/38500 "2025-06-30T11:06:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew2](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/andrew2/32/4044_2.png) [@Andrew2](https://forums.percona.com/u/Andrew2)\
**Post date:** [June 30, 2025, 11:06am UTC](https://forums.percona.com/t/migrating-from-percona-server-to-aurora-with-xtrabackup/38500/1 "2025-06-30T11:06:25Z")

</div>

I’m looking at migrating some of our Percona Server on EC2 instances into Aurora but reading the AWS documentation ( [Physical migration from MySQL by using Percona XtraBackup and Amazon S3 - Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.S3.html#AuroraMySQL.Migrating.ExtMySQL.S3.Limits) ) I noticed this :

> - Percona Server for MySQL isn’t supported as a source database, because it can contain `compression_dictionary*` tables in the `mysql` schema.

I’m sure migrating from Percona Server to Aurora is viable, so is this limitation correct or are there ways around it or for those DBs that don’t have those tables is it not an issue? Due to the DB size and other constraints, MySQLdump isn’t really a practical option.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [June 30, 2025, 3:30pm UTC](https://forums.percona.com/t/migrating-from-percona-server-to-aurora-with-xtrabackup/38500/2 "2025-06-30T15:30:08Z")

</div>

> [@Andrew2](#):
>
> I’m looking at migrating some of our Percona Server on EC2 instances into Aurora

I’ve got to ask… “why”? What’s the reason for moving to Aurora? Having worked with 100s of customers at Percona, Aurora is probably the #1 “buyers remorse” theme I see. Customers move into Aurora, pay 3-5x the cost they were paying before on EC2, then learn that Aurora isn’t doing anything magical for them, and their performance is basically the same as before. I personally have performed several “RDS-\>EC2” / “RDS-\>On Prem” migrations this year due to this.

> [@Andrew2](#):
>
> I’m sure migrating from Percona Server to Aurora is viable

Having done several, yes it is. I have not yet come across this compression\_dictionary tables issue before. Perhaps it’s because none of my customers are using that feature?