vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi gurus, Can I use Jumpstart method to upgrade the OS on a prod machine which is currently running Solaris 2.6 ?? My Jumpstart server is currently loaded with Solaris 8 image. If yes, how do I do it ?? Appreciate your advice. Thanks. Regards, Francis. |
| |||
| On Wed, 17 Sep 2003, Francis wrote: > Hi gurus, > Can I use Jumpstart method to upgrade the OS on a prod machine which > is currently running Solaris 2.6 ?? Yes, assuming you have a Jumpstart server. > My Jumpstart server is currently loaded with Solaris 8 image. > > If yes, how do I do it ?? It's all explained in the Installation docs... I would recommend practising on a machine that isn't your production server first, though! -- Rich Teer, SCNA, SCSA President, Rite Online Inc. Voice: +1 (250) 979-1638 URL: http://www.rite-online.net |
| |||
| In comp.unix.solaris Francis <ong_francis@yahoo.com> wrote: > Hi gurus, > Can I use Jumpstart method to upgrade the OS on a prod machine which > is currently running Solaris 2.6 ?? > My Jumpstart server is currently loaded with Solaris 8 image. > If yes, how do I do it ?? > Appreciate your advice. Thanks. Is there a reason you need to use jumpstart? Setting up and testing out jumpstart takes some time. It pays off when you need to maintain several machines and if need an ability to reinstall them or add new machines quickly when necessary. If you have just one or a few boxes, performing a normal upgrade is probably going to be a lot easier. -- Akop Pogosian This space has been accidentally left blank. |
| |||
| Akop Pogosian wrote: > Francis wrote: > > > Can I use Jumpstart method to upgrade the OS on a prod machine which > > is currently running Solaris 2.6 ?? Certainly. You can even upgrade to Solaris 8 in the process. You want to being running Solaris 8, right? > > My Jumpstart server is currently loaded with Solaris 8 image. Or do you mean you need to be able to install both versions on your jumpstart server? Use a separate tree for the different versions and go through the same sort of set-up process to be able to have both versions. The clients use bootparams, so bootparams will point into the different versions. > Is there a reason you need to use jumpstart? The key word is production. In production repeatabilty, design and disaster recovery are key. If you can reduce a server to jumpstart installability you have acheived all 3 at the push of a button. > Setting up and testing out jumpstart takes some time. He already has one. It's a question of upgrading the server in question vs being able to jumpstart either version. > If you have just one or a few boxes, > performing a normal upgrade is probably going to be a lot easier. In production repeatability, design and DR all beat easy. Your statement is true, but it applies to non-production systems. |
| |||
| * Doug Freyburger wrote: > The key word is production. In production repeatabilty, design and > disaster recovery are key. If you can reduce a server to jumpstart > installability you have acheived all 3 at the push of a button. The key word is actually `upgrade', I think. It tends to be hard (and generally futile) to do repeatable upgrades. In order to reinstall the server this way you would presumably have to jumpstart solaris 2.6, customise it (probably in the jumpstart), *then* do a jumpstart upgrade to 8. Yuck! Much better, I think, to get things set up so you can take a cold machine and jumpstart it to 8 in one go including any customisations. That's what we always try and do anyway - sometimes we do upgrades on machines that are clones of production ones but usually only to find out what customisations we've missed. I agree completely about using JS as a way of getting repeatability &c even for only a small number of machines, I just question the desire to do an upgrade rather than an initial install. --tim |
| |||
| Tim Bradshaw <tfb@cley.com> writes: [...] > 2.6, customise it (probably in the jumpstart), *then* do a > jumpstart upgrade to 8. Yuck! Much better, I think, to get things > set up so you can take a cold machine and jumpstart it to 8 in one > go including any customisations. That's what we always try and do [...] Is there a way to combine Live Upgrade and JumpStart? That way if something goes 'kapoch', you can go back to the old version. (Of course, you'll test to make sure everything works just fine...) -- David Magda <dmagda at ee.ryerson.ca>, http://www.magda.ca/ Because the innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may do well under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI |
| |||
| * David Magda wrote: > Is there a way to combine Live Upgrade and JumpStart? There probably is. Actually what I want (which there probably is a way to do) is a `live initial install' program. > That way if something goes 'kapoch', you can go back to the old > version. (Of course, you'll test to make sure everything works just > fine...) You could do this by having a begin script which copied the old system partitions onto the disk-to-be-installed-on, editing some suitable stuff, I guess, then getting jumpstart to ignore the old disk. I guess the `editing some suitable things' bit is hard though, and what live upgrade does (well, tries to do). --tim |
| ||||
| Tim Bradshaw <tfb@cley.com> wrote in message news:<ey3u179cgyr.fsf@cley.com>... > * David Magda wrote: > > > Is there a way to combine Live Upgrade and JumpStart? > > There probably is. Actually what I want (which there probably is a > way to do) is a `live initial install' program. > > > That way if something goes 'kapoch', you can go back to the old > > version. (Of course, you'll test to make sure everything works just > > fine...) > > You could do this by having a begin script which copied the old system > partitions onto the disk-to-be-installed-on, editing some suitable > stuff, I guess, then getting jumpstart to ignore the old disk. I guess > the `editing some suitable things' bit is hard though, and what live > upgrade does (well, tries to do). > > --tim Live upgrade will work with Flash Archives, I do not know if it will work with jumpstart off the top of my head. If you have a machine running the same OS, you should be able to flash archive it, seperate out the configurations you don't want, and then use it on the upgrade. It's not really what you're asking for, but it IS another opption if you want to use Live Upgrade, and it turns out jumpstart won't work. |
| Thread Tools | |
| Display Modes | |
|
|