IBM Tivoli Storage Manager for System Backup and Recovery - SysBack README.udf.dvdcd.txt Version 5, Release 6, Modification 5, Fix 0 (5.6.5.0) Licensed Materials - Property of IBM 5608-SYS December 17, 2004 ======================================================================= This README is divided into the following sections: 1. $REQ: Hardware & Software Requirements 2. $SPACE: Space Considerations 3. $LIM: Limitations Related DVDs Using UDF Strctured Backups 4. $MED: Media Considerations 5. $SPE: Speed Considerations 6. $REST: Information on restoring from UDF structured DVD Backups 7. $BOOT: Documentation Updates 8. $SYN: mksbcd Syntax for Creating UDF Structured DVD Backups 9. $EXM: Examples ======================================================================= REQUIREMENTS SOFTWARE: Backups using the UDF structure are only available to DVD media and when using AIX 5.2 and higher. (i.e. to mount and read) ISO / UDF Format: Local Backup & Restore Supported Configurations: Client_4.3 ISO only Client_5.1 ISO Only Client_5.2 ISO & UDF Systems using less than AIX 5.2 can remotely send their backups to a system using AIX 5.2 or higher and store the backup image in the UDF format. However, you will not be able to use that media to to perform a local boot / install the client backup system. The local client to be installed must perform a network boot or boot from non-UDF structured media, and then remotely restore from the UDF formatted backup media. ISO / UDF Format: Remote Backup & Restore Supported Configurations: Server_4.3 Server_5.1 Server_5.2 Client_4.3 ISO only ISO only ISO & UDF Client_5.1 ISO Only ISO Only ISO & UDF Client_5.2 ISO only ISO Only ISO & UDF ======================================================================= HARDWARE: SysBack supports IBM’s RS/6000 and ERserver pSeries servers. SysBack supports any DVD device that is supported by AIX and does not require it’s own proprietary drivers or software to operate. For a list of the devices explicitly tested by AIX at your operating system level, please see the file: /usr/lpp/bos.sysmgt/README.oem_writers Your choice of device must not require vendor specific software for writing and reading. Although the AIX /usr/sbin/mkcd command supports the use of GNU Utilities, or a separately purchasable software from Jodian, or the UDF filesystem structure, SysBack ONLY supports the use of the GNU Utilities or the UDF filesystem structure for reading and writing to the devices. Some newer AIX DVD devices use the IDE interface and will not support the use of the GNU utilities / ISO9660 format for writing to the device. These devices only support the use of a UDF file system for writing to the device. Please be mindful of the requirements of your specific CD or DVD device. Essentially, if AIX supports the device with the use of GNU utilities or via the UDF filesystem structure, then SysBack will also support the use of the device. ======================================================================= SPACE: Unlike backups to CD / DVD using the ISO structure that require 3 large disk staging areas, backups to DVD using the UDF structure does not require nearly as much staging space because you can choose to write directly to the media (using the -K flag). However, if you choose not to write directly to the media, or you are writing directly to the media *and* the backup image will not fit on a single DVD, there will be 1 disk staging area. The backup_image is generated and then written to a filesystem. The default name of the filesystem is /mksbcd/backup_image. You also have the choice to specify an existing filesystem name of your choosing. The size of this filesystem must be equal to the size of your backup. For example: If you are backing up rootvg only, and you have a 4 GB root volume group, this file system will have to be 4GB in size. Likewise, if you are backing up rootvg and datavg, where rootvg is 4 GB and datavg is 7 GB, this file system will have to be 11 GB in size. ======================================================================= LIMITATIONS: Many pSeries and RS/6000 systems require certain levels of microcode to be installed in order to boot and install from UDF formatted DVD media. Please check your system hardware documentation and/or the AIX README files in /usr/lpp/bos.sysmgt if you have any questions about your machine's requirements. Also, see and additional limiation in the "SPEED" section below. ======================================================================= MEDIA: Any type of media (blue vs. gold, and multiple write) is supported by SysBack. However, testing proves that the better the quality of the media (usually the more expensive media) yields better results with the writing, reading, and booting. Therefore, just as with tape media, the reliability of your backups depends greatly on the quality of your media. Refer to your individual vendor’s specifications for information on media suggestions and requirements. SysBack imposes no media requirements beyond any requirements dictated by the device manufacturer. ======================================================================= SPEED: Our testing shows that the use of the UDF filesystem for writing to DVD media is inherently slow. In fact, UDF DVD backups are considerably slower than a backup of the same data, on the same system, under the same conditions while writing in the ISO format. This is not something that SysBack can control or influence. Please consider the trade off between speed and staging area space needed when making a choice between UDF formatted backups and ISO formatted backups. ======================================================================= RESTORE: Restoring data from a UDF formatted DVD is no different than restoring data stored on tape. The same options for restoring portions of data are still available: Non-rootvg volume group level File system level Logical volume level File or directory level Additionally, UDF formatted backups to DVD will have a "backup ID" which is like the "squence number" for tape backups. This is because you may stack or append UDF formatted backups to DVD media when previously written to by SysBack. Just as with all other SysBack backup media types, the /usr/sbin/remakevg command will read DVD media backups and allow you to recreate volume groups, file systems, or logical volumes in the same manner as if the data was stored on tape or in file images. You may also use the same SMIT menu restore options as well. ======================================================================= BOOT/INSTALL: You may boot and install from a UDF formatted DVD just as you would with a tape using SysBack. You can also boot from DVD and perform a network install as well. Essentially, the DVD devices may be used in any boot / restore / install combination. For detailed examples of media boot / install combinations, please refer to Page 5-5 in the SysBack Installation and User's Guide. ======================================================================= REMOTE BACKUPS, RESTORES and INSTALLS: When you perform a backup, restore or system install to/from a remote DVD/CD device, you must use the same version, release, modification and fix between both the server and client systems. ======================================================================= mksbcd <---------flags/options----------> vg1 vg2... STANDARD FLAGS: -f device: Specify CD/DVD device in the form of /dev/cd0. This flag is required. Note: The device specified with this flag can not be the same device specified when the optional -s pkg_source_dir is used. If the device is located on a remote host, you must also specify either the '-H' or '-h' flag. The SMIT menu field equivalent to this flag is: "Device Name". -T C|D: Specify the device / media type. "C" represents CD media and "D" represents DVD media. Select one. If this flag is not specified, the process will attempt to determine the type of media based on the device specified with the -f device flag. This flag is optional. The SMIT menu field equivalent to this flag is: "Media Type?". -t "I|U": This flag specifies whether this backup will be ISO9660 formatted or written using a UDF file system. There is no SMIT menu field equivalent to this flag. This option is set via a selection menu when selecting to backup to CD /DVD in SMIT. Note: CD/DVD backups using a ISO structure are described in Chapter 5 of the SysBack Installation and User's Guide. -B : Creates a Boot only CD/DVD. No backup data will be generated. This flag is optional. The SMIT menu field equivalent to this flag is: "Create a Boot only CD/DVD?" -D: Sets the environment variable SBDEBUG=1 to enable debugging of SysBack programs. This flag is optional. The SMIT menu field equivalent to this flag is: "Debug Ouptut?". -e: Estimates the space needed only. This is like the “Preview Only” option with the AIX installp command. This flag is optional. The SMIT menu field equivalent to this flag is: "Estimate Space Needed?". -z: size Specify the media size in MB to override default values. Default DVD size is 4188 MB (4.09 GB). If the size of your media is double sided, only specify the size of one side of the media, not the total aggregate. This flag is optional. The SMIT menu field equivalent to this flag is: "Media Size". -G "chrp": Specify the platform type of the system where the DVD will be utilized. This flag is optional. If you are creating the DVD on the system where it will be used to boot and install, it is not necessary to specify this flag as the process will default to the current platform type. For example: If you were creating this DVD on an F50, it would be created to support the CHRP platform. REMINDER: UDF formatted DVD backups are only supported on AIX 5.2 systems. AIX 5.2 does not support the RSPC and RS6K platform types anymore. Since the process will default to the platform of the system being backed up, and only chrp can use this backup type, the flag is not required. This flag exists for the ISO formatted backups that were developed prior to the UDF support. -s pkg_source_dir: Specify the device or directory containing AIX device and/or kernel support file sets in the bffcreate format for use in either creating boot images or for use as Post Install Device support. This flag is required with the "-G all" flag and optional with any other -G flag combination. See the -G flag for additional details. The SMIT menu field equivalent to this flag is: "Location of Software Packages to copy to CD/ DVD". -l package_list: Specifies a file that contains a list of additional software packages that will be stored in the /usr/sys/inst.images subdirectory of the cd_fs file system. The -l flag requires the use of the -s package_source_dir as these packages will be copied from that file system or device. This would be useful when there are AIX file sets that you would like to have installed, but are not considered required device or kernel support file sets. You may also store other third party software product that you would like to be automatically installed. The SMIT menu field equivalent to this flag is: "File with list of packages to copy to CD/DVD". -m backup_image: Specify an existing backup_image file system that contains a single, previously created backup image. The mksbcd command will then use this image rather than running a new backup during the mksbcd process. Do not specify the "-M backup_image" when using this flag. The SysBack backup utilized with this flag had to have been originally backed up to a file using and the /usr/sbin/sysback command *AND* have used the -2, "-z cdsize", and "-Z maxsize" command flags. This flag is optional. The SMIT menu field equivalent to this flag is: "Exiting Backup Image". -M backup_image: Specify the name of an existing filesystem to be used in place of the default backup_image file system. This will hold the backup image created by the mksbcd backup process. You must ensure that there is enough space in this filesystem as outlined in the section entitled “Space”. If this flag is not specified, the default backup_image file system created is /mksbcd/backup_image. If there is not enough space in this file system, the mksbcd command will enlarge the file system with the AIX /usr/sbin/chfs command to make it large enough. If the chfs command fails, then so will mksbcd. Also, this file system will not be automatically removed by the mksbcd command. However, it’s contents will be removed unless you specify the "-R M" flag. This flag is optional. The SMIT menu field equivalent to this flag is: "File system to store Backup Image". -R M: Specify this flag when you do not want the mksbcd process to remove the defaultly created backup image filesystem. The "-R C" and "-R I" flag combinations are not supported for UDF formatted backups to DVD and are therefore not explained here. This flag is optional. The SMIT menu field equivalent to this flag is: "Do not remove the final CD images". -N [S|V|L|F|D]: Use this flag to specify the backup type to write to the media: S -- System V -- Volume Group F -- Filesystem L -- Logical Volume D -- File/Directory The default is to perform a Full System Backup. This option is set via a selection menu option when selecting to backup to CD /DVD in SMIT. -n: Using this flag will cause the mksbcd process to append data to an existing UDF filesystem (aka the DVD). This flag will cause the DVD to be mounted only so that no data on the DVD is lost. This flag is only valid with a previously UDF formatted DVD. This SMIT menu equivalent to this flag is: "Append Yes" NOTE: If this flag is not used, then the mkscbcd backup process which effectively erases all data on the DVD. -K: Use of this flag causes the mksbcd process to write directly to DVD (i.e. the backup is not staged to the -M backup_image_ dir) The backup images are copied directly to the UDF filesystem provided the backup image will fit on a single DVD. The SMIT menu equivalent is "Backup Directly to DVD?". -c: termdev Specify this flag to indicate the name of a terminal device on which to display volume prompt messages for multi-volume backups. This may be used for local or remote backup volume prompting. Example device names: /dev/console (System console /dev/tty0 (ASCII Terminal) /dev/pts/1 (Usually a window in an AIXwindows environment.) This flag is optional. The SMIT menu field equivalent equivalent to this flag is: "Device name for remote volume prompt". -V vgname: Specify this flag when you do not want the default backup_image filesystem created in the rootvg volume group. This only applies to locally created filesystems. This flag only applies when you are not writing the backup directly to DVD (see -K flag). The SMIT menu field equivalent to this flag is:"Local Volume Group for creation of file systems". -F vgname: Specify this flag when you do not want the default backup_image filesystem created in the rootvg volume group. This applies to creating the filesystem on a remote system and would only be specified in conjunction with the "-H host" or "-h host flags". This flag is optional. This flag only applies when you are not writing the backup directly to DVD (see -K flag). The SMIT menu field equivalent to this flag is: "Remote Volume Group for creation of file systems". -H "hostname": Specify this option when performing backups to a remote DVD device. This will create the backup_image filesystems on the remote system. You may optionally use the "-F vgname" flag to specify which volume group on the remote system in which the filesystem will be created. The SMIT menu field equivalent to this flag is: "Hostname of CD/DVD Server". -h "hostname": Specify this option when performing backups to a remote DVD device. This will create the backup_image filesystem on the local system. You may optionally use the -"F vgname" flag to specify which volume group on the local system in which to create the backup_image file system. The SMIT menu field equivalent to this flag is: "Build Temp Work Space(s) on client." -U "hostname": The hostname of the data destination system on which the selected backup device or file exists. You may edit this field as necessary to specify a the hostname of a remote system not listed in the device selector dialog screen. This is useful when initiating a Pull Backup. The SMIT menu field equivalent to this flag is: "Backup Data Hostname." -Y: This flag will reset the access and modification time of the files backed up to their pre-backup values after a backup has completed successfully. -w :temporary workspace directory: Specify the fully qualified directory name of the location where you would like SysBack to create its temporary work files during this process. Work files created directly by SysBack programs will be generated in the specified location. Any AIX commands that SysBack may call will be unaffected by this option. If no directory is specified, the default workspace location is /tmp. The SMIT menu field equivalent to this flag is: "Temporary workspace directory". -L "filename": Specify the fully qualified path and filename to a file that contains a list of the items that you would like to back up. This option is required when you are attempting to specify entities that can not be displayed on the current display screen such as when using an ASCII terminal with Double-byte character set or Bi-directional languages. In all other cases, use of this option is not required as the specification of non-rootvg volume groups is indicated in the field Non-rootvg volume groups to include. The SMIT menu field equivalent to this flag is: "File containing a list of data to be backed up" Note: When specifying a file list, the file must be formatted such that each line of the file includes the fully qualified path of one file, directory, logical volume, file system, or volume group name. -X: Use this flag to exclude user data logical volumes. System logical volumes such as boot, paging, and jfs logs will not be affected by this flag. Note: If a logical volume name exists in the SysBack exclude list, it will not be included in the backup regardless of whether or not this flag is set. This flag is optional. The SMIT menu field equivalent to this flag is: "Include non-JFS logical volumes?". -x: Use this flag to display a progress indicator which shows the estimated total and elapsed time of the backup process. This flag is optional. The SMIT menu field equivalent to this flag is: "Report output type". -v: Use this flag to display a list of files as they are being backed up. This flag is optional. The SMIT menu field equivalent to this flag is: "Report output type". -P: Use this option to crate a SysBack Power Backup, a backup in which all file system data is backed up as raw logical volumes. In many cases, this will provide better performance during the backup and during installation from this backup. However, there are some limitations on related to customizing the installation. It is not possible to restore select files or directories from this type of backup. This flag is optional. Note: Logical volumes are backed up in their entirety, even if the file systems are only partially full. Therefore, this could decrease the backup and restore performance. The SMIT menu field equivalent to this flag is: "Create a Power Backup?". -p: Specifying this option will cause the data to be compressed by this system prior to writing to the backup device. You should not compress data if the device you are writing to has built-in compression capability. However, if you are writing the backup to a remote host and wish to send less data over the network, this option may be useful. However, verify that the output device does not also have compression set. Compressing data will use considerable CPU processing on this system, but will result in less data written to the backup device (in most cases) and usually better backup performance. This flag is optional. The SMIT menu field equivalent to this flag is: "Compress data before writing to media?". -k "buffer_size": The buffer size indicates the amount of data that is written to the output device in a single output operation. Using a buffer size that best optimizes a particular device can have significant performance advantages. Note: The larger the buffer size, the more memory will be used by the system during the backup. The SMIT menu field equivalent to this flag is: "Buffer size (in Kbytes)". -J: When logical volumes are recreated from a backup, you may choose to create them using the exact same physical partitions on the disks on which they currently reside. This is not possible when installing onto a disk of a different size or physical location on the system. Specifying this option will preserve the current mapping of the logical volume, but will also preserve any fragmentation that currently exists. Preserving the partition mapping is generally not useful unless the logical volumes were originally created using partition maps. This flag is optional. The SMIT menu field equivalent is: "Preserve Physical Partition Mapping". -g "vginfo_file": Specify the name of a previously created LVM information file customized for this backup. See the /usr/sbin/mkvginfo command in Appendix A, “Commands,” on page A-1 for more information on customized LVM information files. This flag is optional. There is no SMIT menu field equivalent to this flag as it is a command line only option. -E "exlcude_list": Enter the fully qualified path and file name to represent the exclude list. Specifying a file name without specifying the path name will cause SysBack to look for the exclude list file in the directory /usr/lpp/sysback. Leaving this field blank will cause the product to default to /usr/lpp/sysback/.exclude_list. This flag is optional. The SMIT menu field equivalent to this flag is: "Exclude List File Name". -d "description": You may enter in this field any information up to 60 characters. This information does not affect the backup, but is written to the backup volume label and will appear when the volume label is read. You may not use the single quote character (’) in this flag. Doing so will result in a syntax error when the backup command is executed. This flag is optional. The SMIT menu field equivalent to this flag is: "User Description". -A: This flag may be used instead of using both the Backup File ID and the Overwrite existing backup with same ID combination to generate a dynamically created backup file id based on the date and time at the command’s execution. This option is useful when the mksbcd command is scripted and schedule to run over some interval. This option takes precedence over the "Backup File ID" and "Overwrite existing backup with same ID" options and is particularly useful when scheduling this command in a backup script. This flag is optional. The SMIT menu field equivalent to this flag is: "Dynamically CreatedBackup File ID". -i "ID": A backup file ID is used to create a unique file name when writing a backup to a disk file during the mksbcd processing. The default ID contains the current date and time. You may change this field to any value you desire to describe the backup. If you choose an ID that is already in use in the specified directory, you must also choose to Overwrite existing backup with same ID, the -O flag, or the backup will fail. This flag is required. The SMIT menu field equivalent to this flag is: "Backup file ID". -O: If the specified Backup file ID, the -i ID flag, is already used to name a backup in the specified directory, you must use this flag to allow the prior backup to be overwritten. Otherwise, you must choose another unique ID or the backup will not continue. This flag is optional. The SMIT menu field equivalent to this flag is: "Overwrite existing backup with same ID?". -a [0... 9]: Select the incremental level of the backup to be performed. The backup level determines the files which will be backed up based on the date and time of the last backup made at a prior level. Leaving this field blank will perform a full backup and no incremental data will be saved. Please refer to Chapter 4 in the SysBack Installation and User's Guide for additional information on understanding incremental backups. ======================================================================= UDF FORMATTED DVD BACKUP COMMAND EXAMPLES: 1. To generate a boot only DVD (with no backup data) to the /dev/cd1 device, issue the command: mksbcd -B -TD -tU -f /dev/cd1 2. To generate a backup of the rootvg volume group to DVD using the device /dev/cd1, issue the command: mksbcd -TD -tU -f /dev/cd1 3. To generate a backup of the rootvg and datavg volume groups to a 5.2 GB (2.6 each side) DVD using the device /dev/cd0, issue the command: mksbcd -TD -tU -f /dev/cd0 -Z 2662 datavg 4. To generate a compressed rootvg backup to dvd using /dev/cd0, and is bootable by all platform types, and where the AIX product cd will act as the package source media and is loaded into /dev/cd1, issue the command: mksbcd -TD -TU -f /dev/cd0 -G all -s /dev/cd1 5. To generate a remote full system backup of rootvg and datavg to the DVD device on sysback1, and create the work space filesystem (backup_image) on that remote host in workvg, issue the command: mksbcd -TD -tU -f /dev/cd0 -H sysback1 -F workvg datavg 6. To generate a backup of the volume group named datavg to DVD using the local device /dev/cd1, and to create the default workspace filesystem (backup_image) in datavg instead of in rootvg,issue the command: mksbcd -TD -tU -NV -f /dev/cd1 -V datavg =======================================================================