SEO

Hello again, all. I have yet ANOTHER newbie question, this time
regarding mksysb.

Let's start with my mounted files in rootvg:

# df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 131072 109020 17% 2161 4% /
/dev/hd2 3801088 1068884 72% 50003 6% /usr
/dev/hd9var 131072 65576 50% 632 2% /var
/dev/hd3 524288 431428 18% 314 1% /tmp
/dev/fwdump 393216 373656 5% 18 1%
/var/adm/ras/platform
/dev/hd1 131072 58244 56% 347 2% /home
/dev/lv00 4194304 4062596 4% 19 1% /usr/sys

I ran "mksysb /dev/rmt0". Got the following:

# mksysb /dev/rmt0
Creating tape boot image....................
bosboot: Boot image is 26859 512 byte blocks.
***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
Creating list of files to back up.
Backing up 3 files.
3 of 3 files (100%)
0512-038 mksysb: Backup Completed Successfully.
bosboot: Boot image is 26859 512 byte blocks.
***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
#

I already checked out the "might fail to boot" message, and I'm in good
shape inasmuch as I have the necessary APAR in the server to allow me
to use this tape to recover from.

My question is: What have I backed up? "3 of 3" files, and "Boot image
is 26859 512 byte blocks." doesn't seem like much.

Google searching on this (yes, I AM trying to figure this out on my
own) led me to run
restore -s4 -Tvqf /dev/rmt0.1 > /tmp/mksysb_list
The output from this is:
# cat mksysb_list
1309 ./bosinst.data
3442 ./image.data
211004 ./tmp/vgdata/rootvg/backup.data
The total size is 215755 bytes.
#

If I look at ./tmp/vgdata/rootvg/backup.data, I have a list of a
boatload of stuff (excerpted below), starting with the config of
rootvg, followed by a list of filesets. I certainly LOOKS like a list
of files and packages, but the backup didn't take very long, and I'm
concerned about the sizes listed. Have I got a (presumeably) good
backup? I know the only way to tell for sure is to try and boot from
it, but that's not an option in this case.

Any help on mksysb options I should have included or any assurances
that I am /am not in good shape appreciated.

# more /tmp/vgdata/rootvg/backup.data
================================
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT
POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 64 128 2 open/syncd N/A
hd8 jfslog 1 2 2 open/syncd N/A
hd4 jfs 1 2 2 open/syncd /
hd2 jfs 29 58 2 open/syncd /usr
hd9var jfs 1 2 2 open/syncd /var
hd3 jfs 4 8 2 open/syncd /tmp
hd1 jfs 1 2 2 open/syncd /home
hd10opt jfs 1 2 2 open/syncd /opt
fwdump jfs 3 6 2 open/syncd
/var/adm/ras/platform
system01lv jfs2 280 560 2 open/syncd /system01
hd7 sysdump 32 32 1 open/syncd N/A
hd7x sysdump 32 32 1 open/syncd N/A
loglv02 jfs2log 1 2 2 open/syncd N/A
lv00 jfs 32 32 1 open/syncd /usr/sys
================================
Fileset Level State Type Description
(Uninstaller)

----------------------------------------------------------------------------
IMNSearch.bld.DBCS 2.4.0.0 C F NetQuestion DBCS
Buildtime
Modules
IMNSearch.bld.SBCS 2.4.0.0 C F NetQuestion SBCS
Buildtime
Modules
IMNSearch.msg.en_US.rte.com
2.4.0.0 C F Text Search Messages
- U.S.
English
IMNSearch.rte.DBCS 2.4.0.10 C F NetQuestion DBCS
Search Engine
IMNSearch.rte.SBCS 2.4.0.10 C F NetQuestion SBCS
Search Engine
IMNSearch.rte.client 2.4.0.0 C F Text Search Client
IMNSearch.rte.com 2.4.0.0 C F Text Search
Client/Server
....
.... skip on down
....
#Package Name:Fileset:Level:State:PTF Id:Fix
State:Typeescriptionestination Dir.:Uninstaller:Message
Catalog:Message Set:Message
Number:Parent:Automatic:EFIX Locked
IMNSearch.bld:IMNSearch.bld.DBCS:2.4.0.0: : :C: :NetQuestion DBCS
Buildtime Modules: : : : : : :0:0:
IMNSearch.bld:IMNSearch.bld.SBCS:2.4.0.0: : :C: :NetQuestion SBCS
Buildtime Modules: : : : : : :0:0:
IMNSearch.msg.en_US.rte.com:IMNSearch.msg.en_US.rt e.com:2.4.0.0: : :C:
:Text Search Messages - U.S. English: : : : : : :0:0:
IMNSearch.rte:IMNSearch.rte.DBCS:2.4.0.10: : :C: :NetQuestion DBCS
Search Engine : : : : : : :0:0:
IMNSearch.rte:IMNSearch.rte.SBCS:2.4.0.10: : :C: :NetQuestion SBCS
Search Engine : : : : : : :0:0:
IMNSearch.rte:IMNSearch.rte.client:2.4.0.0: : :C: :Text Search Client :
: : : : : :0:0:
....
.... skip on down
....
pci.1069B166.09ci.1069B166.09-0509007e-1:0509007e: : :C:R:IBM eServer
PCI-X Dual Channel Ultra320 SCSI RAID Adapter Microcode CCIN
5703/1975: :/bin/rpm -e pci.1069B166.09: : : : :0:
xft:xft-0.0-0:0.0: : :C:R:An empty placeholder RPM for xft.: :/bin/rpm
-e xft: : : : :0:
xrender:xrender-0.0-0:0.0: : :C:R:An empty placeholder RPM for
xrender.: :/bin/rpm -e xrender: : : : :0:
================================
#Shrink Size:Full Size:VG Data Only
16896:17152:no
#

Joe D.

Joe D. wrote:
> Hello again, all. I have yet ANOTHER newbie question, this time
> regarding mksysb.
> I ran "mksysb /dev/rmt0". Got the following:

....
>
> # mksysb /dev/rmt0
> Creating tape boot image....................
> bosboot: Boot image is 26859 512 byte blocks.
> ***** ATTENTION *****
> The boot image you just created might fail to boot because
> the size exceeds the system limit. For information about
> fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
> ***** ATTENTION *****
> Creating list of files to back up.
> Backing up 3 files.
> 3 of 3 files (100%)
> 0512-038 mksysb: Backup Completed Successfully.
> bosboot: Boot image is 26859 512 byte blocks.
> ***** ATTENTION *****
> The boot image you just created might fail to boot because
> the size exceeds the system limit. For information about
> fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
> ***** ATTENTION *****
> #
>
> I already checked out the "might fail to boot" message, and I'm in good
> shape inasmuch as I have the necessary APAR in the server to allow me
> to use this tape to recover from.
>
> My question is: What have I backed up? "3 of 3" files, and "Boot image
> is 26859 512 byte blocks." doesn't seem like much.

1) bootimage
Looks a little bit big.
Lesson :
Please verify that you have IY50487 installed on your system
See
IY50487: MKSYSB TAPE BOOTIMAGE TOO BIG, HANGS ON BOOT
http://www-1.ibm.com/support/docview...id=isg1IY50487
and
$ man instfix


2) mksysb
Check if you have a /etc/exlude.rootvg file and if yes post/verify the
entries. 3 files are really not enough


Latest AIX 5.2 installation tips
http://www-1.ibm.com/support/docview...TIPS082310_815

hth
Hajo

Hajo Ehlers wrote:
> Joe D. wrote:
>
> 1) bootimage
> Looks a little bit big.
> Lesson :
> Please verify that you have IY50487 installed on your system

Yep; I checked this out;

# instfix -ik IY50487
All filesets for IY50487 were found.

> See
> IY50487: MKSYSB TAPE BOOTIMAGE TOO BIG, HANGS ON BOOT
> http://www-1.ibm.com/support/docview...id=isg1IY50487
> and
> $ man instfix
>
>
> 2) mksysb
> Check if you have a /etc/exlude.rootvg file and if yes post/verify the
> entries. 3 files are really not enough

Nope; no exclude entry:

# ls -al /etc/ex*
lrwxrwxrwx 1 bin bin 19 Dec 27 2004 /etc/execerror
-> /usr/sbin/execerror
lrwxrwxrwx 1 root system 18 Dec 27 2004 /etc/exportvg
-> /usr/sbin/exportvg
lrwxrwxrwx 1 root system 18 Dec 27 2004 /etc/extendlv
-> /usr/sbin/extendlv
lrwxrwxrwx 1 root system 18 Dec 27 2004 /etc/extendvg
-> /usr/sbin/extendvg
Besides, if I read the man page correctly, this only is used if I pass
the -e option to mksysb, doesn't it? My mksysb command was simply
"mksysb /dev/rmt0"

