Which operator(s) is this request for?
Why this matters
As MySQL instances grow, full backups become increasingly costly in time, storage, and cloud spend, even when only a fraction of the data changes regularly. Partial backup support lets teams align their backup strategy with actual business needs: protecting only the databases that matter, reducing backup windows, and enabling surgical table-level restores without triggering a full cluster recovery. For organizations running multi-tenant or mixed-workload PXC clusters, this is the difference between a backup solution that fits their data and one that forces them to over-provision storage and tolerate unnecessarily long backup and restore operations.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1177
Community Note
- Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, as they generate noise and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Which operator(s) is this request for?
Why this matters
As MySQL instances grow, full backups become increasingly costly in time, storage, and cloud spend, even when only a fraction of the data changes regularly. Partial backup support lets teams align their backup strategy with actual business needs: protecting only the databases that matter, reducing backup windows, and enabling surgical table-level restores without triggering a full cluster recovery. For organizations running multi-tenant or mixed-workload PXC clusters, this is the difference between a backup solution that fits their data and one that forces them to over-provision storage and tolerate unnecessarily long backup and restore operations.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1177
Community Note