Backing up the database using loaddb CHECKDB
This procedure describes how to manually back up the Content Delivery database with a consistency check on the server. The CHECKDB command checks the database for consistency, and can also be used to manually back up the 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. Only use this command if the recommended loaddb BACKUP command does not work.
Before you begin
Content Delivery will be unavailable for the duration of the execution.
Content Delivery must be running. The database is suspended and all requests will be pending until the backup has completed.
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
CHECKDB command backs up the entire Content Delivery database: users, groups, publications, forms (definitions and instances), audit trails, 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
Example
loaddb.bat -Dlc.file="myBackup1.zip" CHECKDB