>
> Latest AIX 5.2 installation tips
> http://www-1.ibm.com/support/docview...TIPS082310_815
>
> hth
> Hajo

Joe D. wrote:
> Hajo Ehlers wrote:
> > Joe D. wrote:
> >
> > 1) bootimage
> > Looks a little bit big.
> > Lesson :
> > Please verify that you have IY50487 installed on your system
>
> Yep; I checked this out;
>
> # instfix -ik IY50487
> All filesets for IY50487 were found.
>
> > See
> > IY50487: MKSYSB TAPE BOOTIMAGE TOO BIG, HANGS ON BOOT
> > http://www-1.ibm.com/support/docview...id=isg1IY50487
> > and
> > $ man instfix
> >
> >
> > 2) mksysb
> > Check if you have a /etc/exlude.rootvg file and if yes post/verify the
> > entries. 3 files are really not enough
>
> Nope; no exclude entry:
>
> # ls -al /etc/ex*
> lrwxrwxrwx 1 bin bin 19 Dec 27 2004 /etc/execerror
> -> /usr/sbin/execerror
> lrwxrwxrwx 1 root system 18 Dec 27 2004 /etc/exportvg
> -> /usr/sbin/exportvg
> lrwxrwxrwx 1 root system 18 Dec 27 2004 /etc/extendlv
> -> /usr/sbin/extendlv
> lrwxrwxrwx 1 root system 18 Dec 27 2004 /etc/extendvg
> -> /usr/sbin/extendvg
> Besides, if I read the man page correctly, this only is used if I pass
> the -e option to mksysb, doesn't it? My mksysb command was simply
> "mksysb /dev/rmt0"
>
> >
> > Latest AIX 5.2 installation tips
> > http://www-1.ibm.com/support/docview...TIPS082310_815
> >
> > hth
> > Hajo

Try running mksysb with the '-i' flag. It may be that your /image.data
file is incorrect, the -i option will create a new one. Also see the
mkszfile command and take note of the bit in the man page for mkszfile
that says:

The mkszfile command creates the /image.data file. The contents of this
file are defined by the system in which the image was created. The user
can edit the /image.data file before calling the mksysb command. The
mksysb command, in turn, only backs up the file systems specified in
the /image.data file, which reflects the requirements of the rootvg
file system.

Also try running mksysb with the -v option to list the files its
backing up (or trying to backup).

