Documentation Center

Moving the database

Access restrictions, disk space availability, or other issues might require moving the SDL LiveContent Reach database from the SDL LiveContent Reach installation directory to another location.

About this task

You should perform this procedure on your test server first and then repeat it for your production server.

Procedure

  1. On the SDL LiveContent Reach server, stop the Tomcat service or SDL LiveContent Reach database service.
  2. Create a backup copy of the LiveContent_home\conf.xml file.
  3. Update LiveContent_home\conf.xml to reference the new database location.
    1. In the cluster element, change the value of the journalDir attribute from data\journal to the new location.
      For example, if the new database location is D:\LiveContent, change journalDir="data\journal" to journalDir="D:\LiveContent\data\journal".
    2. In the db-connection element, change the value of the files attribute from data to the new location.
      For example, change files="data" to files="D:\LiveContent\data".
    3. In the recovery element, change the value of the journal-dir attribute from data to the new location.
      For example, change journal-dir="data" to journal-dir="D:\LiveContent\data".
  4. Copy the data directory from the LiveContent_home installation directory into the new location.
    For example, if SDL LiveContent Reach is installed in the C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\LiveContent directory and the new database location is D:\LiveContent, copy C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\LiveContent\data to D:\LiveContent\.
  5. Start the stop the Tomcat service or the SDL LiveContent Reach database service.
  6. Log on to SDL LiveContent Reach and verify that the new database location is working properly.
  7. Delete the data directory underneath the LiveContent_home installation directory.