Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion Alert: Exchange Database-Critical Diskspace

We have an Orion Volume Alert set to trigger at 5% Freespace on a SAN Mountpoint that indicates that the Volume is Critical. We created a new SAN-Space with a new Exchange Mailbox Database.

We are scripting Mailbox Moves from the Full Volume to the New.

Sample PS1 Script Reference: New-MoveRequest -Identity 'Email.Prefix' -ArchiveOnly -ArchiveTargetDatabase 'ArcDBName' -BadItemLimit '0'

The Exchange Mailbox Database on the Full Volume however will not change in Volume Size so what is free "White Space" in the Exchange Database is irrelevant to the Volume Alert.

Is there a better Alert Trigger Condition we could use to account for this [Microsoft] so called "White Space" that I could use besides this Volume Alert?

I attached a Screenshot of the Volume Alert Triggers currently set, as a reference to my question.

Thwacks4UrN-put:-)

AlertSample.gif

Find more posts tagged with

Accepted answers

All comments

dragoon231

My question would be, what are you using to monitor storage with? Solarwind's SRM or something else? Or do you only have something like NPM/SAM you are trying to set this up for? If it is the 2nd, I don't think it is possible to set up alerts to avoid the white noise due to thin provisioning in something not really designed for a storage environment. If I'm describing your setup, here are 2 articles that may help out:

Monitoring and Alerting Repairs it Entirely!

Thin Provisioning – Good Idea, Bad Idea, or “It Depends?”

korvfenris

We are using Solarwinds Orion on on a SAN with a 10GB pipe that a Hyper-V Server Cluster has three redundant Mounts to a given Database.

If this is what you mean as a 2nd Case where there is a Monitored NPM/SAM then White Noise is just something we will have to deal with.

Thank you for your insight and valued response to my question. I will review the Article Links and see if there are any solutions or caveats' in this situation.

For now we have elected to Move the Mailboxes to other Databases then Rebuild the White-Noised Database then Move some of the Mailboxes back.

/rmc

image001.gif