If it still doesnt work then try thru smit mksysb to see if that helps
(although it should not make any difference but it cant hurt.

Scott

Joe D. wrote:
> Hajo Ehlers wrote:
....
> Besides, if I read the man page correctly, this only is used if I pass
> the -e option to mksysb, doesn't it? My mksysb command was simply
> "mksysb /dev/rmt0"

Then Scotts suggestion should fit - hopefully

regards and have a good night
Hajo

Just a thought and YMMV

IBM Support has previously told me that ML04 on AIX 5.2 is a buggy
level and to avoid it.


Hajo Ehlers wrote:
> Joe D. wrote:
> > Hajo Ehlers wrote:
> ...
> > Besides, if I read the man page correctly, this only is used if I pass
> > the -e option to mksysb, doesn't it? My mksysb command was simply
> > "mksysb /dev/rmt0"
>
> Then Scotts suggestion should fit - hopefully
>
> regards and have a good night
> Hajo

scott_doyland@johnlewis.co.uk wrote:
>
> Try running mksysb with the '-i' flag. It may be that your /image.data
> file is incorrect, the -i option will create a new one. Also see the
> mkszfile command and take note of the bit in the man page for mkszfile
> that says:
>
> Scott

That seems to have done the trick; I ran it with a -m option, and it
listed well over 100,000 file to be backed up. It ran to end of tape
rather quickly; or at least I'm assuming it reached EOF, otherwise
something else killed it. Regardless, I did not kill the job, but when
I got the prompt back, I created an exclude file to omit a large
directory in rootvg that isn't needed for an OS recovery.

Then kicked off the mksysb again, this time specifying the exclude
file, and it listed @56000 files to back up and ran to successful
completion. Took about 4 hours.

So thanks to both you and Hajo for all your help; I'm gonna try and
figure out how to make it run quicker (specify a blocking cfactor?
Find other files to exclude?); but for now I'm happy that I have a
mksysb!

Thanks again;

Joe D.

> figure out how to make it run quicker (specify a blocking cfactor?
Yes, as far as i know the mksysb set the block size to 512 for the
first 3 section tand reset for the 4th section to the original value.

So depending on your tape drive any value except 0 is a good starting
point. I would test a value of 1024 and 10240

$ lsattr rmt0 -a block_size # get current value
$ chdev -l rmt0 -a block_size=10240
$ mksysb ...
$ chdev -l rm -a block_size=OldValue

> Find other files to exclude?); but for now I'm happy that I have a
> mksysb!

A nice technote from IBM about mksysb

Backing Up the Operating System in AIX 4 and 5
http://www-1.ibm.com/support/docview...d=isg3T1000159

enjoy
Hajo

Hajo Ehlers wrote:
>
> So depending on your tape drive any value except 0 is a good starting
> point. I would test a value of 1024 and 10240
>
> $ lsattr rmt0 -a block_size # get current value
> $ chdev -l rmt0 -a block_size=10240
> $ mksysb ...
> $ chdev -l rm -a block_size=OldValue
>

Thanks for the tip, and the link. I updgraded the server to 5200-09-CSP
(thatks SOOO much for the pointers; hell, handholding is a better
word!). Following the upgrade, I implemneted your suggestion and it ran
much quicker, although there was a real quirk after I upgraded. I'll
save that for another post; I'd be interested to see what you make odf
it, as I could find NOTHING on the web. Maybe the answer lies in the
link you provided. At anyrate, here's the result of the successful
mksysb. OPne error message that I don't think is anything to worry
about:

# mksysb -m -e /dev/rmt0

Creating information file (/image.data) for rootvg..

Creating tape boot image.................
bosboot: Boot image is 27546 512 byte blocks.

***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
.....

Creating list of files to back up.
Backing up 65833 files..............................
257 of 65833 files (0%)..............................
748 of 65833 files (1%)........backup: 0511-449 An error occurred
accessing ./tm
p/man585842: A file or directory in the path name does not exist.
.......................
13995 of 65833 files (21%)..............................
25502 of 65833 files (38%)..............................
43125 of 65833 files (65%)..............................
62708 of 65833 files (95%).......
0512-003 mksysb may not have been able to archive some files.
The messages displayed on the Standard Error contained additional
information.

bosboot: Boot image is 27546 512 byte blocks.

***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
#

Thank you again!

Joe D.

Joe D. wrote:
> Hajo Ehlers wrote:
>
>>So depending on your tape drive any value except 0 is a good starting
>>point. I would test a value of 1024 and 10240
>>
>>$ lsattr rmt0 -a block_size # get current value
>>$ chdev -l rmt0 -a block_size=10240
>>$ mksysb ...
>>$ chdev -l rm -a block_size=OldValue
>>
>
>
> Thanks for the tip, and the link. I updgraded the server to 5200-09-CSP
> (thatks SOOO much for the pointers; hell, handholding is a better
> word!). Following the upgrade, I implemneted your suggestion and it ran
> much quicker, although there was a real quirk after I upgraded. I'll
> save that for another post; I'd be interested to see what you make odf
> it, as I could find NOTHING on the web. Maybe the answer lies in the
> link you provided. At anyrate, here's the result of the successful
> mksysb. OPne error message that I don't think is anything to worry
> about:
>
> # mksysb -m -e /dev/rmt0
>
> Creating information file (/image.data) for rootvg..
>
> Creating tape boot image.................
> bosboot: Boot image is 27546 512 byte blocks.
>
> ***** ATTENTION *****
> The boot image you just created might fail to boot because
> the size exceeds the system limit. For information about
> fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
> ***** ATTENTION *****
> ....
>
> Creating list of files to back up.
> Backing up 65833 files..............................
> 257 of 65833 files (0%)..............................
> 748 of 65833 files (1%)........backup: 0511-449 An error occurred
> accessing ./tm
> p/man585842: A file or directory in the path name does not exist.
> ......................
> 13995 of 65833 files (21%)..............................
> 25502 of 65833 files (38%)..............................
> 43125 of 65833 files (65%)..............................
> 62708 of 65833 files (95%).......
> 0512-003 mksysb may not have been able to archive some files.
> The messages displayed on the Standard Error contained additional
> information.
>
> bosboot: Boot image is 27546 512 byte blocks.
>
> ***** ATTENTION *****
> The boot image you just created might fail to boot because
> the size exceeds the system limit. For information about
> fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
> ***** ATTENTION *****
> #
>
> Thank you again!
>
> Joe D.
>

Its nothing to worry about. You (or somebody else) looked at a man page
while the file list was being created, but finished before the actual
backup started. ;-)