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.

Steps for Upgrading with Databases Down

To upgrade NuoDB with databases down, follow these steps.

  1. 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 shutdown database command.

    nuocmd shutdown database shuts down the database processes "gracefully", allowing client connections to complete their transactions successfully.
  2. 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.

    Use nuocmd show archives to locate the database archive and journal directories. For more information, see the show archive command. Each nuocmd show archive output entry for an archive-id displays an archive directory and a journal-dir directory.
    This step is optional.
  3. Shut down the domain.
    Shut down all Admin Processes (APs) on each host machine. For more information, see Stopping NuoDB Admin.

  4. Install the latest release of NuoDB.
    Install the latest release of NuoDB on each host in the domain. For more information, see Installing NuoDB on Linux or Installing NuoDB on Windows.

  5. Restart the NuoDB admin services on each host.
    Start an AP on each host in the domain. For more information, see Starting NuoDB Admin.

  6. 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 start database command.

After upgrading the database, upgrade the database protocol, if required. For more information, see Upgrade the Database Protocol.