Re: advice on upgrading production FreeBSD 5.4
[EMAIL PROTECTED] wrote: I inherited a production FreeBSD 5.4 used as a web/mail server (Apache, PostgreSQL, php, qmail, vpopmail, Courier). Could anybody help me with information about a web resource on upgrading such system (all, OS only or component by component) with minimum downtime. I looked into cvsup and portupgrade - is this the right way for production systems or is there another one? For example is it possible to have the older version running until the new one downloads/compiles and then to replace it within seconds? Also - what if the new version does not work correctly - is it possible to keep the old and revert to it. regarding rolling-back to an older version, check out the --backup-packages option of portupgrade. It will create a package of the already installed version so that you can reinstall it without recompiling. Thank you, Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on upgrading production FreeBSD 5.4
On 2/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I inherited a production FreeBSD 5.4 used as a web/mail server (Apache, PostgreSQL, php, qmail, vpopmail, Courier). Could anybody help me with information about a web resource on upgrading such system (all, OS only or component by component) with minimum downtime. I looked into cvsup and portupgrade - is this the right way for production systems or is there another one? For example is it possible to have the older version running until the new one downloads/compiles and then to replace it within seconds? Also - what if the new version does not work correctly - is it possible to keep the old and revert to it. Thank you, Iv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] First, you'd better upgrade to 6.1. Read /usr/src/UPDATING and handbook for that. Then use portupgrade to upgrade critical services one by one. Most of the time it happens just as you describe it. Sometimes a service is stopped automatically when new binaries are installed, so you have to /usr/local/etc/rc.d/ /whatever start when you upgrade things like mysql. Then use portupgrade -ak to upgrade the rest of your software and ensure they look good afterwards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on upgrading production FreeBSD 5.4
On 2/26/06, Andrew Pantyukhin [EMAIL PROTECTED] wrote: On 2/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I inherited a production FreeBSD 5.4 used as a web/mail server (Apache, PostgreSQL, php, qmail, vpopmail, Courier). Could anybody help me with information about a web resource on upgrading such system (all, OS only or component by component) with minimum downtime. I looked into cvsup and portupgrade - is this the right way for production systems or is there another one? For example is it possible to have the older version running until the new one downloads/compiles and then to replace it within seconds? Also - what if the new version does not work correctly - is it possible to keep the old and revert to it. First, you'd better upgrade to 6.1. Read /usr/src/UPDATING and handbook for that. I'm not sure if I had a working machine that was up on its security patches that I would upgrade, where admittedly 5.4 to 6.x is not a huge jump (compared to 4 - 5 or even 3 - 4). Assuming all goes well your down- time should be the time it takes the server to reboot, but if (very big) your buildworld has some hidden fault (personal experience when /bin/sh would dump core on every invocation, very difficult to fix) you could be looking at a couple of days of downtime. Whereas I believe that the 6.x series is much better than 5.x, I'm not convinced that the risk/reward payoff is that great, doubly so given that it's a production machine. 5.4, while obsolete from a numerical standpoint, will be useable for a long while: years, probably. If the hardware itself is nothing special, or replaceable for less than the cost of downtime, you might look into putting up a second server running the new software, test carefully for a week or so, and then gracefully transition. All of this is speculation. As a postscript: the tales of 5.x to 6.x upgrades have been for the most part very painless, but in production systems conservatism leads to happy customers. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
