What would you recommend for server running out of hard drive space?

The chances of Raid 5 failing are high enough to consider having a backup plan, in case it fails.

The better Raid Controllers do better with rebuilding yes, and that is what most people should be using, but it is not a sure thing. If I were at a clients site where a Raid 5 rebuild was taking place, I would be stressing out. The stress that is put on the disks could easily kill a second drive. Which means no more data. (More of the point, Raid =/= backup)

The Spiceworks guys are experienced IT Professionals who work in Enterprise Environments. They aren't pizza techs.
 
The chances of Raid 5 failing are high enough to consider having a backup plan, in case it fails..

The fact that I would install and/or support ANY server at a client...a backup plan would be more than considered...it would be mandatory...or else they can go find some 45 dollar an hour pepperoni pizza tech.
 
By backup plan, I mean plans to do a bare metal restore if the rebuild fails. Not, plans to backup, that should be mandatory. If I saw a Raid 5 with a failed drive, I would check my backups and make sure that I could do a bare metal restore before I attempted to rebuild.
 
By backup plan, I mean plans to do a bare metal restore if the rebuild fails. Not, plans to backup, that should be mandatory. If I saw a Raid 5 with a failed drive, I would check my backups and make sure that I could do a bare metal restore before I attempted to rebuild.

I've had a RAID 1 rebuild kill both drives, the new and the original drive. It was the controlled, on a no warning goodbye mission from hell.

You should always be prepared for the worse, always. But I'm not gonna stress out over it, and neither should you. When I do RAID 5 rebuilds, or any rebuild, I try to schedule it at down times, like when everyone goes home for the night, and there is little stress on the server. It's not that hard to do either. Oh disk 1 has failed, let me go get another, and pop it in at the end of day. If it's a RAID 0, I throw up my hands and say "told ya so", and hope there is a backup in place.
 
I've had a RAID 1 rebuild kill both drives, the new and the original drive. It was the controlled, on a no warning goodbye mission from hell.

I bet you have good backups now, if you didn't before that disaster.

You should always be prepared for the worse, always. But I'm not gonna stress out over it, and neither should you. When I do RAID 5 rebuilds, or any rebuild, I try to schedule it at down times, like when everyone goes home for the night, and there is little stress on the server. It's not that hard to do either. Oh disk 1 has failed, let me go get another, and pop it in at the end of day. If it's a RAID 0, I throw up my hands and say "told ya so", and hope there is a backup in place.

I agree, these type of workloads should be during non-production hours. But, a lot of clients don't want to pay the techs Time and a half or Overtime and would rather come during production hours because our rates are lower.

I'm just saying there are some cheap clients out there, where you have to push them hard to say that you need a backup. It's important for all parties to know the risks of running Raid 5 without a backup (or, just the lack of a backup). Because the Pizza techs before us came in and might've said backup is built into Raid 5!

Bottom Line, Raid 1 and Raid 10 rebuilds are a lot faster, safer, and more reliable than Raid 5, and your scenario frederick is not typical at all.
 
Actually there was a backup in place at that time. It was no skin off our knees because the backup was already in operation. So having both drives dump like that meant nothing to me other than ordering some more parts.

Many of my customers are willing to pay the after-hour fees if it means come tomorrow morning all is well again and they are ready to go full blast. It's about gaining the confidence of our customers. There are many times that they call complaining we did or did not do something, completely upset over something that is neither our faults or theirs. After explaining the situation, they are calm, and receptive to it. It all comes down to talking to them like equals and with respect. Never down or like they are ignorant. Lord knows when my accountant speaks, I pull a Homer Simpson cause I have no clue what he is saying (nor do I fully care) because his job his to tell me what I need to do, not about how tax law XYZ is written and how it should relate to me in tax law speech. Give it to me straight. I have to pay the tax man for gross earnings, GOT IT!!! I understand that.

Customers who come to me after having a "pizza tech", or even a big time competitor of mine, are coming to me because I've demonstrated integrity, honesty, respect and a no-BS mentality towards my clients. That's right...no BS. I've told clients many of a times "I'm not going to fix it, I'm going to replace it. It's cheaper, it's easier, and it will be quicker", or "I'm not going to do that for ethical/morale/legal reasons". They like the fact that I tell them whats up. So when they come to me, and say "well X said we don't need a backup caues we have RAID (enter number here)", I tell them "You fired X and hired me. Which means something happened where you can't trust them. I'm telling you that you need a BDR in place". They listen, and they get on board. This is all about separating the average customer from the "lets do this right and give us an honest image" customer. I have a client whose in the CPA line of work that advertises the fact they have a strong firewall, a RAID in place, and tough security, encryption, BDR, etc...and I put it all in place. He's gotten a lot more bigger clients because of that.

what I'm saying here is that you need to take control of your customers, and get them to see the right path and what needs to be done and be done correctly.
 
Hard drive filling up? Could be VSS

I have had an experience where my OS drive seemed to be filling at an alarming rate. I tried everything like WinDir and other programs trying to find where the space was going.
Eventually I found it was VSS copies that weren't being released; most recently on a 2011 SBS.
Go the the drive icon, right click and choose shadow copies. There you may find a lot of disk space you can free up by deleting old, unreleased shadow copies.
 
Back
Top