aix文件系统的备份与修改

AIX备份AIX备份使用 #smit mksysb 备份AIX系统1. 一次完整的备份日志#tail /smit.log[Jul 07 2009, 18:27:59]Command_to_Execute follows below:>> /usr/bin/mksysb '-i' /dev/rmt0Output from Command_to_Execute follows below:---- start ----Creating information file (/image.data) for rootvg. Creating tape boot image......bosboot: Boot image is 37774 512 byte blocks..Creating list of files to back up..Backing up 253800 files..............................24 of 253800 files (0%)..............................34 of 253800 files (0%)..............................954 of 253800 files (0%)..............................1783 of 253800 files (0%)..............................4164 of 253800 files (1%).............................. ...................17451 of 253800 files (6%)..............................19630 of 253800 files (7%)..............................20501 of 253800 files (8%)..............................21455 of 253800 files (8%)..............................41969 of 253800 files (16%)......................cannotaccess ./usr/IBM/WebSphere/PortalServer/log/SystemOut_09.07 .07_16.52.51.log: A file or directory in the path name does not exist.179375 of 253800 files (70%)..............................197964 of 253800 files (78%)..............................239358 of 253800 files (94%)....cannot access ./usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs /exoa1/SystemOut_09.07.07_17.52.50.log: A file or directory in the path name does not exist...........................243252 of 253800 files (95%)..............................245365 of 253800 files (96%)..............................245365 of 253800 files (96%)..............................252065 of 253800 files (99%).....................0512-003 mksysb may not have been able to archive some files.The messages displayed on the Standard Error contained additionalinformation.bosboot: Boot image is 37774 512 byte blocks.---- end ----[Jul 07 2009, 21:50:29]2. 备份的命令# smit mksysb# /usr/bin/mksysb -i /dev/rmt0不想备份的目录写在 /etc/exclude.rootvgbash-3.2# more /etc/exclude.rootvg (内容如下)/IMIS_SOFT/3. 显示备份内容A. 要列出位于缺省设备 /dev/rmt0 下的系统备份内容，请输入：# lsmksysbB. 显示备份的内容# lsmksysb -f /dev/rmt0.1C. 显示指定目录的内容# lsmksysb -l -f /tmp/mybackupD. 要验证 /dev/rmt0 中的卷组备份磁带的每个头的可读性，请输入：# lsmksysb -V -f /dev/rmt01. 磁带能否重复利用？答：不能，重新备份会覆盖以前的内容。

Aix备份流程图BOS Boot Image：bosboot命令创建，包含启动系统需要的系统的内核和设备驱动mkinsttape image：包含./tapeblksz, ./bosinst.data, and ./image.data三个文件./tapeblksz包含mksysb创建的磁带机的block size./bosinst.data 恢复时，用户交互信息存储在这里（相当于安装程序）./image.data包含rootvg里面的fs和lv的sizes, names, maps, mount points等信息。

备份时，可以用mksysb -i来产生一个新的image.datadummy .toc：The dummy Table Of Contents (TOC) is used to have the mksysb tape contain the same number of images as a BOS install tape.rootvg data ：包含所有rootvg上会被mksysb备份的数据image.data的组成：image.data由几个部分组成1。

SHRINK：如果这部分为YES，恢复时会收缩所有文件系统。

2。

BOSINST_FILE：BOS INSTALL结束后，要执行的文件或命令的全路径3。

EXACT_FIT：YES:表示根据mksysb -m 产生的pp map来确的lv在不同pv上的分布mksysb -e 会根据/etc/exclude.rootvg的设置，排除一些文件，目录，文件系统等备份过程中需要8-12MB。

mksysb -X会自动扩展/tmpUse the -p flag (disable software packing of backup) only if you know that your tape drive does not do compression.使用smitty mksysb进行备份，会留下日志。

