System Drive slowly filling up

Hi,

I am looking at a small business server 2003, which has a 12GB system drive, Exchange and user data are not kept on this drive. Over the months it has been slowly filling up - for example last August it had 1.85GB free, now it has 945MB, no new software has been installed and it has been running well.

I would like to find out what is causing this creeping space usage before we get to 0MB.

Regards
markflexmanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

purplepomegraniteCommented:
It could be Exchange Transaction logs.  Even if you move the Exchange databases to another location, this doesn't move the transaction logs - though there is a way to do this.
Look in the Exchange folder on the c: drive for lots of edb files - if they are there, post back and I can give details on how to move them.

Other places to look are:
c:\ClientApps (SBS stores applications here for installation to clients - this can be deleted or moved, but must be a done a certain way)
Usual temp folders.
0
Michael WorshamStaff Infrastructure ArchitectCommented:
Do you have any messages in your EventLog that possibly point to an error or warning on your primary drive?

Also, as 'purplepomegranite' stated, it could be Exchange related. You might need to do an off-line defrag of your Exchange EDB and STM files. I recommend doing a full backup before doing an off-line defrag though.

Determining database free space with Exchange 5.5 Service Pack 1 and later versions of Exchange
http://support.microsoft.com/kb/195914/en-us

How can I defragment Exchange 2000/2003 Server databases?
http://www.petri.co.il/defragment_exchange_2000_2003_server_databases.htm

Online Defragmentation Does Not Reduce Size of .edb Files
http://support.microsoft.com/?id=256352
0
purplepomegraniteCommented:
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).
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

markflexmanAuthor Commented:
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

0
purplepomegraniteCommented:
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?
0
purplepomegraniteCommented:
Actually, I would be interested as to what the unscanned 3.1Gb is too...  What wasn't scanned?
0
markflexmanAuthor Commented:
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?
0
purplepomegraniteCommented:
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.
0
markflexmanAuthor Commented:
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
0
markflexmanAuthor Commented:
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
0
Michael WorshamStaff Infrastructure ArchitectCommented:
How much overall space do you have for the SBS server (i.e. each partition)?
0
markflexmanAuthor Commented:
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
0
Michael WorshamStaff Infrastructure ArchitectCommented:
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?
0
markflexmanAuthor Commented:
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.
0
markflexmanAuthor Commented:
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
0
markflexmanAuthor Commented:
I think I found it, it's the NTbackup catalog files with the extension .V01, they are created every time a backup is sucessful and are about 20MB in size.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.