Relocating the Database or Repository

Overview

There may come a time where you have to move the Database or Repository (or both) to another location or another machine. This guide will walk you through the steps required.

Migrating the Database

These are the steps to move your Database to a new location:

  1. Shut down all the Slave applications running on your render nodes. You don’t want them making changes during the move.
  2. Stop the mongod process on the Database machine.
  3. Copy the Database folder from the original location to the new one.
  4. Update the config.conf file in the data folder to point to the new system log folder and storage folder locations.
  5. Start the mongod process on the Database machine.
  6. Modify the dbConnect.XML file in the settings folder in the Repository to set the new database host name or IP address (if you moved it to another machine).
  7. Start up the Slaves and ensure that they can connect to the new Database.

Here is an example of how you would update the config.conf file if you copied the new database location was C:\NEW_DATABASE_FOLDER:

systemLog:
   destination: file
   path: C:/NEW_DATABASE_FOLDER/data/logs/log.txt
   quiet: true

storage:
   dbPath: C:/NEW_DATABASE_FOLDER/data

Because the Clients use the dbConnect.xml file in the Repository to determine the database connection settings, you don’t have to reconfigure the Clients to find the new database.

Migrating the Repository

These are the steps to move your Repository to a new location:

  1. Ensure that the share for the new location already exists. Also ensure that the proper permissions have been set.
  2. Shut down all the Slave applications running on your render nodes. You don’t want them making changes during the move.
  3. Copy the Repository folder from the original location to the new location.
  4. Redirect all your Client machines to point to the new Repository location.
  5. Start up the Slaves and ensure that they can connect to the new Repository location.
  6. Delete the original Repository (optional).

As an alternative to step (4), you can configure your share name (if the new Repository is on the same machine) or your DNS settings (if the new Repository is on a different machine) so that the new Repository location has the same path as the original. This saves you the hassle of having to reconfigure all of your Client machines.