Documentation Center

Backing up a database using loaddb BACKUP

This procedure backs up a Legacy Content Delivery database. The backup you create can be restored to another system, even if that system has a different operating system than the computer on which you create the backup. The BACKUP command outperforms other ways of restoring the database, especially if the database is large.

Before you begin

Legacy Content Delivery will be unavailable for the duration of the execution.

If the backup you intend to create includes user information and credentials (that is, if it will contain a backup of the folder /db/system/), take note of the admin password now. If this password ever changes, you will need the original password in order to perform a successful restore.

About this task

By default, the BACKUP command backs up the entire Legacy Content Delivery database: users, groups, publications, forms (definitions and instances) and packages. The following files are not part of the database, and are therefore not backed up by this task:
  • conf.xml
  • lc.properties
  • log4j.xml
  • LiveContent*.xml files

If you have modified any or all of these files, you must back up and restore them separately.

Procedure

  1. Make sure that no end users are using Legacy Content Delivery during the execution.
  2. At a command prompt, in the directory where Legacy Content Delivery is installed, type one of the following (without pressing Enter):
    • On a Windows machine, type loaddb.bat
    • On a Unix machine, type loaddb.sh
  3. Specify one or more of the following switches, as needed (again without pressing Enter):
    Switch and valueDescriptionDefault if omitted
    -Dlc.file="FILENAME"The path to, and name of, the ZIP file in which you want to store your database backup.full<datetime>.zip
    -Dlc.host=HOSTNAMEThe host name of the Legacy Content Delivery instance to connect to. When using this parameter to migrate from one server to another, ensure that each server within the secure group shares the same lc_auth_seed value in its lc.properties file. .localhost
    -Dlc.port=PORTNUMBERThe port to connect to.8080
    -Dlc.context=CONTEXTThe specific application context in which Legacy Content Delivery runs (must start with a /)./ContentDelivery
    -Dlc.protocol=HTTPSAdd this switch if you connect to Legacy Content Delivery over a secure HTTPS connection.HTTP
  4. After the batch file name and your switches (if any), add the word BACKUP and press Enter.
    The database is backed up, and a log file with a filename report-YYYYMMDD-HHMM.log, with YYYYMMDD-HHMM as a timestamp of the log, is produced. The log file is located in the same directory as the backup file created by the loaddb command.

Example

Example:
loaddb.bat -Dlc.file="myBackup1.zip" BACKUP