Ibm tivoli storage manager bare machine recovery for aix with sysback - redp3705

Front cover

IBM Tivoli Storage Manager:
Bare Machine Recovery for AIX
with SysBack

Use SYSBACK with ITSM, to protect
your AIX environment

Learn how to configure your
system for recovery

Secure your AIX server
environments

Barry Kadleck
David McFarlane
Pracha Pechsuksan
Wah Han Tan

ibm.com/redbooks Redpaper

International Technical Support Organization

IBM Tivoli Storage Manager: Bare Machine Recovery
for AIX with SYSBACK

October 2003

Note: Before using this information and the product it supports, read the information in “Notices” on
page vii.

First Edition (October 2003)

This edition applies to IBM Tivoli Storage Manager Version 5.2 and above.

© Copyright International Business Machines Corporation 2003. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.

iv IBM Tivoli Storage Manager: Bare Metal Restore for AIX with SYSBACK

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. SysBack introduction and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 SysBack overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 ITSM for System Backup and Recovery (SysBack) supported features . . . . . . . . . . . . . 2

Chapter 2. BMR for AIX with SysBack considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 The Bare Machine Recovery (BMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 BMR for AIX with SysBack integrating with TSM Server concepts . . . . . . . . . . . . . . . . . 7
2.3 Policy domain considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4 Version control for SysBack images on the TSM Server . . . . . . . . . . . . . . . . . . . . . . . 12
2.5 TSM server’s db consumption consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3. BMR for AIX with SysBack installation and setup. . . . . . . . . . . . . . . . . . . . 13
3.1 Prerequisites and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.1 Basic requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.2 SysBack’s system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.3 Prerequisites of SysBack integrated with ITSM . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.4 Limitations of SysBack integrated with ITSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.5 Network Boot Server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.6 Upgrading from System Backup and Recovery for AIX - SysBack . . . . . . . . . . . . 17
3.2 SysBack software and 32-bit TSM API software installation. . . . . . . . . . . . . . . . . . . . . 17
3.2.1 SysBack software install on AIX machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2.2 32-bit TSM API software installation on AIX machine. . . . . . . . . . . . . . . . . . . . . . 20
3.3 Setup and customizing SysBack and 32-bit TSM API . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.1 TSM Server setup (TSM Server on AIX or Windows machine) . . . . . . . . . . . . . . 21
3.3.2 SysBack’s client setup on AIX machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.3 AIX Network Boot Server setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.4 Basic setup and installation of SysBack into the SPOT of the NIM server . . . . . . 38

Chapter 4. BMR for AIX with SysBack operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.1 SysBack’s system backup operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.1.1 SysBack’s system backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.1.2 SysBack query TSM backup images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.1.3 SysBack’s system backup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.4 SysBack’s system backup schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.1.5 SysBack include/exclude setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.2 SysBack’s Bare Machine Recovery operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.2.1 Initiate the network boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.2.2 Bare Machine Recovery for SysBack’s system restore . . . . . . . . . . . . . . . . . . . . 82

Chapter 5. Performance considerations and tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

© Copyright IBM Corp. 2003. All rights reserved. v

5.1 Exclude unnecessary files or directories from SysBack’s system backup . . . . . . . . . . 98
5.2 Network parameter tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.3 SysBack’s parameter tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.4 Storage Pool and Tape drive being used as backup and restore devices . . . . . . . . . . 99

Appendix A. Troubleshooting, hints, and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.5 Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A.0.1 The SysBack command output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A.0.2 The SysBack activity log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A.0.3 SysBack error log for the 32-bit TSM API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A.0.4 Debug options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
A.0.5 Wrong TSM API version in error recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
A.0.6 Wrong password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
A.0.7 NIM problem: /dev/ram0 (/) filesystem 100% full . . . . . . . . . . . . . . . . . . . . . . . . 105
A.0.8 LPAR machine installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.0.9 Volume group to include . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.0.10 No prompt installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.0.11 Install additional Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.0.12 Restore files from SysBack’s system backup images . . . . . . . . . . . . . . . . . . . 111
A.0.13 Restore files from another SysBack’s client backup image . . . . . . . . . . . . . . . 112

Appendix B. Sample parameter and log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
/usr/tivoli/tsm/client/api/bin/dsm.sys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
/usr/tivoli/tsm/client/api/bin/dsm.opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
/usr/lpp/sysback/tsm/dsm.opt.tsm0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
/usr/lpp/sysback/.settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
/usr/lpp/sysback/.exclude_list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
/usr/lpp/sysback/sbscripts/monthly_system_backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
/usr/lpp/sysback/sbtsmerror.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
/var/adm/ras/sysback.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
/tmp/debug.out.mmddyy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
/tmp/output.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
SysBack’s files after Network Boot up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
/tmp/tsminfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
/tmp/instdevinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
/tmp/device.pkgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
/tmp/dsm.opt.tsm0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/dsm.sys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/instdev. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/instdevdesc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/instdevinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/netinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/nfsdev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
/tmp/nfsdevfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
/tmp/nfsinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
/tmp/pvinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
/tmp/tsm_client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
/tmp/tsminfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
/tmp/tsmnetdevs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

vi IBM Tivoli Storage Manager: Bare Metal Restore for AIX with SYSBACK

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are
inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring
any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and
distribute these sample programs in any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2003. All rights reserved. vii

Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
ibm.com® HACMP/6000™ SP2®
pSeries® IBM® Tivoli®
AIX 5L™ Redbooks™ Redbooks(logo) ™
AIX® RS/6000® IBM ™
GDPS® SysBack™

The following terms are trademarks of other companies:

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United
States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic
Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.

viii IBM Tivoli Storage Manager: Bare Metal Restore for AIX with SYSBACK

Preface

This Redpaper will help you install, tailor, and configure SysBack™ with IBM® Tivoli®
Storage Manager (ITSM) to protect your systems from catastrophic failures.

The team that wrote this Redpaper
This Redpaper was produced by a team of specialists from around the world working at the
International Technical Support Organization, San Jose Center.

Barry Kadleck is responsible for tape and Tivoli Storage projects at the International
Technical Support Organization, San Jose. He has a degree in Electronic Engineering and
joined IBM U.K. in 1985. He has been working with storage software and hardware for the
last 10 years. Before joining the ITSO in 2001, Barry worked at the Product Introduction
Consultancy, Hursley, U.K. as a Program Manager, introducing new Tivoli Storage products
into Europe.

David McFarlane is a Technical Solutions Architect in Australia. He has 19 years of
experience in the I/T industry. His areas of expertise include storage management, VTS, and
z/series solutions. He has participated in two other ITSO residencies: IBM TotalStorage
Virtual Tape server: Planning, Implementing and Monitoring SG24-2229-04, and produced
course materials for “GDPS®, XRC, PPRC,VTS Peer to Peer.”

Pracha Pechsuksan is an I/T Specialist in Thailand. He has six years of experience in AIX®
field and two years of experience in the TSM field. He has worked at IBM for 12 years. His
areas of expertise include AIX, TSM, SP2®, and HACMP/6000™.

Wah Han Tan is an IT Specialist with the pSeries® services team in Singapore. He has
worked at IBM Singapore for seven years. His areas of expertise include AIX, TSM, SP2, and
HACMP/6000.

Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with
specific products or solutions, while getting hands-on experience with leading-edge
technologies. You'll team with IBM technical professionals, Business Partners and/or
customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus,
you'll develop a network of contacts in IBM development labs, and increase your productivity
and marketability.

Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html

Comments welcome
Your comments are important to us!

© Copyright IBM Corp. 2003. All rights reserved. ix

We want our papers to be as helpful as possible. Send us your comments about this
Redpaper or other Redbooks™ in one of the following ways:
Use the online Contact us review redbook form found at:
ibm.com/redbooks
Send your comments in an Internet note to:
redbook@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. QXXE Building 80-E2
650 Harry Road
San Jose, California 95120-6099

x IBM Tivoli Storage Manager: Bare Metal Restore for AIX with SYSBACK

1

Chapter 1. SysBack introduction and
overview
This chapter provides an overview of the introduction, product history, product packaging and
product support features of IBM Tivoli Storage Manager (ITSM) for System Backup and
Recovery (SysBack).

In this chapter, the following topics are described:
Introduction
Introduction to ITSM for System Backup and Recovery (SysBack)
ITSM for System Backup and Recovery (SysBack) support features

© Copyright IBM Corp. 2003. All rights reserved. 1

1.1 Introduction
The objective of this paper to give information and guidance on how to set up system backup
and Bare Machine Recovery (BMR) recovery with IBM Tivoli Storage Manager (ITSM) for
System Backup and Recovery or know as SysBack for AIX.

SysBack has a many features, one of which is integrating and using TSM Server as a backup
device to keep AIX system backup images. This paper provides the steps to quickly set up
Sysback with TSM Server to backup AIX system (rootvg) for the purpose of doing Bare
Machine Recovery (BMR) in case of AIX system (rootvg) crash, or system hard disk damage.
This paper will not cover the setup features of SysBack doing backup to tape devices (directly
from sysback), CD, and DVD on local or remote system.

1.2 SysBack overview
The previous name of ITSM for System Backup and Recovery is “IBM Operation Support
Services, System Backup and Recovery for AIX - SysBack” with a component ID of 6942-09D.
SysBack has been a services offering of IBM Global Services, Integrated Technology
Services in US for 10 years. SysBack began with series of scripts and has grown up to be a
set of robust utilities that support complex operations.

IBM Tivoli Storage Manager (ITSM) for System Backup and Recovery will be referred to as
SysBack within this book. The Product ID (PID) of ITSM for System Backup and Recovery is
5698-SYS. ITSM for System Backup and Recovery (SysBack) version 5.5 became Generally
Available (GA) on December 20, 2002. ITSM for System Backup and Recovery (SysBack)
was integrated with IBM Tivoli Storage Manager (ITSM) on version 5.6, which became GA on
April, 2003.

1.3 ITSM for System Backup and Recovery (SysBack)
supported features
IBM Tivoli Storage Manager for System Backup and Recovery provides system
administrators and other system users with a simple, efficient way to back up 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:
Create various types of backups, including:
– Full system (installation image)
– Volume groups
– Logical volumes (raw data)
– Filesystems
– Specific directories or files
Incrementally backup and restore data
Perform “power” system backups that enable faster backup and restore times by backing
up all data as raw logical volumes and heightens read/write performance while reducing
CPU usage

2 IBM Tivoli Storage Manager: Bare Metal Restore for AIX with SYSBACK

Perform backups to locally attached tape drives or files on disk and remote hosts across
the network
Selectively exclude specific files, directories, filesystems, or logical volumes from backups
Centrally manage backup clients using “pull” backups from a single server
Create backup scripts for easy automation
Define backup schedules for easy automation
Execute pre and post-backup scripts that enable environment-specific task automation,
including halting database applications before beginning a backup
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
Perform backups to multiple parallel devices, called “striping,” which lets you complete a
single backup in a fraction of the normal time
Create multiple copies of a single backup to different devices in approximately the same
time it takes for a single copy
View progress status indicators that display estimated backup or restore sizes, times,
performance estimates, and a completion percentage estimate
Receive completion status logs on all backup, list, and verification operations
Use SMIT menus to configure SysBack options, which let you back up and restore volume
groups, logical volumes, filesystems, directories or files, and lists, and verify backup
images
Use sequential autoloading devices to minimize manual intervention and tape loading
operations
“Stack” multiple backups on a single tape for all backup types
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”)
Install the system from local boot/installation media or from a TSM Server
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
Perform Recovery Installation that restores only the base operating system (root and /user
filesystems) without affecting other data in the rootvg or other volume groups
Preserve multi-copied (mirrored) or striped logical volumes on recreate
Import, ignore, or recreate/restore each volume group or logical volume from a single
backup media during installation
Retain exact partition placement of logical volumes, or make contiguous partitions of any
volumes that have become fragmented; this will improve I/O performance on recreate.
Execute post-installation scripts to perform environment specific tasks
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
Set network and tape boot defaults to minimize, and often eliminate, the need for user
prompting during an installation.
Edit or change the physical location and attributes of volume groups, logical volumes, and
filesystems during recreation

