IBM Tivoli Storage Manag e r for System B acku p and
Recovery
Installation and User’s Guide
Version 5 Release 6
GC32-9076-01
IBM Tivoli Storage Manag e r for System Backup and
Recovery
Installation and User’s Guide
Version 5 Release 6
GC32-9076-01
Second Edition (April 2003)
This edition notice applies to the IBM Tivoli Storage Manager for System Backup and Recovery Version 5 Release 6
(program number 5698-SYS) and to any subsequent releases until otherwise indicate in new editions or technical newsletters.
This edition replaces GC32-9076-00. IBM Tivoli Storage Manager for System Backup and Recovery will be referred
to as “SysBack” in certain text within this document.
The following paragraph does not apply to the United Kingdom or any country where such provisions are
inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
MANUAL “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. Some states do not allow disclaimer of expressed or implied warranties in certain
transactions; therefore, this statement may not apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of this publication. IBM may make
improvements and/or changes in the product(s) and/or program(s) described in this publication at any time.
Requests for copies of this publication and for technical information about IBM products should be made to your
sales office or the IBM Branch Office serving your locality.
You feedback is important in helping to provide the most accurate and high quality information. If you have
comments about this book or any other IBM Tivoli Storage Manager documentation, please see “Contacting
Customer Support” on page ix.
IBM and AIX are registered trademarks of International Business Machines Corporation.
Chapter 11. Changing the Volume
Group, Logical Volume and
Filesystem Attributes........11-1
Selecting Physical Volumes for Volume Groups11-2
Change Physical Volume Attributes ......11-4
Changing Volume Group Attributes......11-4
Selecting Physical Volumes for Logical Volumes11-8
Changing Logical Volume Attributes .....11-9
Changing Filesystem Attributes .......11-16
Advance Install Options .........11-20
Chapter 12. System Installation and
Maintenance ...........12-1
RecoveryInstallation ..........12-1
No-promptInstallation..........12-1
HandlingInstallationErrors........12-2
The SysBack Installation and Maintenance Menu12-2
Changing the Installation Device.....12-3
Changing Volume Group & Logical Volume
Information.............12-7
Installing the System with Current Settings12-8
Utilities Menu...........12-11
Rebooting the System Menu .......12-18
Chapter 13. Network Boot/Installation
Configuration ...........13-1
Classic Network Boot and NIM Resource Boot13-1
Classic Boot............13-1
NIM Resource Boot ..........13-2
Classic Network Boot ..........13-2
Accessing and Configuring the Classic Network
Boot Menus.............13-2
Configuring or Updating a Network Boot
Image ..............13-3
Adding or Changing a Network Boot Client13-3
Setting the Network Install Client Defaults . . 13-5
Rebuilding Network Boot Images .....13-9
Removing a Network Boot/Install Client . . . 13-9
NIM Resource Boot ...........13-10
Accessing and Configuring the NIM Resource
Menus..............13-10
Installing SysBack into a SPOT Resource. . . 13-10
Querying for SysBack Installation in SPOT
Resource.............13-12
Adding or Changing a Network Boot Client13-12
Rebuilding Network Boot Images .....13-13
Removing a Network Boot/Install Client13-13
Initiating an SP Node Boot and Install . . . 13-13
Chapter 14. RS/6000 Scalable
POWERParallel Systems
®
(SP) Boot
and Install Utilities .........14-1
Advantages of the SysBack SP Boot and
Installation Utilities ...........14-1
How SysBack works with NIM on the SP System14-2
Special Assumptions ...........14-2
Accessing the SP Boot and Install Options. . . 14-3
Completing the Initiate SP Node Boot and Install
Menu................14-3
Unprompted and Prompted Installations ....14-4
TroubleshootingTips ..........14-4
Chapter 15. Integrating to IBM Tivoli
Storage Manager.........15-1
Prerequisites, Limitations, and Exclusions....15-1
BasicSetupandConfigurationTasks.....15-2
Register a TSM Node .........15-2
Install the API Client.........15-2
Configure the TSM Client System Options File15-2
Set TSM Environment Variables ......15-3
CreatetheTSMVirtualDevice......15-4
Additional Configuration for Bare Metal
Recovery .............15-4
Creating, Listing, Changing, and Removing the
TSMVirtualDeviceforSysBack.......15-4
CreatingaTSMVirtualDevice......15-4
Listing a TSM Virtual Device .......15-6
Changing the TSM Virtual Device .....15-7
RemovingtheTSMVirtualDevice.....15-9
Performing Backups to a TSM Server .....15-11
Listing and Verifying Backups in a TSM Server15-11
Querying Backups and TSM Management Classes 15-11
Querying Backups ..........15-11
Querying Current Management Class
Bindings.............15-15
Querying File Spaces on the TSM Server. . 15-16
Binding and Rebinding Backups to TSM
Management Classes ..........15-17
Binding Backups..........15-17
Rebinding Backups ..........15-18
Excluding Objects from Backups ......15-18
Restoring Backups from a TSM Server ....15-18
Configuring Network Boot Options for a TSM
BareMetalRecovery..........15-18
Bare Metal Recovery and System Reinstallation
fromaTSMServer...........15-21
Additional Information Resources .....15-25
Using Multiple Backup and Restore Sessions15-25
Problem Determination .........15-26
TheSysBackCommandOutput......15-26
The SysBack Activity Log........15-26
SysBackErrorLogfortheTSMAPI....15-26
DebugOptions...........15-27
Interoperability with System Backup and
Recovery for AIX - SysBack Versions 5.1 - 5.4 . . 15-27
Chapter 16. Utilities ........16-1
Displaying SysBack Product Installation History16-1
Printing or Displaying System Configuration. . 16-2
ivIBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Creating a Bootable Tape (Without Data) ....16-3
Creating a Bootable CD/DVD (Without Data) . . 16-5
Changing SysBack Tape Boot Defaults .....16-9
Changing SysBack CD/DVD Boot Defaults . . . 16-12
Changing the Read Permission on a Disk Image
File................16-16
Creating or Editing an LVM Information File16-18
Creating a Custom Installation Diskette ....16-19
Changing SysBack Program Defaults .....16-21
BackupFormatSettings........16-22
End of Tape (EOT) Processing Options . . . 16-23
Error Handling Settings ........16-25
SysBack Network Settings .......16-26
Logging..............16-27
Chapter 17. Copying Backups to a
New Media Type ..........17-1
Copy Backup from Disk Image or CD/DVD to
Tape................17-1
Copy Backup Tape to Backup Disk Image. . . 17-3
Copy Backup Tape to Backup Tape ......17-5
Chapter 18. Listing or Verifying
Backups .............18-1
Listing Backup Contents .........18-1
Verifying Files on System Backup ......18-3
Chapter 19. Activity Logging....19-1
Accessing the SysBack Logging Menus....19-1
Changing the SysBack Logging Attributes (Size
andLocation).............19-1
DisplayingtheSysBackLog........19-2
Chapter 20. Scheduled Backups and
Scripts ..............20-1
Scripts ...............20-1
Accessing the Backup Scripts Menu.....20-1
Creating a Backup Script File .......20-1
Changing a Backup Script File ......20-3
Removing a Backup Script File ......20-4
Accessing the Backup Schedules Menus ....20-4
Creating a Backup Schedule .......20-5
Updating a Backup Schedule .......20-6
Listing Backup Schedules ........20-7
RemovingaBackupSchedule.......20-7
Chapter 21. Virtual Devices .....21-1
Types of Virtual Devices .........21-2
Volume Numbering ...........21-2
Autoloaders .............21-3
Adding a Virtual Device .........21-3
Listing Virtual Devices ..........21-5
RemovingaVirtualDevice ........21-5
Chapter 22. Tape Drives......22-1
Listing tape drives ...........22-1
Configuring a defined tape drive......22-2
UnconfiguringanAvailableTapeDrive....22-2
Changing Tape Drive Characteristics .....22-2
Unloading or Ejecting a Tape from the Drive. . 22-3
Appendix A. Commands.......A-1
cfgremrootaccess ............A-2
chimagefile ..............A-4
chinstclient ..............A-6
cfglocaccess .............A-10
cfgremaccess .............A-12
cfgremserver .............A-15
cfgremsvs..............A-17
cfgvirdev..............A-18
chexcludelist .............A-20
editlvminfo.............A-22
getlvminfo ..............A-23
lscfginfo...............A-27
mkdirback..............A-29
mkjfsback..............A-33
mklvback ..............A-37
mksbnetboot .............A-41
mkvgback ..............A-45
mkvginfo ..............A-49
readsbheader.............A-53
remakevg..............A-55
sbalog...............A-58
sbclient ...............A-59
sbcomp and sbuncomp..........A-62
sbcron...............A-63
sbdevice ..............A-65
sbejecttape ..............A-67
sbeot................A-68
sbfwd...............A-69
sbread...............A-71
sbscript ...............A-74
sbspboot..............A-76
sbspotcust..............A-77
sbtsmdevice.............A-79
sbtsmlist..............A-81
sbtsmnetcfg .............A-83
sbwrite ...............A-85
sysback...............A-90
sysrestore ..............A-96
Appendix B. Booting a System for
SysBack Installation or Maintenance . B-1
Initiating the boot process .........B-1
Common Hardware Reference Platform (uni or
multi-processor) ...........B-1
Microchannel-based RISC System/6000
(uniprocessor) ............B-1
Microchannel-based RISC System/6000 SMP
(multiprocessor) ...........B-2
PCI-based (RSPC) RISC System/6000 (uni or
multi-processor) ...........B-3
Initiating the Network Boot.........B-4
Completing the Boot Process ........B-4
Troubleshooting a Network Boot .......B-5
Determining the Network Adapter Hardware
Address ..............B-5
Appendix C. LEDS .........C-1
Contentsv
Appendix D. Creating Scripts for
Customizing the System Backup and
Install Process ...........D-1
Script Names .............D-1
Post-Installation Scripts ..........D-3
Sample Scripts .............D-3
IBM 7331 8mm Tape Library ........E-2
IBM 7332 4mm Tape Library ........E-3
Other Tape Libraries or Autoloaders ......E-3
IBM 7133 Serial Storage Architecture (SSA) disk
subsystem ..............E-3
IBM 7135 RAIDiant Array .........E-4
IBM 7137 and Other RAID Devices ......E-4
Appendix E. Device/System-Specific
Information ............E-1
IBM 7208 8mm Tape Drives........E-1
IBM 3490, Magstar
OtherTapeDrives............E-2
®
, DLT and LTO Tape DrivesE-1
Appendix F. Accessibility ......F-1
Appendix G. Notices ........G-1
Trademarks..............G-3
viIBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
IBM Tivoli Storage Manager for System Backup and Recovery
Overview
IBM Tivoli Storage Manager for System Backup and Recovery (also known as
“SysBack”) provides system administrators and other system users with a simple,
efficient way to backup and recover data from a command line or a SMIT
menu-driven interface. SysBack lets you recover all or part of the system. SysBack
is also flexible; you can install one system installation image to another system
with either identical or different hardware configurations, called “cloning”
SysBack features let you:
v Create various types of backups, including:
– Full system (installation image)
– Volume groups
– Logical volumes (raw data)
– Filesystems
– Specific directories or files
v Incrementally backup and restore data.
v Perform “power” system backups that enable faster backup and restore times by
backing up all data as raw logical volumes and heighten read/write
performance while reducing CPU usage.
v Perform backups to locally attached tape drives or files on disk and remote
hosts across the network.
v Selectively exclude specific files, directories, filesystems, or logical volumes from
backups.
v Centrally manage backup clients using “pull” backups from a single server.
v Create backup scripts for easy automation.
v Define backup schedules for easy automation.
v Execute pre and post-backup scripts that enable environment-specific task
automation, including halting database applications before beginning a backup.
v Perform backups to multiple sequential devices, automatically continuing the
backup on the next device when the first is full and minimizing manual
intervention when autoloading libraries are not available.
v Perform backups to multiple parallel devices, called “striping,” which lets you
complete a single backup in a fraction of the normal time.
v Create multiple copies of a single backup to different devices in approximately
the same time it takes for a single copy.
v View progress status indicators that display estimated backup or restore sizes,
times, performance estimates and a completion percentage estimate.
v Receive completion status logs on all backup, list and verification operations.
v Use SMIT menus to configure SysBack options, which let you backup and
restore volume groups, logical volumes, filesystems, directories, or files and list
and verifying backup images.
v Use sequential autoloading devices to minimize manual intervention and tape
loading operations.
v “Stack” multiple backups on a single tape for all backup types.
v Reinstall the system to its original device configuration, including the volume
group and logical volume placement on disk and attached devices, using Full
System (Installation) Image to the same or different system (also called
“cloning”).
v Install the system from local boot/installation media or from a TSM server.
v Perform a network boot or installation to alleviate the need for local boot or
installation media using SysBack functions or existing Network Installation
Manager (NIM) resources.
v Perform Recovery Installation that restores only the base operating system (root
and /usr filesystems) without affecting other data in the rootvg or other volume
groups.
v Preserve multi-copied (mirrored) or striped logical volumes on recreate.
v Import, ignore, or recreate/restore each volume group or logical volume from a
single backup media during installation.
v Retain exact partition placement of logical volumes or make contiguous
partitions of any that have become fragmented; this will improve I/O
performance on recreate.
v Execute post-installation scripts to perform environment specific tasks.
v Use post-installation to remove SysBack or network configuration after cloning a
backup image to a different machine or to indicate the location of installation
media for automatically installing device support to the new machine.
v Set network and tape boot defaults to minimize, and often eliminate, the need
for user prompting during an installation.
v Edit or change the physical location and attributes of volume groups, logical
volumes, and filesystems during recreation.
v Restore data at the volume group, logical volume, filesystem, directory or file
level.
v Interactively select files to restore by letting you specify a filelist, use a search
word or use a wildcard to narrow the list.
v Exclude select filesystems or logical volumes during restore operations.
viiiIBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
About This Book
This book contains information on configuring and using IBM Tivoli Storage
Manager for System Backup and Recovery (also known as “SysBack”). The book
contains instructions on using the System Management Interface Tool (SMIT)
menus for performing backups as well as a commands reference to perform
SysBack functions without the SMIT menus.
Who Should Read This Publication
This book is intended for system administrators responsible for managing the AIX
operating system on RS/6000®or pSeries™systems. Readers of this book are
expected to have a basic understanding of the SMIT menus and have already
configured devices for backing up the operating system. Readers should also be
familiar with the general layout of the AIX system, including an understanding of
the volume groups, logical volumes, and filesystems.
IBM Tivoli Storage Manager for System Backup and Recovery
Documentation
IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli Information Center Web
site. You can access updated publications in the Tivoli Information Center from the
following Customer Support for Tivoli products Web site:
v International customers should consult the web site for customer support
telephone numbers.
v You can also review the IBM Software Support Guide which is available on our
web site at: http://techsupport.services.ibm.com/guides/handbook.html
xIBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Chapter 1. Installation
To install IBM®Tivoli®Storage Manager for System Backup and Recovery, also
know as, SysBack™, you must have the prerequisite software installed on your
system.
System Requirements
Hardware Requirements
SysBack supports the following hardware:
v IBM Eserver pSeries™and RS/6000®systems, including RS/6000 SP
environments, and systems capable of the logical partitioning of AIX®.
v Eserver pSeries Cluster 1600 systems using the PSSP option
Software Requirements
The following software is required to use SysBack:
v AIX V4.3.0 or later, AIX 5L V5.1, or V5.2
v If you will be using the TSM Integration feature, you will also need:
– A previously configured TSM server must be at level 5.1.5 or higher.
– The 32-bit TSM API client must be installed and at level 5.1.5 or higher
– The TSM node name used for SysBack backups must be registered on the
TSM server and configured to use the passwordaccess generate option.
™
Note: This feature is not available in SysBack versions less than 5.6.
v The bos.sysmgt.sysbr fileset.
v If you will be using the Remote Services functions of SysBack, install the
following:
– bos.rte.net
– bos.net.tcp.client
v If you will be using the Classic Network Boot functions for the Network
Installs, install bos.net.nfs.client
v If you will be using the NIM Resource Network Boot functions for Network
Installs, the NIM environment and resources must first be installed and
configured in the desired locations for SysBack to use these resources. For
information on installing and configuring NIM, see the book, Network Installation
Management Guide and Reference
v If you will be using SysBack on SP or Cluster 1600 systems, you must be using
PSSP level 3.4 or 3.5.
Note: At this time, SysBack does not include support for Eserver pSeries
Cluster1600 systems using the CSM option available in AIX 5.2.
v When AIX is installed, the following are installed automatically with the system
and may not be removed in order for SysBack to function properly:
– bos.rte.bosinst
– bos.rte.archive
– bos.rte.libnetsvc (when using Network Install functions)
v If you will be using the CD / DVD backup feature, please refer to Chapter 5,
“Backups to CD or DVD”, on page 5-1 for additional requirements specific to
this feature.
Upgrading from System Backup and Recovery for AIX - SysBack
If you are upgrading from System Backup and Recovery for AIX - SysBack
versions 5.1.x, 5.2.x, 5.3.x, or 5.4.x, you will not need to uninstall it before installing
the IBM Tivoli Storage Manager for System Backup and Recovery (SysBack)
version 5.5 or 5.6 product.
The installation process for IBM Tivoli Storage Manager for System Backup and
Recovery will preserve any previous configurations, as well as, to automatically
make the sysback.rte fileset obsolete.
Procedure for Installation from CD-ROM
After the prerequisite software is installed:
1. Log in as a root user. You will see the following:
IBM AIX Operating System
(c) Copyright IBM Corp. 19XX, 19XX
(/dev/console)
login: root
2. Insert the IBM Tivoli Storage Manager for System Backup and Recovery
installation CD into the CD-ROM drive.
3. Type the AIX command smitty install.
™
Note: This command invokes the System Management Interface Tool (SMIT),
which presents a menu-driven environment for the installation process.
The argument install is a fastpath that takes you directly to the
software installation process. The menu selections differ from one
version and release of the operating system to another, so menu
selections displayed on your system may differ slightly.
4. From the Software Installation and Maintenance menu, select Install and
Update Software.
5. Select Install and Update from the LATEST Available Software.
6. At the INPUT device/directory for software prompt, type the device name of
the CD-ROM drive. For example, /dev/cd0.
7. The following screen is displayed:
1-2IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Install and Update from LATEST Available Software
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
* INPUT device/directory for software/dev/cd0
* SOFTWARE to install[_all_latest]+
PREVIEW only? (install operation will NOT occur)no+
COMMIT software updates?yes+
SAVE replaced files?no+
AUTOMATICALLY install requisite software?yes+
EXTEND file systems if space needed?yes+
OVERWRITE same or newer versions?no+
VERIFY install and check file sizes?no+
Include corresponding LANGUAGE filesets?yes+
DETAILED output?no+
Process multiple volumes?yes+
Figure 1-1. The Install and Update from Latest Available Software Menu
[Entry Fields]
8. To install the SysBack product, accept the default settings.
To install individual filesets, highlight Software to install and press F4.
Individually, select the filesets to install.
Notes:
a. The SysBack 5.5 and 5.6 product fileset is: tivoli.tsm.client.sysback.rte
b. The SysBack 5.5 and 5.6 license filesets are:
tivoli.tsm.client.sysback.license.rte and
tivoli.tsm.client.sysback.license.cert
c. The SysBack 5.1 - 5.4 product fileset is: sysback.rte
d. Licensing for SysBack 5.1 - 5.4 is key specific. Please refer to
http://sysback.services.ibm.com/or other documentation that
accompanied your order.
e. The SysBack HTML version of the manual is no longer available as the
fileset sysback.html.en_US. To view the manual in HTML form, please
refer to http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
9. Press Enter to confirm selections and install the software.
10. On AIX 5.1 systems, you will be prompted to “accept”the electronic license
agreement. Indicating a “No”response will prohibit the installation of these
filesets.
Accessing the Online Documentation
IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli Information Center Web
Site. You can access updated publications in the Tivoli Information Center from the
following Customer Support for Tivoli products web site:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
Chapter 1. Installation1-3
1-4IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Chapter 2. SMIT Overview
This chapter provides information about the SMIT menu interface. SMIT is used
for virtually all AIX system administrative tasks.
Accessing the IBM Tivoli Storage Manager for System Backup and
Recovery
To access the System Backup & Recovery for AIX menus, type smit to access the
System Management Interface Tool. After SysBack is installed, IBM Tivoli Storage
Manager for System Backup and Recovery is displayed at the bottom of the main
menu. Select this option to access additional SysBack screens. You can alternatively
type smit sysback to jump directly to the SysBack screens. The following is an
example of the SysBack Main SMIT Menu as shown using the ASCII SMIT menu.
IBM Tivoli Storage Manager for System Backup and Recovery
Figure 2-1. ASCII version of the SysBack Main SMIT Menu
The ASCII SMIT menu is displayed by default if AIXwindows is not running. If
AIXwindows is running, and SMIT is started from the desktop or from an aixterm
window, the graphical version of SMIT (msmit) is displayed by default. The
remainder of the screens displayed in this section use the ASCII SMIT format.
Note: To use most of the options within the SysBack menus, log in to the system
as a root user. This is for several reasons:
1. Only a root user has authority to read, and therefore backup or restore,
many files in the system.
2. When restoring files under a non-root user, that user, if permitted to read
the files, becomes the new owner of the files. Files are returned to their
original ownership only when restored by a root user.
3. Many options, such as changing the block size of the tape drive, creating
network boot images, or configuring network server and client options,
require that you have root privileges to perform the task.
The menus are organized by the type of backups that you can perform, followed
by additional options used for configuring or customizing additional SysBack
options. The SysBack Main Menu includes the following options:
Backup & Recovery Options
Use this option to display additional options for backing up, listing, verifying, or
restoring files from a backup depending on the type of backup performed. It is not
necessary to know the backup type to perform any of the list, verify, recreate or
restore options, as the system will read the backup to determine the backup type,
and presents only additional options that are relevant to that type of backup.
Backup & Recovery Options
Move cursor to desired item and press Enter.
Backup Options
List Backup Contents
Verify a Backup
Recreate Volume Groups, Logical Volumes & Filesystems
Restore Data from a Backup
Initiate SP Node Boot and Install
Use Backup Options to create a backup of the system that can be used to reinstall
the system from a system failure, or to use the backup to install other systems.
Additional options available from the Backup Options menu enable you to back up
a smaller part of the system or only specific files or directories.
Configuration Options
This menu provides additional options for configuration tasks, such as providing
access to local and remote users, adding and deleting entries from exclude lists,
and creating or deleting virtual device descriptions. The this menu is displayed
below:
2-2IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Configuration Options
Move cursor to desired item and press Enter.
Local User Access
Remote Services
Remote Command Access
Virtual Devices
Exclude Lists
Network Boot/Install Configuration
License Configuration
Provides backup permission to specific or all users on the system.
You can also indicate which local tape drives or virtual devices the
users are allowed to access and the directories to which they are
allowed to save backup images.
Remote Services
Virtual Devices
Exclude ListsEnters, lists, or deletes entries from an exclude file. The exclude file
Network Boot Configuration
Tape Drives
Use this option to change the physical block size of tape drives or enable or
disable tape drives on the system. This is particularly useful when you want to
temporarily disable client machines from accessing the tape drives. An additional
option enables you to unload or eject a tape cartridge from a tape drive or tape
autoloader. The menu is displayed below:
Provides backup access from remote systems to local devices or
directories. You can indicate which users on the remote hosts are
allowed access and the specific devices or directories to which they
are allowed to backup.
This option is also used on the client system to indicate which
servers to which they want to backup. Only servers that have
granted access to the client can be configured on the client.
Adds, lists, and removes virtual devices. Virtual devices are logical
device names assigned to one or more physical devices, providing
a simpler way to back up to multiple devices or autoloaders.
contains names of individual files or directories to exclude from all
backups generated by SysBack.
Creates network boot images that enable client machines to be
booted from the network, therefore requiring no local boot media.
Chapter 2. SMIT Overview2-3
Tape Drives
Move cursor to desired item and press Enter.
List All Defined Tape Drives
Configure a Defined Tape Drive
Unconfigure an Available Tape Drive
Change Tape Drive Characteristics
Unload/Eject Tape from Drive
This menu provides a list of miscellaneous options. The options on this menu
might differ depending on your level of AIX installed and might change as new
options are added to SysBack.
Utilities
Move cursor to desired item and press Enter.
Display Sysback Product Install History
Print or Display System Configuration
Create a Bootable Tape (without data)
Change Sysback Tape Boot Defaults
Change Read Permission on a Disk Image File
Create or Edit an LVM Information File
Create a Custom Installation Diskette
Change Sysback Program Defaults
Sysback Logging
When selecting a backup, list, verify, recreate or restore option from any SMIT
menu, you are prompted for the device, directory, or filename to use.
Various tape devices, virtual devices, or filename options are displayed, depending
on the backup permission granted the specific user or host. When you back up to a
local device or directory, the backup options are determined by the local access, as
defined using the Add or Change Device/Directory access to Local Users option.
2-4IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
When you back up to a remote backup server, the backup options are determined
by the Add or Change Client Host Access to this Server option executed on the
server. If no directories are defined for disk image file backups, then no disk file
options are provided.
Figure 2-6 shows the backup options that might be included on the SMIT menu:
Backup Options
Move cursor to desired item and press Enter.
Backup the System (Installation Image)
Backup Volume Groups
Backup Filesystems
Backup Logical Volumes
Backup Files or Directories
+--------------------------------------------------------------------------+
|Select Backup Device or Network Install Image Directory|
||
| Move cursor to desired item and press Enter.|
||
|Dir/usr/lpp/sysback/images/local|
|hambone.austin.ibm.com /dev/rmt05.0 GB 8mm Tape Drive|
||
| F1=HelpF2=RefreshF3=Cancel|
The first column contains the device type and can be any of the following:
VirDevVirtual devices that you have configured. The device name (vdev0)
TapeTape drives available on the local system. Local tape drives are
DsktDiskette drives on the local system. A diskette option is not
DirFor backup options, a directory name, if the user has permission to
FileFor list, verify, recreate and restore options, the name of a local
Hostname:A remote option. The hostname is the name of a server for which
is automatically assigned by the system. The description shown is
either one that you assign or a default description assigned by the
system. The physical devices that make up the virtual device are
listed at the end of the line in parentheses.
always displayed first in the list.
displayed for a system backup.
back up to a disk file. The directory shown is the directory or
directories specified when backup permission was enabled for the
user. For list, verify, and restore options, all files in the user’s
backup directories are displayed.
disk image file. Only files in the directories the user has access to
are displayed. Files of all backup types are shown.
this host has remote access. The information can be any one of the
following:
Chapter 2. SMIT Overview2-5
Tape Drive Name
Tape drives on the remote machine. Only remote
tape drives on hosts that have granted access to
this host, as well as those that have been defined
by the local host, are included on this selector
screen.
Virtual Device Name
Virtual devices configured on the server. The
virtual device description from the remote machine
and the physical tape drive name(s) are shown.
Only virtual devices for hosts that have granted
access to this host, as well as those that have been
defined by the local host, are included on this
selector screen.
File or Directory
For list, verify, recreate and restore options, a
filename is shown for each disk image backup file
that exists on the server in the directories for which
this host has access. For backup options, a
directory name is shown for all directories this host
has permission to write to.
You must select one of the options provided on the selector screen before
proceeding. After you select an option, you can change the device, filename or
unique ID selected on the dialog screen that follows, but the backup cannot
execute unless you have permission to access the specified device or directory.
Backups to Disk Image Files
To perform a disk file backup, select a directory name from the device selector
screen. A filename is automatically generated as follows:
/Directory/Type.Hostname.UniqueID
The filename contains the following parts:
DirectoryThe directory selected.
TypeThe type of backup to be performed. One of the following is used:
SBSystem Backup
VGVolume group
LVLogical Volume
FSFilesystem
FDFile/Directory
Period (.)Delimiter.
HostnameThe name of the host performing the backup. This is set to
“localhost” if no hostname is defined.
Period (.)Delimiter.
UniqueIDA unique ID that, by default, contains the date and time of the
backup in “MMDDhhmm” format. For example, if a backup is
made on Feb. 28 at 3:20 P.M., the unique ID would be “02281520”.
2-6IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
You can later change this ID to any other value that might more
accurately describe the backup contents.
Although the filename in SMIT is displayed only as shown above, most backups
actually create more than one file, each named as above, but with an additional
extension. The first file has a “.TOC” extension, indicating the file is the table of
contents of the backup. For a File/Directory backup, the “.TOC” file also contains
the backup data, because there is always only one image in this backup. For all
other backup types, an additional file is created for each logical volume or
filesystem included in the backup, with the logical volume name as the file
extension. This file contains the actual backup data for each logical volume or
filesystem.
Backup, List, Verify and Restore Command Output Screen
The output screen for the backup, list, verify, and restore options is different from
that of other SMIT-executed commands. This screen provides the following
advantages:
v Output is not saved in the SMIT log file (smit.log). This prevents very long file
lists from taking unnecessary space on the disk. You are still provided the option
of writing the output to a log file after the command has completed.
v There is no delay when the command has completed. The delay is normally
required for SMIT processing and writing of the smit.log file.
v Command output (stdout) and error (stderr) are displayed in separate windows.
This provides much cleaner output for commands that provide both standard
output and standard error messages.
v The complete command and the time the command started and ended is
displayed at the top of the screen.
The following is an example of the output of a file/directory backup executed
from SMIT:
COMMAND: mkdirback -hhambone.austin.ibm.com -f/sysback.images/fatrat/backu ...
STARTED: Feb 28 18:37:36ENDED:STATUS: Running
Generating file list ..
NOTE: Estimated megabytes is approximate since data is compressed.
Backing up Files "/tivoli"
Figure 2-7. The output of a file/directory executed from SMIT
Command Output
Command Error / Status
ESTIMATED PROGRESS
Note that the screen is separated into two “windows.” The first is for Command
Output (stdout). The second is for Command Error (stderr) and Status. The
Chapter 2. SMIT Overview2-7
Command Error section is always used to display error messages but is also often
used for other output, such as file lists, status indicators, and so on.
In the above example, a file/directory backup of the /home/data directory was
performed. The user selected the progress indicator report output type during the
backup, rather than the list of files. The progress indicator shows the estimated
time and amount of data to be backed up, the actual percent, time, and amount
complete, and the average performance in kilobytes per second.
When the command has completed, you can perform the following functions by
pressing the appropriate function key:
F1 HelpDisplays a help screen that provides details of the functions you
can perform from this output screen.
F2 RefreshErases and redisplays all the information you see. This is necessary
only if there are other commands, such as system console
information, running that output to this terminal and overwrite the
command output.
F3 ReturnReturns to the previous SMIT dialog screen.
F4 SelectToggles between the Command Output and the Command
Error/Status window, enabling each to scroll independently. The
active window is indicated by the arrows (===> window<===).
After you have selected the window to scroll, you can then move
through the output using the following keys:
Page DownScroll forward one screen
Page UpScroll backward one screen
Down—Arrow/EnterScroll backward one line
Up—ArrowScroll back one line
HomeDisplay first screen
EndDisplay last screen
F5 SaveSave the entire output in a log file. You are asked to enter the
name of the log file. The default file is $HOME/sysback.log, where
$HOME is the user’s home directory. Either enter a new file name
or press Enter to accept the default. The following example shows
a sample output file:
COMMAND:mkdirback -f/dev/rmt1 -s /home/tj
START TIME: Mar 20 02:22:30
END TIME:Mar 20 02:25:49
STATUS:Successful
Start date is Thu Mar 20 02:22:33 1997
User is root at sysdev41
Estimated size is 169 MB
2-8IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
SMIT Help Screens
You can obtain help information from any point within SMIT. If a menu selection
is currently displayed, highlight a function and press F1 for information regarding
the use of that function. For any dialog selection, F1 provides information on the
use of that selection, the options available, and how they affect the function being
performed.
SMIT Fastpaths
From any SMIT menu or dialog screen (where you type or change options), press
F8 to display the SMIT fastpath for quickly reaching that selection from the
command line. Later, to skip directly to the desired selection, you can type smitfastpath at the command line, where fastpath is the fastpath for the desired
selection.
ESTIMATED PROGRESS
---------------------------------------------------------% Complete | Elapsed Time | Megabytes | Kbytes/Sec
Backup ended Thu Mar 20 02:25:46 1997
170 megabytes written to 1 volume.
Obtaining Command Line Options from SMIT
You can execute any SMIT command outside of SMIT by placing the command in
a shell script. You can place multiple commands in shell scripts to be executed in
sequence, enabling a sequence of multiple commands to be performed without
user interaction. You can also place the shell scripts in cron, an AIX job scheduling
facility.
To obtain the command line options for a SMIT command, use the following steps:
1. Select the SMIT option to perform and any additional selections required for
this function.
2. Fill out any fields or change the field values in the dialog screen as you would
when executing the command from SMIT.
3. Before pressing Enter to execute the command from SMIT, press F6 to show the
command on the screen.
The following is an example of the SMIT output when you press F6:
Chapter 2. SMIT Overview2-9
Backup Files or Directories
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
Hostname of serverhambone.austin.ibm.com
Device name/dev/rmt0
Report output typeprogress indicator+
+--------------------------------------------------------------------------++
|SHOW COMMAND STRING|+
||#
| Press Enter or Cancel to return to the|
| application.|+#
||
* |# Ignore "/usr/sbin/sbsmitout -sN" prefix|+
|# when executing outside of SMIT:|
||
|/usr/sbin/sbsmitout -s7 mkdirback -h’hambone.austin.ibm.com’ -f’/dev/r |
|mt0’ ’-x’ ’/home’|
Figure 2-8. Results of Using the F6 Key to Show the Command String
Single quotes (’) around text are required only when there is more than one word
to a single command argument. They do not need to be used to surround a single
word.
Backup, list, verify and restore commands contain the comment indicating that the
prefix of the command /usr/sbin/sbsmitout -sN should be omitted. This prefix
causes the command to be executed within the two-part SysBack SMIT command
output screen previously described. Do not use this output screen should when
executing commands at the command line if the intention is to not require user
interaction.
2-10IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Chapter 3. License Configuration
To license your IBM Tivoli Storage Manager for System Backup and Recovery
(SysBack) software, you must simply install the:
v tivoli.tsm.client.sysback.license.rte
v tivoli.tsm.client.sysback.license.cert
filesets included on your product media in addition to the installation of the base
tivoli.tsm.client.sysback.rte fileset.
Special licensing measures apply for customers using SysBack versions 5.1 - 5.4.
There are no license filesets for this version of SysBack. For detailed information
related to licensing your product, please refer to your product README file
located at: /usr/lpp/sysback/README.txt, http://sysback.services.ibm.com, or
other documentation that accompanied your order.
You can select any of the backup options, each of which are described in detail in
this chapter. The first option, Backup the System (Installation Image), is used to
create a backup of the operating system and any additionally selected volume
groups. This is the only backup from which the system can be reinstalled after an
operating system failure. All other backups options back up smaller increments of
data, such as volume groups or select file systems.
Understanding Incremental Backups
Incremental backups make it possible to back up only data that has changed since
a prior backup, significantly reducing the backup time and media usage.
Incremental backups can be performed for both volume group and file system
backups.
You perform an incremental backup by indicating an incremental backup level.
This level indicates that only files that have changed since the most recent previous
level should be included in the backup. Specifying level 0 indicates that all files
should be backed up. Level 0 is still considered an incremental level; it is the base
for all incremental levels that follow.
Any number of incremental levels from 0 through 9 can be used, but using too
many levels can complicate the restore process.
Consider the following incremental backup examples:
Incremental backup of a file system is performed as follows:
Mondaylevel 0
Tuesdaylevel 1
Wednesdaylevel 2
Thursdaylevel 3
Fridaylevel 4
Saturdaylevel 5
Sundaylevel 6
In this case, if you need to restore the entire file system from the backup
performed on Sunday, you must restore every single backup from 0 through 6 in
order to incrementally reapply the changes to date. Always restore level 0 first
(when restoring from scratch) because only level 0 contains a backup of the entire
file system. Then, in the correct sequence, reapply each level that follows, adding,
replacing, and removing files until the file systems return to their most recent state.
Incremental backup of all volume groups, except the rootvg group, is performed
as follows:
1st of monthlevel 0
every Fridaylevel 4
Monday-Thursdaylevel 7
In this example, a volume group backup is performed on the first day of the
month. Every Friday a level 4 is performed, and every other day of the week
(excluding Saturday and Sunday) a level 7 is performed. Because only three levels
are used, no more than three backups need to be restored. If you need to restore
the entire volume group because of failure, the restore sequence would be:
1. Restore level 0.
2. Restore the most recent level 4 if a level 4 was performed since the last level 0.
3. Restore the most recent level 7 if a level 7 was performed since the last level 4
or level 0.
Note: Use care when combining both volume group and file system incremental
backups. An incremental volume group backup is identical to performing an
incremental backup of each individual logical volume and file system in the
volume group. Therefore, after performing a volume group level 0 backup,
you can perform other incremental backup levels for specific file systems. If
a level 0 backup of a file system is performed after a level 0 of the volume
group containing that file system, any higher-level incremental levels for
that file system are applied to the most recent (file system) backup.
4-2IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide
Loading...
+ 372 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.