01 Aix

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 2

Flexible Installation Options

System Resource Controller (SRC)


Logical Volume Manager (LVM)
File System Management
Device Configuration

The Logical Volume Manager (LVM) allows logical volumes to span multiple physical
volumes. Data on logical volumes appears to be contiguous to the user, but might not
be contiguous on the physical volume. This allows file systems, paging space, and
other logical volumes to be resized or relocated, span multiple physical volumes, and
have their contents replicated for greater flexibility and availability.

Commands for System Administrators

AIX offers migration as a method of moving to a new release or version of the


operating system while maintaining your system configuration and user
configuration data. Migration installations preserve the root volume group and
user volume groups. New user configuration files are either merged or saved
when updated. Saved files can then be replaced by either the new or existing
files to a separate directory for the user to merge with existing files and continue
using existing files, or save existing files to a separate directory while new
configuration files are introduced and tested.

The Logical Volume Manager (LVM) consists of the logical volume device driver
(LVDD) and the LVM subroutine interface library. The LVDD is a pseudo-device driver
that manages and processes all I/O. It translates logical addresses into physical
addresses and sends I/O requests to specific device drivers. The LVM subroutine
interface library contains routines that are used by the system management
commands to perform system management tasks for the logical and physical
volumes of a system. The programming interface for the library is available to anyone
who wishes to expand the function of the system management commands for logical
volumes.

Traditionally, backups have stored data on hard disks. If you have a CD writer
and associated software, AIX gives you the option of backing up your system to
CD. Compared to other backup media, CDs are portable, cheap, and highly
reliable.
You can create a bootable root-volume group backup or user-volume group
backup.
In addition to system recovery, backups can be used to install additional systems
with the same image as the system that was originally backed up (called cloning)
or to create a customized installation CD for other machines.
You can use generic AIX backups confidently on other RS/6000 machines
without regard to hardware options.
You don't have to restore an entire backup. You can list the contents of a system
backup and choose to restore only selected files on a running system.

The Network Installation Manager (NIM) lets you centralize installation administration
for multiple machines and schedule those installations to minimize disruptions and
inconvenience.

You can choose to install all networked machines at the same time or stagger
those installations.
Within NIM, you can remain at your console while installing AIX on remote
machines. You can even run typical installations unattended.
You can install each machine with unique options or install all machines with
consistent options.
You can make a system backup to a NIM server using the mksysb command
and use that backup to install another machine (cloning).

Benefits that the LVM offers are:

Continuous data usage in the event of a drive failure: Mirroring is the process of
writing data to two or more drives simultaneously. This allows for continuous data
usage should one drive fail. LVM allows you to mirror the root volume group.
Spread I/O over multiple disks: Disk Striping allows you to spread I/O for large
reads and writes over multiple disks and allows for simultaneous read operations.
Dynamically grow file systems: Management tools allow you to add and remove
mirrors online without data interruption.
Access a volume group from more than one location using a concurrent access
volume group.

A file system is a complete directory structure, including a root directory and any
subdirectories and files beneath the directory. File systems are confined to a single
logical volume. Some of the most important system management tasks have to do
with file systems, specifically:

Allocating space for file systems on logical volumes


Creating file systems
Making file system space available to system users
Monitoring file system space usage
Backing up file systems to guard against data loss in the event of system failures
Maintaining file systems in a consistent state.

The native file system type is called the journaled file system (JFS). This file system
uses database journaling techniques to maintain its structural consistency, preventing
damage to the file system when the system is halted abnormally. It supports the
entire set of file system semantics.
Some of the benefits of a journaled file system include:

Isolate part of the file tree to work on: Each journaled file system resides on a
separate logical volume. The operating system mounts journaled file systems
during initialization. This multiple file system configuration is useful for system
management functions such as backup, restore, and repair, because it isolates a
part of the file tree so that you can work on it.
Minimize wasted space: The block size for an enhanced journaled file system
(JFS2) is specified during its creation. Smaller block sizes minimize wasted disk
space by more efficiently storing the data in a file or directory's partial logical
blocks.
Contiguous storage: JFS is an extent--based file system, allowing data to be
stored in a more contiguous manner.
Ordered storage: Directory entries are stored in alphabetic order.
I-node directory storage: Small directory entries are stored directly on the i-node,
not on disk.

Note: Journaled file system (JFS) is native to the PowerPC platform


and is not available on the IA-64 platform.
Note: Enhanced journaled file system (JFS2) is native to IA-64
platform. Although JFS2 is not native to the PowerPC platform, it is
available.

You might also like