HP Dynamic Root Disk (DRD) manual Glossary, Booted system

Page 71

Glossary

Booted system

The system environment that is currently running — also known as the current, active, or running

environment

system environment.

CLI

Command line user interface

Clone

* (noun) - clone - a Cloned System Image . * (verb) - clone - to create a Cloned System Image.

Cloned system

A copy of the booted volume group from the system image of a booted system environment —

image

produced by the drd clone command. A cloned system image may be inactive, or the cloned

 

system image may be booted, in which case the system activities are started and the clone

 

becomes the system image in the booted system environment. When a particular system image

 

is booted, all other system images are inactive. A system administrator may modify a cloned

 

system image by installing software on it using the drd runcmd command.

DRD

Dynamic Root Disk. The collection of utilities that manages creation, modification, and booting

 

of system images.

DRD-chrooted shell

The modification environment provided by the DRD utilities for managing (swinstalling, swremoving,

 

and swverifying) software to and from an inactive system image while logged on to a booted

 

system environment. Because the POSIX shell is running in an environment provided by the chroot

 

command, modifications to the booted system environment's files are prevented. In addition, the

 

file systems of the inactive system image, mounted under the chroot directory, are available

 

for software management on the inactive system image.

DRD-safe

Refers to software packages for HP-UX, as well as to HP-UX commands. A package is DRD-safe

 

if it can be swinstalled, swremoved, and swverified on an inactive system image without modifying

 

any part of the booted system environment. There is no requirement that the package can be

 

configured on an inactive system image. Examples of components of the booted system environment

 

that cannot be changed are: the installed software, file systems, device configuration, process

 

space, kernel definition, networking configuration, users and passwords, and auditing and

 

security. A command is DRD-safe if it can be run in a DRD runcmd environment without modifying

 

any part of the booted system environment. Further information on DRD-safe is available in the

 

Dynamic Root Disk: Quick Start & Best Practices white paper, which is available at http://

 

www.hp.com/go/drd-docs.

Hot backup

See Hot recovery

Hot maintenance

The ability to perform modifications to an inactive system image using commands issued on the

 

booted system environment without affecting the booted system environment.

Hot recovery

The ability to return to a known good system environment simply by booting. That is, have a

 

backup system image standing by waiting to be used. Sometimes referred to as hot backup.

LVM

Logical Volume Manager. A subsystem that manages disk space — supplied at no charge with

 

HP-UX.

Original system

A booted system environment whose system image is cloned to create another system image.

environment

Each system image has exactly one original system environment. (That is, the booted system

 

environment at the time the drd clone command was issued.)

Rehost

The capability to boot a DRD clone of an LVM-managed Itanium-based copy of HP-UX 11i v3 on

 

a system other than the one where it was created. DRD provides the drd rehost command

 

that copies the system information file—containing hostname, IP address, and other system-specific

 

information—to EFI/HPUX/SYSINFO.TXT on the disk to be rehosted.

Root file system

The file system that must be mounted at /.

System activities

All of the running processes that correspond to programs on a booted system. This includes the

 

running kernel, all network processes, all daemons and all other processes — both system and

 

user. System activities frequently access in-memory copies of data. Thus any change to in-memory

 

data may affect system activities.

System

The combination of the system image and the system activities that comprise a running installation

environment

of HP-UX.

71

Image 71
Contents Dynamic Root Disk A.3.10.* Administrators Guide Document Part Number DRD Version Supported Operating Systems Table of Contents Glossary Index Troubleshooting DRD Support and other resourcesDRD commands Rehosting and unrehosting systemsList of Figures List of Examples Terminology Commands overviewAbout Dynamic Root Disk Conceptual overviewDownloading and installing Dynamic Root Disk Locating disks on HP-UX 11i v2 systems Cloning the active system imageActive system image Locating disks# /usr/sbin/ioscan -fnkC disk Locating disks on HP-UX 11i v3 Integrity systems# /usr/sbin/ioscan -m dsf Choosing a target disk Using other utilities to determine disk availabilityUsing DRD for limited disk availability checks Creating the clone Using drd clone to analyze disk sizeCloning the active system image Success Error Example 2-7 The drd clone command outputAdding or removing a disk Example 2-8 The drd clone command output for SAN diskUpdating and maintaining software on the clone DRD-Safe commands and PackagesSwinstall Swremove Swlist Swmodify Swverify Swjob DRD-Safe patches and the drdunsafepatchlist file Kctune Update-ux View Kcmodule Kconfig Mkkernel Swm jobUpdating and managing patches with drd runcmd Special considerations for firmware patches Patches with special installation instructionsUpdating and managing products with drd runcmd Viewing logs Mounting the inactive system image Accessing the inactive system imagePerforming administrative tasks on the inactive system image Enter the patches into a file such as Unmounting the inactive system image Compare vxconfigbackup with the clone copyUnmounting the inactive system image Page Quick start-basic synchronization OverviewTrimming the list of files to be synchronized Drd sync commandDetermining the list of files in the booted volume group Files that have changed on the clone Copying the files to the inactive clone image Drd sync system shutdown script Page Preparing the inactive system image to activate later Activating the inactive system image# /opt/drd/bin/drd activate Undoing activation of the inactive system image # /usr/bin/more /stand/bootconf l /dev/dsk/c2t0d0s2Activating the inactive system image Undoing activation of the inactive system image Page Rehosting examples Rehosting and unrehosting systemsRehosting overview Example 7-1 Provisioning a new system Rehosting a mirrored image# rm /var/opt/drd/registry/registry.xml Unrehosting overviewPage Troubleshooting DRD Page Contacting HP Support and other resourcesRelated information Typographic conventions New and changed information in this editionLocating this guide Find1 Page Drd activate command DRD commandsDRD command syntax Logverbosity=4 HAalternatebootdisk=blockdevicespecialfileIgnoreunmountedfs=truefalse Logfile=/var/opt/drd/drd.logCopyautofile option Drd clone commandReboot=truefalse Verbosity=3 DefaultCopyautofile=truefalseblockdevicespecialfile TtargetdevicefileEnforcedsa=truefalse Drd deactivate command Drd mount command Example A-1 File system mount points Drd rehost command Devicespecialfile -v-xextended option=value -x-?-Xoptionfile Extended options Drd runcmd command Extended options Drd status command Alternatebootdisk=blockdevicespecialfile Usr/sbin/swlist -l file, or Drd sync commandExcludelist= Drd umount commandAlternatebootdisk=blockdevicespecialfile Drd unrehost command Fsysteminformationfile Mirrordisk=blockdevicespecialfile Page Glossary Booted systemSystem image Index Idisk partition, 10, 11 inactive system file system