Basic patch execution on HP-UX
Tuesday, February 26, 2008
1. Donwload the required package
2. Make an OS ignite backup
For a virtual server, the ignite backup can be stored in HDD with the command below
# make_net_recovery -s svr6601 -v -x inc_entire=vg00 -x exclude=/var/adm/crash -a svr6601:/var/opt/ignite/clients/svr6604
make_net_recovery
creates a system recovery archive and stores the archive on the network.
Option
-s
Specifies the hostname of the Ignite-UX server. The onfiguration files, defaults and contents files for the client system will be written to the Ignite-UX server in /var/opt/ignite/clients/0xLLA/recovery. The make_net_recovery tool will NFS mount the per-client directory to access this information.
-v
Display verbose progress messages while creating the system recovery archive. Includes information such as which volume groups/disks will be included in the system recovery archive.
-x inc_entire=disk|vg_name
Includes all file systems contained on the specified disk or volume group. Use a block device file (e.g.,"/dev/dsk/c0t5d0") when specifying a whole-disk (non-volume manager) file system. Use the volume group name (such as vg00) when you want all file systems that are part of that LVM volume group to be included in the archive.
-x exclude=file|directory
Excludes the file or directory from the archive. When a directory is specified, no files beneath that directory will be stored in the archive. If the excluded directory is an unmounted file system shown in the /etc/fstab file, a WARNING ("Filesystem xxx is not mounted. It will be ignored.") message will be displayed.
3. Unpack the patch file, assuming we are unpacking the USB driver 11.23_USB-00_C.01.04.06.001.shar. A new file *.depot will be created after unpack.
# sh 11.23_USB-00_C.01.04.06.001.shar
4. Install the patch
# swinstall -s 11.23_USB-00_C.01.04.06.001.depot
A GUI patch management will pop-up. Follow the installation screen, make sure that the patch packages is in READY mode. Do not proceed if it is in READY & WARNING mode. The WARNING needs to be rectify before proceeding. Please note a server reboot will be require if it touches on the kernel.
2. Make an OS ignite backup
For a virtual server, the ignite backup can be stored in HDD with the command below
# make_net_recovery -s svr6601 -v -x inc_entire=vg00 -x exclude=/var/adm/crash -a svr6601:/var/opt/ignite/clients/svr6604
make_net_recovery
creates a system recovery archive and stores the archive on the network.
Option
-s
Specifies the hostname of the Ignite-UX server. The onfiguration files, defaults and contents files for the client system will be written to the Ignite-UX server in /var/opt/ignite/clients/0xLLA/recovery. The make_net_recovery tool will NFS mount the per-client directory to access this information.
-v
Display verbose progress messages while creating the system recovery archive. Includes information such as which volume groups/disks will be included in the system recovery archive.
-x inc_entire=disk|vg_name
Includes all file systems contained on the specified disk or volume group. Use a block device file (e.g.,"/dev/dsk/c0t5d0") when specifying a whole-disk (non-volume manager) file system. Use the volume group name (such as vg00) when you want all file systems that are part of that LVM volume group to be included in the archive.
-x exclude=file|directory
Excludes the file or directory from the archive. When a directory is specified, no files beneath that directory will be stored in the archive. If the excluded directory is an unmounted file system shown in the /etc/fstab file, a WARNING ("Filesystem xxx is not mounted. It will be ignored.") message will be displayed.
3. Unpack the patch file, assuming we are unpacking the USB driver 11.23_USB-00_C.01.04.06.001.shar. A new file *.depot will be created after unpack.
# sh 11.23_USB-00_C.01.04.06.001.shar
4. Install the patch
# swinstall -s 11.23_USB-00_C.01.04.06.001.depot
A GUI patch management will pop-up. Follow the installation screen, make sure that the patch packages is in READY mode. Do not proceed if it is in READY & WARNING mode. The WARNING needs to be rectify before proceeding. Please note a server reboot will be require if it touches on the kernel.
