RE: Live System Upgrade : Call for suggestions

that, I am assuming you keep your OS on a separate disk array than your data. I do. HTH, Steven -Original Message- From: Ashley M. Kirchner [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Live System Upgrade : Call for suggestions

Re: Live System Upgrade : Call for suggestions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27-Jun-2002/13:55 -0700, Keith Morse <[EMAIL PROTECTED]> wrote: >files to be concerned with that I can think of: > >/etc/hosts >/etc/exports >/etc/sendmail.cf or /etc/postfix/* I would add /etc/mail/* Tony - -- Anthony E. Greene

Re: Live System Upgrade : Call for suggestions

On Thu, 27 Jun 2002, Ashley M. Kirchner wrote: > Keith Morse wrote: > > > Save your self some down time here and generate an up to date errata image > > that contains the updates, and hence will be a part of the upgrade. > > I'll look into this. Thank you for the suggestion. > > > > This

Re: Live System Upgrade : Call for suggestions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27-Jun-2002/09:46 -0600, "Ashley M. Kirchner" <[EMAIL PROTECTED]> wrote: > >I need to upgrade a live system, and I wonder how people tackle this >problem. The system hosts users and their websites, email and several >other services. I need to per

Re: Live System Upgrade : Call for suggestions

On Thu, Jun 27, 2002 at 10:12:13AM -0600, Ashley M. Kirchner wrote: > Trevor wrote: > > > If it's that critical, build a separate server (new hardware). That way if > > everyone starts complaining, you still have a back up server. Hardware is > > dirt cheap. > > We don't have that kind of

Re: Live System Upgrade : Call for suggestions

Keith Morse wrote: > Save your self some down time here and generate an up to date errata image > that contains the updates, and hence will be a part of the upgrade. I'll look into this. Thank you for the suggestion. > This is not correct. I believe if the new sshd finds existing system

Re: Live System Upgrade : Call for suggestions

Point by Point then. On Thu, 27 Jun 2002, Ashley M. Kirchner wrote: > > I need to upgrade a live system, and I wonder how people tackle this > problem. The system hosts users and their websites, email and several other > services. I need to perform a full OS upgrade (mainly because I'm mo

Re: Live System Upgrade : Call for suggestions

"Lesniak, Steven" wrote: > Another thought, how about buying another "root" disk and loading fresh on > that? Take the current "root" out of the box and load onto a new one. This might actually be a better solution. Extra disks aren't a problem. > Having said that, I am assuming you keep

Re: Live System Upgrade : Call for suggestions

Trevor wrote: > If it's that critical, build a separate server (new hardware). That way if > everyone starts complaining, you still have a back up server. Hardware is > dirt cheap. We don't have that kind of spending money just for an upgrade, specially since after the upgrade, the extra m

RE: Live System Upgrade : Call for suggestions

If it's that critical, build a separate server (new hardware). That way if everyone starts complaining, you still have a back up server. Hardware is dirt cheap. >How do you folks deal with having to take the system down to perform an OS >upgrade, without much of a downtime to your users? Overn

Live System Upgrade : Call for suggestions

I need to upgrade a live system, and I wonder how people tackle this problem. The system hosts users and their websites, email and several other services. I need to perform a full OS upgrade (mainly because I'm more comfortable doing that, than the usual Upgrade path), so naturally the syst