Support Center > Search Results > SecureKnowledge Details
How to migrate the events database from SmartEvent server R7x to SmartEvent R80 and above server
Solution

Background

The SmartEvent database is not migrated during an advanced upgrade. The SmartEvent administrator should perform several steps to migrate the database from the source SmartEvent server R7x to the target SmartEvent server R80 and above.

The SmartEvent database can be very large. Therefore, its migration should be performed separately, since it may take a long time.

The earliest SmartEvent version supported for such an upgrade is R70.20

 

Procedure

  1. Copy the $RTDIR/bin/eva_db_backup.csh script from SmartEvent R80 server to the $RTDIR/bin/ directory on SmartEvent R7x server.

  2. Connect to the command line on SmartEvent R7x server.

  3. Log in to Expert mode.

  4. If you copied the eva_db_backup.csh script via a Windows machine, then convert it from DOS to UNIX format:

    [Expert@HostName:0]# dos2unix $RTDIR/bin/eva_db_backup.csh
  5. Assign the required ownership and permissions:

    [Expert@HostName:0]# chown -v admin:root $RTDIR/bin/eva_db_backup.csh
    [Expert@HostName:0]# chmod -v 0755 $RTDIR/bin/eva_db_backup.csh
  6. Back up the SmartEvent R7x database:

    [Expert@HostName:0]# cd /var/log/
    [Expert@HostName:0]# $RTDIR/bin/eva_db_backup.csh
  7. Copy the output backup file date-db_backup.backup and eventiaUpgrade.tar from the SmartEvent R7x server
    to the SmartEvent R80 server (into some directory, e.g., /some_path_to_R77_bkp/).

    Note: The backup TAR file is created in the current directory, in which the eva_db_backup.csh script was executed.
  8. Connect with SmartConsole to SmartEvent server R80 and above.

  9. Enable the SmartEvent blade.

  10. Restore the SmartEvent database copied from the SmartEvent server R7x to the SmartEvent server R80 and above in the Solr database:

    [Expert@HostName:0]# $RTDIR/bin/eventiaUpgrade.sh -upgrade /some_path_to_R77_bkp/eventiaUpgrade.tar

 

Notes

  1. For a database that is tens of GB in size, the upgrade may take a few hours.

  2. The following message is displayed when the database upgrade process ends:
    Progress: 100%. Upgrade completed successfully

  3. To monitor the upgrade progress, open another shell and run:
    [Expert@HostName:0]# watch $RTDIR/bin/eventiaUpgrade.sh -status

    1. Restoring the data into the Postgres database:

      1. This stage cannot be paused.
      2. Running 'eventiaUpgrade.sh -status' will print: "Restoring events_db into postgres"
    2. Indexing the data into the Solr database:

      1. This stage can be controlled by the administrator (stop / start / pause / resume the process).
      2. Running 'eventiaUpgrade.sh -status' will print the progress of the upgrade in percentage, time since last started, rate of upgrade, etc.
      3. During the running of eventiaUpgrade.sh, the output will be: "[RESTORE] Restore finished successfully"
  4. Relevant logs are saved in the $RTDIR/log/eventiaUpgrade/ directory.

  5. Currently, after this upgrade, it is not possible to view the events in R80 and above with a new customized administrator.
    There are plans to resolve this issue in one of the next Takes of sk111536 - Jumbo Hotfix Accumulator for R80 (R80_jumbo_hf).

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment