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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problems with backup of 'rootvg'

Status
Not open for further replies.

holdahl

IS-IT--Management
Apr 4, 2006
213
NO
At my workplace, we are doing a backup of the rootvg once a week.
The last couple of weeks we have kept getting an error when trying to run this backup. Have tried to change the tape, but it doesnt help.
Here is the error message we keep getting:
--------------------------------------------------------
Creating information file (/image.data) for rootvg..

Creating tape boot image..
0512-016 mksysb: Attempt to create a bootable tape failed:
bosboot -d /dev/rmt0.1 -a failed with return code 48.

*** mksysb failed

rewind tape
---------------------------------------------------------
does anyone know/have suggestions to what may cause this problem?

- image too large?


sH
 
/dev/rmt0.1, is a no-rewind device

so maybe it is full now...?
 
I'd check for free space in /tmp.

Also, error 48 in bosboot is related to dd-ing the created boot image to the device. Is your tapedrive set to 512 block size?

Verify with

lsattr -E -l rmt0


HTH,

p5wizard
 
it says that the block size is 2048, should it be 512 instead?

sH
 
I tried changing the block_size to 512, but the same error came.

How large should /tmp be to make sure that there is sufficient space?


sH
 
the size now:

root@storm:/ # df -m /tmp
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/hd3 64.00 43.97 32% 210 2% /tmp


sH
 
See what happens if you clean up some more in /tmp or make /tmp a bit bigger (you can do that online)...


HTH,

p5wizard
 
I got this from man mksysb:

Code:
-i Calls the mkszfile command, which generates the /image.data file. The
/image.data file contains information on volume groups, logical volumes, file
systems, paging space, and physical volumes. This information is included in the
backup for future use by the installation process. Note: Before running the
mkszfile command, ensure that enough space is available in the /tmp file to
store a boot image. This space is needed during both backup and installation. To
determine the amount of space needed in the /tmp file, issue the following
command:
bosboot -q -a -d device

If you use the -X flag with the mksysb command, you do not need to run the
bosboot command to determine the amount of space needed in the /tmp file.

-X Specifies to automatically expand the /tmp file system if necessary. The /tmp
file system may need to be extended to make room for the boot image when
creating a bootable backup to tape.

so if you want to determine how much space needed for your /tmp use the following as specified:

bosboot -q -a -d /dev/rmt0

Regards,
Khalid
 
It says that it needs 26,21 MB space in /tmp when I do a
#bosboot -q -a -d /dev/rmt0

there is 43,97 MB free space in /tmp so I do not see the problem lying there.


sH
 
Well, mount your tape in the drive and launch the command

bosboot -d /dev/rmt0.1 -a

from the command line prompt and see what the underlying problem is. Also: /usr/sbin/bosboot is a Korn shell script, and you can run it with "debug on" like so:

ksh -x /usr/sbin/bosboot -d /dev/rmt0.1 -a

so you can see which command leads to the error 48...


HTH,

p5wizard
 
For some strange reason it seems to work now...
Not sure I understand why, but at least it works.


sH
 
Now you made me feel that i want to know :)

Any way good luck

regards,
Khalid
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top