Backing Up and Restoring a Database

You use the exportData and importData cmtool commands to back up and restore a database.

Manual migration using the exportData and importData commands is recommended only to replicate data between Cluster Manager instances running the same version of the Cluster Manager. For example, you could use it to make a backup dump and then restore it to a new instance of the Cluster Manager of the same version.

Backing Up Your Database

Run the following command to export the Cluster Manager data to a file:

cmtool exportData <file_name>

where < file_name > is the file name or path to export to. If you use a file name, the destination is the current working directory of the Java process ( /opt/ecloud/i686_Linux or C:\ECloud\i686_win32 by default. If you use a path, the Cluster Manager Java user ( eacmuser ) must have execute and write access to that path.

This is a full database dump, which might take substantial time for a large database.

Restoring Your Database

Run the following command to import the Cluster Manager data from a file:

cmtool importData <file_name>

where < file_name > is the name of the file to import. The file’s path is relative to the current working directory of the Java process ( /opt/ecloud/i686_Linux or C:\ECloud\i686_win32 by default).

This command imports a full database dump, which might take substantial time for a large database.

Make sure that you

  • manually delete any old or unused agents from the agents list.

  • update the license file after import, if it has previously expired.