SolarWinds Backup Options

Hello All,

Would like to know what is the best possible way to backup the SolarWinds servers

We have Application server and SQL server, we have daily incremental and weekly full backup with 30 days retention period.

With this backup, can we restore the complete functionality of SolarWinds if the server crashes? Or Do we need to enable any specific type of backup (for eg: File level) to restore complete data?

At last, whether backup to both the servers are must, to restore the SolarWinds functionality or just SQL is good? Please provide some insights!

Find more posts tagged with

Accepted answers

All comments

michael.kent

I would recommend backing up both servers. On the SQL server you can just do SQL backups. That will get you by. However, whole server restoration is easier if you've backed up everything.

On the application server, you need to backup the solarwinds program files (default C:\program files (x86)\solarwinds\ ) and the web directory (defaults to C:\inetpub\solarwinds). But as before bare metal restoration is easier if you do a complete server backup.

cabeza

Thank you for recommendation and answer. In our environment servers are in built VMware, so I am afraid bare metal recovery is not an option. But as you suggest I would go with specific backups on SQL and application.

michael.kent

If you are using VMware have you considered using snapshot backups? It's far easier than digging into the filesystems.

cabeza

Thank you

Yes, that's a good option. Will set the snapshot backup and backup the snapshots in remote place to restore in case of server crash. Will check the possibility of this in our environment

conguir

the best way to take backups for your installation will depend on the modules and versions installed. If you are just running the latest version of NPM, the vast majority of configurations are stored on the database, hence backing up the SolarWinds database is key.

However there are some minor things such as report definitions from report writer, Orion logs, or even web resource customizations (don't confuse with web layout configuration) will be stored in the application server itself. It means that if you don't have/need any of those, you wouldn't need to backupn the application server, if it crashes just spin up a new vm with the same modules and versions pointing to the same database. If you are interested on those element, as mentioned before, use snapshots, or take a copy of the C:\Inetpub\SolarWinds, C:\Programdata\SolarWinds\logs and C:\Program files (x86)\SolarWinds\Orion\Reports folder. Please bear in mind the root to these paths may be different in your installation.

Raul Gonzalez

Prosperon - UK SolarWinds Partners

Installation | Consultancy | Training | Licenses