Upgrading Your First Database to Be Minimally Redundant

In Creating Your First Database, you create a simple NuoDB database whose domain includes one host with one storage manager (SM) and one transaction engine (TE) running on it. Suppose you are ready to deploy this database and have decided to start with a minimally redundant database, that is, one with two TEs and two SMs for data redundancy. Accomplishing this requires the following:

Configuring a Second Domain Host

To configure a minimally redundant database, you need at least two physical hosts available for the NuoDB processes to use. Also, there must be one broker running on each host in your domain. To start a broker on another host, you must install NuoDB software on the second host. See Installing NuoDB. When installing NuoDB on the second host, defer starting NuoDB services automatically.

After NuoDB is installed on the second host, edit the $NUODB_HOME/etc/default.properties file on the second host as follows:

Scaling the Database to Run on Two Hosts

Start (or restart) NuoDB services on the second host. See Starting and Stopping NuoDB Services.

Once you have created your second domain host, you can execute the following commands from either host.

From a Linux prompt, create the second set of database SM and TE processes:

hostname2 = the host name of the second host machine.

$ nuodbmgr --broker <hostname2> --password <domain password> 
nuodb [domain] > start process sm database <dbname> host <hostname2> archive /var/opt/nuodb/production-archives/<dbname> initialize true

nuodb [domain] > start process te database <dbname> host <hostname2>

Done! You have upgraded your first NuoDB database to be minimally redundant! You can view your new database using the following command.

nuodb [domain] > show domain summary

Save a database description file to easily restart your database later.

nuodb [domain] > capture database <dbname> dbFile /directory/<dbname>.desc
nuodb [domain] > exit