ORION SOLARWIND DB VERY HIGH (more than 212Go)

Hi thwack community,

Happy new year to yall,

First of all I'm new to SOLARWIND, I found out my orion database is getting very big. Is there any way to make it smaller without disrupting production ?

The DB size is about 212Go right now. I heard about retention setting with I modify already without any positive result. I have also been advise to not shrink the DB. Your help will be very welcomed. Thanks in advance.

Frejus

Find more posts tagged with

orion

sql

Database

Accepted answers

niksam

Hi Frejus,

First, I would like to tell that I agree with the points shared by Ashley, but also you can do the below checks or changes to troubleshoot the issue

i). You can follow the below link to configure proper data retention

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-optimization-historical-data.htm

ii). You can also increase/decrease or set different polling intervals for the devices.

iii). check logs created in SolarWinds. --> If you have more logs created then you can use the log adjuster to make some tweaks to increase performance.

iv). Fine-tune SQL filesystems by taking help from the SQL DBA team.

v). In SolarWinds under Settings >> All Settings >> My Deployment >> Deployment Health.

Check for any Database related issues.

vi). You can check the Database table size so that you will get a better idea that which table is consuming more space and what monitoring data is getting stored in that table so you can take the appropriate action based on that.

vii). If you are keeping data for a longer duration of time then you can create some scheduled jobs that can archive data on a regular basis so you do not have to shrink the database size.

All comments

ashley.heilbronn

Some general guidelines I follow are the following, that keeps my db under 100gb which holds syslog, npm and nta data for 400 nodes.

monitor only priority links like trunk interface, wan interfaces, wan sub interfaces and tunnels, uplinks to access points. anything out of that scope I don't find helpful for troubleshooting and monitoring.
syslog and traps, review what messages level you are sending from your devices to syslog, things like tear down messages from a firewall I think just bloat the database, if needed from your SOC, I'd ask them to poney up their own syslog service which you can forward these messages over to, you will need to work with your network team to validate this.
NTA make sure your aren't sending duplicated data from your netflow source, you will need to work with your network team to validate this.
work with your SQL expert team to implement a sql maintenance plan, like re-index, defrag, compact etc.
review how many netpath services you have running, they can use quite bit of space.

niksam

Hi Frejus,

First, I would like to tell that I agree with the points shared by Ashley, but also you can do the below checks or changes to troubleshoot the issue

i). You can follow the below link to configure proper data retention

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-optimization-historical-data.htm

ii). You can also increase/decrease or set different polling intervals for the devices.

iii). check logs created in SolarWinds. --> If you have more logs created then you can use the log adjuster to make some tweaks to increase performance.

iv). Fine-tune SQL filesystems by taking help from the SQL DBA team.

v). In SolarWinds under Settings >> All Settings >> My Deployment >> Deployment Health.

Check for any Database related issues.

vii). If you are keeping data for a longer duration of time then you can create some scheduled jobs that can archive data on a regular basis so you do not have to shrink the database size.

mnsh_majumder

HI @Frejus_MAits quite normal for Orion main poller DB having that size as for my environment its around 190+GB. yes you can discuss with your customer & reduce the retention period, delete unwanted device/interface/volume etc. check if any unwanted syslog/traps are being sent as sometimes even NW team stays in the dark where even they are not aware what they are enabling

Make sure DB maintenance is running on daily basis as that will remove unwanted stuff from our SW DB.

Most important you should keep a check on your OLV DB as that can move to more than 600+GB even for a smaller infra as I've faced the same.