End-of-Life (EoL)

Migrate Objects to Elasticsearch for a Distributed Database

Follow these instructions to migrate Cortex XSOAR objects to Elasticsearch from a distributed database environment.
You should migrate Cortex XSOAR objects to Elasticsearch if you plan to ingest a large amount of objects.
When you run the migration tool, the contents of the Cortex XSOAR database are read, and a corresponding object is created in Elasticsearch. The migration tool is run from the main database machine and from each database node.
In the BoltDB, data related to incidents and indicators is stored in partitions by month. To minimize downtime during the migration, we recommend you create a copy of the database, then migrate data that is older than three months from the copy, while continuing to work in your current environment. Once the initial migration is completed, you should then migrate the last three months.
All commands are run from the Cortex XSOAR server machine.
To migrate your data, use the migration tool. You cannot run more than one migration tool process at a time.
Always migrate older data before newer data. Migrating partitions out of order can cause duplicate incident ids.
  1. For the main database, copy the Cortex XSOAR database either by taking a snapshot OR manually create a copy of the
    /var/lib/demisto/data
    directory and the
    demisto.conf
    file. Then follow the same procedure for each node.
  2. Download the migration tool by appending
    downloadName=elasticsearch_migration_tool_6_1_0
    to the end of the download link that you received, when installing Cortex XSOAR.
  3. Copy your database and migrate data from the copy database to Elasticsearch.
    It is recommended to copy your data up to the last 3 months, without any downtime. If you do not want to do this, go to step 4.
    1. Copy the Cortex XSOAR database by doing one of the following:
    2. Copy the
      demisto.conf
      file.
    3. Edit the copy of the
      demisto.conf
      file, by adding your Elasticsearch configuration.
      Ensure that the same Elasticsearch object exists in the
      demisto.conf
      on the app server and the main database and hat
      elasticsearch
      is the top-level object in the
      demisto.config
      file (within the main curly brackets).
      Edit the copies of
      demisto.conf
      for the main database and for each node to add your Elasticsearch configuration.
    4. For the main database and for each node, using
      demisto
      or
      sudo
      permissions, run the following command:
      sudo ./elasticMigrator -config-path
      <file path-of-copy-of-demisto.conf>
      -db-path
      <path-of-the-copy-of-the-demisto-database>
      -
      <flags>
      For a full list of the flags, see Migration Tool Flags. For example, to exclude the last 3 partitions from the migration, add the
      -partitions-to-ignore
      flag and value to the command by typing the following:
      sudo ./elasticMigrator -config-path /usr/local/dev/copy_of_demisto.conf -db-path /usr/local/dev/lib_demisto_copy/data -partitions-to-ignore '042021,052021,062021'
      When you run the migration tool, parameter values specified in the
      demisto.conf
      file override values supplied for tool flags and default values. If no value exists in the
      demisto.conf
      file, values supplied in the tool flags override default values, but do not write the values to the
      demisto.config
      file.
    5. Complete steps 1 to 3 in Validate the migration.
  4. After the migration of the data is complete and validated, migrate your data from the active database to Elasticsearch.
    1. Create a backup copy of the
      demisto.conf
      file for your active database.
    2. Edit the original
      demisto.conf
      file (not a copy) for the main database and for each node to add your Elasticsearch configuration. Ensure that the same Elasticsearch object exists in the
      demisto.conf
      on the app server and the main database.
    3. For the main database and for each node, stop the Cortex XSOAR server.
      • CentOS:
        sudo systemctl stop demisto
      • Ubuntu:
        sudo service demisto stop
    4. For the main database and for each node, run the
      ./elasticMigrator
      command with either
      demisto
      or
      sudo
      permissions. Use the
      -partitions
      flag to specify the remaining partitions.
      Example:
      sudo ./elasticMigrator -partitions '
      042021,052021,062021
      '

Migration Tool Flags

Flag
Type
Description
Required
accounts
(multi-tenant only)
String
A comma-separated list of accounts to migrate. If not specified, all accounts are migrated.
Optional
config-path
String
The path to the configuration file for the server. Default: /etc/demisto.conf.
Optional
db-path
String
The path to the database directory. Default: /var/lib/demisto.
Optional
elastic-batch-size
integer
The number of indicators per batch to write to Elasticsearch indexes. Default: 700.
Optional
elastic-index-prefix
String
The index prefix used in Elasticsearch.
Optional
elastic-key
String
The API key to connect to Elasticsearch.
Required (unless a username and password are used)
elastic-password
String
The password to connect to Elasticsearch.
Required (unless API key is used)
elastic-url
String
The URL of your Elasticsearch environment. Default: http://localhost:9200.
Required
elastic-username
String
The username to connect to Elasticsearch.
Required (unless API key is used)
ignore-ids-path
String
The path to the file with the IDs to ignore, per object.
Optional
log-level
String
The log level to display. Default: info.
Optional
logfile
String
The location of the log file.Default: /var/log/demisto/elastic_migration.log
Optional
migrate-all
true
By default, the Elasticsearch tool checks existing indexes and migrates only the ones that are new. Using this flag, the Elasticsearch tool migrates all indexes even if they currently exist. This is useful, for example, if there was an error or invalid data that was fixed. When used, the objects-to-migrate and objects-to-ignore flags are ignored.
Optional
objects-to-ignore
String
Comma-separated list of objects not to migrate. When the migrate-all flag is used, this flag is ignored.
Optional
objects-to-migrate
String
Comma-separated list of objects to migrate. When the migrate-all flag is used, this flag is ignored.
Optional
partitions
String
Comma-separated list of partitions to migrate. If no partitions are specified, all partitions are migrated.
Optional
partitions-to-ignore
String
Comma-separated list of partitions to exclude.
Optional
previous-results
Show results of the previous migration.
Optional
skip-existing-indicators
false
Existing indicators are not modified during the migration.
Optional
version
Prints the migration tool version.
Optional
y
false
Answers yes to all questions, unless there is an error.
Optional

Recommended For You