restore mksysb from bigger disk to smaller disk

[alex06...@gmail.com]

Hi,

Some on could tel me how can i do to restore mksysb
from server with 2 disk 18 GO mirrored onto an other server with 2
disk 9 GO not mirrored ?

Thank's

[Levy "Lewis" S.]

Hi,
mksysb only contain the data that you have done the image, so if your
data is less than 9G you can do the restore smoothly,

bye,
Levy 'Lewis' S.

[JesperBergh]

If your mksysb contains more data than 9Gb you will have to edit
"image.data"
each lv definition in the image.data file has to be altered to:
COPIES=1
PP=XX/2
This to remove the LV mirror copies.

I belive it got to be a new and better way to do this but that is how
it was done back in the 4.3.3/5.1 days and should work now aswell.

However if your current rootvg is smaller than 9Gb just restore it
mirrored.

//Jesper

[le pierre]

thank you for your response it's ok.

I have find this link also : http://www.ibm.com/support/docview.wss?uid=isg3T1000127

Restoring a mksysb Without Preserving Mirrors
Technote (FAQ)

Question
Restoring a mksysb Without Preserving Mirrors

Answer

This document describes how to restore a mksysb image without
preserving mirrors. Information in this document is valid for AIX
Versions 4.x and 5L.

WARNING: This procedure is valid ONLY with a mksysb image and will not
work with a Sysback 6000 system backup.
Creating a mksysb without mirroring
Breaking mirrors on an existing mksysb
Creating a mksysb without mirroring
If the ability to rerun the mksysb is available, the following
procedure will allow you to create a mksysb without preserving
mirroring.

1. To create a new image.data file, run the following command:

mkszfile

2. Change into the / directory and vi the image.data file. Enter:

cd /
vi image.data

3. The following examples show an lv_data stanza of an image.data
file. The first example is with mirroring, while the second example
shows the edited version without mirroring. The lines that need
changes are marked by --> and are boldfaced. In the second example,
the changes are made to those lines.

To view and edit the file, enter:

vi image.data

Example 1

lv_data:
VOLUME_GROUP= rootvg
--> LV_SOURCE_DISK_LIST= hdisk0 hdisk1
LV_IDENTIFIER= 00000001113f3c62.5
LOGICAL_VOLUME= hd2
VG_STAT= active/complete
TYPE= jfs
MAX_LPS= 512
--> COPIES = 2
LPs = 70
STALE_PPs= 0
INTER_POLICY= minimum
INTRA_POLICY= center
MOUNT_POINT= /usr
MIRROR_WRITE_CONSISTENCY= on
LV_SEPARATE_PV= yes
PERMISSION= read/write
LV_STATE= opened/syncd
WRITE_VERIFY= off
PP_SIZE= 4
SCHED_POLICY= parallel
--> PP = 140
BB_POLICY= relocatable
RELOCATABLE= yes
UPPER_BOUND= 32
LABEL= /usr
MAPFILE=
LV_MIN_LPS= 68

Example 2

lv_data:
VOLUME_GROUP= rootvg
--> LV_SOURCE_DISK_LIST= hdisk0
LV_IDENTIFIER= 00000001113f3c62.5
LOGICAL_VOLUME= hd2
VG_STAT= active/complete
TYPE= jfs
MAX_LPS= 512
--> COPIES = 1
LPs = 70
STALE_PPs= 0
INTER_POLICY= minimum
INTRA_POLICY= center
MOUNT_POINT= /usr
MIRROR_WRITE_CONSISTENCY= on
LV_SEPARATE_PV= yes
PERMISSION= read/write
LV_STATE= opened/syncd
WRITE_VERIFY= off
PP_SIZE= 4
SCHED_POLICY= parallel
--> PP = 70
BB_POLICY= relocatable
RELOCATABLE= yes
UPPER_BOUND= 32
LABEL= /usr
MAPFILE=
LV_MIN_LPS= 68

In Example 2 the LV_SOURCE_DISK_LIST has been changed to specify
one disk, the COPIES value has been changed to 1 and the PP value is
set equal to the LPs value. Make these changes to each of the lv_data
stanzas in the image.data file. Once the changes are made, save the
file and exit.
4. Run another mksysb from the command line that will utilize your
edited image.data file.

mksysb /dev/rmtX (where X is the number of your tape
drive)

WARNINGS:
* Do not run the mksysb in SMIT because this will update the
image.data file and overwrite any changes made.
* Do not run the mksysb with the -i flag because this will
update the image.data file as well.