Chapter 1. SysBack introduction and overview 3

Restore data at the volume group, logical volume, filesystem, directory, or file level
Interactively select files to restore by letting you specify a files list, use a search word, or
use a wildcard to narrow the list
Exclude select filesystems or logical volumes during restore operations

The IBM Tivoli Storage Manager for System Backup and Recovery (SysBack) version 5.6 and
later allows for the storage of backup objects into an IBM Tivoli Storage Manager server.
Backups to a TSM Server may be manipulated like any other SysBack backup. They may be
listed, verified, restored, and used for system reinstallation. Combining the SysBack backup,
restore, and network boot and install functions with a TSM Server provides Bare Machine
Recovery (BMR) capability for TSM configurations. SysBack will back up and recover a
system’s volume group, logical volume, and file system information. Optionally, SysBack will
back up any non-rootvg data specified. Customers may use SysBack simply to recover the
rootvg volume group, and then use TSM to restore and manage other user data.

The backup images of root volume group (rootvg) from any AIX machine by using SysBack
are stored on the TSM Server. You can query the backup images by using the “smitty
sysback.” You can query the content inside each backup image from Sysback on the client
side.


2

Chapter 2. BMR for AIX with SysBack
considerations
In this chapter we introduce the concepts, configuration considerations, and guidelines for
Bare Machine Recovery (BMR) for AIX with IBM Tivoli Storage Manager (ITSM) for System
Backup and Recovery (SysBack) to the TSM Server.

