System Backup and restoration of Aix learning logs (iii!

Now at 09:54, I finally watched the third part, so I can easily paste the Learning Log for my friends who are interested in it!
2006-4-29
1. Backup Type
System Backup: backs up the entire operating system, that is, backing up rootvg.
Full backup: backs up all user data and configuration files
Incremental Backup: All changes since the last backup
There are two methods for Incremental backup. The first method is to start a full backup within a week, and then backup the changes since the previous day every day. This backup method is fast, but requires a lot of backup media, which takes a long time to recover. After the backup is complete, any problem occurs in a series of media, will make the subsequent backup data useless; the second method: in a week, start to make a full backup, and then in the remaining time, backup changes since the last full backup every day. In this way, the backup time is longer than the previous method, but there is no disadvantage of the previous method.
Backup Policy
System Backup> full backup> Incremental Backup
Back up data that cannot be backed up by all system backups, including all user data, all changed system files, and all user applications Program ; All non-rootvg data.
Do not back up data: There is no change to the application file; there is no need to configure software that can be quickly installed from the installation media.
2. Backup Device-soft disk drive
/Dev/fd0 standard configuration 3.5 floppy disk drive
/Dev/fd1 second floppy disk drive (3.5 or 5.25)
A soft disk can be used as a backup, but is generally only used as a small file with a small number of backups. The format command defaults (without parameters) to format the floppy disk in the drive/dev/fd0 according to the high density, -D parameter: select the soft drive device where the floppy disk to be formatted is located, and-L option indicates low-density formatting.
Backup Device-tape drive (tape does not need to be formatted, they are formatted at factory time)
8mm tape drive (5g, 10g, 20g); the devices and media used for backup are generally tape drives and tapes; the tape drive device is/dev/RGP, the system also generates seven sub-devices for each tape drive device:/dev/rmtx.1 to/dev/rmtx.7; their differences are:

Rootvg backup-mksysb: Only rootvg is backed up. Only mounted file systems are backed up. Boot tapes are created in backup format. The device definitions of the paging space in rootvg are saved and logical volume policies are saved, active users and applications should be minimized during Backup;
Smit mksysb creates an operating system backup. If there is a file system created by the user in rootvg, the file system will be backed up as long as it has been mounted. the user-created logical volume content and definition excluding the file system will not be backed up, backup tapes created by mksysb can be started and can be installed by Bos. When rootvg backup is restored from the tape, all file systems are recovered and logical volumes are automatically created, the file system log device is created based on the default size (a logical partition), and a page feed Space Device of the same size is generated based on the saved page feed space settings. You can use the rootvg backup generated on one system to recover to another system, provided that the two systems have the same structure, and the bus structure is different or the SMP and non-SMP systems cannot perform the above operations.
Parameters in Smit mksysb:
Creation of a map file: whether to generate an image file from a logical partition to a physical partition for each logical volume to be backed up in the volume group, this ing file ensures the same ing relationship between the logical volume policy and the logical partition to the physical partition during recovery. We recommend that you create a ing file;
Exclude files: If yes is selected, the files and directories listed in the/etc/exclude. rootvg file will not be backed up;
Make bootable backup: whether to generate a boot backup. The default value is-yes;
Expand/tmp if needed: whether to automatically expand the/tmp file system as needed. Yes is strongly recommended;
Number of blocks to write in a single output: select the data volume written each time, in the unit of 512 bytes.
Backup of a non-rootvg volume group: Smit savevg
3. Restore rootvg backup
Start mksysb tape by following the steps for installing the operating system from tape

 

Restore A non-rootvg volume group backup: Smit restvg. There is a parameter, shrink the filesystems: whether to limit the space to the minimum value that can accommodate all files when creating each file system, instead of the file system size during backup, the default value is no. This is the only method when the/usr file system needs to be reduced.
Backup by file name-smit backfile
4. other backup commands
Tar command:
Create a backup: tar-CVF device file1 can be backed up to tape or disk, and directory tree can be backed up, for example, tar-CVF/dev/rmt0/home
Backup Recovery: tar-xvf device file1 restores part or all of the files or directories in the backup media. When restored as a root user, all file permissions and owner information can be restored. For example: tar-xvf/dev/rmt0/home/team01/mydir
Display and verify the content on the backup media: tar-tvf Device
Simulate the tar-x operation, but does not actually restore any files.
Cpio command:
Create a backup: cpio-ov <listfile> Device
-O Id output; file name list read from standard input; generated backup output to standard output device; for example: Find/home-print | cpio-ov>/dev/rmt0
Backup Recovery: cpio-ivdm </dev/rmt0, where-I indicates input,-d Indicates Directory creation, and-M indicates that the modified time after file recovery is equal to the backup value.
Display and verify the content on the backup media: cpio-ITV <Device