This article outlines one method for performing a backup and recovery on a MySQL database. This article is not intended as a comprehensive technical guide of specific database backup and recovery features, but is meant to be an outline of basic MySQL commands needed for a database administrator to create a reliable database backup strategy for LiveCycle ES.
Caution: As with any other aspect of your LiveCycle ES implementation, your backup and recovery strategy needs to be developed and tested in a development or staging environment before being used in production in order to ensure that the entire solution is working as expected with no data loss.
Use MySQLAdmin, or modify the ini files in Windows, to configure your MySQL database to run in binary log mode. (See MySQL binary logging.) A hot backup tool for MySQL is also available from InnoBase software. For more information about hot backup by Innobase, see Innobase Hot Backup.
You can use the mysqldump utility to obtain the full database backup. Full backups are needed but they are not always convenient. They produce big backup files and take time to generate. To do an incremental backup, ensure you start the server with the log-bin option as described in the previous section. Each time the MySQL server restarts, it stops writing to the current binary log, creates a new one and from then on, and the new one will become the current one. You can force a switch manually with the FLUSH LOGS SQL command. After the first full backup, subsequent incremental backups are done by using mysqladmin with the flush-logs command which will create the next log file.
For more information about MySQL database backup and recovery, see Backup Strategies.