Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NIM "PULL" mksysb to smaller disk

Status
Not open for further replies.

jkc924

MIS
Aug 5, 2002
35
0
0
US
I have been tasked to take a mksysb of a client on my NIM server and pull it over to another server - Problem is that the mksysb was created on a server with 72 GB internal drives and I am trying to pull it over to 36 GB drives. Keep getting "not enough partition/space errors" when it is trying to create the rootvg filesystems - Is this even possible to do or do the drives on both servers have to be the same size?
Thanks in advance for any advice.
 
It's possible, but you have to hack the bosinst.data file as per this IBM site

Note the target disk data stanza.

Briefly the process is
[ol]
[li]Create mksysb image using NIM[/li]
[li]Edit bosinst.data as required[/li]
[li]Add bosinst.data to NIM[/li]
[li]Use NIM to push out mysysb image and bosinst.data[/li]
[/ol]
Godd luck.

Ceci n'est pas une signature
Columb Healy
 
I had a modified bosinst.data file as follows and it did not work:
CONSOLE = Default
INSTALL_METHOD = overwrite
PROMPT = no
EXISTING_SYSTEM_OVERWRITE = yes
INSTALL_X_IF_ADAPTER = yes
RUN_STARTUP = yes
RM_INST_ROOTS = no
ERROR_EXIT =
CUSTOMIZATION_FILE =
TCB = no
INSTALL_TYPE =
BUNDLES =
RECOVER_DEVICES = no
BOSINST_DEBUG = no
ACCEPT_LICENSES = yes
DESKTOP = NONE
INSTALL_DEVICES_AND_UPDATES = yes
IMPORT_USER_VGS =
ENABLE_64BIT_KERNEL = yes
CREATE_JFS2_FS = yes
ALL_DEVICES_KERNELS = yes
GRAPHICS_BUNDLE = yes
MOZILLA_BUNDLE = no
KERBEROS_5_BUNDLE = no
SERVER_BUNDLE = yes
ALT_DISK_INSTALL_BUNDLE = yes
REMOVE_JAVA_118 = no
HARDWARE_DUMP = yes
ADD_CDE = no
ADD_GNOME = no
ADD_KDE = no
ERASE_ITERATIONS = 0
ERASE_PATTERNS =

target_disk_data:
LOCATION =
SIZE_MB =
HDISKNAME = hdisk0

locale:
 
OK, back to basics, you are sure that you haven't defined more than 36Gb of file systems in the rootvg of the source machine?

Asuming the answer is no check the image.data file and the logical volume policy stanza

Ceci n'est pas une signature
Columb Healy
 
It's the image.data file that contains PP, LP, and COPIES as well as the other relevant information that needs to be edited.

The file is created by mkszfile. Don't make an exact map.

But the problem is going from 72 to 36. Not recommeded. It may work but if there are problems then you no it didn't.

If there are 2 copies in image.data reduce it to one copy, one source disk, halve the PP.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top