Like we have options to unmanage Nodes, Application & Interface, we need option to unmanage volumes.
What is the driving force for this one? I can see nodes/interfaces being out for maintenance, but why would you need to unmanage volumes ?
e.g. A volume that will always be at 99% and you don't want to waste the resources to monitor it and maintain data about it.
aLTeReGo
We have 25+ cluster servers in our environment, when we complete failover activity on every Saturday there are 40 "Disk is Offline" alerts pending in our system.
We need these cluster disks alerts during the activity to see the primary and secondary cluster nodes has the respective disks
It's recommended that you monitor the cluster VIP as a node in Orion and monitored shared disks through that VIP rather than via the individual cluster members. This would ensure the volumes are always monitored, regardless of which member of the cluster is active.
Hi,
We are using 2 nodes in a cluster, both are active nodes, both host primary DBs for different applications.
We need to monitor on individual node so that we get alert in any of the disk gets failed to another node.
I have similar situation and this option is really needed.
This is already possible:
(screenshot from 2020.2.5)
Also, the volume can be unmanaged using the API.
All of the options below are functional, however, there still needs to be a global way to manage Volumes. This has been an outstanding feature request going back to 2010 or before. No one wants to manage volumes one at a time or expand nodes to select multiple volumes to work with across various activities such as editing properties, setting thresholds, deleting, and the maintenance level like mute/unmute and unmange and remanage.
