Upgrade with Databases Down
Upgrading with databases down involves stopping the NuoDB databases, installing the latest NuoDB software on all the hosts, then restarting the databases. If you prefer to upgrade your database with no downtime, see Rolling Upgrade: Databases Remain Available.
|All NuoDB processes on the host, even from different databases or domains, must be stopped to upgrade the NuoDB software on that host.
To upgrade NuoDB with databases down, follow these steps.
Shut down all databases in the domain.
For each database in the domain, shut down all Storage Managers (SMs) and Transaction Engines (TEs) for that database using
nuocmd shutdown database. For more information, see the Shutting down a Database and the
nuocmd shutdown databaseshuts down the database processes "gracefully", allowing client connections to complete their transactions successfully.
Back up the database archive directories.
For each host in the domain, make a copy of the content in each SM’s archives, journal directories, and the NuoDB Admin Raft log file (
$NUODB_VARDIR/raftlog). Store each copy separately. By default, the journal is stored inside the archive; if it is stored outside the archive, both need to be backed up. For information on backing up databases, see Backing Up and Restoring Databases.
nuocmd show archivesto locate the database archive and journal directories. For more information, see the
show archivecommand. Each
nuocmd show archiveoutput entry for an
archivedirectory and a
This step is optional.
Shut down the domain.
Shut down all Admin Processes (APs) on each host machine. For more information, see Stopping NuoDB Admin.
Restart the NuoDB admin services on each host.
Start an AP on each host in the domain. For more information, see Starting NuoDB Admin.
Restart each NuoDB database processes (SMs and TEs).
Start all NuoDB SM and TE processes for all databases in the domain using
nuocmd start database. For more information, see Restarting a Database and the
After upgrading the database, upgrade the database protocol, if required.
For more information, see Upgrade the Database Protocol.