The chapter discusses the following topics:
The Bare Machine Recovery (BMR)
BMR concept for ITSM for System Backup and Recovery (SysBack) with TSM Application
Program Interface (API) integrated with TSM Server
TSM Server’s policy domain, policy set, management class, backup copy group, and
storage pool for SysBack considerations
Version control for SysBack system backup images on TSM Server’s storage pool
TSM Server’s db consumption considerations


2.1 The Bare Machine Recovery (BMR)
The main purpose of Bare Machine Recovery (BMR) is situations when the operating system
(OS) goes down or crashes for any reason. For example, during hard disk failure or human
error when the problem cannot be fixed with any other method (such as when there is an
accidental delete of important system files from the system). The system administrator will
then need to recover the operating system from scratch within the shortest time, and restore
the application data back to the system to resume normal operations.

For AIX, there are several procedures to recover the AIX operating system from scratch (Bare
Machine):
Make System Backup Utilities (smitty mksysb): This method will back up the system
(rootvg) to keep on tape cartridge. To restore, the Bare machine must reboot from the tape
cartridge and restore the Root Volume Group (rootvg). This method is supported on any
version of AIX:
Pro: With this method it is easy to do the system backup. This method needs a tape drive
to be connected to the AIX system. The system administrator must issue a command to
do a backup.
Con: The system administrator needs to keep track of the tape volumes. If you have many
machines in the computer center, it might be difficult for the system administrator to
manage the system backups. This method is not a type of backup consolidation.
Make CD utilities (smitty mkcd): This method will create a backup image on a disk
space and then invoke the mkisofs utilities to create a CD image (ISO9660 standard) and
then write this CD images to CD-ROM. This method is supported on AIX 5L™ (but not on
AIX 4.3) and needs a CD writer to be connected to the AIX machine. To restore, the Bare
machine will have to boot from the CD just created and then restore all rootvg:
Pro: This method provides shorter times to do system backup and restore compared with
backup to tape.
Con: This method needs more disk space to keep the images of the CD. The system
administrator needs to keep track of the CD volume. This method is not a kind of backup
consolidation.
Set up one AIX machine as Network Installation Manager (NIM): Then do a system
backup by using mksysb to create the system backup image files to keep on the disk
spaces. The disk space in here may be a local filesystem on an AIX machine, then FTP
the backup image files to the NIM server. Otherwise, create a network filesystem on a NIM
server, then export the NFS to another AIX machine for use as the filesystem to keep the
system backup images. To restore the Bare machine, do a network boot to the NIM server,
then restore the AIX operating system from the system backup images, which were kept
on the hard disk of the NIM server:
Pro: This method provides backup consolidation and shorter times to do the
backup/restore compared to mksysb to the tape drive.
Con: This method needs more disk space to keep the AIX backup images of all machines
in the environment. If disk space is limited, the system administrator will need to back up
the backup image files to tape media, and then keep track of tape media.
IBM Tivoli Storage Manager for System Backup and Recovery (SysBack). This
software provides several methods to do Bare Machine Recovery. To use SysBack, we
installed SysBack program to the AIX machine. If you integrate the SysBack with Tivoli
Storage Manager (TSM) Server, you need to install 32-bit TSM API along with SysBack
software on the AIX client, and on the AIX network boot server. The 32-bit TSM API will
generate virtual devices for SysBack to use as devices to send backup images to TSM
Server. These backup images will be sent to the storage pool of the TSM Server. The
SysBack software provides a variety of backup/restore methods. You can do system
backup/restore of the volume group, filesystem, logical volume, files/directory to tape, to


CD or DVD on the local machine, or to remote machine. You can do push or pull mode
backups. SysBack also provides a kind of backup consolidation. SysBack, integrating with
TSM Server, provides a good consolidated backup/restore methodology especially when
you have already used the TSM Server to do our application data backups in this
environment. In this case, the TSM Server will manage the version control and Storage
Pool of backup images.
Reinstall AIX Operating System from AIX CD. This method will not recover any setup
on the system. You must reinstall all application programs on the system and reconfigure
everything on system again. This is a not recommended method.

There are several methods to do Bare Machine Recovery (BMR) for AIX. It is dependant on
which method provides the suitable Bare Machine Recovery to serve your requirements.

2.2 BMR for AIX with SysBack integrating with TSM Server
concepts
The IBM Tivoli Storage Manager for System Backup and Recovery (SysBack) integrating with
Tivoli Storage Manager Server (TSM Server) provides a good Bare Machine Recovery
option. SysBack uses the 32-bit TSM API to create a virtual device for SysBack to send the
AIX backup images to the TSM Server.

The following 2 figures represent a BMR backup/restore process for the case of a TSM Server
and network boot server which reside on the same machine.

BMR Backup :
The TSM Server and the Network Boot Server located on the
same machine

Network
SysBack Boot
server

TSM
TSM
Server
API

AIX machine :
AIX machine : - TSM Server
- Install SysBack - Boot Server
-TSM API - Install SysBack
- Install 32-bit TSM
API

Figure 2-1 SysBack Backup process (TSM Server and network boot server on same machine)

The backup example in Figure 2-1 shows that SysBack will create an AIX system backup
image on the Storage Pool of the TSM Server using the virtual device (32-bit TSM API, tsmx).
The number of backup images (versions) that will be kept on the TSM Server will depend on
the parameter set for ‘Backup Copy Group’ in the Management Class in use by this client.

Chapter 2. BMR for AIX with SysBack considerations 7

BMR Restore :
The TSM Server and the Network Boot Server located on the
same machine

SysBack 1 Network
from boot Boot
server
server 2

TSM
TSM API
from
3 Server
boot
server 4

AIX machine : Using AIX machine :
SysBack and TSM - TSM Server
API code from - Boot Server
Network Boot Server - Install SysBack
- Install 32-bit TSM API

Figure 2-2 SysBack Restore Process (TSM Server and network boot server on same machine)

