Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method for re-installing AIX while preserving the SAP installation

IP.com Disclosure Number: IPCOM000178324D
Original Publication Date: 2009-Jan-22
Included in the Prior Art Database: 2009-Jan-22
Document File: 6 page(s) / 70K

Publishing Venue

IBM

Abstract

Described is a method to plan and deploy the SAP software installation, in a manner such that the AIX operating system, which supports the SAP installation, can be re-installed during a one hour outage, and be fully operational following the outage. There are certain types of AIX operating system installations (preservation install or complete overwrite to alter the AIX security) that would normally require a complete re-install of the SAP software. However using this method, the SAP installation is preserved.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 29% of the total text.

Page 1 of 6

Method for re-installing AIX while preserving the SAP installation

This procedure re-installs the AIX™ operating system, while preserving the SAP installation. This is useful when switching AIX security methods or when performing an AIX preservation or complete overwrite. For example, turning on Trusted Compute Base (TCB) security requires that AIX be re-installed with a complete overwrite installation. In that scenario, the SAP installation would be lost, unless following this process.

The examples used, reflect test scenarios of a P5-561, Solution Manager 4.0 system, SAP SID: PUG, contained in three volume groups: rootvg, sapvg, and db2vg. Remember to substitute your SAP SID for PUG, used in these examples.

These techniques are disruptive to the running SAP System, but can be used to reduce the system outage duration. They can be applied to AIX versions older than AIX6.1, as well as Virtual I/O Servers (VIOS). Additionally, the procedure describes using Alt

_

                                                    Disk cloning, so that a user has a second copy of AIX retained without updates. If for some reason it is necessary to reboot the original AIX image, it is available.

Begin the process with an AIX NIM install to an alternate disk, by installing the alt

bundle.

Next, choose from the three installation types: migration, preservation, or complete overwrite.

Complete overwrite may seem like overkill; but if one wants to enable a different security level, (e.g. TCB and CAPP/EAL4+ install) or move from local disks to SAN disks, these types of changes are best done with an overwrite installation.

Preservation installation

The preservation installation will preserve /home. This lets a user re-install on the same or newer AIX, and saves the non-rootvg /etc/filesystems.

This could be useful in a "beta test" situation where a user will receive updated AIX builds to try, and do not want to re-install SAP each time.

Complete overwrite installation

The complete-overwrite installation lets a user install AIX on the same, older or newer level. This preserves nothing, so some added steps are required, and will be detailed below, where different from the preservation installation. Again, because rootvg is first cloned, one stills has the original AIX version to use, if needed. In a nutshell, it is identical to the preservation method, except

Copy /home to /db2/temp/ (a non-rootvg filesystem) so that users, created by ' sapinst', can have the existing /home restored.

Preserve the non-rootvg volume groups (e.g. sapvg and db2vg), with varyoffvg and exportvg.

Installation details

The example detailed here demonstrates the AIX re-installation of a P5-561, Solution

1

_disk

Page 2 of 6

Manager 4.0 system, SAP SID: PUG, contained in three volume groups: rootvg, sapvg, and db2vg.
1. From the NIM Client, PUG, begin the clone:
smitty install alt disk clone rootvg to another hdisk
2. In this optional step, a user would reboot to the newly cloned disk, and...