Duplication of monitored disks associated with Nodes

Hi, if this has been covered elsewhere in the forums, apologies, I did search but couldn't find any mentions of this type of 'issue'

In short, it appears that certain monitored nodes show a duplication of monitored disks? These appear to be the 'same' disk however the label information has changed slightly, updating the monitored resources doesn't clear this, however, removing & re-adding the node does as I suspect it's writing a completely new entry to whatever table this information is stored in. I'm guessing the duplication is caused by mild corruption of the initial entry?

I really wanted to know whether there was some sort of cleanup I could run on the server itself to clear out redundant entries such as these? Without having to remove > re-add nodes each time.

I hope I've explained this clearly, if more info is needed, please let me know & thanks in advance,

Find more posts tagged with

Disk

monitor

solarwinds

duplication

Accepted answers

All comments

mharvey

Rather than removing the entire node, you should be able to go under node management, expand the node, select the volume you don't want, then select More Actions at the top and delete, which should remove the volume you no longer want to see.

Regards,

Matthew Harvey

Loop1 Systems

http://www.loop1systems.com

danielgilbey

Hi Matthew,

Thanks for responding, I don't think I clearly explained the issue... I'm aware of the method you mention, the trouble is that the monitored volumes are almost like 'ghosts' of the actual volume. So, on a particular server, let's say I'm monitoring the C:\ drive & it's labelled 123abc after a period of time, I see

C:\ volume abc123 (& xx% usage etc)

C:\volume system label abc123 (& xx% usage etc) <- this would show current stats, the above one would be static as it's a 'ghost'

I'll see if I can find an example tomorrow & post a screen shot

mharvey

I've seen that issue several times. The problem is that the mapping to the volume has changed. More than likely the VolumeIndex has changed. If that's the case, if both are in the database with different volumeindexes then you "could" try to move the historic data over to the volume showing the current values using a SQL query , but that's about the only way you could merge them together again and keep the data from both.

aLTeReGo

Since these are Windows Servers you're having these issues with, you may find switching to WMI as your polling method for these servers eliminates or reduces the frequency of phantom volumes appearing in Orion.