用Sysback备份和恢复AIX系统1、环境介绍1.1、硬件环境介绍1.1.1、服务器端硬件——IBM P5 570、16路处理器、64G内存——8块内部硬盘：两块分给rootvg，其余为TSM备份/归档存储池卷1.1.2、客户端硬件——IBM P5 550、4路处理器、16G内存——8块内部硬盘：两块分给rootvg，其余备用1.2、软件环境介绍1.2.1、服务器端软件A、TSM Server 5.5——gsksa.rte——tivoli.tsm.devices.acsls——tivoli.tsm.devices.aix5.rte——tivoli.tsm.license.aix5.rte64——tivoli.tsm.license.cert——tivoli.tsm.loc.server.ela——tivoli.tsm.msg.en_US.devices——tivoli.tsm.msg.en_US.server——tivoli.tsm.server.aix5.rte64————tivoli.tsm.server.webconB、Sysback 6.1——tivoli.tsm.client.api.aix43.32bit ——tivoli.tivguid——tivoli.tsm.client.sysback.license.cert ——tivoli.tsm.client.sysback.license.rte ——tivoli.tsm.client.sysback.rteC、TSM Client5.5——gsksa.rte——gskta.rte——tivoli.tsm.client.api.32bit ——tivoli.tsm.client.api.64bit ——tivoli.tsm.client.ba——tivoli.tsm.client.jbb——tivoli.tsm.filepath_aixD、NIM Master 6.1——bos.sysmgt.nim.master1.2.2、客户端软件A、Sysback 6.1——tivoli.tsm.client.api.aix43.32bit ——tivoli.tivguid——tivoli.tsm.client.sysback.license.cert——tivoli.tsm.client.sysback.license.rte——tivoli.tsm.client.sysback.rteB、TSM B/A Client 5.5——gsksa.rte——gskta.rte——tivoli.tsm.client.api.32bit——tivoli.tsm.client.api.64bit——tivoli.tsm.client.ba——tivoli.tsm.client.jbb——tivoli.tsm.filepath_aixC、NIM Client——bos.sysmgt.nim.client注意：所有软件集的选择请严格按照上面的名称，如有不同，可能造成安装失败甚至配置不成功等很多问题。

AIX的备份和恢复1.mksysb命令1.1概述mksysb命令针对rootvg上已经mount的file system建立一个bootable image，该文件是backup-file格式，用户定义的paging space、未mount的file system、raw device不包含在备份集中。

1.2备份文件的格式BOS boot image + mkinsttape image + dummy.toc + rootvg data...~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~BOS boot image ：包含从mksysb 磁带引导所需的系统内核和设备驱动的副本。

由bosboot 命令创建。

mkinsttape image ：有三个重要的文件./tapeblksz 文件包含mksysb 命令运行时设定磁带驱动器的块大小。

./bosinst.data 文件包含自定义的BOS 安装过程和指示BOS 安装程序如何运行。

执行mksysb 命令前可自定义该文件，或映像备份完成后使用程序自定义该文件。

./image.data 文件包含描述BOS 安装过程中安装的映像的信息。

这些信息包括逻辑卷的大小、名称、映射以及在rootvg 的安装点。

可在使用mksysb 命令之前自定义该文件，或在备份期间运行mksysb -i 命令在磁带上生成一个新的 ./image.data 文件。

mkszfile 命令生成 ./image.data 文件。

./image.data 文件以stanza 格式安排。

table of contents：使mksysb 磁带包含和BOS安装磁带同样数目的映像。

rootvg data ：包含mksysb 命令备份的rootvg 卷组上的所有数据。

mksysb 命令使用backup 命令保存rootvg 上安装JFS 数据内容，除了raw 数据。

