Not long ago I posted about using the Reliability and Performance Monitor tool to figure out where all that disk-bashing was coming from in Vista. After some feedback from people "in the wild" and some work on my own, I've found the two biggest sources of unexpected disk activity are:
- The defrag application running in the background, and
- Volume Shadow Services.
The latter is the one most people are not immediately aware of. I've noticed that VSS kicks in on a notebook when you bring it up out of hibernation or sleep mode, and it's been off for a long enough period of time that a new shadow copy repository is about due to be created. When this happens, you see a lot of disk activity that doesn't seem to be related to anything -- and, as I've found, if you start doing regular work with the computer, it doesn't seem to affect performance very much, since VSS runs at a lower I/O priority than most other things. (The same goes for defrag.)
Here's how I figured it out: the next time I fired up my notebook and saw the disk bashing, I used the R&PM to single out disk activity and sort it by writes, and looked at the File column. Sure enough, the file in question was one of the shadow-copy repositories (found in the hidden C:\System Volume Information directory). You could turn off System Restore to prevent this behavior, but to me, that's kind of self-defeating -- especially since System Restore and shadow copies have saved my bacon more than a few times.
As it turns out, the scheduling for how System Restore runs is now controlled in Vista by -- you guessed it -- the Task Scheduler. A default task is created for creating System Restore points, and I'm going to look into seeing if there's some way to tweak how it's triggered so that it works better with my particular habits.
