Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Archive > 2017December28 - Deletes > Back up critical data for the Orion Platform

Back up critical data for the Orion Platform

Table of contents
Created by Michael Perez, last modified by Gerald.Prado on Dec 28, 2017

Views: 1,012 Votes: 0 Revisions: 9


There is always potential for critical failure that would result in losing one of your Orion servers, the SQL server holding the Orion database, or both.  This article describes how to create a backup of your data to minimize both downtime and data loss in such an event.  


  • SolarWinds Server & Application Monitor (SAM)
  • Orion Enterprise Operations Console (EOC)
  • Orion IP Address Manager (IPAM)
  • VoIP and Network Quality Manager (VNQM)
  • Integrated Virtual Infrastructure Monitor (IVIM)
  • Orion NetFlow Traffic Analyzer (NTA)
  • Orion Network Configuration Manager (NCM) Integration
  • SolarWinds Storage Resource Monitor
  • SolarWinds Web Performance Monitor (WPM) - formerly SEUM
  • SolarWinds User Device Tracker (UDT)


Note:  As a best practice, the related backup files should not be stored on the same servers as the applications you are backing up.  As an extra layer of protection in the event of a disaster, a different physical location is advised.  For example, should a disaster compromise your entire datacenter any backups stored at a remote location could still be recovered.  

  1. ​​Take a full backup of all related databases. The following applications may hold a unique database outside of the primary Orion database:
    • EOC has a dedicated database which is not stored in the Orion database.  
    • NTA 4.x and newer use the Flow Storage database (Please see:  
    • NCM 7.2.x and earlier have a separate ConfigMgmt database, later versions merged that information into the Orion database.  
  2. Create a backup the reports folder on the primary Orion server. The default location of the reports folder in the drive Orion is installed on is:
  3. 34-bit: Program Files\Solarwinds\Orion
  4. 64-bit: Program Files x86\Solarwinds\Orion
  5. Keep a record of what products and what version of each product is currently in use.  This can be found at the bottom of the page in the Orion web console.  For example: Orion Platform 2015.1.2, WPM 2.2.0, NPM 11.5.2, QoE 2.0, NTA 4.1.0, IVIM 2.1.0, SAM 6.2.0

As long as items noted above are available, it is possible to get Orion back in production with minimum data loss.  



Last modified