AIX Backup Performance Best Practices and Guidelines on IBM Power Systems Virtual ServerIBM Power Systems Performance TeamAuthorsSaritha VinodGayathri M04 March 2022Table of Contents1.Introduction (2)1.1File level Backup for AIX VMs in PowerVS Using Spectrum Protect (2)2.IBM Spectrum Protect Configuration and Tunings for Backup (3)2.1Spectrum Protect Configuration (3)2.2Spectrum Protect Server Tunings (3)3.Backup Performance Guidelines (4)3.1Backup Performance Measurements with 1Gbps DL 2.0 Link (4)3.1.1Performance Guidelines for Spectrum Protect Server-side Deduplication andCompression with 1Gbs DL 2.0 Link (4)3.1.2Performance Guidelines for Spectrum Protect Client-side Deduplication andCompression with 1Gbs DL 2.0 Link (5)3.1.3Settings and Best Practices for Spectrum Protect Client-side Deduplication andCompression (5)3.2Backup Performance Measurements with 10Gbps DL 2.0 Link (6)3.2.1Performance Guidelines for Spectrum Protect Server-side Deduplication andCompression with 10Gbs DL 2.0 Link (7)3.2.2Performance Guidelines for Spectrum Protect Client-side Deduplication andCompression with 10Gbs DL 2.0 Link (7)4.Acknowledgements (8)1.IntroductionThis document specifies the best practices, guidelines, and tunings for optimum performance of file level backup for AIX virtual machines on Power Systems Virtual Server (PowerVS) using IBM Spectrum Protect. Based on benchmarking results with the best practices and tunings discussed in this document, below table provides a summarized view of the guidelines for backup rates that are achievable on different network link bandwidths. The sections below detail each of these different configs and some of the trade-offs to be considered while using these backup settings.1.1File level Backup for AIX VMs in PowerVS Using Spectrum ProtectFor file level backup, IBM Spectrum Protect Server is installed and configured on an x86 Linux VSI located in the IBM Cloud Classic Infrastructure area of IBM Cloud. PowerVS AIX Virtual Server Instance connects to the Spectrum protect Server using the Direct Link 2.0 (DL 2.0) for backup-restore operations and can access Cloud Object Storage using an internal endpoint for data storage/retrieval as depicted in Figure 1 below. The installation details of Spectrum protect is outside the scope of this document. Refer to this link for a tutorial on the details of installation of Spectrum Protect for PowerVS AIX backup.https:///media/docs/downloads/power-iaas-tutorials/PowerVS_AIX_Backups_Tutorial_v1.pdfFigure 1: Backup environment using Spectrum Protect for AIX Virtual Machines on PowerVS2.IBM Spectrum Protect Configuration and Tunings for BackupThis section provides the configurations and tunings applied for IBM Spectrum Protect Server and Client.2.1Spectrum Protect ConfigurationAll guidelines and tunings mentioned in this document is using the Spectrum Protect Direct-to-Cloud Configuration, where backup data is stored directly to cost-effective IBM Cloud Object Storage (hosted within IBM Cloud).For the direct-to-cloud architectures, backup data is ingested directly into a cloud-container storage pool with a performant cloud ac celerator cache disk location tuned for a system’s ingestion workload as the initial “landing spot”. Data is then immediately, asynchronously transferred to cloud object storage while further data is also ingested into the disk staging area.Below provided configuration is used to deploy an extra-small system for IBM Spectrum Protect Server as defined in the IBM Spectrum Protect Cloud Blueprints for IBM Cloud.•Spectrum Protect Server Version 8.1.12• 4 cores Intel Xeon CPU (M1.4x32 Virtual Server Instance in IBM Cloud Classic Infrastructure) •32 GB RAM•Operating System – RHEL 8.3•Block Storage (SAN Storage Volumes)o100GB Volume (boot volume)o300GB Volume (database and active log disk)o500GB Volume (database backup and archive log disk)o1TB Volume (Cloud accelerator cache disk)•Networko1Gbps public and private network•Private IBM Cloud Object Storage endpoint (Regional)Spectrum Protect Client (Version 8.1.11) is installed on an AIX 7.2 virtual machine in PowerVS in the same Cloud region as the virtual server instance for Spectrum Protect Server. PowerVS AIX VM used for performance measurements is allocated 4 cores and 64GB memory and the CPU, memory, disk and network resources on AIX VM was mainly consumed by Spectrum protect during the backup operation. The required CPU/memory allocations on AIX VM can vary based on the workload running on VM. Backup measurements used Oracle Database type data from a workload generator on the AIX VM.PowerVS AIX VM can use either 1Gbps or 10Gbps Direct Link Connect 2.0 (DL 2.0). The Direct Link Connect 2.0 service creates a seamless connection that allows access to Spectrum Protect Server virtual instance on IBM Cloud from Power Systems Virtual Server instance.2.2Spectrum Protect Server TuningsBelow provided are the recommended tunings in general on the Spectrum Protect Server. It is recommended that below settings should be applied as soon as possible after a node is defined and before initial backups take place.•Kernel tuningso kernel.randomize_va_space = 0o vm.swappiness = 5•OS ulimit tuningso nofile = 65536•Network Settingso TCPWINDOWSIZE of 0 which is the default.•Spectrum Protect server tuningso Tune MINIMUMExtentsize parameter value from 50KB (default) to 250KB (recommended for Oracle database type workloads)o Note that, when there is a change to the extent size parameter, the subsequent first backup (irrespective of incremental or not) can take slightly longer, as further backupswould not dedup well against older backups.3.Backup Performance GuidelinesThe following sections outline the guidelines, tunings and best practices based on the backup throughput results that were measured in the IBM Cloud and PowerVS environments with the configurations described above.In some of the scenarios, multiple instances of IBM Spectrum Protect client backup sessions were initiated in parallel as mentioned in respective sections. In such case, the results presented here for backup represent the aggregate throughput experienced with the largest number of sessions tested against the system. Data sizes used for measurements varied between 250GB to 750GB.All throughput values are obtained for the actual data size specified for backup. These are the data rates reported by Spectrum Protect Client as the average aggregate throughput when backing up data to the IBM Spectrum Protect server. On ingestion, the actual quantity of data that makes it to accelerator cache disk and onwards to cloud object storage will be less, depending on the data deduplication and compression rates.3.1Backup Performance Measurements with 1Gbps DL 2.0 LinkThis section in particular talks about backup performance guidelines when using the 1Gbps DL 2.0 link between Spectrum Protect Client in PowerVS and Spectrum Protect Server in IBM Cloud. This includes two configurations – (1) with default Spectrum Protect Server-side Deduplication and Compression,(2) enabling Spectrum Protect Client-side Deduplication and Compression3.1.1Performance Guidelines for Spectrum Protect Server-side Deduplication andCompression with 1Gbs DL 2.0 LinkBy default, inline data deduplication, compression and encryption are enabled on the Spectrum Protect server. This occurs during client backup operations, data is automatically deduplicated and compressed as it is ingested into the cloud-container storage pool at the server. However, the actualbackup data size gets transferred over the network (through DL 2.0 link) from the AIX virtual machine to Spectrum Protect server on IBM Cloud.With the settings discussed above, for a full backup operation peak network utilization of ~80% and aggregate network utilization of ~72% was measured on a 1Gbps DL 2.0 link. With these settings, full backup data transfer rate of up to ~300-310 GB/hour can be attained considering 50% deduplication rates for the data being backed up using a 1Gbps DL 2.0 link. If the data deduplication rates for backed up data is higher, the backup data transfer rate per hour also can increase. The above rate is achieved with “MINIMUMExtentsize” parameter value of 250KB (mentioned as tunings in Section 2.3).3.1.2Performance Guidelines for Spectrum Protect Client-side Deduplication andCompression with 1Gbs DL 2.0 LinkClient-side data deduplication and compression can be enabled to work together with server-side de-duplication. In this case deduplication and compression of data happens at the client before the data gets transferred to the server over the network (via the DL 2.0 link). This can reduce the size of actual data transferred over network, depending on the deduplication and compression rates achieved. The steps to enable client-side deduplication and compression and best practices to be followed while doing so are discussed in Section 3.1.3 below. Following those best practices, for a full backup operation peak network utilization up to ~76% was measured on a 1Gbps DL 2.0 link with multiple parallel instances (up to 4 instances), with 50% data deduplication rate and dedup cache turned off. With these settings, full backup data transfer rate of up to ~330-530 GB/hour can be attained considering 50% deduplication rates for the data being backed up using a 1Gbps DL 2.0 link. The above rate is achieved with “MINIMUMExtentsize” parameter value of 250KB (mentioned as tunings in Section 2.3).3.1.3Settings and Best Practices for Spectrum Protect Client-side Deduplication andCompressionEnable client-side de-duplication to work together with server-side de-duplication as below:– On the Server: use below commands (replace nodename with name of the client node) update node <nodename> compression=yesupdate node <nodename> deduplication=clientorserver– On the Client: update the dsm.sys file to add these linescompression yesdeduplication yesFor a detailed description of these commands refer to Spectrum Protect documentation links below.https:///docs/en/spectrum-protect/8.1.12?topic=commands-update-node-update-node-attributeshttps:///docs/en/spectrum-protect/8.1.12?topic=reference-compressionhttps:///docs/en/spectrum-protect/8.1.12?topic=reference-deduplicationBelow provided are some best practices to use client-side data deduplication•Use compression along with deduplication at client side.•On the Client: update the dsm.sys file to add these lines•compression yes•deduplication yes•Use multiple parallel sessions to improve backup time and network utilization. This can be done by initiating multiple dsmc incr command and splitting the subdirectories between these commands. Eg :•dsmc incr /dir/subdir1/ -subdir=yes•dsmc incr /dir/subdir2/ -subdir=yes•Use the default resource utilization (RU = 2)•Use de-dup cache turned off with lower data deduplication rates.To turn off the deduplication cache from the client, edit the dsm.sys file to add this line enablededupcache no•Turn on de-dup cache when the data deduplication is higher (de-dup close to 100%) To turn on the dedupe cache from the client, edit the dsm.sys file to add this lineenablededupcache yesNOTE on client-side deduplication cache:•For applications that use the IBM Spectrum Protect API, do not use the client data deduplication cache (enablededupcache option). The dedup cache can be used with backup-archive clients. This is a restriction in IBM spectrum Protect. Please refer to this Spectrum Protect documentation link for more details on this:https:///docs/en/spectrum-protect/8.1.12?topic=throughput-tuning-client-side-data-deduplication3.2Backup Performance Measurements with 10Gbps DL 2.0 LinkThis section in particular talks about backup performance guidelines when using the 10Gbps DL 2.0 link between Spectrum Protect Client in PowerVS and Spectrum Protect Server in IBM Cloud. This includes two configurations –(1) with default Spectrum Protect Server-side Deduplication and Compression, (2) enabling Spectrum Protect Client-side Deduplication and CompressionAlso note that the extra-small configuration used for Spectrum Protect Server (described in Section 2.2) uses a x86 Virtual Server Instance in IBM Cloud Classic Infrastructure that has a 1Gbps non-rate limited link for public and private network. Hence the 10Gbps DL 2.0 link connectivity from PowerVS AIX VM to Spectrum Protect server cannot be fully utilized.With that limitation, the best practices used for backup with 10Gbps DL 2.0 link are as follows:•For server-side as well as client-side deduplication, use multiple parallel instances (below guidelines are with 4 instances) to maximize utilization of the 10Gbps link with jumbo frames enabled at client and server•To enable jumbo frames at Spectrum Protect Server (RHEL OS):•Check the current setting by running the command: “ip link show dev eth0”•Change the current setting to support 9000 MTU by running the command: “ip link set mtu 9000 dev eth0”•Change the setting so that it persists after the system is restarted. Edit the file “/etc/sysconfig/network-scripts/ifcfg-eth0”, and add “MTU=9000”•To enable jumbo frames at Spectrum Protect Client (AIX OS): (Note: change interface name below based on the actual interface used)•chdev -Pl ent2 -a jumbo_frames=yes•chdev -Pl en2 -a mtu=9000•Client-side deduplication and compression:•Use client-side deduplication and compression for data that has higher deduplication rates (50% and above).3.2.1Performance Guidelines for Spectrum Protect Server-side Deduplication andCompression with 10Gbs DL 2.0 LinkWith server-side deduplication and compression and the above settings, full back up data transfer rate of up to ~560-615 GB/hour can be attained considering 50% deduplication rates for the data being backed up using a 10Gbps DL 2.0 link. The above rate is achieved with “MINIMUMExtentsize” parameter value of 250KB (mentioned as tunings in Section 2.3).If the “MINIMUMExtentsize” parameter value is increased to 750KB, full back up data transfer rate can increase up to ~680-725 GB/hour considering 50% deduplication rates for the data being backed up using a 10Gbps DL 2.0 link.Note that using 750KB extent size could increase the network bandwidth utilization, thereby reducing the backup time taken. However, it may have other trade-offs and may not suite all types of workloads (one implication could be that de-dup rates achieved might decrease). Hence setting 250KB extent size is recommended for workloads like Oracle databases, where higher de-duplication is expected.3.2.2Performance Guidelines for Spectrum Protect Client-side Deduplication andCompression with 10Gbs DL 2.0 LinkWith client-side deduplication and compression, with de-dup cache turned off, and with “MINIMUMExtentsize” parameter value of 750KB, full back up data transfer rate of up to ~780-880 GB/hour can be attained considering 50% deduplication rates for the data being backed up using a 10Gbps DL 2.0 link.4.AcknowledgementsWe hereby acknowledge the following people for their review feedback, suggestions and support while creating these best practices guide.•Rakesh Sharma, Power Systems Virtual Server Networking•James Damgar, Spectrum Protect Systems•Jeff Tenner, Power Systems Performance•Kokil Deuri, Power Systems Performance。