In Figure 2-2 we display the process to do Bare Machine Recovery. At restoration time, the
BMR for Sysback integrated with TSM Server only supports network boot restore, boot from
tape or boot from CD are not supported. The network boot server can be AIX’s Classical
Network Boot server or AIX’s Network Installation Manager (NIM) Boot server.
Step 1: Bare machine does a network ‘bootp ‘ request to the network boot server.
Step 2: The network boot server responds with an acknowledgment packet and:
• An AIX boot kernel
• The Sysback program
• Virtual device (tsm0), an 32-bit TSM API
All three programs will reside in the target machine’s memory.
Step 3: After the system administrator completes the setup and configures the parameters
on the SysBack menu (with network boot) we stared the installation process. SysBack
sends a request to the virtual device (32-bit TSM API) and a request for restoration to the
TSM Server.
Step 4: The TSM Server responds to the request from the SysBack client and then sends
the restore image to be installed on the bare machine until successful. SysBack will then
reboot the machine automatically twice.

The following 2 figures represent BMR backup/restore process for the case where the TSM
Server and network boot server reside on different machines.


B M R B a ck u p :
T h e T S M S erver a n d th e N e tw o rk B o o t S erver lo ca te d o n th e
d ifferen t m ac h in e

N e tw o rk
Boot
S ys B a ck S e rve r

A IX m a c hin e :
- N e tw o rk B o ot S erve r
TSM
- Ins tall S ys B ac k
API - Ins talll 3 2-bit T S M A P I

A IX m a c h ine :
- In s ta ll S ysB a ck
- TSM API TSM
S e rv e r

A IX o r W in do w s
m ac hine :
- T S M S e rv er

Figure 2-3 SysBack backup process (TSM Server and network boot server on different machine)

The backup example in Figure 2-3 shows that SysBack will create an AIX system backup
image on the Storage Pool of the TSM Server using the virtual device (32-bit TSM API, tsmx).
The number of backup images (versions) that will be kept on the TSM Server will depend on
the parameter set for Backup Copy Group in the Management Class in use by this client.

B M R R es to re :
T h e T S M S e rve r an d th e N e tw o rk B o o t S e rve r lo c a te d o n th e
d iffe re n t m a ch in e

N e tw o rk
S ysB a c k Boot
fro m b o o t S e rver
se rve r 1
2
A IX m ac hine :
TSM API - N etw ork B oo t S e rve r
fro m
- Ins ta ll S ys B ac k
bo ot
s erv er - Ins ta lll 32 -bit T S M A P

3

A IX m a c h ine : U sing
S ysB a c k a n d T S M 4
A P I co d e fro m TSM
N e tw o rk B oo t S e rve r S e rve r

A IX o r W in d o w s
m a ch in e :
- T S M S e rv e r

Figure 2-4 SysBack Restore Process (TSM Server and network boot server on different machine)

In Figure 2-4 we display the process to do Bare Machine Recovery. At restoration time, the
BMR for Sysback integrated with TSM Server only supports network boot restore, boot from
tape or boot from CD are not supported. The network boot server can be AIX’s Classical
Network Boot server or AIX’s Network Installation Manager (NIM) Boot server.


Step 1: Bare machine does a network ‘bootp ‘ request to the network boot server.
Step 2: The network boot server responds with an acknowledgment packet and:
• An AIX boot kernel
• The Sysback program
• Virtual device (tsm0), an 32-bit TSM API
All three programs will reside in the target machine’s memory.
Step 3: After the system administrator completes the setup and configures the parameters
on the SysBack menu (with network boot), start the installation process. SysBack sends a
request to the virtual device (32-bit TSM API) and a request for restoration to the TSM
Server.
Step 4: The TSM Server responds to the request from the SysBack client and then sends
the restore image to be installed on the bare machine until successful. SysBack will then
reboot the machine automatically twice.

2.3 Policy domain considerations
Here we set up SysBack, we created a TSM’s client for SysBack’s client with passwordaccess
parameter set to generate. This SysBack’s client can use any policy domain defined on TSM
Server. We also can define the new Policy Domain specific for SysBack backup/restore. The
separated Policy Domain will help separate the groups of backups and make it easier for the
system administrator to manage the environment. Whether you decide to a use separate
policy domain or to use a previously defined policy domain depends on your individual
environment.

T S M P o lic y a n d D e v ic e C la s s

ts m _ c lie n t, s b _ c lie n t C lie n t
node

P o lic y T S M S e rv e r
D o m a in

P o lic y S e t

M anagem ent M ana gem ent D e v ic e C la s s 1 D e v ic e C la s s 2
MC2
C la s s 1 C la s s 3

B ackup L ib r a r y
C o p yg ro u p

Ta p e Ta p e
S to r a g e p o o l V o lu m e D e v ic e s 1 D e v ic e s 2

Figure 2-5 TSM Server Policy


T S M P o licy an d D evic e C lass
tsm _c lie n t, sb _ clie n t C lie n t
node

p d .sysb a ck T S M S erver

p s .s ysb a c k

m c .s ys b ac k.m o n th ly m c .s ysb a c k m c .s ysb a c k.s a ve vg D e vice C la ss D e vice C las s

B a cku p L ib ra ry
C o p ygro u p

Tap e Ta pe
S to rag e p o o l V o lu m e D e v ice s D e v ice s

Figure 2-6 Example of TSM Policy

In the previous example, we defined a new policy domain, policy set, management class, and
backup copy group for SysBack’s client. You can define several management classes under
the same policy domain for the purpose of controlling the number of versions of backup
images. The variable defined in the backup copy group under each management class will
identify how many versions of SysBack backup images are kept on the TSM Server.

The TSM storage pool consideration
you may set up disk storage pools then migrate these to tape storage pools (two-tier storage
pool) on TSM, if you have enough disk space on TSM Server. This will help reduce the
backup time for SysBack and can help reduce the restoration time as well. You also can move
the backup images which migrated to the tape storage pool back to a disk storage pool before
you start doing SysBack BMR system restore.

M ig r a te S to r a g e P o o l
D is k S t o r a g e P o o l Ta p e S to r a g e P o o l

N e x t S to ra g e P o o l

Figure 2-7 Migrate Storage Pool


2.4 Version control for SysBack images on the TSM Server
The number of versions kept within the TSM Server Storage Pool can be defined by a
parameter in the Backup Copy Group. The parameter: “Version Data Exists” sets the number
of SysBack backup images (versions) to be kept.

The following screen displays the number of SysBack backup images version kept on the
TSM Server’s storage pool:

Figure 2-8 The Version Data Exists parameter

In the previous example screen (Figure 2-8), the TSM Server will keep three versions of
SysBack’s system backup images on Storage Pool for the client name, sb_atlantic. This client
was created under the pd.sysback Policy Domain, ps.sysback Policy Set, mc.sysback
Managament Class and standard Backup Copy Group.

