KBEC-00467 - Back up and Restore DevOps Insight Server Data

Article ID:360054880071
1 minute readKnowledge base

Summary

You need to back up and restore your DevOps Insight Server data. This need may arise if you are migrating or reinstalling your DevOps Insight Server.

Solution

Back up data

  1. Stop the 'commanderElasticsearch' and 'commanderLogstash' (Linux) or 'CloudBees CD Elasticsearch Service' and 'CloudBees CD Logstash Service' (Windows) services

    • Linux: Run

      sudo /etc/init.d/commanderElasticsearch stop
sudo /etc/init.d/commanderLogstash stop

    • Windows: Use Services window to stop services

  2. Back-up the data directory

    • Linux: Run

      mv /path/to/datadirectory/ /otherpath/to/datadirectory-old/

    • Windows: Use file explorer to relocate datadirectory folder (Located in C:\ProgramData\Electric Cloud\ElectricCommander by default)

  3. Uninstall DevOps Insight (For re-install)

Restore data

  1. Re-install DevOps Insight and use the same data directory path (For re-install)

  2. Stop the 'commanderElasticsearch' and 'commanderLogstash' (Linux) or 'CloudBees CD Elasticsearch Service' and 'CloudBees CD Logstash Service' (Windows) services

  3. Replace the existing data directory with the backup

    • Linux: Run

      mv /path/to/datadirectory/ /path/to/datadirectory-old2/
mv /otherpath/to/datadirectory-old/ /path/to/datadirectory/

    • Windows: Use file explorer to restore datadirectory folder

  4. Start the 'commanderElasticsearch' and 'commanderLogstash' (Linux) or 'CloudBees CD Elasticsearch Service' and 'CloudBees CD Logstash Service' (Windows) services

    • Linux: Run

      sudo /etc/init.d/commanderElasticsearch start
sudo /etc/init.d/commanderLogstash start

    • Windows: Use Services window to start services

Notes

  • the DevOps Insight Server is not recommended to be running on the same host as your CloudBees CD server.

  • Make sure to check that you have enough disk space available before backing up your data directory.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.