Upgrading to a New Release

There are two ways to upgrade your NuoDB database. The following table provides a brief description of each upgrade method:

Upgrade Method Brief Description
Upgrading with databases down

Shut down your database(s), install the latest NuoDB release on each host, then restart your database(s).

When continuous database availability is not required , follow instructions at Upgrading With Databases Down.

Rolling Upgrade

Install the latest NuoDB release on one host at a time. Your database(s) remain(s) available throughout the upgrade procedure.

When continuous data availability is required, follow instructions at Rolling Upgrade: Databases Remain Available.

During a rolling upgrade, your database upgrades to the new version when the last node in the database is upgraded, but not before. As long as there is one node in the database that is running the old version, the database has not been upgraded

Whether using either method to upgrade your database, NuoDB supports all upgrades from version 2.6.

Caution: Once your database has been upgraded, it may not be possible to downgrade. For information on downgrading, see Downgrading to a Previous Release.

Note: When upgrading from version 2.6.1 and lower to version 3.0 and higher, you must clear your browser cache to view the new icons on the NuoDB Home page.

Upgrade considerations

When deciding which upgrade method to use, consider the following:

Note: When opting to use a rolling upgrade, be aware that if your database has only one transaction engine (or if it has a storage group that is served by only one storage manager), then some or all of your database is unavailable when you upgrade the system which hosts the transaction engine or storage manager.