For example, if you do a system backup once a month and need to keep twelve versions of
system back up, set the Version Data Exists parameter to twelve. This setting will cover twelve
versions of SysBack’s system backup for this client machine.

2.5 TSM server’s db consumption consideration
The SysBack’s system backup integrating with TSM Server will consume only a few KBytes of
the TSM Server’s database for each SysBack’s system backup image.


3

Chapter 3. BMR for AIX with SysBack
installation and setup
This chapter provides information on how to install ITSM for System Backup and Recovery
(SysBack) software products on an AIX machine; how to set up and customize your TSM
Server; and how to set up the SysBack program and initiate a backup, then send the backup
image to be kept on the TSM Server.

This chapter contains the following:
Prerequisites and requirements
SysBack software and 32-bit TSM API software installation
Set up and customizing SysBack with 32-bit TSM API
Basic NIM server setup


3.1 Prerequisites and requirements
In the following sections we cover the important requirements.

3.1.1 Basic requirements
Those who will implement the BMR for ITSM for System Backup and Recovery (SysBack)
need an understanding of AIX system administration and TSM administration.

3.1.2 SysBack’s system requirements
Hardware requirements
SysBack supports the following hardware:
IBM eServer, pSeries, and RS/6000® systems, including RS/6000 SP environments, and
systems capable of the logical partitioning of AIX
IBM eServer, pSeries Cluster 1600 systems using the PSSP option

Software requirements
The following software is required to use by SysBack:
AIX V4.3.0 or later, AIX 5L V5.1, or V5.2
If you are using the TSM Integration feature, you also need:
– A previously configured TSM Server, which must be at level 5.1.5 or higher
– A 32-bit TSM API client, which 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: TSM integration feature is not available in SysBack versions less than 5.6.

The bos.sysmgt.sysbr fileset
If you will be using the remote services functions of SysBack, install the following:
– bos.rte.net
– bos.net.tcp.client

Note: This Redpaper will not include remote services configuration or setup.

If you will be using the Classic Network Boot functions for the network installs, install
bos.net.nfs.client.
If you will be using the NIM Resource Network Boot functions for network installs, the NIM
server 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 “Basic NIM installation part” in the AIX Network Installation Management Guide
and Reference.
If you will be using SysBack on SP or Cluster 1600 systems, you must be using PSSP
level 3.4 or 3.5:
– bos.rte.bosinst
– bos.rte.archive
– bos.rte.libnetsvc (when using network install functions)


Note: At this time, SysBack does not include support for IBM eServer, pSeries
Cluster1600 systems using the CSM option available in AIX 5.2. When AIX is installed,
the following are installed automatically with the system, and may not be removed in
order for SysBack to function properly.

Note: This Redpaper will not cover SysBack for SP or Cluster 1600 system setup.

3.1.3 Prerequisites of SysBack integrated with ITSM
The following are prerequisites for SysBack under TSM with the backup images to be kept on
the storage pool of the TSM Server:
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.
Only JFS and JFS2 file systems are supported for all of the backup types.
The file and directory backup type may also be used to back up CD-ROM and NFS file
systems.
All backup, restore, list, verify, and query operations must be performed as the root user.

3.1.4 Limitations of SysBack integrated with ITSM
The following limitations and exclusions apply to interaction with TSM:
SysBack should not be used to back up TSM HSM managed file systems. You will need to
explicitly specify any HSM managed file system in the SysBack exclude list. For detailed
information on SysBack exclude lists, please refer to “SysBack EXCLUDE setup” on
page 63.

Note: Using SysBack to back up HSM managed file systems will cause all of the
migrated data to be recalled for the backup operation. This can cause lengthy backup
times. Also, there may not be enough space in the file system to recall all of the
migrated data. Use the TSM backup/archive client to back up the HSM file systems
instead.

LAN-free backups are not supported.
COMMMethod TCPIP is the only supported TSM communication method.
GPFS file systems are not supported.

Note: The TSM backup/archive client supports the backup of GPFS file systems.

Veritas file systems are not supported.

Chapter 3. BMR for AIX with SysBack installation and setup 15

3.1.5 Network Boot Server requirements
Here are some of the important requirements.

Classical network boot server requirements
The network boot server and AIX client machine, which perform the network boot must be the
same version of AIX. For example, the network boot server is AIX 5.1, so the AIX client
machine must be AIX 5.1. The classical network boot server must be an AIX machine and
can either be the same machine as TSM Server machine or a different machine. The TSM
Server can be set up on a Microsoft Windows or AIX machine, but the classical network boot
server must be an AIX machine. You can initiate a network boot to one network boot server,
then restore system images from another TSM Server machine.

The SysBack Classic Network Boot method used in versions earlier than Version 5 continues
in Version 5 for environments that do not use AIX NIM (Network Installation Manager)
resources.

The Classic Network Boot method relies on the / and /usr filesystems of the network boot
server to create the network boot image. The network boot server also fulfills other
processing requirements for the client during the boot and installation process. Therefore, the
network boot server must meet certain requirements in order for the boot client to
successfully utilize the boot server’s resources. Specifically:
The operating system level of the network boot server must be the same level as the boot
client when using SysBack only to boot into maintenance mode. (The client must boot
from the same level as what is currently installed.)
The operating system level of the network boot server must be the same level as the
installation and restore image used to reinstall the client machine when booting and
installing the client. (The client must boot from the same level as the image to be installed.)
The boot server must have installed any AIX filesets required for the client to support
attached hardware.

Note: If filesets are installed specifically to support a boot client, the server must be
rebooted, and the network boot image updated and recreated before the client will
successfully boot from the boot server.

The boot server must have installed kernel filesets to support the processor type
(uniprocessor or multiprocessor) of the boot client regardless of whether or not the boot
server is of the same processor type.

rebooted and the network boot image updated or recreated before the client can

SysBack must be installed on the boot server.

rebooted and the network boot image updated or recreated before the client can

The TSM 32-bit API client and the tivoli.tivguid (prerequisite of the API client) filesets must
be installed onto the network boot server.


Network Installation Manager (NIM) network boot server requirements
The Network Installation Manager (NIM) will be needed when the AIX client machine does a
network boot to restore an AIX system image from a TSM Server that has a different version
of AIX from boot server. For example, the boot server is at AIX 5.2, but the AIX client machine
is at AIX 5.1. To support this kind of network boot, you need to set up NIM on the network
boot server. NIM is an IBM product that comes on the AIX installation CD. You can install NIM
server filesets and customize NIM server on AIX machine. The basic NIM server setup is
described in 3.3.4 “Basic setup and installation of SysBack into the SPOT of the NIM server”
on page 38.

