8.3 Backup the Repository

The following is an example of how to use mysqldump to export all databases in the repository instance to a dump file named mem.dump:

Note

This example assumes you are using the MySQL instance solely as the repository for MySQL Enterprise Service Manager and not for any other purpose. This is the recommended implementation.

$> mysqldump --single-transaction -uservice_manager -pPassword 
       -P13306 -h127.0.0.1 —all-databases > mem.dump

The above command creates a file, mem.dump, containing all MySQL Enterprise Service Manager data.

To restore the dump file, run the following mysql command on a clean instance:

$> mysql -u <user> -p -P13306 -h127.0.0.1 < mem.dump

You should also backup the following files:

• apache-tomcat/conf/Keystore

• apache-tomcat/conf/server.xml

• java/lib/security/cacerts

• apache-tomcat/webapps/ROOT/WEB-INF/config.properties

• apache-tomcat/webapps/ROOT/WEB-INF/configArea/mem.keystore

You can also use MySQL Enterprise Backup to manage your repository backup process. For more information, see the MySQL Enterprise Backup documentation.

Note

It is also possible to shut down MySQL Enterprise Service Manager, copy the entire data directory to another location, and restart. To restore the copy, simply shut down MySQL Enterprise Service Manager and overwrite the data directory with the backup, and restart. This is the same process used by MySQL Enterprise Service Manager upgrade installer.