Backup and Restore
Learn how to create a backup of the data in your on-premises deployment, including the hardware configuration, virtual devices, projects, users, custom firmware, snapshots, and more.
Prepare to Back Up the Data
Before starting the backup, make sure that all devices are stopped (shut down) and that no users are interacting with the web interface or the API.
The Components to Back Up
The following components are required for a complete backup:
- The MariaDB database, using
mysqldump
- The configuration files in
/etc/corellium/
- The image files, referenced by
imageDataPath
incoordinator.json
- The firmware files mounted to
/var/ipsw/
- The LVM device volumes listed in
lvs -S 'lv_attr !~ ^t' stack-volumes
Restore a Server Backup
Recover the data that was backed up:
- The MariaDB database state
- The configuration files
- The image files
- The firmware files
- The LVM device volumes
Migration
To save time when updating your Corellium hardware, you can use the corellium-admin
tool to migrate data from your old device to your new one.
In order to use corellium-admin
, you need the following to be true:
- Both servers on the same RC and license
- Both servers up and running
- Both servers on the same network and reachable from your console
The list of commands in corellium-admin
are:
migrate <list, export, import>
vm <list, export, import>
image <list, export, import>
db <export, import>
project <list>
user <list>
help
You will need to run corellium-admin
from your new hardware, and all commands are formatted as $ corellium-admin <command> <sub-command> <arguments>
, for example the migration command would be:
corellium-admin migrate --all --from 10.0.0.1
In our example, we use 10.0.0.1
as our IP address for our old hardware, yours will likely differ. We are also doing a complete migration with the --all
subcommand; you can elect to migrate the entirety of your Corellium instance, or you can migrate it piecemeal.