Upgrade from 5.7 to 8.0 overview¶
Upgrading your server to 8.0 has the following benefits:
| Benefits | Description |
|---|---|
| Security fixes | These patches and updates protect your data from cyberattacks and address vulnerabilities or bugs in the database software. |
| New or improved features | You have access to new or improved features which enhance the functionality, performance, and availability of the database. |
| Reduced labor | You can automate some routine tasks. |
| Relevance | Your customers and stakeholders have changing needs and expectations. Using the latest version can help to deliver solutions faster. |
| Reduced operational costs | An upgraded database server can help reduce your operational costs because the server has improved efficiency and scalability. |
Not upgrading your database can have the following risks:
| Risks | Description |
|---|---|
| Security risks | Your database server is vulnerable to cyberattacks because you do not receive security fixes. These attacks can result in data breaches, data loss, and data corruption. These actions can harm the organization’s reputation and lose money. |
| Service risks | You do not benefit from new or improved features. This risk may cause poor user experience, reduced productivity, and increased downtime. |
| Support risks | You are limited in support access. This risk can result in longer resolution times, unresolved issues, and higher support costs. |
| Compatibility risks | You can experience compatibility issues with hardware, operating system, or applications since the older version is not supported on newer platforms. At some point, the database server is no longer supportable. |
| Failure risk | A failure in either hardware, operating system or application may force an upgrade at the wrong time. |
Create a test environment to verify the upgrade before you upgrade the production servers. The test environment is crucial to the success of the upgrade. There is no supported downgrade procedure. You can try to replicate from an 8.0 version to 5.7 or restore a backup.
Several tools in the Percona Toolkit can help with the upgrade process.
We recommend upgrading to the latest version. The following topics describe the major changes from 5.7 to 8.0:
- General changes
- InnoDB changes
- Security and account management changes
- Deprecated in 8.0
- Removed in 8.0
Review the documentation for other changes between 5.7 to 8.0.
Review Upgrade Strategies for an overview of the major strategies.
The following list summarizes a number of the changes in the 8.0 series and has useful guides that can help you perform a smooth upgrade. We strongly recommend reading this information:
Review other Percona blogs that contain upgrade information.
Implemented in Percona Server for MySQL 8.0.15-5, Percona Server for MySQL uses the upstream implementation of binary log file encryption and relay log file encryption.
Known limitation¶
The Percona 5.7 and Percona 8.0 Dockerfiles have a different user ID (UID). This difference can create compatibility and permissions issues. The UID determines the permissions for the anonymous volume mounts. Since the UIDs differ between versions, the container does not have the necessary permissions to access or modify these volumes.
Get expert help¶
If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.