Summary
This article discusses how to backup and move the Cluster Manager (CM) database.
Solution
The preferred method to back up the CM database is to use the database’s native export and import tools.
Backing Up the Database
Assuming you’re using the default built-in database, here are the commands to export your database:
cd /opt/ecloud/i686_Linux
./mysql/bin/mysqldump ecloud > /tmp/ecloud.dmp
Importing a Database
Assuming you’re using the default built-in database, here are the commands to import your database (as root):
/etc/init.d/clustermanager stop
/etc/init.d/clustermanager startmariadb
/opt/ecloud/i686_Linux/mysql/bin/mysql ecloud < /path/to/ecloud.dmp
/etc/init.d/clustermanager start
Another method to back up a smaller CM database is to use the cmtool
command.
Backing Up the Database
Example running cmtool
from the CM machine:
cmtool login
cmtool exportData
Example running cmtool
from a different machine with eMake installed:
cmtool --cm= login
cmtool --cm= exportData
Importing a Database
Example running cmtool
from the CM:
cmtool login
cmtool importData
Example running cmtool
from a different machine with eMake installed:
cmtool --cm= login
cmtool --cm= importData
Previously Documented Method
Note: Although the ecbackupdb.bat
script is still available on the CM, it has been deprecated so it may or may not work.
- On the CM machine that contains the database you want to back up, run
ecbackupdb.bat
This creates c:\eccm_full_dump.sql
or /tmp/eccm_full_dump.sql
-
Copy
eccm_full_dump.sql
to the new CM machine. -
Perform the following on the new CM:
cd c:\ECloud\i686_Win32\mysql\bin or /opt/ecloud/i686_Linux/mysql/bin
-
Then type:
mysql ecloud < eccm_full_dump.sql
-
OS versions: All
0 Comments