网络备份网络Sysback是基于TSM API 来备份AIX 操作系统的，在备份之前要对TSM Server 和TSM Client 之间进行配置。

网络备份需要额外增加TSM软件，同时配置也较复杂，因此本次搬迁不推荐使用此方法进行备份。

磁带备份AIX mksysb命令将操作系统在线备份到磁带中（即root 卷组）。

如果系统破坏，可以使用磁带来重新安装系统到它的原始状态。

备份步骤：1.将磁带放入外置或内置的磁带机中。

2.mksysb -i /dev/rmt0恢复步骤：1.将磁带放入磁带机中。

2.开机进入SMS菜单中设置从磁带启动。

3.磁带启动后选择从磁带安装操作系统。

光盘备份使用AIX 提供的mkcd可在线备份操作系统(rootvg)成image映像文件，再将image映像文件刻录成DVD光盘用于恢复操作系统。

备份步骤：1.挂接3个存放备份映像的文件系统。

/mkcd/cd_images ; /mkcd/cd_fs和/mkcd/cd_images2.运行命令mkcd–R -S3.将备份后的image映像文件用bin模式传到windowns PC上。

4.使用刻录软件将image映像文件恢复到DVD盘上。

恢复步骤：1.将光盘放入光驱中。

2.开机进入SMS菜单中设置从光驱启动。

