Re: Best Practice
From: S. Pidgorny [MVP] (email@example.com)
From: "S. Pidgorny [MVP]" <firstname.lastname@example.org> Date: Sun, 13 Apr 2003 17:33:16 +1000
That's a reasonable way to prepare for back-out (assuming RAID1 or
RAID1+0)... However, you're losing disk fault-tolerance for some time -
thus, do that on server farms i.e. NLB Web farms, seek alternative solution
for database servers and alikes.
-- Svyatoslav Pidgorny, MS MVP, MCSE -= F1 is the key =- "Kahiel" <email@example.com> wrote in message news:eCqxolTADHA.2376@TK2MSFTNGP10.phx.gbl... > Well, Thanks for all replies. What about this scenario? > > > > Since most of our servers are mirrored RAID-. We will break the disk mirror, > run MSBA, apply all fixes "critical or non-critical" as identified by MSBA, > wait for 3 days of activities. If no problems reported, rebuild disk > mirrors. > > > > The above can be repeated as monthly or every time a critical fix is > released. > > > > > > > > "Kahiel" <firstname.lastname@example.org> wrote in message > news:OJGT5Zr$CHA.2052@TK2MSFTNGP11.phx.gbl... > > What is the best practice applying security fixes? I believe we should > apply > > any fixes identified by Baseline Analyser. Others, suggesting to do > > thorough checking for application conflicts with each fix, which is not a > > practical solution since we support many servers with many different > > applications? > > > > Any advise? Any experience of application conflicts when applying patches? > > > > Thanks > > > > > >