Open topic with navigation
Before you upgrade to a newer NuoDB release, best practices include the following steps:
Stop the database.
nuochk ‑‑repair on the "leader" archive only; then, if that archive was modified, copy that modified archive to all other archive locations OR
nuochk ‑‑repair on the "leader" archive only; then, if that archive was modified, delete all other archiveLocations so that the other SMs will SYNC the contents of the repaired archive.
nuochk ‑‑repairon *all* archives, however,if different archives have different errors (which is possible), then the result when restarting the database afterwards will be non-deterministic and could result in new corruptions, depending on which SMs SYNC what and from where.
Note: For more information, see NuoDB Check.
Determine whether you will want to change any NuoDB configuration files to take advantage of new features or changes to features. See New Features in This Release and Changes in This Release. On each upgraded host, you will want to make any necessary updates to configuration files before you restart the broker on that host.
Installation of the new NuoDB release will not overwrite any existing configuration files:
Instead, a new
nuodb-rest-api.yml.sample file are installed in