Re: mksysb restore in AIX 5.2 ML4 problem
From: IanT (ian_at_itcontracts.biz)
Date: 04/06/05
- Next message: Florian Heigl: "Re: AIX on RAID"
- Previous message: Michael Kraemer: "Re: very large program support"
- In reply to: Dohhhh: "Re: mksysb restore in AIX 5.2 ML4 problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 6 Apr 2005 05:50:37 -0700
Dohhhh <whynot@verizon.net> wrote in message news:<Fkz3e.8271$db.4219@trndny07>...
> Patrice Quet wrote:
> > ian@itcontracts.biz (IanT) wrote in message news:<f98b5211.0503310206.290d2b75@posting.google.com>...
> >
> >>All
> >>As part of commissioning a p5 550 system, we are required to do a
> >>backup/restore on the system to prove that we can recover the system
> >>in the unlikely event...
> >>Yesterday I created the mksysb tape ( 3 actually, safety in numbers )
> >>and a helpful message informed me that the boot image was too large
> >>and told me to read the /usr/lpp/bos.sysmgt/README which pointed out
> >>that we may not be able to restore directly from the tape.
> >>All well and good, boot from the original build cd and access the tape
> >>restore facility from there, option 3 'Access Advanced Maintenance
> >>Functions', option 4 'Install from a System Backup'. The tape restored
> >>and then the system loaded some stuff from cd1 and cd2 before
> >>completing the restore process.
> >>Having restored in this fashion, I tried in vain to access the system
> >>across the network. It appears that the bos.net package had been
> >>corrupted, which left me without any of that good stuff that allows a
> >>system to speak to other systems, tcp/ip and all of that wasn't
> >>available. All of the network functionality was present prior to the
> >>restore and nothing was changed between the time of the backup and the
> >>time of the restore.
> >>Tried to install bos.net via smit install from the cd, but it failed;
> >>couldn't find /usr/lpp/save.config/usr/sbin/nsupdate. This is a link
> >>to /usr/sbin/nsupdate4, which was missing. Having no alternative and
> >>throwing all caution to the wind, I touched the file and tried again.
> >>Hey, presto, bos.net installed with no problems; the system was back
> >>on the network and I heaved one large sigh of relief.
> >>My reasons for posting are these: -
> >>Has anyone else experienced this behaviour previously?
> >>Did I do something wrong?
> >>It could also be a note of caution!
> >>
> >>Your advice and thoughts are, as always, welcome.
> >>
> >>Thanks - Ian
> >
> >
> > Hello,
> > If you are in AIX 5.2 ML4 level, you should have the appropriate apar
> > (I can't remember its IY number !!!)installed into your image that
> > should enable you to perform the following procedure and make it work
> > :
> > 1) Specify your tape as the first boot device.
> > 2) Reboot your server.
> > 3) When earing 2 beeps, you should see firmwares messages on the
> > display (display, speaker, ....)
> > 4) Hit 8 (if you have an ASCII terminal) or PF8 (for a graphic
> > terminal) to get the firmware prompt which is a ">".
> > 5) when you have this prompt, type the followings 2 commands :
> >
> >>setenv real-base 1000000
> >>reset-all
> >
> > 6) Your system will reboot and after waiting a while (about 10
> > minutes) during E14D led code and message "starting software, please
> > wait ..." displayed on your terminal, your system will reach to boot
> > on your tape and get the classical mksysb restoration menus.
> > You finally just need to specify to restore your mksysb and it should
> > work.
> > Be carefull, you'll need to do so every time you'll have to restore a
> > mksysb with a boot image being larger than the one IBM supports for
> > instance...
> > Hope this helps.
> > Patrice Quet
> ==
> (IIRC - the readme indicates) one workaround is to remove any filesets
> you KNOW you won't be using on the system; one of the biggest culprits
> are the various device drivers (i.e., devices.nnn.nnn...). How did they
> get on the system (you may ask <G>)? During installation, I believe AIX
> 5 defaults to "enable this system image to be used on other systems" -
> designed to "facilitate" cloning the system on other hardware, don'tcha
> know - which means, EVERY KNOWN hardware driver is loaded whether the
> system has that piece of hardware or not!
>
> Glad to hear you were finally able to resolve everything...one a side
> note (kinda a "helpful tip" for the future <G>), ever consider using
> NIM? You can create mksysb images and store them on the master or
> another machine designated as a NIM "resource" server. This gets you
> around the boot image being too large AND (as I discovered yesterday)
> also enables performing rootvg maintenance in standalone mode all at
> network speed VS. waiting for the scsi devices to be read along w/all
> the tape related activity (i.e., tensioning, counting the file markers,
> etc...)...of course, the NIM master needs to get backed up (I'm in a 3
> disk mirrored/quorumed rootvg with the NIM images stored on a separate
> VG on RAID5 sets <G>) but that's another "thread" (yay sysbak)!!
>
> Just some thoughts... <G>
>
> PS
> p.s. My NIM "discovery" worked wonderfully and allowed me to get 4
> systems back on line in 1/4 the time it would have doing the same thing
> from a tape...pms
All
Thanks for the replies; I was aware of most of the aforementioned.
However, I'm still perplexed as to what happened to the bos.net and
the IP stack and all of the networky stuff, why it didn't restore,
etc. and what happened with nsupdate, this was my major concern during
this process.
We stayed with the 'vanilla as-supplied' install, which added all of
the stuff we don't need; if budgets allow, we'll remove the
unnecessary lpp's to trim down the payload.
I would like to use NIM, but the other systems on site are at a lower
level of AIX, so...
TIA - Ian
- Next message: Florian Heigl: "Re: AIX on RAID"
- Previous message: Michael Kraemer: "Re: very large program support"
- In reply to: Dohhhh: "Re: mksysb restore in AIX 5.2 ML4 problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
