Scribd Logo
Upload

Welcome to Scribd!

  • 178 views

    Aix Updates Using Multibos

    Uploaded by

    Azimul Hasnain Zaidi
    This document discusses AIX updates using multibos, which allows maintaining two bootable AIX instances in the same root volume group. It describes how to create a standby BOS instance by copying file systems to new logical volumes, update the standby instance to a new fix pack or technology level, and reboot the system from the updated standby instance with minimal downtime. The process involves removing any previous standby instance, previewing and creating the new standby copy, applying updates to it, verifying the update, setting the boot list to the standby volume, and rebooting.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Aix Updates Using Multibos

    Uploaded by

    Azimul Hasnain Zaidi
    178 views11 pages
    This document discusses AIX updates using multibos, which allows maintaining two bootable AIX instances in the same root volume group. It describes how to create a standby BOS instance by copying file systems to new logical volumes, update the standby instance to a new fix pack or technology level, and reboot the system from the updated standby instance with minimal downtime. The process involves removing any previous standby instance, previewing and creating the new standby copy, applying updates to it, verifying the update, setting the boot list to the standby volume, and rebooting.

    Original Description:

    aix updates using multibos.ppt

    Original Title

    aix updates using multibos.ppt

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses AIX updates using multibos, which allows maintaining two bootable AIX instances in the same root volume group. It describes how to create a standby BOS instance by copying file systems to new logical volumes, update the standby instance to a new fix pack or technology level, and reboot the system from the updated standby instance with minimal downtime. The process involves removing any previous standby instance, previewing and creating the new standby copy, applying updates to it, verifying the update, setting the boot list to the standby volume, and rebooting.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    178 views11 pages

    Aix Updates Using Multibos

    Uploaded by

    Azimul Hasnain Zaidi
    This document discusses AIX updates using multibos, which allows maintaining two bootable AIX instances in the same root volume group. It describes how to create a standby BOS instance by copying file systems to new logical volumes, update the standby instance to a new fix pack or technology level, and reboot the system from the updated standby instance with minimal downtime. The process involves removing any previous standby instance, previewing and creating the new standby copy, applying updates to it, verifying the update, setting the boot list to the standby volume, and rebooting.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 11
    At a glance
    Powered by AI
    Multibos allows maintaining two separate bootable instances of the AIX OS within the same root volume group to more easily apply updates and roll back if needed.

    Multibos allows creating and maintaining two separate bootable AIX OS instances in the same root volume group (rootvg). It copies the BOS file systems and BLV by default, while sharing other file systems and LVs. This avoids needing an additional disk for maintenance.

    The steps to create a standby BOS instance include removing any previous instance, previewing the operation, and then using the multibos command to create the new LV and file systems for each BOS copy prefixed with 'bos_'.

    AIX Updates with Multibos

    What is multibos?
    Introduced with AIX 5.3 TL3. Create and maintain two separate, bootable instances of the AIX OS within the same root volume group (rootvg). Standby BOS. Install, update and customize a standby instance of the AIX OS. By default, the BOS file systems in rootvg(/, /usr, /var, and /opt) and the BLV are copied. All other file systems and LVs are shared between BOS instances. Similar alternate disk: no additional disk, some LV shared between instances.

    AIX Updates with Multibos.


    Valuable in environments with tight maintenance windows. Apply a new TL or SP. AIX migration not supported.yet! Only need a small outage at a convenient time to reboot the system. Reduce the size of the after-hours effort. Backing out from an AIX TL update is also easier.

    Getting Started
    AIX 5.3 with TL3 or higher. Free space in rootvg for a copy of each BOS logical volume (# lsvg rootvg | grep FREE ). If all of the requirements cant be met, then a traditional update should be performed. Document the system and perform a mksysb before performing any maintenance activity.

    Creating a Standby BOS Instance


    Example: well upgrade an AIX 5.3 system from TL4 to TL6. Remove any previous standby BOS instance using multibos R. Preview the operation first (using multibos sXp). Review the multibos log for any errors (i.e., alog of/etc/multibos/logs/op.alog).

    Creating a Standby BOS Instance, cont.


    Create the standby BOS instance. This may take several minutes and should create a new LV and file system for each BOS copy. Each new LV and file system is prefixed by bos_.
    # multibos sX # lsvg -l rootvg | grep bos bos_hd5 boot 1 bos_hd4 jfs 4 bos_hd2 jfs 48 bos_hd9var jfs 21 bos_hd10opt jfs 4

    1 4 48 21 4

    1 1 1 1 1

    closed/syncd N/A closed/syncd /bos_inst closed/syncd /bos_inst/usr closed/syncd /bos_inst/var closed/syncd /bos_inst/opt

    Updating and Booting the Standby BOS


    Apply TL6 to the standby BOS. The TL6 lppsource is mounted from our NIM master. Perform a preview operation and then execute the actual update to the standby instance. Again, checking the log file for any issues.
    # mount nimmast:/export/lpp_source/lpp_sourceaix530603 /mnt # multibos -Xacp -l /mnt # multibos -Xac -l /mnt

    Updating and Booting the Standby BOS, cont.


    Weve now successfully applied TL6 to the standby BOS. Start a multibos shell and verify that the standby BOS has been updated.
    # multibos S ... # oslevel -s 5300-06-03-0732 # exit

    Ready to boot the standby BOS


    BOS may be upgraded during the day, but the system may be restarted after hours depending on the available outage windows for this system. Verify the bootlist and ensure that the BLV is set to the standby BOS (bos_hd5). Check the correct BLV. Compare the output from bootlist with Welcome to AIX banner.
    # bootlist -m normal -ov ibm,max-boot-devices = 0x5 NVRAM variable: (boot-device=/vdevice/v-scsi@30000004/disk@8100000000000000:2 /vdevice/vscsi@30000004/disk@8100000000000000:4) Path name: (/vdevice/v-scsi@30000004/disk@8100000000000000:4) hdisk0 blv=bos_hd5 Path name: (/vdevice/v-scsi@30000004/disk@8100000000000000:2) hdisk0 blv=hd5 --------------------------------------------------------------------Welcome to AIX. boot image timestamp: 02:24 06/05 The current time and date: 02:25:27 09/03/2007 number of processors: 1 size of memory: 4096MB boot device: /vdevice/v-scsi@30000004/disk@8100000000000000:4 kernel size: 14154989; 64 bit kernel ---------------------------------------------------------------------

    Booting the Standby BOS


    Reboot the system now with the shutdown Fr command. After the reboot, confirm the TL level via oslevel r. Verify which BLV the system booted from with the bootinfo v command. Multibos LVs and file systems are now open and mounted. The original file systems are renamed with a bos_ prefix but their original LV names are preserved.

    Back out a TL or SP
    If you need to back out of the update and return to the previous TL, all thats required is to boot the previous (original) BOS instance. Set the bootlist and verify that the BLV is set to the previous BOS instance (hd5).
    # bootlist -m normal hdisk0 blv=hd5 hdisk0 blv=bos_hd5 # bootlist -m normal -o hdisk0 blv=hd5 hdisk0 blv=bos_hd5

    You might also like