Workaround to allow Sysback V3.X to work on AIX V4.3

Contents

About this document

This document describes modifications to version 3 of Sysback that will allow it to be run on AIX Versions 4.3.x.

It is recommended that before making these changes, the Sysback version should be 3.3.3.17 or 3.3.3.18.

Sysback Version 3 is at End of Service, and as such, this is an unsupported procedure and is only a temporary measure until Sysback can be upgraded to Version 4.2.1 or later.

umask problem

This problem occurs because of a change in the umask value in /sbin/rc.boot at AIX 4.3. A mkdir with a umask of 077 is run from that script when a system is cloned using Sysback. At AIX 3.2, 4.1, 4.2 and very early releases of 4.3, the default umask is 000. However, at AIX 4.3 the default umask is 077. This means that the underlying directories /var, /usr and /tmp are created without read, write or execute permissions for non-root users.

This umask problem will also affect the permissions on the /dev/pts device special files in /dev; this is fixed with APAR IX74957.

This problem has been fixed with Sysback Version 4.2

Version 3.3 efix for umask problem

1. Enter the following commands:

       cd /usr/lpp/sysback/inst
       cp sysmain sysmain.org

2. Open the sysmain file in your favorite editor. Enter:

       vi sysmain

3. Make the following changes to sysmain.

Change from this:

 #######
 # Subroutines
 #######
 . /usr/lpp/sysback/inst/sysinst.lib
 unset updatevginfo pv_to_hdisk update_lvpps

to this:

 #######
 # Subroutines
 #######
 . /usr/lpp/sysback/inst/sysinst.lib
 umask 000   #ADD THIS LINE 
 unset updatevginfo pv_to_hdisk update_lvpps

4. Save the file.

Boot image size

Sometimes when doing a tape boot or network boot, you will get the error messages No space left on device. The size of the ramfs in service mode needs to be increased.

Version 3.3 efix for boot image size

Changes for the network boot image

1. Enter the following commands:

       cd /usr/sbin
       cp mksbnetboot mksbnetboot.org

2. Open the the mksbnetboot file in your favorite editor. Enter:

       vi mksbnetboot

3. Change the mksbnetboot file from this:

       head -1 $proto | read x blocks x
       sed "s/ $blocks/ 16384/" $proto > $tmp_proto

to this:

    head -1 $proto | read x blocks x
    sed "s/ $blocks/ 26624/" $proto > $tmp_proto

4. Save the file.
5. Rebuild the network boot images.

NOTE: You increased the size of the ramfs file system for service mode from 16384 to 26624. You must remake any network boot images.

Changes for the tape boot image

1. Enter the following commands:

       cd /usr/sbin
       cp mkboottape.4 mkboottape.4.org

2. Open the mkboottape.4 file in your favorite editor. Enter:

       vi mkboottape.4

Change the mkboottape.4 file from this:

    sed "s+/usr/lpp/bosinst/bi_main[    ]*$+$sysinit+" | \
    sed "s/ $blocks/ 16384/" > /tmp/$proto

to this:

    sed "s+/usr/lpp/bosinst/bi_main[    ]*$+$sysinit+" | \
    sed "s/ $blocks/ 26624/" > /tmp/$proto

3. Save the file.
4. Rebuild the tape boot images.

NOTE: You increased the size of the ramfs file system for service mode from 16384 to 26624. Remake any tape boot images for the changes to take effect.

mklv and mkvg errors

Due to a software defect within AIX, both mkvg and mklv produce error messages but run successfully (return code of 0).

Version 3.3 efix for mklv and mkvg errors

1. Enter the following commands:

       cd /usr/lpp/sysback
       cp sysrvg sysrvg.org

2. Open the sysrvg file in your favorite editor. Enter:

       vi sysrvg

Change the sysrvg file from this:

    if [ $? -ne 0 -o -s /tmp/mklv.err ]
    then # Error - try again using default disks, 1 copy,

to this:

    if [ $? -ne 0 ]
    then # Error - try again using default disks, 1 copy,

NOTE: There are two places within this file where you will need to make the same exact change: remove the

        -o -s /tmp/mklv.err

from the if statement.
3. Save the file.
4. Next, enter the following commands:

       cd /usr/lpp/sysback
       cp sysuvg sysuvg.org

5. Open the sysuvg file in your favorite editor. Enter:

       vi sysuvg

Change the sysuvg file from this:

    if [ $? -ne 0 -o -s /tmp/mklv.err ]
    then # Error - try again using default disks, 1 copy,

to this:

    if [ $? -ne 0 ]
    then # Error - try again using default disks, 1 copy,

NOTE: There are two places within this file where you will need to make the same exact change:

remove the

-o -s /tmp/mklv.err

from the if statement.
6. Save the file.

Rebuild the boot images

Once all three of these changes have been made, it is important to rebuild your boot images. This is required for the changes to be in effect.

Network boot images

1. From an AIX prompt enter smitty sysback.
2. Select the following options in sequence:

   Configuration Options
   Network Boot Configuration
   Update a network boot image
   

3. Fill in the details for your boot client.
4. Re-run these steps for each network boot client.
5. Remake the network boot image or tape boot images for the changes to take effect.

Sysback boot tape

1. From an AIX prompt enter smitty sysback
2. Select the following options in sequence:

   Utilities
   Create a bootable tape (without data)
   

3. Fill in the specifics of your required boot tape.