Sys Maintenance: ESA Backup and Recovery

Document created by RSA Information Design and Development on Mar 22, 2017Last modified by RSA Information Design and Development on Aug 1, 2017
Version 8Show Document
  • View in full screen mode
 

Administrators can back up and restore configuration and database files for ESA, so that if information is lost or deleted, it can be restored.

Back Up Files

To back up configuration files:

  1. Stop the ESA service using the following command:

    service rsa-esa stop

  2. Run the following command. Ensure that the command consists of a single line.

    mongodump -d 'sa' -c 'rule' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'ruleTemplate' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'synchronization' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'enrichmentSource' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'databaseReference' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'outputActionProvider' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'template' -o '/tmp/esa-mongo-backup' -v && mongodump -d 'sa' -c 'esaInventory' -o '/tmp/esa-mongo-backup' -v

    cd /tmp
  3. Create the tar file:
    tar -cvjf esa-mongo-backup.tar.bz2 esa-mongo-backup/sa

Restore Files

When you are restoring files that have been backed up, put the files in a consistent place. In this document, we are using the /tmp/ folder as the location for the tar files to be extracted. You can use a different folder if needed.

To restore the configuration files:

  1. Log into the host you intend to restore from a saved backup using SSH.
  2. Stop the ESA service using the following command:
    service rsa-esa stop
  3. Copy the tar file into the /tmp folder.

  4. cd /tmp
  5. Extract the tar file:
    tar -xvjf esa-mongo-backup.tar.bz2
  6. Run the following command. Ensure that the command is all on one line.
    mongorestore -d 'sa' -c 'rule' --drop '/tmp/esa-mongo-backup/sa/rule.bson' -v && mongorestore -d 'sa' -c 'ruleTemplate' --drop '/tmp/esa-mongo-backup/sa/ruleTemplate.bson' -v && mongorestore -d 'sa' -c 'synchronization' --drop '/tmp/esa-mongo-backup/sa/synchronization.bson' -v && mongorestore -d 'sa' -c 'enrichmentSource' --drop '/tmp/esa-mongo-backup/sa/enrichmentSource.bson' -v && mongorestore -d 'sa' -c 'databaseReference' --drop '/tmp/esa-mongo-backup/sa/databaseReference.bson' -v && mongorestore -d 'sa' -c 'outputActionProvider' --drop '/tmp/esa-mongo-backup/sa/outputActionProvider.bson' -v && mongorestore -d 'sa' -c 'template' --drop '/tmp/esa-mongo-backup/sa/template.bson' -v && mongorestore -d 'sa' -c 'esaInventory' --drop '/tmp/esa-mongo-backup/sa/esaInventory.bson' -v
  7. Restart the Jetty server by running the following command.
    restart jettysrv
You are here
Table of Contents > Sys Maintenance: ESA Backup and Recovery

Attachments

    Outcomes