Beruflich Dokumente
Kultur Dokumente
uid=isg3T1011782
Software
Operating System
AIX family
Installation, backup,
restore
Technote (FAQ)
Operating system(s):
This document applies only to the following AIX
language version(s):
US English Software version:
For the purposes of this document, all references to tape or CD drives will be
rmt0 and cd0. Your devices may vary.
____________________________________________________________________________
1 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
2. Check to make sure the block size of the tape drive has been changed:
3. 'cd' to the /tmp directory (or a directory where you would like to store the
/image.data file from the mksysb image) and restore the /image.data file from
the tape:
# cd /tmp
# restore –s2 -xqvf /dev/rmt0.1 ./image.data
*The image.data file from the tape will be restored to the /tmp directory
1. ‘cd’ to the /tmp directory (or a directory where you would like to store the
/image.data file from the mksysb image) and restore the /image.data file from
the mksysb:
# cd /tmp
# restore -xqvf </location/of/mksysb/file> ./image.data
***The image.data file from the mksysb image will be restored to the /tmp
directory
____________________________________________________________________________
# cd /
# mkszfile
2. vi the image.data file to break the mirror, by running the following command:
2 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
# vi /image.data
3. What you are looking for are the “lv_data” stanzas. There will be one for
every logical volume associated with rootvg.
lv_data:
VOLUME_GROUP= rootvg
--> LV_SOURCE_DISK_LIST= hdisk0 hdisk1
LV_IDENTIFIER= 000693da00004c00000001203de2aa29.14
LOGICAL_VOLUME= fslv01
VG_STAT= active/complete
TYPE= jfs2
MAX_LPS= 512
---> COPIES= 2
LPs= 20
STALE_PPs= 0
INTER_POLICY= minimum
INTRA_POLICY= middle
MOUNT_POINT= /chris
MIRROR_WRITE_CONSISTENCY= on/ACTIVE
LV_SEPARATE_PV= yes
PERMISSION= read/write
LV_STATE= opened/syncd
WRITE_VERIFY= off
PP_SIZE= 256
SCHED_POLICY= parallel
--> PP= 40
BB_POLICY= relocatable
RELOCATABLE= yes
UPPER_BOUND= 32
LABEL= /chris
MAPFILE=
LV_MIN_LPS= 1
STRIPE_WIDTH=
STRIPE_SIZE=
SERIALIZE_IO= no
FS_TAG= vfs=jfs2:log=/dev/hd8:mount=true:options=rw:account=false
DEV_SUBTYP=
3 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
lv_data:
VOLUME_GROUP= rootvg
---> LV_SOURCE_DISK_LIST= hdisk0
LV_IDENTIFIER= 000693da00004c00000001203de2aa29.14
LOGICAL_VOLUME= fslv01
VG_STAT= active/complete
TYPE= jfs2
MAX_LPS= 512
---> COPIES= 1
LPs= 20
STALE_PPs= 0
INTER_POLICY= minimum
INTRA_POLICY= middle
MOUNT_POINT= /chris
MIRROR_WRITE_CONSISTENCY= on/ACTIVE
LV_SEPARATE_PV= yes
PERMISSION= read/write
LV_STATE= opened/syncd
WRITE_VERIFY= off
PP_SIZE= 256
SCHED_POLICY= parallel
---> PP= 20
BB_POLICY= relocatable
RELOCATABLE= yes
UPPER_BOUND= 32
LABEL= /chris
MAPFILE=
LV_MIN_LPS= 1
STRIPE_WIDTH=
STRIPE_SIZE=
SERIALIZE_IO= no
FS_TAG= vfs=jfs2:log=/dev/hd8:mount=true:options=rw:account=false
DEV_SUBTYP=
6. At this point you can use the edited image.data file to do one of the
following:
You can now use your newly edited image.data file to create a new mksysb to
file, tape, or DVD..
Example :
To file or tape : place the edited image.data file in the / (root) directory and
rerun your mksysb command without using the “-i” flag. If running the backup
4 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
through SMIT, make sure you set the option “Generate new /image.data file?”
to 'no'. (By default it is set to 'yes')
To DVD : Use the -i flag and specify the </location> of the edited image.data
file. If running through SMIT specify the edited image.data file location in the
“User supplied image.data file” field.
Within NIM you would create an 'image_data' resource for use with NIM to
restore a mksysb without preserving mirrors.
____________________________________________________________________________
# cd /
# mkszfile
2. Break the mirror in the /image.data file as shown in the steps above
# mv /tmp/edited.image.data /image.data
3. Use the mksysb command to create a new mksysb with the /image.data file
that has the broken mirror.
To file:
# mksysb /location/of/mksysb/file
***NOTE: DO NOT use the '-i' or '-m' flags. These flags will create a new
/image.data file based upon the systems current configuration. This means that
the mirrors will still be in tact in the mksysb. All other mksysb flags can be
used.
- OR -
Using smit:
# smit mksysb
5 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
[Entry Fields]
WARNING: Execution of the mksysb command will
result in the loss of all material
previously stored on the selected
output medium. This command backs
up only rootvg volume group.
* Backup DEVICE or FILE [/dev/rmt0] +/
Create MAP files? no +
EXCLUDE files? no +
List files as they are backed up? no +
Verify readability if tape device? no +
Generate new /image.data file? no + <---
EXPAND /tmp if needed? no +
Disable software packing of backup? no +
Backup extended attributes? yes +
Number of BLOCKS to write in a single output [] #
(Leave blank to use a system default)
Location of existing mksysb image [] /
File system to use for temporary work space [] /
(If blank, /tmp will be used.)
Back up encrypted files? yes +
Back up DMAPI filesystem files? yes +
____________________________________________________________________________
1. Transfer the /image.data file to the NIM master and store it in the location
you desire. It is a good idea to place the file, or any NIM resource for that
matter, in a descriptive manor.
Ex : /export/nim/image_data
This will ensure you can easily identify your "image_data" NIM resource file
locations, should you have the need for multiple "image_data" resources.
Make sure your image.data filenames are descriptive also. A common way to
name the file would be in relation to your clientname.
Ex : ClientA.imagedata
2. Run the nim command, or use smitty and the fast path ‘nim_mkres’ to define
the file that you have edited using the steps above:
6 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
# smit nim_mkres
--> select 'image_data' as the Resource Type
Define a Resource
[Entry Fields]
* Resource Name [mksysb_image_data]
* Resource Type image_data
* Server of Resource [master] +
* Location of Resource [/export/nim/image_data/ClientA.imagedata /
NFS Client Security Method [] +
NFS Version Access [] +
Comments [image.data file with broken mirror for testlpar]
Source for Replication [] +
3. Run the following command to make sure the 'image_data' resource was
created:
# lsnim -t image_data
# lsnim -l mksysb_image_data
____________________________________________________________________________
7 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
1. Specify using the 'image_data' resource when running the 'bosinst' command
from the NIM master:
From command line on the NIM master:
- OR -
# smit nim_bosinst
>select the client to install
>select 'mksysb' as the type of install
>select a SPOT at the same level as the mksysb you are installing
>select an lpp_source at the same level than the mksysb you are installing.
8 of 9 11/30/2010 11:23 AM
IBM Creating and Restoring a Mksysb Without Preserving Mirrors (Using... http://www-01.ibm.com/support/docview.wss?uid=isg3T1011782
this target?
For information regarding creating a mksysb to DVD please visit our Document
Control Facility at
http://www.ibm.com/support/us/en
In the “Search all of support” box type in the following search string :
Creating a mksysb backup to DVD in AIX
9 of 9 11/30/2010 11:23 AM