Upgrading an Aurora global database follows the same procedures as upgrading Aurora DB clusters. However, following are some important differences to take note of before you start the process.
We recommend that you upgrade the primary and secondary DB clusters to the same version. You can only perform a managed cross-Region database failover on an Aurora global database if the primary and secondary DB clusters have the same major, minor, and patch level engine versions. However, the patch levels can be different, depending on the minor engine version. For more information, see Patch level compatibility for managed cross-Region switchovers and failovers.
Major version upgradesWhen you perform a major version upgrade of an Amazon Aurora global database, you upgrade the global database cluster instead the individual clusters that it contains.
To learn how to upgrade an Aurora PostgreSQL global database to a higher major version, see Major upgrades for global databases.
To learn how to upgrade an Aurora MySQL global database to a higher major version, see In-place major upgrades for global databases.
NoteWith an Aurora global database based on Aurora MySQL, you can perform an in-place upgrade from Aurora MySQL version 2 to version 3 only if you set the lower_case_table_names parameter to default and you reboot your global database.
To perform a major version upgrade to Aurora MySQL version 3 when using lower_case_table_names, use the following process:
You can also use the snapshot restore method instead. For more information, see Restoring from a DB cluster snapshot.
Minor version upgradesFor a minor upgrade on an Aurora global database, you upgrade all of the secondary clusters before you upgrade the primary cluster.
To learn how to upgrade an Aurora PostgreSQL global database to a higher minor version, see How to perform minor version upgrades and apply patches. To learn how to upgrade an Aurora MySQL global database to a higher minor version, see Upgrading Aurora MySQL by modifying the engine version.
Before you perform the upgrade, review the following considerations:
Upgrading the minor version of a secondary cluster doesn't affect availability or usage of the primary cluster in any way.
A secondary cluster must have at least one DB instance to perform a minor upgrade.
If you upgrade an Aurora MySQL global database to version 2.11.*, you must upgrade your primary and secondary DB clusters to exactly the same version, including the patch level.
If you upgrade an Aurora PostgreSQL global database, you must upgrade your primary and secondary DB clusters to exactly the same version and patch level. To update the patch level, apply all pending maintenance actions on the secondary cluster.
To support managed cross-Region switchovers or failovers, you might need to upgrade your primary and secondary DB clusters to the exact same version, including the patch level. This requirement applies to Aurora MySQL and some Aurora PostgreSQL versions. For a list of versions that allow switchovers and failovers between clusters running different patch levels, see Patch level compatibility for managed cross-Region switchovers and failovers.
If your Aurora Global Database is running one of the following minor engine versions, you can perform managed cross-Region switchovers or failovers even if the patch levels of your primary and secondary DB clusters don't match. For minor engine versions lower than the ones on this list, your primary and secondary DB clusters must be running the same major, minor, and patch levels to perform managed cross-Region switchovers or failovers. Make sure to review the version information and the notes in the following table when planning upgrades for your primary cluster, secondary clusters, or both.
NoteFor manual cross-Region failovers, you can perform the failover process as long as the target secondary DB cluster is running the same major and minor engine version as the primary DB cluster. In this case, the patch levels don't need to match.
If your engine versions require identical patch levels, you can perform the failover manually by following the steps in Performing manual failovers for Aurora global databases.
Database engine Minor engine versions NotesAurora MySQL
No minor versions
None of the Aurora MySQL minor versions allow managed cross-Region switchovers or failovers with differing patch levels between the primary and secondary DB clusters.
Aurora PostgreSQL
Version 15 or higher major versions
Version 14.5 or higher minor versions
Version 13.8 or higher minor versions
Version 12.12 or higher minor versions
Version 11.17 or higher minor versions
With the engine versions listed in the previous column, you can perform managed cross-Region switchovers or failovers from a primary DB cluster with one patch level to a secondary DB cluster with a different patch level.
With minor versions lower than these, you can perform managed cross-Region switchovers or failovers only if the patch levels of the primary and secondary DB clusters match.
WarningWhen you update a cluster in your global database to any of the following patch versions, you won't be able to perform cross-Region switchovers or failovers until all of the clusters in your global database are running one of these patch versions or a newer one.
Patch versions 16.1.6, 16.2.4, 16.3.2, and 16.4.2
Patch versions 15.3.8, 15.4.9, 15.5.6, 15.6.4, 15.7.2, and 15.8.2
Patch versions 14.8.8, 14.9.9, 14.10.6, 14.11.4, 14.12.2, and 14.13.2
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4