Re: "Patch bloat"?
- From: Madman <Madman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 4 Apr 2007 09:18:07 -0700
Thanks again. Time to bite the bullet.
"Shenan Stanley" wrote:
Madman wrote:.
I am curious how others are dealing with the inevitable shrinking
of system partition disk space due to patching, what I like to
fondly call "patch bloat". I am periodically deleting the
uninstall package for each patch once I determine I won't need to
uninstall it, but am still losing the battle. I thought I
read/heard that when a patch is installed it moves the old files
somewhere (besides the uninstall folder) and creates a second
copy of the new file somewhere else (besides the system folder),
but I don't know where those locations are or if it would be safe
to delete those "extra" copies...if this is even the case.
Anyone have any ideas? Thanks in advance.
Shenan Stanley wrote:
Your 'system partition' should be large enough to take this in
account.
If it is not - expand it or consider that bad planning.
I like 20-40GB myself.
As far as there being copies of old files/etc in different places
- the only *safe* place to delete the files is the majority of the
$uninstall directories... After that, you are taking a risk and
if you are worried about "... sooner or later it will be broke
..." because of what you are calling "Patch Bloat" - you should be
twice as worried about what damage you might cause yourself with
careless cleanup.
Make larger system partitions.
Madman wrote:
Well, thanks to all for replying. When "inheriting" production
servers with 4GB C: partitions on RAID 5 configurations and a tight
budget - "buying a bigger hard drive" is not a very good answer to
hear but apparently it seems to be the "workaround" of choice.
It isn't a 'workaround' - it is the only logical solution.
Anything else you do - any space you free up - is a pure stop-gap measure
and just sets you up for a larger failure further down the line.
I understand budgetary constraints - etc... However - there are some places
where you have to let go of the budget now or face more loss possibly later.
What if you decide to hold off on a critical patch because you have no space
and can no longer squeeze the necessary space out (easily accomplished with
a 4GB partition for Windows 2003 and needing to apply SP2...) and then -
because you are unpatched - something catastrophic happens and *poof* -
server is down? Can you afford to be down hours? Days? Is your backup
schedule so good that there will be NO loss of data?
You can only stick so much gum over the hole in the dam and it's still gonna
burst.
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
- References:
- Re: "Patch bloat"?
- From: Shenan Stanley
- Re: "Patch bloat"?
- From: Shenan Stanley
- Re: "Patch bloat"?
- Prev by Date: Re: "Patch bloat"?
- Next by Date: Re: 2) Trojan-Horse PUSHU Cannot be deleted using anti-virus software
- Previous by thread: Re: "Patch bloat"?
- Next by thread: Re: "Patch bloat"?
- Index(es):
Relevant Pages
|
