System Drive slowly filling up

Sorry, was a bit confused in my earlier reply.  The Exchange transaction logs are not, of course, edb files... they are files ending in .log and looking like E0000B1A.log, for example.  They are normally found in the mdbdata folder (the original one) unless they have been moved (but as I said, moving the databases doesn't move the log location).

Thanks for the prompt responses,

The .log files are minimal, and the exchange stores are not on that drive

Spacemonger shows:

My docs 1.2GB
prog files 2.28GB
windows 6.37GB (but with a size on disk of 4.63GB)
unscanned 3.1GB

To give you an idea of the speed of filling up, last months report showed 1.26GB free and now 0.98

Regards

Then the culprit is the Windows folder.
Do you have lots of $NtUninstallKB941644$ type folders?  They will be compressed, but one is created everytime an update is applied.  These folders can be deleted to recover the disk space.

Does Spacemonger give further breakdown of where the space is being taken up in the Windows folder?

Actually, I would be interested as to what the unscanned 3.1Gb is too...  What wasn't scanned?

As far as I can tell all folders were scanned, could this be sys vol info, shadow copy is not enabled on this drive and the swap files are mainly on another drive (except for 0.5GB) or perhaps its related to the size on disk difference in windows?

The size on disk difference is due to the compressed updates I'd have thought - if the size on disk is significantly less than actual size, then there is definitely compression at work!

The Sys Vol could explain the unscanned... though I am surprised at 3Gb being unscanned and would try to find out where that 3Gb was.  It seems rather a large segment to be unaccounted for.

Thanks for the tip about the $NtUninstallKB941644$ type files, i will delete them.

However because automatic updates is not turned on they do not explain the disappearing space (in fact one of the reasons I want to solve this is to turn updates on again and want enough 'elbow room' to cope with 1.5 years of windows updates!)

Re the sys vol/unscanned space, I could measure it over a period of months and see if it is the culprit (i.e. slowly expanding) - but it would be nice to sort more quickly.

regards

According to the space monger site, this unscannable area is the sys vol.

I looked at another SBS server, much newer (4 months) and not as complex (fewer users, less configuration etc) and it too had an unscannable area but this time 0.7GB.

Regards

How much overall space do you have for the SBS server (i.e. each partition)?

Hi,

C: 12GB 1.38 free
D: 136GB 44.4 free (exchange and users folders)
E: 409GB 255 free (shared data)
F: 124GB 106 free (exchange logs and bits and bobs)

Regards

Is the C: mount its own drive or partitioned?

The reason I am asking it you might want to look at upgrading the hard drive and giving the C: drive something more like 30GB or more, especially for patches and any application needs.

Also is RAID running on this server as well?

It is partitioned and the configuration is, in total, 8 drives, a mixture of RAID 1 and 5, and these occupy all the available drive bays.

Hi,

I have been monitoring the disk usage since the last post- it is now down to 920MB free, both the 'unscanned' i.e. sysvol information and the windows directory are growing. I can't belive that this is the only SBS box that has this issue - any one got any thoughts?

Regards