Creates an installable image of the root volume group either in a file or onto a bootable tape.
The mksysb command creates a backup of the operating system (that is, the root volume group). You can use this backup to reinstall a system to its original state if it is corrupted. If you create the backup on tape or user defined file system (UDFS) capable media, the backup is bootable and includes the installation programs that are needed to install from the backup.
You can also use a mksysb image to restore another system.
The file system image is in backup-file format. The tape format includes a boot image, a bosinstall image, and an empty table of contents followed by the system backup (root volume group) image. The root volume group image is in backup-file format, starting with the data files and then any optional map files.
of the data files that the mksysb command uses
is the /bosinst.data file. If the /bosinst.data file
does not exist, the /var/adm/ras/bosinst.data file
is copied to / (root). The mksysb command
always updates the
target_disk_data stanzas in the bosinst.data file
to match the disks currently in the root volume group of the system
where the mksysb command is running.
you are using a customized /bosinst.data file
and do not want the
target_disk_data stanzas that
are updated, you must create /save_bosinst.data_file.
The mksysb command does not update /bosinst.data if
the /save_bosinst.data_file exists.
- When the mksysb command is running, ensure that system activity is minimal.
- The image that the mksysb command creates does not include data on raw devices or in user-defined paging spaces.
- If you are using a system with a remote-mounted /usr file system, you cannot reinstall your system from a backup image.
- The mksysb command might not restore all device configurations for special features, such as /dev/netbios and some device drivers that are not shipped with the product.
- The mksysb command uses the backup command to create an archive image. The mksysb command also saves the extended attributes (EA) format for any Enhanced Journaled File System (JFS2) that are being backed up. It uses the /usr/bin/mkszfile shell script to save this information.
- If you remove the
/dev/ipldevicebefore running the mksysb command, the
0301-150 bosbooterror occurs. This message, in most cases, can be ignored. Confirm the success of the mksysb command by the return code.
- If you are creating a tape backup and have encrypted file systems, you must use the -Z flag. You cannot reinstall your system from a tape backup image that contains encrypted file systems.
|-a||Does not back up extended attributes or Network File System version 4 (NFS4) access control lists (ACLs).|
|-A||Backs up Data Management API (DMAPI) file system files.|
|-b number||Specifies the number of 512-byte blocks to write in a single
output operation. When the backup command writes
to tape devices, the default is 100 for backups by name.
The write size is the number of blocks that are multiplied by the block size. The default write size for the backup command that writes to tape devices is 51200 (100 * 512) for backups by name. The write size must be an even multiple of the tape's physical block size.
|-C||Specifies whether the
/usr/lpp/bos.alt_disk_install/boot_images/bosboot.disk.chrp boot image can be
replaced with a new boot image when you create the mksysb image.
This flag should be used if the interim fixes that affect the kernel are installed on your system and if you plan to use the alt_disk_mksysb command to install the mksysb image. The bos.alt_disk_install.boot_images fileset must be installed on your system if you want to use the –C flag. You must specify the –i flag to build a new image.data file, when using the –C flag. The new bosboot.disk.chrp image is replaced by the original image at the end of the mksysb image creation. The -C flag is not available when you create the mksysb image when defining a NIM resource. A multibos Base Operating System (BOS) standby instance is not affected by the -C flag.
Note: If required, the size of the /usr file system can be increased to include the new boot image by using the -X flag with the -C flag.
|-e||Excludes files that are listed in the /etc/exclude.rootvg file
from being backed up. The rules for exclusion follow the pattern matching
rules of the grep command.
If you want to exclude certain files from the backup, create the /etc/exclude.rootvg file, with an ASCII editor, and enter the patterns of file names that you do not want included in your system backup image. The patterns in this file are input to the pattern matching conventions of the grep command to determine which files will be excluded from the backup. If you want to exclude files that are listed in the /etc/exclude.rootvg file, select the Exclude Files field and press the Tab key once to change the default value to yes.
All files are backed up relative to . (current working directory). To exclude any file or directory for which it is important to have the search match the string at the beginning of the line, use the ^ (caret character) as the first character in the search string, followed by . (dot character), followed by the file name or directory to be excluded.
If the file name or directory that is being excluded is a substring of another file name or directory, use the ^. (caret character followed by dot character) to indicate that the search must begin at the beginning of the line and use the $ (dollar sign character) to indicate that the search must end at the end of the line.
|-F filename||Specifies a previously created mksysb image from which a backup tape is created. An attempt is made to make the backup tape bootable. Additionally, this flag must be used with a tape device.|
|-G||Excludes WPAR file systems from the system backup. This flag is not valid with -N flag.|
|-i||Calls the mkszfile command, which generates the
/image.data file. The /image.data file contains details
about volume groups, logical volumes, file systems, paging space, and physical volumes. This
information is included in the backup for future use by the installation process.
You must use the -i flag. Otherwise, an older /image.data file might be saved that does not contain adequate space requirements to restore the system backup.
Note: Before you run the mkszfile command, ensure that enough space is available in the /tmp file to store a boot image. This space is needed during both backup and installation. To determine the amount of space that is needed in the /tmp file, enter the following command:
If you are using UDFS capable device named /dev/usbms0, you must specify /dev/cd0 as the device name because the /dev/usbms0 device is not supported by the bosboot command. If you use the -X flag with the mksysb command, you do not need to run the bosboot command to determine the amount of space needed in the /tmp file.
|-m||Calls the mkszfile command, with the -m flag
to generate map files.
Note: The use of the -m flag causes the functions of the -i flag to be executed also.
|-M||Creates a backup file that is intended for use with the multibos command. The -M flag backs up the /, /usr, /var, and /opt file systems. Do not use the backup to reinstall a system. You must install the bos.alt_disk_install.boot_images fileset at the same level as the system.|
|-N||Includes file systems that belong to a workload partition (WPAR) in the defined state in the system backup.
Note: To be included in the backup, all file systems that belong to a WPAR in the defined state must be in the rootvg volume group.
|-p||Disables software packing of the files as they are backed up. Some tape drives use their own packing or compression algorithms.|
|-P||Excludes files that are listed line by line in the
or /etc/exclude_packing.WPARname file from being packed.
For example, to exclude the /etc/filesystems and /usr/bin/zcat file from being packed during the mksysb backup, edit the /etc/exclude_packing.type to add on consecutive lines /etc/filesystems and /usr/bin/zcat.
In this case, the file /etc/exclude_packing.type must look like:
The -P and -p flags are mutually exclusive.
|-t argument||Specifies the path to the directory or file system that is used to create a boot image from the mksysb file that is specified by the -F flag. If the -t flag is not used with the -F flag, the boot image is created in the /tmp file by default. Approximately 100 MB of free space is required. After the boot image is created, this space is freed.|
|-T||Creates backup by using snapshots. This command applies only to JFS2 file systems.
When you specify the -T flag to use snapshots for creating a volume group backup, external JFS2 snapshots are created. Snapshots allow for a point-in-time image of a JFS2 file system and thus, do not require a system to be put into a temporarily inactive state. The size of the snapshot is 2% - 15% of the size of the file system. The snapshot logical volumes are removed when backup is complete. However, snapshots are not removed if a file system already has other snapshots. Additionally, if a file system has internal snapshots, external snapshots cannot be created and thus, snapshots are not used for creating the backup of the file system. The use of the -T flag does not affect any JFS file systems that are present in the volume group that is being backed up. These file systems are backed up in the same manner as done previously.
When you specify the -T flag, you must also specify the -i flag. If you do not specify the -i flag, an older /image.data file might not have adequate space requirements. Therefore, a failure might occur when you save data to the snapshot.
|-v||Verbose mode. Lists files as they are backed up.|
|-V||Verifies a tape backup. This flag causes the mksysb command to verify the file header of each file on the backup tape and report any read errors as they occur.|
|-x file||Excludes the file systems that are listed in the file from the system backup. File system mount points must be listed one per line.|
|-X||Specifies to automatically expand the /tmp file system if necessary. The /tmp file system might need to be extended to make room for the boot image when creating a bootable backup to tape.|
|-Z||Specifies that the Encrypted File System (EFS) information for all the files, directories, and file systems is not backed up.The -Z flag is required if you have encrypted file systems and are creating a backup on a tape.|
|Device | File||Specifies the name of the device or file.|
|0||The command completed successfully.|
|1||An error in the mksysb command use occurred.|
|2||An error in the savevg command use occurred. The savevg is a link to mksysb.|
|3||An error occurred before any file systems were mounted.|
|4||Exit because of trap.|
|5||Exit because there was no space.|
|6||Exit because a volume group name was not valid.|
- To generate a system backup and create an /image.data file
(generated by the mkszfile command) to a tape device
named /dev/rmt0, enter the following command:
mksysb -i /dev/rmt0
- To generate a system backup and create an /image.data file
with map files (generated by the mkszfile command)
to a tape device named /dev/rmt1, enter the following command:
mksysb -m /dev/rmt1
- To generate a system backup with a new /image.data file,
but exclude the files in directory /home/user1/tmp,
create the file /etc/exclude.rootvg containing
the line /home/user1/tmp/, and enter the following command:
This command backs up the /home/user1/tmp directory but not the files it contains.
mksysb -i -e /dev/rmt1
- To generate a system backup file named /mksysb_images/node1 and
a new /image.data file for that image, enter
the following command:
mksysb -i /mksysb_images/node1Note: This file is not bootable and can be installed only by using Network Installation Management (NIM).
- After running the mkszfile command
independently, to generate a system backup on the tape device /dev/rmt0,
and then to verify the readability of file headers, enter the following
mksysb /dev/rmt0 -V
- To generate a system backup file named /mksysb_images/mksysb1 to
be used with the multibos command, and to create
an /image.data file for that image, enter the
mksysb -iM /mksysb_images/mksysb1
- To generate a system backup and create an /image.data file (generated by
the mkszfile command) to a UDFS capable device named
/dev/usbms0, enter the following command:
mksysb -i /dev/usbms0
|/usr/bin/mksysb||Contains the mksysb command.|