From: cbaker@GOODYEAR.COM
Date: Wed Apr 28 2004 - 12:05:38 EDT
Marcelino,
(Someone correct me if I have this order wrong..... Been a few months since last did this.)
First, run the mkszfile command. That will (re)create your "/image.data" file.
Now edit that "/image.data" file and change the PPSIZE and PP_SIZE from 8 to 16.
Also change the PP= and LP= to half so that your LV and FS stay the same size.
Now run the "smitty mksysb", but this time change the line:
Generate new /image.data file?
from "yes" to "no".
Now it will create the mksysb using the altered /image.data file. Then it will restore setting up the rootvg with PP size=16
(To be quite honest, seems to me I have not used this "back door" method since early 4.3.3 when I needed to shrink the LV's and JFS's
to fit a smaller hard drive. So, I know this will work for you, but I want to think that there is "better" ways to do this now, but
this will work too. Also, you said your 4.5 GB drive is maxxed? You can use this method to shrink JFS's with this too - Assuming the
amount of data in the JFS is less than the present size. - But, again, I believe the restore of a mksysb offers you the ability to
"shrink" filesystems to just enough to fit the data, so again there is a newer, safer way to do that too.)
Hope I have not completely confused you? Suffice to say, YOU CAN PUT YOUR 4.5 GB rootvg ONTO YOUR 9.1 GB DRIVE!
Good luck with "Plan A"
Christopher M. Baker
Senior Technical Support Analyst
DSE/TCO
Goodyear Tire and Rubber Company
=================================================
Contains Confidential and/or Proprietary Information.
May not be copied or disseminated without the expressed
written consent of The Goodyear Tire & Rubber Company.
=================================================
Marcelino Mata
<mmata@MULTIMATI To: aix-l@Princeton.EDU
C.COM> cc: (bcc: Chris Baker/NA/GDYR)
Sent by: IBM AIX Subject: Re: Correct procedure for restoring system image data
Discussion List
<aix-l@Princeton
.EDU>
04/28/04 11:13
AM
Please respond
to IBM AIX
Discussion List
Christopher,
While migrating to large rootvg disks works fine in certain environments (
It worked fine on my test computer), it did not work in the server since I
used 8 MB PP size for the disk. This limits me to 1016 PP's. I need over
1080 PP's for 9.1Gb disk. If I only used 16MB PP, this would of been so
easy/simple....oh, well.
Time for plan B....
Marcelino
>-----Original Message-----
>From: Marcelino Mata
>Sent: Tuesday, April 27, 2004 4:47 PM
>To: 'IBM AIX Discussion List'
>Subject: RE: Correct procedure for restoring system image data
>
>
>Christopher,
>
>See response below...
>
>>-----Original Message-----
>>From: cbaker@GOODYEAR.COM [mailto:cbaker@GOODYEAR.COM]
>>Sent: Tuesday, April 27, 2004 3:45 PM
>>To: aix-l@Princeton.EDU
>>Subject: Re: Correct procedure for restoring system image data
>>Importance: High
>>
>>
>>Marcelino,
>>
>>Don't know why it is doing what it is doing, but since you are
>>back to square-one, may I ask a few questions and make a few
>>observations:
>>
>>1) You can go from AIX 4.3.3 ML9 directly to AIX 5.1. No need
>>(that I am aware of) to go to ML11 in the interim.
>>
>
>I read it somewhere that AIX 5.1 upgrade can fail if AIX 4.3
>is not at the last released ML level. IBM performed testing
>at the lastest ML level so it better practice to start from that level.
>
>>2) If you can connect both the 4.5 GB and the 9.1 GB drive at
>>the same time, you then only need to mirror to the 9.1 then break the
>>mirror to have your OS drive be the 9.1 GB
>>
>
>I can do this. I did not know that this would work. I
>thought that if I did this type of thing, the 9.1Gb disk would
>be "formatted" to be 4.5GB disk. I use the work "formatted"
>since I don't know the AIX lingo for this type of thing. I
>manage AIX, Tru64, Solaris and Linux so I can't stay on top of this...
>
>>3) We have AIX 5.1 and AIX 5.2 on systems with only a single
>>4.5 GB drive. If it is only the rootvg and it is only the OS,
>>it should
>>fit.
>>
>
>I have no free PP's on the disk now and I'm told a migrated
>4.3->5.1 requires more space than fresh install of 5.1. There
>is also a couple filesystems I on the RAID volume group which
>I want to move to rootvg.
>
>
>>4) Why not use "mksysb" and then clone it back onto the system
>>after you swap drives? (Assuming you can't do #2 above.)
>>
>
>Do you recommend of mksysb site or can you provide the command
>line for using myksysb? Sysbackup is idiot proof so I was
>going to stick to that....I'm open to mksysb is I have run
>into a Sysbackup bug/limitation. (Suggestion #2 seems like a
>better idea)
>
>>5) You would be very wise to have all other VG's varied-off /
>>exported and even have the drives off or disconnected so that
>you don't
>>screw those up.
>
>This was going to be plan B...
>>
>>I am guessing that sysbackup restore is only trying to make
>>the VG definitions in the rootvg / system area and thus will not hurt
>>other VG's, but I would NOT have the other VG's live or
>>connected when I was doing this.
>>
>
>I think I will test a few things on spare 43P's before proceeding...
>
>>Hope that helped,
>>
>>Christopher M. Baker
>>Senior Technical Support Analyst
>>DSE/TCO
>>Goodyear Tire and Rubber Company
>>
>>=================================================
>>Contains Confidential and/or Proprietary Information.
>>May not be copied or disseminated without the expressed
>>written consent of The Goodyear Tire & Rubber Company.
>>=================================================
>>
>>
>>
>>
>> Marcelino Mata
>> <mmata@MULTIMATI To:
>>aix-l@Princeton.EDU
>> C.COM> cc: (bcc:
>>Chris Baker/NA/GDYR)
>> Sent by: IBM AIX Subject:
>>Correct procedure for restoring system image data
>> Discussion List
>> <aix-l@Princeton
>> .EDU>
>>
>>
>> 04/27/04 03:01
>> PM
>> Please respond
>> to IBM AIX
>> Discussion List
>>
>>
>>
>>
>>
>>
>>I am making preparation to move from AIX 4.3.3ML9 to ML11 then
>>AIX 5.1. As
>>I need to perform upgrades, I do not have enough disk space on
>>the current
>>4.5Gb O/S disks. I was planning on replacing the 4.5Gb disks
>>with 9.1Gb
>>disks. I was going to just use the user friendly program Sysbackup to
>>accomplish this. I made a system image of the rootvg ONLY and
>>replaced the
>>disks. Everything was going fine during the restore until it
>>informed me
>>that a volume group was missing and it wanted to know if
>>sysbackup restore
>>should create or delete it. The volume group is a 270GB RAID
>>volume which
>>are still present in the system but I do not want touched by sysbackup
>>restore. My guess would be to select the create option and
>>then it will
>>continue. As I can not afford to lose time due to errors I
>>did nothing (put
>>the old disks back in) until I get clarification on what it
>>was actually
>>going to do next. If I select "create", will it continue the restore
>>without me assigning any filesystem to it or will it force me
>to assign
>>something to it before continuing?
>>
>>TIA,
>>
>>Marcelino
>>
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:52 EDT