manage_server restore
Restore Enterprise server data from archive (requires server to be running)
Usage: manage_server restore [OPTIONS]
Options:
-f, --file <file>
[default: bn_enterprise_backup.tar]
--swarm[=<STACK_NAME>]
Operate in docker swarm mode
--registry-host <HOSTNAME>
Hostname of registry [default: registry.enterprise.binary.ninja]
-l, --license-file <license-file>
Path to Binary Ninja license file [default: license.dat]
--uid <uid>
User ID used for data and tasks (defaults to current User ID)
--gid <gid>
Group ID used for data and tasks (defaults to current Group ID)
-h, --help
Print help information
Database Options:
--db-name <NAME> Name of database to use [default: binaryninja_enterprise]
--db-host <HOSTNAME> Name of host to use when connecting to database [default: database]
--db-port <PORT> The port to use when connecting to database [default: 5432]
--db-user <USERNAME> The user to use when connecting to database [default:
binaryninja_enterprise]
--db-password-file <FILE> Path to file containing password to authenticate with the database [default:
./secrets/db_password]
--redis-host <HOSTNAME> Name of host to use when connecting to message broker [default:
redis]
--redis-port <PORT> Port to use when connecting to message broker [default: 6379]
Object Store Options:
--object-store-bucket-name <BUCKET>
Object store bucket name (must be between 3 and 63 characters, only using lowercase
letters, numbers, dot, and hyphen) [default: binaryninja-enterprise]
--object-store-endpoint-url <URL>
Object store endpoint URL [default: https://object-store:9000]
--object-store-key-id-file <FILE>
Path to file containing the access key ID to use when authenticating with the object store [default:
./secrets/object_store_access_key_id]
--object-store-secret-key-file <FILE>
Path to file containing the secret access key to use when authenticating with the object
store [default: ./secrets/object_store_secret_access_key]
Note
Please remember that the user running this command must have permissions to run docker
commands for it to complete successfully.
Danger
We strongly recommend restarting the Enterprise server after restoring from a backup