3.启动后选择从光驱安装操作系统。

/usr/sbin/mkcd -M '/test/image' -C '/test/cd/str' -I '/test/cd' –V 'rootvg' '-R' '-S'I l1 ISO9660 (CD format)/usr/sbin/mkcd -L -M '/test/image' -C '/test/str' -I '/test/dvd' -V'rootvg' '-R' '-S'不要用2 UDF (Universal Disk Format)/usr/sbin/mkcd -U -M '/test/image' -V 'rootvg'排除文件–emkcd -M /mkcd/image -C /mkcd/cd/str -I /mkcd/cd -V rootvg -R -S -e &mkcd-L -M /mkcd/image -C /mkcd/cd/str -I /mkcd/cd -V rootvg -R -S -e &tail -f /var/adm/ras/mkcd.logmkcd 命令用途从mksysb或savevg备份映像创建一个（或多个）多卷的 CD。

经典之AIX安装教程一、安装基本操作系统(BOS)打开计算机或在开机状态下重新启动(#reboot)将AIX安装盘放入光驱当系统自检keyboard 通过后,按"5"(从光驱引导)系统提示：Please define the system Console后,按"1"(确认终端)系统提示:Type a "1" and press Enter to use this terminal as the system console后按1(选择英语为安装语言)进入安装程序,按系统提示操作:选择" 2 Chang/show Installation Settings and Install" 其它选项不需改变,只需改以下两项：将安装方式改为"New and Complete Installation"选择所要安装系统的disk开始install。

二、设置终端类型(TTY)结束安装后,第一次启动时,系统提示选择终端类型,应选择ibm3151用"root"登录,接着出现系统设置(时间，密码等),直接退出即可#export TERM=ibm3151（设置终端类型，否则无法进入smit）#smit tty (设置终端类型，否则以后启动还会要求选择终端类型)选择chang/show characeristics of a TTY (修改)修改ENABLE LOGIN 为"enable"修改TERMINAL type 为ibm3151三、安装Bundle#smit easy_install选择INPUT device / directory for software 为[/dev/cd0]（按F4选择）选择Select a FileSet Bundle 为Server 及App-Dev(有图形设备需选Graphics-Startup)四、选择安装软件#smit进入Software Installation and Maintenance-〉Install and Update-〉SoftwareInstall and Updata from LATEST Available Software选择INPUT device / directory for software 为[/dev/cd0](按F4选择)进入SOFTWARE to install选择所需安装的软件开头有"@"符即已安装过开头有"+"符即未安装过如不装图形终端,则以"X11"开头的不装以下必须装:pat (兼容AIX 3)bos.databos.dosutil (dos utility)有关info,msg的必须装五、设置TCP/IP#lsdev -Cc adapter查看网卡设置(选择IBM 10/100 Mbps Ethernet PCI Adapter)#smit tcpip选择"Minimum Configuration & Startup"在"Available Network Interfaces"对话框中选择"en0 Standard Ethernet Network Interface"注意:如有多块网卡,根据前面查看的设置,选择正确的网卡,一般不选"et0 IEEE 802.3 Ethernet Network Interface"在HOSTNAME中填入所起的主机名(F50-CMIS).在Internet ADDRESS (dotted decimal)设IP地址(16.54.2.7)在Network MASK (dotted decimal)设掩码(255.255.255.0)在Default GATEW AY Address设网关在Your CABLE Type选择"TP"全部选定后按回车（Enter）运行六、设置VG（卷组）#smit vg选择Add a Volume Group设置V olume Grorp Name设置Physical partition Size in megabytes(PP值，一般2.2G可设4，4.5G可设8，9.1G可设16)设置Physical Volume Names(选择所需disk)全部选定后按回车（Enter）运行七、设置LV（逻辑卷）#smit lv选择Add a Logical V olumeVOLUME GROUP name中选择VG nameLogical volume NAME中填入所起的LV 的名字Number of LOGICAL PARTITIONS中填入LV大小(这里的数量为Logical Partition数量,一块LP缺省值等于一块PP)全部选定后按回车（Enter）运行八、设置File Systems#smit进入System Storage Management (Physical & Logical Storage)-&gt;File Systems-&gt;Add/Chang/Show/Delete File Systems-&gt;Journaled File System-&gt;Add Journaled File System修改本文件系统块数(Size of File System)，一块为512 Bytes修改Mount Point(为文件系统指定PA THS,如[/oracle])决定是否在系统启动时自动Mount该文件系统全部选定后按回车（Enter）运行九、安装C及C++语言查看C安装手册中安装C语言所必须先安装的软件(Software Must be Installed)#lslpp -l|grep bos.adt.include#lslpp -l|grep bos.adt.lib用上述两条命令查看这些文件是否Comitted#smit install_latest将C/C++语言安装盘放入光驱进入INPUT device / directory for software 选择"/dev/cd0 (SCSI Multimedia CD-ROM Drive)"，SOFTWARE to install按"F4"，系统显示选择安装文件选择以xlc开头的所有文件全部选定后按回车（Enter）运行十、连接7133磁盘阵列中的磁盘将7133中磁盘连上(具体连接方法可查看7133/Model600随机资料)注意:7133 SSA接口的磁盘为回路连接,从主机后SSA ADAPTER连出后从另一根线连进,此回路中所串联的硬盘即该主机所使用硬盘#cfgmgr (激活系统,配置磁盘)注意:在关机状态下连接后再开系统自动调用cfgmgr十一、系统磁盘热插拔必须将所需拔出的磁盘中所在VG中的LV(Logical Volume)与File System进行umount#lsvg -l datavg (查看datavg中的详细信息).#df -k (查看文件系统的信息)#umount /cmis (umount 文件系统cmis)#varyoffvg datavg (切断datavg)#lsvg -o (查看当前激活的VG)#exportvg datavg.(输出datavg)此时可以拿出该磁盘(该磁盘可以为内置式).将该磁盘放入另外一台主机#importvg -y datavg hdisk1(在另外一台主机上键入该命令).十二、备份策略rootvg可采用#smit mksysb 来备份datavg 中的文件系统可进入smit-&gt;System Storage Management (Physical & Logical Storage)-&gt;File Systems-&gt;Backup a File System，选定预备份的文件系统，回车确认即可datavg可采用smit命令smit vg-&gt;Back Up a V olume Group，选定预备份的vg，回车确认即可AIX安装后的基本系统设置，补丁，优化等等的东西，确实有用哈----许多用户在*作系统安装完后，不对系统进行一些基本设置，而使用系统的缺省参数。