To set up the NIM server, the NIM server machine must be the highest Version of AIX in the
environment to support network boot down level version of AIX. e.g. NIM server machine is
AIX 5.1, then AIX client machine can be AIX 5.1 or AIX 4.3.

Each version of AIX in the NIM server will need about 1GB of disk space to keep AIX Licence
Program Product (LPP). e.g. If the NIM server supports AIX 4.3 and 5.1 network boots then
this NIM server will need at least 2 GB of disk space to be configured.

When performing a SysBack NIM Resource Network Boot, the 32-bit TSM API client and
tivoli.tivguid (prerequisite of the API client) filesets must be installed into the NIM System
Product Object Tree (SPOT).

Note: There is not a SysBack utility available for installing the TSM filesets into the NIM
SPOT. You must install them yourself using standard NIM commands.

3.1.6 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.

3.2 SysBack software and 32-bit TSM API software installation
Here is the installation information you will need.

3.2.1 SysBack software install on AIX machine
This section describes how to install ITSM for System Backup and Recovery (SysBack) on an
AIX machine both on AIX network boot server and on an AIX client machine doing system
backups.

SysBack has only one set of code. We used the same code to install on AIX network boot
server (Classical network boot and NIM network boot server) and on the AIX client machine
doing SysBack system backups.

Note: Install SysBack software and 32-bit TSM API on AIX network boot server and AIX
Client machine doing SysBack system backups


Set TSM Environment Variables
The 32-bit TSM API client provides the following environment variables:

DSMI_CONFIG - The fully qualified name for the client options file usually named dsm.opt.
Setting this variable is not supported with SysBack. SysBack will always set this variable to
/usr/lpp/sysback/tsm/dsm.opt.tsmXX where X represents the TSM virtual device number.

DSMI_DIR - The path that contains the dsm.sys, dsmtca, and the en_US subdirectory.
Setting this variable is not supported with SysBack. SysBack will always look to the default
API installation directory of /usr/tivoli/tsm/client/api/bin to locate these items in order to allow
the bare machine recovery functions.

DSMI_LOG - The path that points to the API error log. You may configure this variable to
designate the location and filename of the API error log. If this variable is not set, the API
error log for SysBack operations will be located in /usr/lpp/sysback/sbtsmerror.log.

Note: This does not log the output of the SysBack command processing. This only logs the
information for the API communications between the SysBack command processing and
the TSM Server. For more information related to process logging, please refer to 5.5
“Problem determination” on page 102.

Procedure to Install 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 menus
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 or Press F4 to see device lists or put name of directory which
we put SysBack filesets into.

Note: If you put SysBack filesets into a directory, make sure that you run the
command:
# inutoc /<sysback_fileset_directory_name> before you put the directory name to
INPUT device/directory for software prompt field to create a toc file.


7. The following screen is displayed in Figure 3-1.

Figure 3-1 The install and update from latest available software menu

Note: On AIX 5.1 or later, the parameter Accept new license agreements? must be set
to yes.

8. To install the SysBack product, accept the default settings.

To install individual filesets, move the highlighted cursor to Software to install and press F4.
Individually, select the filesets to install by pressing F7 over each fileset.

Note:
– 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 the 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.


3.2.2 32-bit TSM API software installation on AIX machine
As stated in 3.1 “Prerequisites and requirements” on page 14, SysBack integrated with TSM
Server needs the TSM Application Program Interface (API) to be installed and set up on the
AIX machine prior to the first SysBack backup.

The following command displays the number of bits in use on an AIX’s kernel and hardware
processor:
# bootinfo -K -> Check to see AIX kernel is 32-bit or 64-bit
# bootinfo -y -> Check to see the machine processor support 32-bit or 64-bit

There are two filesets for TSM API version 5.2. Those two filesets are:
tivoli.tsm.client.api.32bit 5.2.0.0 or
tivoli.tsm.client.api.64bit 5.2.0.0

Important: Use only the tivoli.tsm.client.api.32bit fileset no matter the number of bits in
your AIX operating system. The SysBack V5.6 does not support using the 64-bit API
fileset.

The SysBack and 32-bit TSM API fileset work on AIX’s 32-bit kernel mode or AIX’s 64-bit
kernel mode.

The steps to install 32-bit TSM API is same as 3.2.1, “SysBack software install on AIX
machine” on page 17 just change the filesets to Tivoli.tsm.client.api.32bit to be installed
and continue to follow the other steps.

3.3 Setup and customizing SysBack and 32-bit TSM API
This section describes how to set up ITSM for System Backup and Recovery (SysBack)
starting from customizing TSM Server then customizing SysBack on an AIX machine.

Figure 3-2 displays parameters and configurations used in the setup.


B M R C o n fig u r a tio n D ia g r a m
A IX : A IX :
- C la s s ic a l N e tw o r k B o o t - T S M S e rv e r
- C la s s ic a l N e tw o r k B o o t S e r v e r
C lie n t - N IM N e t w o rk B o o t S e r v e r

H o s t n a m e : A t la n tic H o s t n a m e : b a lt ic

S y s B a c k C lie n t n a m e A IX b o o t S e rv e r, T S M
: s b _ A tla n t ic S e rv e r, N IM S e rv e r

A I X V e r s io n : 5 . 1 A I X V e r s io n : 5 . 1

P la t f o r m : c h r p / m p P la t f o r m : c h r p / m p

IP A d d r e s : 9 . 1 . 3 9 . 9 2 IP A d d re s : 9 .1 .3 9 .9 5
E th e rN e t

N e t M A S K 2 5 5 . 2 5 5 .2 5 4 . 0

H o s tn a m e : a z o v H o s tn a m e : k a d re s 4

S y s B a c k C lie n t n a m e T S M S e rv e r
: sb_azov

A I X V e r s io n : 5 . 1 W in d o w s X P

P la t f o r m : c h r p / m p P la t f o r m : W in d o w s

IP A d d re s : 9 .1 .3 9 .8 9 IP A d d re s s
9 .1 .3 8 .1 4 8

A IX :
- N I M N e t w o r k B o o t C lie n t W in d o w s 2 0 0 0 :
-T S M S e rve r

Figure 3-2 configuration and parameter used in setup

3.3.1 TSM Server setup (TSM Server on AIX or Windows machine)
This section describes how to define new a policy domain for the SysBack client node to keep
system backup images on TSM Server. You may use the previously defined policy domain for
other client nodes but this may become difficult to manage. The other alternative is to define a
new policy domain on TSM Server. However, you have to consider which configuration or
design is suitable for each environment.

Note: The TSM Server must be installed and set up properly prior to this task. This section
will not include how to install and set up TSM Server.

