aix文件系统的备份与修改
AIX备份恢复命令解析
ｍｋ ｙ ｂ命 令 的特 点使 克 隆 一 个 系统 镜 像 到 多个 ｓｓ
目标 系统成 为 可能 。
２ ２ 非 ｒｏｖ ． ｏ ｔｇ的备份 和恢 复
一
ｉ ｇ ． ａａ文件 ｍａ ｅ ｄ ｔ
一
ｓｖｖ 可 备 份 ｖｒｏ ａｅｇ ａｙ ｎ状 态 的 用 户 卷 组 中 已 ｍｏ ｎ 的 文件 系统 ， 不 能备份 裸设 备 上 的内容 ， 备 ｕｔ 但 该
命 令 行方式 ：
＃ ｍｋ ｙ ｂ ｍ—— ｉ ｄ ｖ ｒ ０ ｓ ｓ — ｖＶ— ／ ｅ ／ ｍｔ
主要 参 数说 明 ：
一
ｅ排 除列 在／ ｔ／ ｘ ｌｄ ．ｏ ｔｇ中 的文件 ｅｃ ｅ ｃ ｅ ｒ ｏｖ ｕ Ｉ调 用 ｍｋ ｚ ｌ ｓｆ ｅ命 令 ， 备 份 中 自 动 获 取 ／ ｉ 在 ｍ 调用 ｍｋ ｚ ｌ 令得 到 ｍａ ｓｆｅ命 ｉ ｐ文件 ＊ Ｓ ｖｖ ： ａ ｅ ｇ 用于 ｒｏ ｖ ｏ ｔｇ以外 的卷组 备 份 。 主要 参数 说 明 ：
的 系统维 护 提供 了一 个便 捷 的知 识库 ，对 提高 ＡＩ 系统 管理 人 员 的运 维水 平起 到 一定 的帮助 作用 。 Ｘ
【 关键 词】 ＡＩ Ｘ，备份 ，卷 组 ，文件 系统
中 圈分 类 号 ｔ Ｐ ０ ． Ｔ ３ ９ ３ 文 献 标 识 码 ；Ａ
ＡＢＳ ＴＲＡＣＴ Ｔｈ ｒ ｒ ｏ ｆｃ ｍ ｍａ ｄ ａ ｅ ｕ ｅ Ｏ ｂ ｃ ｕ ｎ ｔ ｅ ＵＮＩ ｓ ｓ ｅ ，ｔ ｉ ａ ｔｃｅ ｓ ｍｍａ ｉｅ ｈ ｈ ｏ ｄｔｏ ｅ ｅ ａ ｅ ａ ｌ ｔｏ ｏ ｎ ｓ ｃ ｎ ｂ ｓ ｄ ｔ ａ ｋ ｐ ｉ ｈ Ｘ ｙ ｔ ｍ ｈ ｓ ｒｉ ｌ ｕ ｒｚ ｓ ｔ ｅ ｔ ｅ ｃ ｎ ｉｉｎ
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备份及恢复
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系统完整手册
![[原创]用Sysback备份和恢复AIX系统完整手册](https://img.taocdn.com/s3/m/e0f0c568a98271fe910ef9fe.png)
用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的备份和恢复
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 备份性能最佳实践和指南说明书
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。
aix备份与恢复
dd命令读取InFile参数或标准输入，执行指定的转换，然后将转换后的数据复制到OutFile参数或标准输出。可以指定输入和输出块的大小以利用原始物理I/O。
pax命令应该是用于系统转储和2 GB以上的映像的首选存档方法。
mksysb命令在文件中或在可启动的磁带上创建根卷组的可安装映像。
-s SeekBackup
指定backup在一个多备份磁带存档上查找并恢复。-s标志仅适用于将存档写到磁带设备的情况。要正确使用-s标志，必须指定一个no-rewind-on-close和no-retension-on-open磁带设备，例如/dev/rmt0.1或/dev/rmt0.5。
-t
显示有关备份存档的信息。如果存档为文件系统格式，则将该存档中找到的文件列表写到标准输出。
-q
指示可移动介质已准备就绪。当您指定–q标志时，backup命令将继续执行而不提示您准备备份介质。按Enter键继续。
Байду номын сангаас-u
使用上次增量备份的时间、日期和级别来更新/etc/dumpdates。
-v
致使backup命令显示有关该备份的附加信息。
restore
-d
指示在File参数为目录的情况下，应该恢复该目录中的所有文件。仅当存档为文件名格式时，才可以使用此标志。
-s
指定所创建的逻辑卷在容纳文件系统的情况下具有尽可能小的大小。
tctl
-b
指定用于从磁带设备读取或写到磁带设备的块大小（以字节为单位）。
-f
指定要使用的磁带设备。
mksysb命令
mksysb命令创建rootvg卷组上所有已挂载的文件系统的可启动映像。可以使用此备份命令将系统重新安装为其原始状态。
aix 系统备份
INTER_POLICY= minimum
INTRA_POLICY= center
MOUNT_POINT= /usr
exclude files：如果选择yes，将使得文件/etc/exclude.rootvg文件中列出的文件和目录不被备份；
make bootable backup：是否生成可启动备份，一般取默认值－yes；
expand /tmp if needed：是否在需要时自动扩展/tmp文件系统，强烈建议选yes；
MIRROR_WRITE_CONSISTENCY= on
LV_SEPARATE_PV= yes
PERMISSION= read/write
LV_STATE= opened/syncd
WRITE_VERIFY= off
PP_SIZE= 4
SCHED_POLICY= parallel
--> PP = 140
BB_POLICY= relocatable
RELOCATABLE= yes
UPPER_BOUND= 32
VOLUME_GROUP= rootvg
LV_SOURCE_DISK_LIST= hdisk0
LV_IDENTIFIER= 00000001113f3c62.5
--> COPIES = 1
LPs = 70
STALE_PPs= 0
INTER_POLICY= minimum
INTRA_POLICY= center
MOUNT_POINT= /usr
MIRROR_WRITE_CONSISTENCY= on
恢复系统