Andreas,

THERE ARE some problems one has to expect restoring a mksysb:

(1) if you are loosing your non-rootvg information an importvg should do
the job. importvg keeps the LV names (since those are stored on the disks)
as long as there are no conflicts with already existing LVs during import.
Also /etc/filesystems gets updated. Just do a "mount all" after importvg
and everything should be ok.

(2) network settings: in most cases those are preserved. Do you - by chance
have two(2) NICs in your box? Since restoring an mksysb means installing
AIX from scratch adapters may be identified in "wrong" sequence, i.e. tok0
may become tok1 etc. which then may lead into the situation you described

(3) it is a very good idea to keep some configuration information besides
your normal backups. We use shellscripts for collecting almost every
information about AIX and store it - depending on customer requirements -
as ASCII files, in Databases or as printouts. A very simple way is to use
the snap command. Or have a look at the restvg/savevg scripts.

Mit freundlichem Gruss/Best Regards

Michael Abel
IBM Certified Advanced Technical Expert
==================================
res nova Unternehmensberatung GmbH
                   ...aktiv in AIX
MAIL:  Ruppmannstrasse 41
       D-70565 Stuttgart, Germany
FON:   +49 711 78888 0
FAX:   +49 711 78888 99
WWW:   http://www.resnova.de
EMAIL: Michael.Abel AT resnova DOT de




Andreas Landhaeusser <Andreas.Landhaeusser AT DLR DOT DE> on 19.08.98 13:58:43

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Michael Abel/resnova)
Subject:  Restore OS disk on a sys w/ HSM V2 (was Re: replace OS disk)




On Wed, 19 Aug 1998, Heiko Weber wrote:

> It will work. I've done it on a J30/AIX 4.1.4 two years ago.

I'm running AIX 4.1.4 with ADSM HSM

I had to replace a defective hdisk0 some weeks ago. I'm not sure if I did
something wrong.
I had a current mksysb -i /dev/rmt0

I booted from the mksysb, and the system came up properly, but as it
seems, the restored system only had the rootvg information in the ODM.
I had to manually importvg every of the 57 filesystems, taking care that
every filesystem sits on the correct original /dev/lv??.

Also the system lost some configuration data, like default route and
default network interface.

Did I miss something, when making the mksysb ?

I suspected this behaviour, so I'm also writing some data onto the rootvg
to the backuped tape, like lsfs, lslv -l LogicalVolume, to make sure to be
able to import the volumegroups.

I do NOT know, if this happens to every AIX 4.1.4, but this happened to
me, and it was a really hard day ... :-((

Anyone has an idea, how to improve this procedure?

Thank you

        Andreas

>
> Anyway: As long as you do not erase your current 4.5 GB hdisk0
> you should be able to boot yout old (current) system if something
> goes wrong.

Nice idea :-)

        Andreas

--
Andreas R. Landhaeusser
Andreas R. Landhaeusser
Deutsches Zentrum fuer Luft- und Raumfahrt e.V. (DLR)
Bunsenstr. 10, D-37073 Goettingen, Germany, phone: +49 551 709 2379