The following steps can be used to define the new policy domain, policy set, management
class, storage pool and backup copy group. Then register the new SysBack client node to
new the policy domain. You may use TSM Server WEBadmin or the TSM command line;
these steps will show you how to define the parameters using the command line:
1. Log in as system administrator on TSM Server:
– # dsmadmc
2. Define a new policy domain, PD.SYSBACK
– > DEFINE DOMAIN pd.sysback DESCRIPTION="Policy Domain
SysBack"BACKRETENTION=30 ARCHRETENTION=365
3. Define a new policy set, PS.SYSBACK
– > DEFINE POLICYSET PD.SYSBACK ps.sysback DESCRIPTION="Policy Set for
SysBack"
4. Define a new management class, MC.SYSBACK
– > DEFINE MGMTCLASS PD.SYSBACK PS.SYSBACK MC.SYSBACK
DESCRIPTION="Management Class SysBack" SPACEMGTECHNIQUE=NONE
AUTOMIGNONUSE=0 MIGREQUIRESBKUP=YES


5. Define a new storage pool. As discussed in design, you may set up a two-tier storage pool,
use DISK storage pool as primary your storage pool and use tape (sequential storage
pool) as the secondary storage pool.

Note: Disk storage pool will be defined in /tsm/storage filesystems for this example.
The size of the filesystem and size of the DISK storage pool must be big enough to
keep backup images, this means, the size of rootvg (root volume group) of the AIX
machine doing SysBack system backup

a. Define the sequential storage pool (tape pool) first.
– > DEFINE STGPOOL sp.sysback.tape LTO DESCRIPTION="Sequential Storage Pool
for SysBack" ACCESS=READWRITE COLLOCATE=NO MAXSCRATCH=0
REUSEDELAY=0 DATAFORMAT=NATIVE

Note: The previous command uses LTO (Linear Tape Open Devices) as device
class and tape backup devices.

b. Then, Define DISK Storage Pool (DISK) to point to next Storage Pool on Tape Pool
– > DEFINE STGPOOL sp.sysback.disk DISK DESCRIPTION="Storage Pool for
Sysback on Disk" ACCESS=READWRITE MAXSIZE=NOLIMIT
NEXTSTGPOOL=SP.SYSBACK.TAPE HIGHMIG=90 LOWMIG=70 CACHE=NO
MIGPROCESS=1 MIGDELAY=0 MIGCONTINUE=YES COPYCONTINUE=YES
CRCDATA=NO
c. Define a volume into DISK storage pool
– > DEFINE VOLUME SP.SYSBACK.DISK /tsm/storages/sysbackstg01.dsm
ACCESS=READWRITE FORMATSIZE=8192 WAIT=YES
6. Define a new backup copy group to the previously defined policy domain, policy set,
management class.
– > DEFINE COPYGROUP PD.SYSBACK PS.SYSBACK MC.SYSBACK
DESTINATION=SP.SYSBACK.DISK FREQUENCY=0 VEREXISTS=4
VERDELETED=1 RETEXTRA=30 RETONLY=60 MODE=MODIFIED
SERIALIZATION=SHRDYNAMIC

Note: The VEREXISTS (Version Data Exist) depends on how many versions you need
to keep of the backup images.

7. Assign the default management class by the following command:
– > ASSIGN DEFMGMTCLASS PD.SYSBACK PS.SYSBACK MC.SYSBACK
8. Validate and activate the previously defined policy set.
– > VALIDATE POLICYSET PD.SYSBACK PS.SYSBACK
– > ACTIVATE POLICYSET PD.SYSBACK PS.SYSBACK
9. Now, you are ready to register the new node to the previously defined policy domain.
– > REGISTER NODE sb_atlantic sb_atlantic DOMAIN=PD.SYSBACK
AUTOFSRENAME=NO ARCHDELETE=YES BACKDELETE=NO
FORCEPWRESET=YES TYPE=CLIENT KEEPMP=NO MAXNUMMP=2
URL=http://client.host.name:1581 PASSEXP=0 TXNGROUPMAX=0
DATAWRITEPATH=ANY DATAREADPATH=ANY SESSIONINIT=CLIENTORSERVER


Note: The SysBack Client node name in here is sb_atlantic. See Figure 3-2 on
page 21 for the server name and client name.

3.3.2 SysBack’s client setup on AIX machine
This section describes how to set up Sysback and the 32-bit TSM API on an AIX machine.

Note: Do this step only on an AIX machine, which is going to do the SysBack system
backup. You do not need to do this step on the TSM Server or on the network boot server.

You need to complete the steps in 3.2.1 “SysBack software install on AIX machine” on
page 17, and 3.2.2 “32-bit TSM API software installation on AIX machine” on page 20 prior to
doing this task.
1. Log in as root user ID.
2. Edit file /usr/tivoli/tsm/client/api/bin/dsm.opt by using “vi” editor as the following example.
Put Servername into this file.

Note: The Servername can be any name refer to Servername in
/usr/tivoli/tsm/client/api/bin/dsm.sys file. Our example uses sb_atlantic where sb stands
for SysBack because some customers use the hostname as client for backup/archive.

Figure 3-3 /usr/tivoli/tsm/client/api/bin/dsm.opt file

3. Edit file /usr/tivoli/tsm/client/api/bin/dsm.sys by using “vi” editor as the following example.

Note: The Servername must be the same as /usr/tivoli/tsm/client/api/bin/dsm.opt. The
nodename must be the same as the SysBack client node name that you registered on
TSM Server. The Passwordaccess parameter must be generate.

Servername sb_atlantic
COMMmethod TCPIP
TCPPort 1500


Nodename sb_atlantic
Passwordaccess generate

Figure 3-4 /usr/tivoli/tsm/client/api/bin/dsm.sys file

Note: More parameter can be found in ITSM for System Backup and Recovery
(SysBack) Installation and Setup manual or “/usr/tivoli/tsm/client/api/bin/dsm.sys” on
page 114.

4. Create the TSM virtual device on the SysBack client machine. This virtual device is used
for sending backup images to the TSM Server.
To access the TSM Virtual Device configuration menus:
a. Log in as root user ID.
b. Type smitty sysback then press Enter.
The following screen is displayed.

Figure 3-5 smitty sysback menu

c. Select TSM Configuration then press Enter.


The following screen is displayed.

Figure 3-6 The TSM Configuration menu

d. Select TSM Virtual Device Configuration then press Enter.
The following screen is displayed in Figure 3-7.

Figure 3-7 TSM Virtual Device Configuration Menu

e. Select Add a TSM Virtual Device then press Enter.



f. Move the cursor bar to the desired TSM Server name when prompted at the Select a
TSM Server dialogue and press Enter.

Note: The list of TSM Server names is generated from the contents of
Appendix “/usr/tivoli/tsm/client/api/bin/dsm.sys” on page 114.

