Upgrading With Databases Down

For each database in the domain, shut down all NuoDB Storage Managers (SMs) and Transaction Engines (TEs) for that database using the nuocmd shutdown database command. For more information, see Shutting down a Database and NuoDB Command Reference.

While this step is optional, it is recommended as a best practice. For each host in the domain, make a copy of the content in each SM’s archive and journal directories, as well as the NuoDB Admin raftlog file ($NUODB_VARDIR/raftlog). Store each copy separately. For information on backing up databases, see Backing Up and Restoring Databases. The location of the database archive and journal directories can be determined using the nuocmd show archives command. For more information, see NuoDB Command Reference. Each nuocmd show archive output entry for an archive-id displays an archive directory and a journal-dir directory. By default the journal is stored inside the archive; if it is stored outside the archive then both need to be backed up.

Shut down all NuoDB Admin processes (APs) on each host machine. For more information, see the Domain Operations section, Starting and Stopping NuoDB Admin.

On each host in the domain, install the new NuoDB software release. According to the platform on which you are installing NuoDB, see one of:

Start an AP on each host in the domain; see Starting and Stopping NuoDB Admin.

Start all NuoDB SM and TE processes for all databases in the domain using the nuocmd start database command. For more information, see Restarting a Database and NuoDB Command Reference.

After completing the above steps, see After You Upgrade.