Server 2008 running out of space

benutne

[H]ard|Gawd
Joined
Apr 15, 2001
Messages
1,492
I've got a Server 2008 box running on an 18GB 15K SCSI hard drive. It is nearly out of space on the drive. I've got an identical 18GB unpartitioned drive in the machine right now. Since it is a server, reinstalling is pretty much out of the question. How can I use that extra drive space on the server? I know I can mount the drive in an NTFS folder, but that doesn't help much. I'm running out of space all over.

Ideas?
 
Forklift the data with acronis, repartition, then drop the data back on.

Thats the only way i would do it with a server, you need to partition it correctly with a solid partition application.

Make it a weekend project
 
You could move your page file to the other drive.

You could uninstall any programs that you can take off for a while and reinstall them on the second drive.

You could mount the drive in whatever folder is taking the most disk space?

Can't you choose where to store user data at?
 
I took Chris' idea and moved the 2.5GB swap file to the empty drive. Most of the storage is on the RAID array in the server so I figured not much space would be needed on the C: partition. Guess I was wrong.
 
Moving the pagefile works, did't know you had it on the OS drive
 
Yeah, the server has kind of grown from a "lets play with this to see if we like it" to a "OMG I can't live without it!" sort of thing. All sorts of stuff that I normally do to a production server didn't get done.
 
Yeah, the server has kind of grown from a "lets play with this to see if we like it" to a "OMG I can't live without it!" sort of thing. All sorts of stuff that I normally do to a production server didn't get done.

Happens to a log of people lol
 
Yeah, the server has kind of grown from a "lets play with this to see if we like it" to a "OMG I can't live without it!" sort of thing. All sorts of stuff that I normally do to a production server didn't get done.

lol I feel ya on that one dude. At my company we have some really sketchy machines doing mission-critical work. Like old G4 powermacs, and homebrew caseless pentium 4 machines.

But I'm not the IT guy, so its not my problem when they blow up haha. We do have a good backup system in place though.
 
lol I feel ya on that one dude. At my company we have some really sketchy machines doing mission-critical work. Like old G4 powermacs, and homebrew caseless pentium 4 machines.

But I'm not the IT guy, so its not my problem when they blow up haha. We do have a good backup system in place though.

Sad part is, I AM the IT guy. I set up something, sorta like "Hey, what do you guys think of this new software found? Don't get too attached to it. It isn't a permanent system. I just want to see if it is useful." Three weeks pass and I decide to take it offline one night since I haven't heard anything and within five goddamn minutes, I get two texts, three emails, and one phone call all saying the same thing; "What happened to the server!!?! I was keeping all my very, very, important mission critical data on there!!!11one. OMG! Life has ended as I know it!"

Well, I exaggerate...but you understand.
 
Sad part is, I AM the IT guy. I set up something, sorta like "Hey, what do you guys think of this new software found? Don't get too attached to it. It isn't a permanent system. I just want to see if it is useful." Three weeks pass and I decide to take it offline one night since I haven't heard anything and within five goddamn minutes, I get two texts, three emails, and one phone call all saying the same thing; "What happened to the server!!?! I was keeping all my very, very, important mission critical data on there!!!11one. OMG! Life has ended as I know it!"

Well, I exaggerate...but you understand.

My response to this is usually 5 minutes of "your data is gone and probably unrecoverable because that was a test machine", and its disks are in the process of being wiped. Let that sink in.

Wait one hour, turn the machine back on and the tell them after woking with recovery utilities for an hour that maybe you got to it just in time. That they manually need to verify any data files that are important to them before trusting them and that you will NEVER go this far to MAYBE get their data back again.

They will never store important data on a test machine again, ever.
 
My response to this is usually 5 minutes of "your data is gone and probably unrecoverable because that was a test machine", and its disks are in the process of being wiped. Let that sink in.

Wait one hour, turn the machine back on and the tell them after woking with recovery utilities for an hour that maybe you got to it just in time. That they manually need to verify any data files that are important to them before trusting them and that you will NEVER go this far to MAYBE get their data back again.

They will never store important data on a test machine again, ever.

You sir, are my new hero of the week. Bravo.
 
Check around for logs and settings where you move logs off your system drive. IIS log, SMTP logs, Exchange log, SQL log and so on. Get it all off your system drive. Logs bloat!
 
Back
Top