The following screen in Figure 3-9 is displayed.

Figure 3-9 Add a TSM Virtual Device Menu

g. Enter the password that corresponds to the node name defined in this server stanza in
the Client Node Password field then press Enter.
The following screen is displayed Figure 3-10.



AIX command line: # /usr/sbin/sbtsmdevice -a -s'sb_atlantic' -p'sb_atlantic'

Note: You should be aware of the following information related to the password field:
If this is the first connection to the TSM Server for this node name, the password
will be encrypted and stored in /etc/security/adsm or as specified with the
PASSWORDIR option in the dsm.sys file. The password being entered must be
the same as the password we used to register the SysBack client node on the
TSM Server.
The SysBack Client Node Password being entered here will be used when you
do “Network Boot” when the SysBack menu is displayed to do SysBack’s system
restoration.
If a connection to the TSM Server has previously been established by this, or any
other TSM client using this node name, you must enter the password that was
previously stored in /etc/security/adsm or where specified with the
PASSWORDDIR option in the dsm.sys file. If you do not know this password, you
have two options:
– Specify the password to the administrative ID created for this node name
which has OWNER access.
– Log into the TSM Server and issue the command: update node nodename
newpassword before attempting to create the TSM virtual device.

For more information regarding the update node command, please refer to “IBM
Tivoli Storage Manager for AIX: Administrator’s Reference,” GC32-0769.

5. To list the TSM Virtual Device, we created on this Sysback client machine the following:
a. Log in as a root user ID on system.
c. Select TSM Configurations then press Enter. Select TSM Virtual Device
Configuration then press Enter. Select List TSM Virtual Devices then press Enter.


Figure 3-11 TSM Virtual Device Configuration List

AIX command line: # /usr/sbin/sbtsmdevice -l

6. To remove the TSM Virtual Device, we created on this Sysback client machine. (This is
just in case we did something wrong and want to delete the TSM Virtual Device and
recreate it again.):
a. Log in as root user ID on system.
c. Select TSM Configurations then press Enter. Select TSM Virtual Device
Configuration then press Enter. Select Remove a TSM Virtual Device then press
Enter.

Figure 3-12 TSM Virtual Device Configuration Remove

d. Select the TSMx Virtual Device which you want to remove, then press Enter twice.


Figure 3-13 TSM Virtual Device Configuration Remove

AIX command line: # /usr/sbin/sbtsmdevice -r -n'tsm0'

3.3.3 AIX Network Boot Server setup
This section describes how to set up the network boot server for ITSM for System Backup and
Recovery (SysBack) Bare Machine Recovery (BMR) environment. The network boot server
will be needed at the time you need to do BMR restoration. You need to initiate the network
boot from the AIX SysBack client machine, this AIX SysBack client machine will send a bootp
request to AIX network boot server. After the bootp request and bootp acknowledgment
complete, the root’s filesystem / and /usr network filesystem (/usr of network boot server
for classical network boot or /usr from SPOT for NIM network boot server) will be mounted on
the AIX SysBack client machine. Then the SysBack program will be started up and come up
with the SysBack menu on the screen to continue doing the system restore.

SysBack on AIX Classical Network Boot Server setup
This section describes how to set up the Classical Network boot on an AIX network boot
server. As state before, the SysBack program and 32-bit TSM API client must be installed on
the network boot server to support the Sysback menus after complete Network Boot.

SysBack on AIX Classical Network Boot Server setup
1. Add the Network boot Client on the AIX network boot server using the SysBack menu.
c. Select Configuration Options then press Enter. Select Network boot/Install
Configuration then press Enter. Select Classical Network Boot then press Enter.
Select Add or Change a Network Boot Client then press Enter.
The following screen is displayed Figure 3-14.


Figure 3-14 Add or Change a Network Boot client Menu

d. Type in the host name of the AIX SysBack Client machine going to do network boot
e.g. atlantic then press Enter.

Note: The client hostname in here is the hostname of the AIX SysBack client machine
which can be resolved by /etc/hosts or Domain Name Server (DNS) on this AIX network
boot server machine.


Figure 3-15 Add or Change a Network Boot Client

e. Input the parameters like the following screen display the press Enter.


Figure 3-16 Add or Change a Network Boot Client

Note: The client platform/kernel type must correspond with your hardware machine type.

AIX command line: # /usr/sbin/mksbnetboot -h'atlantic' -d'ethernet' '-T chrp'
'-k mp' -S' 9.1.38.95' -s'255.255.254.0'

2. Set Network Install Client Defaults:
Select Set Network Install Client Defaults then press Enter.

Figure 3-17 Classic Network Boot Menu, Set Network Install Client Defaults


d. Select the Network Boot Client that you want to set and then press Enter.

Figure 3-18 Set Network Install Client Defaults Menu

e. Input the required parameters as the following lists then press Enter.
Install Server IP address [9.1.38.95] --> IP address of Boot Server
Gateway address [9.1.38.95] --> IP address of Gateway
Network device name [ ] --> left blank for this parameter
Subnet mask [255.255.254.0] --> Subnetmask
The rest of the parameters should be left as default values.

AIX command line: # chinstclient -bN -h 'atlantic.almaden.ibm.com®' -M
'prompt' '-D' -v 'root' -R 'n' -N 'n' -A 'n' -S '9.1.38.95' -g '9.1.38.95'
-s '255.255.254.0'

3. Set TSM Network Install Client Defaults:
Select Set TSM Network Install Client Defaults then press Enter.


Figure 3-19 Classic Network Boot Menu, Set TSM Network Install Client Defaults

d. Select the Network Boot Client that you want to set and then press Enter, e.g.
atlantic.almaden.ibm.com.

Figure 3-20 Set TSM Network Install Client Defaults Menu

e. Input the require parameter as in the following lists then press Enter.
Hostname atlantic.almaden.ibm.com
TSM Client Node Name [sb_atlantic]
TSM Admin ID [admin]
TSM Server Port [1500]
Gateway []
Client Node or Admin Password [admin] --> See note below


Ibm tivoli storage manager bare machine recovery for aix with sysback - redp3705

Ibm tivoli storage manager bare machine recovery for aix with sysback - redp3705

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (16)

En vedette

En vedette (20)

Similaire à Ibm tivoli storage manager bare machine recovery for aix with sysback - redp3705

Similaire à Ibm tivoli storage manager bare machine recovery for aix with sysback - redp3705 (20)

Plus de Banking at Ho Chi Minh city

Plus de Banking at Ho Chi Minh city (20)

Dernier

Dernier (20)

Ibm tivoli storage manager bare machine recovery for aix with sysback - redp3705