Moving transactional data - upgrades only

As of release 2019.1, we are moving transactional audit log and flow history data from Neo4j to Elasticsearch to improve the maintenance of and access to this data.

Note: New installations are not affected by this change.
If you are performing an upgrade from a previous version of Spectrum, the upgrade process will export all of this data into two *.zip files:
  • Archive_Upgrade_18.2_history.zip
  • Archive_Upgrade_18.2_audit.zip
The more data you have, the larger the *.zip files.
Important: To avoid building large export files, we suggest that you purge or archive the data before you begin the upgrade process.

If you have a standard installation (server and database installed together on a machine), the upgrade process exports files into a directory (SpectrumDirectory/server/import). From this directory, Spectrum imports the files automatically on the first startup of Spectrum. Standard installations require no manual steps to accomplish this task.

If you have a separate installation, where the database was installed separately from the server, following the upgrade process, you must manually move the files from the database machine ((SpectrumDirectory/server/import) to the server machine (SpectrumDirectory/server/import). Once you move the files to the server machine, Spectrum imports those files automatically on the first startup of the server.

Depending on how much data you are moving, you can expect the first startup to be considerably slower than usual while this data is imported back into the system and into the Elasticsearch repository. Once Spectrum imports all the data successfully, it deletes the *.zip files from the server machine automatically.