Documentation Center

Database backup and restore

SDL LiveContent Reach provides a backup option to suit your specific needs.

An automated database back up is created based on the schedule that was established when SDL LiveContent Reach was installed. If a manual back up is required, there are several options, depending on whether you require users to be able to access SDL LiveContent Reach during the backup activity. Database restore options also depend on that same requirement.
  • If you require users to be able to access SDL LiveContent Reach during the backup or restore activity, then select one of the client-side backup/restore options.

  • If you can take SDL LiveContent Reach offline temporarily, server-side backup/restore options are your best choices.

Client-side backups are the least intrusive (you do not have to shut down SDL LiveContent Reach), but you could miss some online database transactions that may have occurred during the backup. Server-side backups prevent access to SDL LiveContent Reach, but guarantee a full snapshot of the database.
  • Client-side
    • loaddb BACKUP/RESTORE
    • loaddb client (eXist Remote mode backup and restore tools)
  • Server-side
    • loaddb CHECKDB -Dlc.backup=yes (backup only)
    • loaddb client (eXist Embedded mode backup and restore tools)

Loaddb CHECKDB is a server-side backup, but SDL LiveContent Reach and Tomcat are online; therefore, it locks out user access while backing up the database. It uses the same mechanism as a scheduled backup. This is the most-efficient backup method; however, there is no expectation that the backup will start immediately, as database transactions may be in progress. In this case, backup will be delayed until pending transactions have been written, at which point it will then lock out user access and proceed with the backup.