sbsmonitoring.mdf
Our 2008 sbs has some high disk read activity (see images) that seems to be caused by the sbsmonitoring.mdf database.
Any tips that can reduce it or help me find the cause? These images were taken at 7:15 am with almost no one else on the system and maybe one person working remotely. When everyone is here, the average is closer to .045.
Any tips that can reduce it or help me find the cause? These images were taken at 7:15 am with almost no one else on the system and maybe one person working remotely. When everyone is here, the average is closer to .045.
ASKER
Thanks, antivirus was something I checked when this first started happening and it wasn't scanning it. I've never seen that processexplorer before, cool little program. I'll have to wait for it to go nuts again, it seems to go in streaks where it's fine for a couple hours, then high read counts for a few hours. It's in a down time right now.
How much disk space do you have free on the drive that the monitoring database is on? Could be that if it's heavily fragmented and disk space is low, then read activities may generate much more disk activity than necessary.
ASKER
That was a problem before, but I recently upgraded the drives to WD raptors in a raid 0+1 config followed by a bare metal restore. That cleared up most of our problems, but we still occasionally get exchange disconnects whenever the read activity gets above the mid 40's. The C drive now has over 200 GB's of free space.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I can't seem to find the monitoring wizard, does it still exist in 2008?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I haven't seen average sec/read go over .010, even under full load, since running the sql fix.
ASKER
Shack-Daddy pointed me in the right direction and I'm pretty sure his solution would have worked if I had been able to find the monitoring wizard in 2008 sbs. If the monitoring wizard doesn't exist in 2008, there must be a new way to do what he suggested.
I'm picking my solution as well since it fixed the problem, but I wouldn't have found it if I hadn't been trying to follow shack-Daddy's suggestion.
I'm picking my solution as well since it fixed the problem, but I wouldn't have found it if I hadn't been trying to follow shack-Daddy's suggestion.
I would use ProcessExplorer and see exactly which other files the process that's touching sbsmonitoring.mdf is touching so that you can exclude all the potentially involved files. Initially though, you could just exclude that file in your real-time AV settings.