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

ibm.com/redbooks Redpaper

Front cover

IBM Tivoli Storage Manager:Bare Machine Recovery for AIXwith SysBack

Barry KadleckDavid McFarlane

Pracha PechsuksanWah Han Tan

Use SYSBACK with ITSM, to protect your AIX environment

Learn how to configure your system for recovery

Secure your AIX server environments

http://www.redbooks.ibm.com/


International Technical Support Organization

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

October 2003

First Edition (October 2003)

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

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

© 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 ScheduleContract with IBM Corp.

iii

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

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. SysBack introduction and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 SysBack overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 ITSM for System Backup and Recovery (SysBack) supported features. . . . . . . . . . . . . 2

Chapter 2. BMR for AIX with SysBack considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 The Bare Machine Recovery (BMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 BMR for AIX with SysBack integrating with TSM Server concepts . . . . . . . . . . . . . . . . . 72.3 Policy domain considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.4 Version control for SysBack images on the TSM Server . . . . . . . . . . . . . . . . . . . . . . . 122.5 TSM server’s db consumption consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3. BMR for AIX with SysBack installation and setup. . . . . . . . . . . . . . . . . . . . 133.1 Prerequisites and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.1.1 Basic requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1.2 SysBack’s system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1.3 Prerequisites of SysBack integrated with ITSM . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.4 Limitations of SysBack integrated with ITSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.5 Network Boot Server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.6 Upgrading from System Backup and Recovery for AIX - SysBack . . . . . . . . . . . . 17

3.2 SysBack software and 32-bit TSM API software installation. . . . . . . . . . . . . . . . . . . . . 173.2.1 SysBack software install on AIX machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.2 32-bit TSM API software installation on AIX machine. . . . . . . . . . . . . . . . . . . . . . 20

3.3 Setup and customizing SysBack and 32-bit TSM API . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.1 TSM Server setup (TSM Server on AIX or Windows machine) . . . . . . . . . . . . . . 213.3.2 SysBack’s client setup on AIX machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3.3 AIX Network Boot Server setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3.4 Basic setup and installation of SysBack into the SPOT of the NIM server . . . . . . 38

Chapter 4. BMR for AIX with SysBack operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.1 SysBack’s system backup operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.1.1 SysBack’s system backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.1.2 SysBack query TSM backup images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.1.3 SysBack’s system backup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.4 SysBack’s system backup schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.1.5 SysBack include/exclude setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.2 SysBack’s Bare Machine Recovery operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.2.1 Initiate the network boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.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 . . . . . . . . . . 985.2 Network parameter tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985.3 SysBack’s parameter tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995.4 Storage Pool and Tape drive being used as backup and restore devices . . . . . . . . . . 99

Appendix A. Troubleshooting, hints, and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015.5 Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

A.0.1 The SysBack command output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102A.0.2 The SysBack activity log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102A.0.3 SysBack error log for the 32-bit TSM API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102A.0.4 Debug options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103A.0.5 Wrong TSM API version in error recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104A.0.6 Wrong password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104A.0.7 NIM problem: /dev/ram0 (/) filesystem 100% full . . . . . . . . . . . . . . . . . . . . . . . . 105A.0.8 LPAR machine installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108A.0.9 Volume group to include. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108A.0.10 No prompt installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108A.0.11 Install additional Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108A.0.12 Restore files from SysBack’s system backup images . . . . . . . . . . . . . . . . . . . 111A.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118SysBack’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

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

ibm.com®pSeries®AIX 5L™AIX®GDPS®

HACMP/6000™IBM®Redbooks™RS/6000®SysBack™

SP2®Tivoli®Redbooks(logo) ™IBM ™

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 RedpaperThis 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 authorJoin 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 welcomeYour comments are important to us!

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

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html

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:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099

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


http://www.ibm.com/redbooks/

http://www.ibm.com/redbooks/

http://www.redbooks.ibm.com/contacts.html

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

1

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

1.1 IntroductionThe 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 overviewThe 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.


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


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.

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.

TSM API

AIX machine :- Install SysBack-TSM API

SysBack

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

TSM Server

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

Network Boot

server

Chapter 2. BMR for AIX with SysBack considerations 7

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.

TSM API from boot

server

AIX machine : Using SysBack and TSM API code from Network Boot Server

SysBack from boot

server

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

TSM Server

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

3

2

1 Network Boot

server

4


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.

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.

TSM API

AIX m achine : - Insta ll SysBack- TSM API

SysBack

AIX or W indows m achine : - TSM Server

TSM Server

AIX m achine : - N etwork Boot Server- Install SysBack- Installl 32-bit TSM API

N etwork Boot

Server

BM R Backup : The TSM Server and the N etw ork Boot Server located on the d ifferent m achine

TS M AP I from boot

server

A IX m achine : U sing SysBack and TSM API code from N etwork Boot Server

SysBack from boot

server

A IX or W indows m achine : - TSM Server

TSM Server

A IX m achine : - N etwork Boot Server- Insta ll SysBack- Insta lll 32-bit TS M A P

N etw ork Boot

Server

B M R R estore : The TSM Server and the Netw ork B oot Server located on the d ifferent m achine

12

3

4


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

Figure 2-5 TSM Server Policy

P o lic y D o m a in

P olic y S et

M a n a g e m e n t C la s s 1

B a ck u p C o p yg ro u p

S to ra g e p o o l

M C 2 M a n a ge m e n t C la ss3

V o lu m e

C lie n t n o d e

D e v ice C la ss 1

L ib rary

Ta p e D e v ic e s 1

D e v ice C la ss 2

Ta p e D e v ic e s2

T S M P o licy a n d D e vic e C la ss

T S M S e rve r

tsm _ c lien t, sb _ c lie n t


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

Figure 2-7 Migrate Storage Pool

pd.sysback

ps.sysback

m c.sysback.m onthly

Backup Copygroup

Storagepool

m c.sysback m c.sysback.savevg

Volum e

C lient node

Device C lass

Library

Tape Dev ices

Device Class

Tape Dev ices

TSM Policy and Device C lass

TSM Server

tsm _client, sb_client

D is k S to ra g e P o o l Ta p e S to r a g e P o o l

M ig r a te S to r a g e P o o l

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


2.4 Version control for SysBack images on the TSM ServerThe 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 considerationThe 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.


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


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

3.1.1 Basic requirementsThose 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 requirementsSysBack 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 requirementsThe 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.

� 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

� 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: TSM integration feature is not available in SysBack versions less than 5.6.

Note: This Redpaper will not include remote services configuration or 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.

� LAN-free backups are not supported.

� COMMMethod TCPIP is the only supported TSM communication method.

� GPFS file systems are not supported.

� Veritas file systems are not supported.

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.

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.

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

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

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

Classical network boot server requirementsThe 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.

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

� SysBack must be installed on the boot server.

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

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.

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

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


Network Installation Manager (NIM) network boot server requirementsThe 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).

3.1.6 Upgrading from System Backup and Recovery for AIX - SysBackIf 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 installationHere is the installation information you will need.

3.2.1 SysBack software install on AIX machineThis 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: 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.

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

Procedure to Install from CD-ROMAfter 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.

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

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.

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

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.

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

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

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


http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

http://sysback.services.ibm.com/

3.2.2 32-bit TSM API software installation on AIX machineAs 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

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

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.


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.

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

H o s tn a m e : A t la n tic

S y s B a c k C lie n t n a m e : s b _ A tla n t ic

A IX V e rs io n : 5 .1

P la t fo rm : c h rp /m p

IP A d d re s : 9 .1 .3 9 .9 2

B M R C o n f ig u r a t io n D ia g r a m

H o s tn a m e : b a lt ic

A IX b o o t S e rv e r , T S M S e rv e r , N IM S e rv e r


P la t fo r m : c h rp /m p

IP A d d re s : 9 .1 .3 9 .9 5

H o s tn a m e : a z o v

S y s B a c k C lie n t n a m e : s b _ a z o v


P la t fo rm : c h rp /m p

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

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

T S M S e rv e r

W in d o w s X P

P la t f o rm : W in d o w s

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

A IX : -T S M S e rv e r-C la s s ic a l N e tw o rk B o o t S e rv e r-N IM N e tw o rk B o o t S e rv e r

A IX : -C la s s ic a l N e tw o rk B o o t C lie n t

A IX : - N IM N e tw o rk B o o t C lie n t W in d o w s 2 0 0 0 :

- T S M S e r v e r

E th e rN e t

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

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.


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.

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

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

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: 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

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

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


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

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.

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.

Servername sb_atlanticCOMMmethod TCPIPTCPPort 1500

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.

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.

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.

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.


Nodename sb_atlanticPasswordaccess generate

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

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.

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.


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.

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.

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.



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.


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.


Figure 3-11 TSM Virtual Device Configuration List

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.


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


Figure 3-13 TSM Virtual Device Configuration Remove

3.3.3 AIX Network Boot Server setupThis 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 setupThis 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 setup1. 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.


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


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.


Figure 3-15 Add or Change a Network Boot Client

e. Input the parameters like the following screen display the 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-16 Add or Change a Network Boot Client

2. Set Network Install Client Defaults:



c. Select Configuration Options then press Enter. Select Network boot/Install Configuration then press Enter. Select Classical Network Boot then press Enter. Select Set Network Install Client Defaults then press Enter.


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

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'


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.

3. Set TSM Network Install Client Defaults:



c. Select Configuration Options then press Enter. Select Network boot/Install Configuration then press Enter. Select Classical Network Boot then press Enter. Select Set TSM Network Install Client Defaults then press Enter.


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'


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


TSM network device name [ ] -> left blank

TSM Server IP address [9.1.38.95] --> See note below

Subnet Mask [255.255.254.0]

Token-ring speed (if applicable)

Ethernet Interface (if applicable)

Ethernet Connection Type

f. After you finish this task, you can go to test the BMR restoration process, see 4.2 “SysBack’s Bare Machine Recovery operation” on page 64.

SysBack on NIM Network Boot Server setupThis section describes how to setup the Sysback parameter and environment on a 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 the complete Network Boot.

SysBack on NIM Network Boot Server setupYou need to complete 3.3.4 “Basic setup and installation of SysBack into the SPOT of the NIM server” on page 38 prior to doing this setup. Otherwise, there is no resource or NIM client to do this task:

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 NIM Resource Boot then press Enter. Select Add or Change a Network Boot Client then press Enter.


Note: Put only one password, either client node or administrator password in the Client Node or Admin Password field. This password must be the same as Admin user or SysBack client node on the TSM Server that you registered.

Note: This TSM Server IP address can be different from the network boot server if you boot from one network boot server then restore from another TSM Server.

AIX command line: # sbtsmnetcfg -h 'atlantic.almaden.ibm.com' -n 'sb_atlantic' -a 'admin' -p '1500' -P 'admin' -s '9.1.38.95' -S '255.255.254.0'


Figure 3-21 NIM Resource Boot Menu

d. Select the NIM client name the press Enter. The NIM client name is the client name which was defined in step 2. “Add the NIM Client machine on the NIM server.” on page 41.


Figure 3-22 Add or Change a Network Boot Client (By using SysBack menu on Boot Server)

2. Set Network Install Client Defaults (NIM).

Note: Select the NIM SPOT resource name and the NIM LPP source name, which correspond with our backup images. e.g if our backup image is AIX 5.1 you need a NIM’s SPOT created for AIX 5.1 or if our backup image is AIX 4.3 you need a NIM’s SPOT created for AIX 4.3. These SPOTs will be created by the NIM server setup.

AIX command line: # /usr/sbin/mksbnetboot -h 'azov' -n 'spot1' -l 'lpp_source1'




c. Select Configuration Options then press Enter. Select Network boot/Install Configuration then press Enter. Select NIM Resource Boot then press Enter. Select Set Network Install Client Defaults then press Enter.


Figure 3-23 NIM Resource Boot

d. Select the NIM network boot client then press Enter.


Figure 3-24 Set Network Install Client Defaults Menu (NIM)

e. Input the require parameter 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] --> Subnet mask


The rest of the parameters should be left as the default values.

3. Set TSM Network Install Client Defaults (NIM):



c. Select Configuration Options then press Enter. Select Network boot/Install Configuration then press Enter. Select NIM Network Boot then press Enter. Select Set TSM Network Install Client Defaults then press Enter.


Figure 3-25 NIM Resource Boot Menu

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


Figure 3-26 Set TSM Network Install Client Default (NIM)

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


e. Input the required parameters as the following example then press Enter.

Hostname azov.almaden.ibm.com

TSM Client Node Name [sb_azov]

TSM Admin ID [admin]

TSM Server Port [1500]

Gateway [ ]

Client Node or Admin Password [admin]

TSM network device name [ ] --> left blank

TSM Server IP address [9.1.38.95]

Subnet Mask [255.255.254.0] --> Subnet mask

Token-ring speed (if applicable)

Ethernet Interface (if applicable)

Ethernet Connection Type

f. After you finish this task, you can go to test BMR restoration process on 4.2 “SysBack’s Bare Machine Recovery operation” on page 64 of this paper.

3.3.4 Basic setup and installation of SysBack into the SPOT of the NIM serverThis section describes how to set up the basic NIM server as a network boot server. For further information about Network Installation Manager (NIM), please see the “AIX Network Installation Manager: Installation and Setup User Manual.”

The following filesets must be installed on the AIX machine prior to the setup of the NIM server:

bos.sysmgt.nim.masterbos.sysmgt.nim.spotbos.sysmgt.nim.client

bos.net.nfs.cachefsbos.net.nfs.clientbos.net.nfs.server

Run the following command to check whether the NIM server filesets are installed on the system.

Note: Put only one password, either client node or administrator password in the Client Node or Admin Password field. This password must be the same as the administrator user or the SysBack client node on the TSM Server that we registered.

Note: This TSM Server IP address can be different from the network boot server if we boot from one network boot server and then restore from another TSM Server.

AIX command line: # sbtsmnetcfg -h 'azov.almaden.ibm.com' -n '9.1.38.89' -a 'admin' -p '1500' -g '9.1.38.89' -P 'abcde' -s '9.1.39.148' -S '255.255.254.0'


# lslpp -L | grep bos.sysmgt.nim# lslpp -L | grep bos.net.nfs

How to Create a basic NIM server as a Network Boot Server1. Configure the NIM environment:


b. Put AIX Base OS CD #1 for AIX Version (e.g. AIX version 5.1) into CD-ROM drive.

c. Type smitty nim then press Enter.


Figure 3-27 Network Installation Manager Menu

d. Select Configure the NIM Environment then press Enter. Select Configure a Basic NIM Environment (Easy Startup) then press Enter.


Figure 3-28 Configure a Basic NIM environment (Easy Startup)

e. Input the parameters as the following examples. Press F1 on any highlighted line for help or Press F4 for any pop up selectable choice. Then press Enter.


Initialize the NIM Master:

*Primary Network Interface for the NIM Master [ ] --> Press F4 and select our network interface. e.g. en0

*Input device for installation images [ ] --> Press F4 then select device e.g. /dev/cd0

*LPP_SOURCE Name [lpp_source1] --> Use default value

*LPP_SOURCE Directory [/export/lpp_source] --> Use default value

Create new filesystem for LPP_SOURCE? [yes] --> Use default value, This will create /export/lpp_source for you.

Filesystem SIZE (MB) [650] --> May change to be 1024 MB (1 GB)

VOLUME GROUP for new filesystem [rootvg] --> Select your volume group to keep the /export/lpp_source filesystems. We may choose other Volume Group on this system to keep /export/lpp_source filesystems for us.

*SPOT Name [spot1] --> Use default value

*SPOT Directory [/export/spot] --> Use default value

Create new filesystem for SPOT? [yes] --> Use default value, This will create /export/spot filesystem for you.

Filesystem SIZE (MB) [350] --> May change to be 512 MB

VOLUME GROUP for new filesystem [rootvg] --> Select your volume group to keep /export/spot filesystem.

Create Diskless/Dataless Machine Resources? [no]

Specify Resource Name to Define:

ROOT (required for diskless and dataless) [root1] --> Use default value

DUMP (required for diskless and dataless) [dump1] --> Use default value

PAGING (required for diskless) [paging1] --> Use default value

HOME (optional) [home1] --> Use default value

SHARED_HOME (optional) [shared_home1] --> Use default value

TMP (optional) [tmp1] --> Use default value

Diskless/Dataless resource directory [/export/dd_resource] --> Use default value

Create new filesystem for resources? [yes] --> Use default value

Filesystem SIZE (MB) [150] --> Use default value

VOLUME GROUP for new filesystem [rootvg] --> Use default value

Define NIM System Bundles? [yes]

Add Machines from a Definition File? [no]

Specify Filename [ ]

* Remove all newly added NIM definitions [no] --> Use default value

and filesystems if any part of this operation fails?


2. Add the NIM Client machine on the NIM server.


b. Type smitty nim then press Enter.

c. Select Perform NIM Administration Tasks then press Enter. Select Manage Machines then press Enter. Select Define a Machine then press Enter.


Figure 3-29 Define a machine Menu (Define NIM client)

d. Input the hostname of the AIX client machine that we want to initiate a network boot to the NIM server. Then press Enter.

Press F1 for help and press F4 for popup list.


Note: This step will take some time to finish because system will create a directory and then copy those LPP filesets into /export/lpp_source/lpp_source1/installp/ppc directory for us and then create the SPOT for this AIX version. Please follow the “AIX Network Installation Manager: Installation and Setup Guide” if any errors occur during the NIM setup.


Figure 3-30 Define a Machine Menu (Define NIM Client)

* NIM Machine Name [azov] --> Client hostname

* Machine Type [standalone] --> Use default or change

* Hardware Platform Type [chrp] --> Use the one that match your hardware type

Kernel to use for Network Boot [mp] --> Uni/Multi Processor

Primary Network Install Interface

* Cable Type tp

NIM Network network1 --> This is NIM network define.

* Host Name azov --> Client hostname

Network Adapter Hardware Address [0]

Network Adapter Logical Device Name [ ] --> Left blank for this parameter

IPL ROM Emulation Device [ ] --> Left blank for this parameter

CPU Id [ ] --> Left blank for this parameter

Machine Group [ ] --> Left blank for this parameter

Comments [ ] --> Left blank for this parameter

3. To change/show characteristics of a machine. Incase, we need to change some parameter:


b. Type smitty nim then press Enter.

c. Select Perform NIM Administration Tasks then press Enter. Select Manage Machines then press Enter. Select Change/Show Characteristics of a Machine then press Enter.



Figure 3-31 Manage Machines Menu (Change/Show characteristic of a Machine)

d. Select the machine that you want to change the characteristics on then press Enter. Change parameter as needed then press Enter to accept change.

4. Check /etc/bootptab as to whether there is any boot information for this network boot client.eg:

# more /etc/bootptab

The following example information is displayed in Figure 3-32.

Figure 3-32 /etc/bootptab file

The last two lines in the above example indicate client name, client IP address, and network boot server IP address.

5. Check /tftpboot to see whether each network boot client points to either the Classical Network Boot or the NIM Network Boot. eg:

# ls -al /tftpboot

The following example screen is displayed in Figure 3-33.


Figure 3-33 ls -al /tftpboot

From the previous screen you can see that the azov network boot client will be booted from the NIM network boot server and the atlantic network boot client will be booted from the classical network boot server.

6. When you finish this task, you can go to “SysBack on NIM Network Boot Server setup” on page 34.

How to install SysBack software and 32-bit TSM API into NIM’s SPOTThis section describes how to do the software installation into the NIM System Product Object Tree (SPOT).

The NIM’s SPOT works like the installation devices for the network boot. NIM’s SPOT will provide the “/usr” network filesystem to network boot client machine once the bootp process is successful.

Prior to updating the software into SPOT, you need to update the software into NIM’s master component.

Step to update software into the SPOT of the NIM server:

Copy SysBack software and 32-bit TSM API software from CD into lpp_source1. Place the SysBack installation CD into the CD-ROM drive.


3. Type smitty nim then press Enter.



Figure 3-34 Network installation manager menu

4. Select Perform NIM Software Installation and Maintenance Tasks then press Enter. Select Install and Update Software then press Enter. Select software Maintenance and Utilities then press Enter. Select Copy Software to hard Disk for Future Installation.


Figure 3-35 Copy software to hard disk for future installation

5. Press F4 key to see the device lists or type in /dev/cd0 and then press Enter.



Figure 3-36 Copy Software to Hard Disk for Future Installation Menu (NIM)

Fill in the parameters as in the following examples. Then press Enter.

* INPUT device / directory for software /dev/cd0

* SOFTWARE package to copy [all]

* DIRECTORY for storing software packages [/export/lpp_source/lpp_source1/installp/ppc] --> Press F4 over this line to select lpp_source we defined before to add SysBack software filesets into.

DIRECTORY for temporary storage during copying [/tmp]

EXTEND filesystems if space needed? [yes]

Create an LPP_SOURCE [no]

LPP_SOURCE Name [ ] --> Left blank

Architecture of Resource [ ] --> Left blank

6. After press Enter on the previous screen, the following screen is displayed in Figure 3-37.

Note: The previous directory maybe different on different version of AIX.


Figure 3-37 Copy software to lpp_source menu (NIM)

7. After the previous step is finished then copy the 32-bit TSM API software into the same lpp_source by using the same steps.

Install SysBack software and 32-bit TSM API into NIM master and NIM SPOT1. Log in as root user ID.

2. Type smitty nim then press Enter.

3. Select Perform NIM Software Installation and Maintenance Tasks then press Enter. Select Install and Update Software then press Enter. Select Install and Update from ALL Available Software then press Enter.


Figure 3-38 Install and Update Software (NIM)

4. Select master machines master then press Enter.



Figure 3-39 Install and Update Software Menu (NIM Master)

5. Select the lpp_source that correspond with your NIM server version. e.g. In this example we use lpp_source1 for AIX 5.1. Then select lpp_source1 resource lpp_source and press Enter.


Figure 3-40 Install and Update from ALL Available Software

Fill in the parameters as in the following examples:

* Installation Target master

* LPP_SOURCE lpp_source1

* Software to Install [ ] --> Press F4 then move to select the following three filesets of SysBack software and one for 32-bit TSM API in the lists. Press F7 over each fileset to select:

> tivoli.tsm.client.sysback.license.cert> tivoli.tsm.client.sysback.license.rte> tivoli.tsm.client.sysback.rte> tivoli.tsm.client.api.32bit


Customization SCRIPT to run after installation [ ] --> Left blank

(not applicable to SPOTs)

Force no

installp Flags

PREVIEW only? [no]

COMMIT software updates? [yes]

SAVE replaced files? [no]

AUTOMATICALLY install requisite software? [yes]

EXTEND filesystems if space needed? [yes]

OVERWRITE same or newer versions? [no]

VERIFY install and check file sizes? [no]

ACCEPT new license agreements? [YES] --> Must be changed to Yes.

Preview new LICENSE agreements? [no]

Group controls (only valid for group targets):

Number of concurrent operations [ ]

Time limit (hours) [ ]

Schedule a Job [no]

YEAR [ ]

MONTH [ ]

DAY (1-31) [ ]

HOUR (0-23) [ ]

MINUTES (0-59) [ ]

6. Press Enter after filling in the required parameters. This will complete the installation of the SysBack software and 32-bit TSM API into NIM’s master server.

7. Follow the same (step 1 to 13) but this time select Select a TARGET for the operation, Please select spot1 resource spot instead. This will install the SysBack software and 32-bit TSM API into our NIM’s SPOT.

8. If we have several versions of NIM’s SPOT to support, please redo all the steps for all NIM’s SPOTs.

9. Run the following command to verify whether SysBack filesets are already installed on the NIM’s SPOT:

# nim -o lslpp spot1 | grep sysback

and:

# nim -o lslpp spot1 | grep api

10.Run the following command to show all NIM resources:

# lsnim -l

11.We have already completed the basic NIM setup on the AIX network boot server. Now we can go to section “SysBack on NIM Network Boot Server setup” on page 34 to set up SysBack on the NIM network boot server.



Chapter 4. BMR for AIX with SysBack operation

This chapter provides information about system backup and BMR system restore using SysBack. This section also includes information on how to set up a backup schedule for SysBack’s system backup:

� SysBack’s system backup operation� SysBack’s Bare Machine Recovery operation

4


4.1 SysBack’s system backup operationThis section describes how to do SysBack’s system backup using Sysback and then send backup images to be kept on a TSM Server. We also include information how to set up a schedule for SysBack’s system backup.

4.1.1 SysBack’s system backupThe SysBack’s system backup similar to the mksysb command of the AIX utility. The SysBack’s system backup command will create an image of the AIX operating system, and then sends this image to be kept on the TSM Server through a 32-bit TSM API.

To do SysBack’s system backup on AIX SysBack’s client machine:

1. On AIX Sysback’s client machine, log in as root user ID.

2. Type smitty sysback then press Enter.

3. Select Backup & Recovery Options then press Enter. Select Backup Options then press Enter. Select Backup the System (Installation Image) then press Enter.


Figure 4-1 SysBack Backup Options Menu

4. Select Tsmdev tsm0 sb_atlantic on the Select Backup Device or Network Install Image Directory menu, then press Enter.



Figure 4-2 SysBack Backup the System Menu

5. Input the parameters as need. Normally, there is no need to change any parameter here just press Enter.


Figure 4-3 SysBack Backup screen

Chapter 4. BMR for AIX with SysBack operation 53

Figure 4-4 SysBack Backup Screen

6. Wait until the SysBack’s system backup completes successfully.

4.1.2 SysBack query TSM backup imagesThis section describes how to query SysBack’s system backup images that reside on the TSM Server. This query can be done only from SysBack’s client side. You cannot do this query on TSM Server.

To query SysBack’s system backup images on TSM Server:

1. Log in as root user ID (On AIX Sysback client machine).


3. Select Backup & Recovery Options then press Enter. Select TSM Configuration then press Enter. Select TSM Backup Management then press Enter. Select Query TSM Backup Images then press Enter.


AIX command line: # /usr/sbin/sbsmitout -s7 sysback -f'tsm0' '-v'


Figure 4-5 TSM Backup Management Menu

4. Select TSM0 sb_atlantic or the virtual device that coresponds to our virtual devices from the Select a TSM Virtual Device menu, then press Enter.

The following screen is displayed is Figure 4-6.

Figure 4-6 SysBack Query TSM Backup Images Menu

5. Then press Enter on the previous screen.



Figure 4-7 SysBack: Query TSM backup images

6. The previous screen shows the SysBack’s system backup images for this AIX machine. The number of version (number of lines showing out) may be different depending on how many versions you defined for the Backup Copy Group on the TSM Server.

4.1.3 SysBack’s system backup scriptThis section describes how to create a SysBack’s system backup script.

The SysBack software has a SMIT menu to create backup scripts on AIX. With this menu, you create a shell script file and put it into the /usr/lpp/sysback/sbscripts/ directory with a script name, which you specify in the parameter field.

The following are the steps to create the SysBack’s system backup script on AIX:

1. Log in as root user ID (on AIX SysBack’s client machine).


3. Select Backup Schedules and Scripts then press Enter. Select Backup Scripts then press Enter. Select Create a Backup Script File then press Enter. Select Create a System Backup Script then press Enter.


Note: The possible values for the type of backup images field are:

SB: Full System (Installation Image) backupVG: Volume Group level backupFS: File System level backupLV: Logical Volume level backupFD: File / Directory level backup

AIX command line: # /usr/sbin/sbtsmlist -l -n'tsm0'


Figure 4-8 Create a Backup Script Files Menu (SysBack)

4. Select a TSM virtual device from the option list Select Backup Device or Network Install Image Directory menu (e.g. Tsmdev tsm0 sb_atlantic from menu) then press Enter.


Figure 4-9 Create a System Backup Script Menu

5. Input parameters as required then press Enter. The following are examples of parameters:

* Backup Script name [monthly_system_backup] --> Script name

Script Description [System Backup]

Overwrite Existing Script no

Save Backup Output to a Log? YES --> This will log output from command to file

Location of Log File [/tmp/sysbacklog] --> The previous line must be “YES”

Overwrite Previous Log? no

--------- command options ----------- sysback

Hostname of server [ ]


Images directory [tsm0]

Create a Power Backup? no

*Backup file ID [06181622]

Dynamically Created Backup file ID YES

Report output type progress indicator

Include non-JFS logical volumes? yes

Compress data before writing to media? yes

User Description [ ]

Host read permission all hosts

User read permission all users

Buffer size (in Kbytes) [64]

Preserve physical partition mapping? no

Exclude List File Name [ ] --> This file will name all the files which you. DO NOT wish to backup

PULL BACKUP OPTIONS

Hostname to Backup [ ]

Overwrite existing backup with same ID? no

CD/DVD FILE FORMAT OPTIONS

CD/DVD Media Size [ ]

Media Available Space [ ]

Format backup image on a 2gb limit? no

Non-rootvg Volume Groups to include [ ]

6. Afterwards, press Enter, the following screen is displayed.

Figure 4-10 Create Backup Script Result (SysBack)


4.1.4 SysBack’s system backup scheduleThis section describes how to set up a schedule for SysBack’s system backup.

You should find the suitable time to schedule the SysBack’s system backup. This schedule will be different for each environment. Try to do SysBack’s system backup when the system has a minimum load.

There are two types of schedules you can set up:

� Distributed schedule on each AIX system� Consolidated schedule on TSM Server

Distributed schedule on each AIX systemThis setup will create a SysBack’s system backup schedule on each AIX machine. The SysBack software has a SMIT menu to define schedules for AIX. This SMIT menu will insert one command line into the scheduler (crontab). You can set up a schedule manually if you are familiar with crontab, otherwise, follow the following steps to set up SysBack’s system backup schedule:

1. Log in as root user ID (on AIX SysBack’s client machine).


3. Select Backup Schedules and Scripts then press Enter. Select Backup Schedules then press Enter. Select Create a Backup Schedule then press Enter.


Figure 4-11 Create a Backup Schedule Menu (SysBack)

4. Fill in the parameters as required. You can highlight Script Name and press F4 to see the backup scripts that you defined previously. The following example shows what the screen should look like if you want the system to start SysBack’s system backup on 25th of every month at 10.00 PM.


Figure 4-12 Create a Backup Schedule

5. The following screen displays after press Enter.

Figure 4-13 SysBack Schedule setup

6. You can check to see what is scheduled in crontab by running command # crontab -l.

The following screen displays output from # crontab -l command.


Figure 4-14 crontab -l output

Consolidated schedule on TSM ServerYou can also use the TSM scheduler for TSM Server and TSM Client to set up a schedule. This procedure requires the TSM backup client fileset to be installed on the AIX machine doing SysBack’s system backup along with 32-bit TSM API. You can choose TSM Server Prompt mode or TSM Client Polling mode to set up this scheduler. You put the SysBack’s system backup script name, which was created on previous step into the Object field of schedule you are defining. For details on the TSM Server and TSM client scheduler, please see the BM Tivoli Storage Manager Server, Installation and setup guide.

4.1.5 SysBack include/exclude setupThis section describes on how to INCLUDE/EXCLUDE files, directories, or filesystems from backup lists.

If there is no INCLUDE/EXCLUDE file in SysBack’s system backup, the Back up the System (installation image) will back up all filesystems in rootvg that are mounted. SysBack will not back up any filesystems in rootvg if they are not mounted at the time you start SysBack’s system backup.

SysBack INCLUDE setup (binding and rebinding Management Class)The purpose of INCLUDE in SysBack’s system backup is only to bind an object to a Management Class (MC) other than the default Management Class. Please see 1.2, “SysBack overview” on page 2.

Binding is a TSM term that refers to associating a file with a Management Class. When a backup is performed, the backup objects (images) are either bound to the default Management Class for the active policy set, or the objects are bound to the Management Class specified in our include and exclude lists.

Include statements are used to bind an object to a Management Class other than the default Management Class. The include statements are either placed directly in the /usr/tivoli/tsm/client/api/bin/dsm.sys file, or into an include and exclude files referenced by the specified server stanza in the dsm.sys file.


Include statements to bind SysBack backups to a non-default management class are a little different than the usual TSM include statements. There are only five possible include statements, which affect the binding of backups initiated by Sysback. They are:

INCLUDE /TSM4SBR/SB/* FullSystemBackupClass

INCLUDE /TSM4SBR/VG/* VolumeGroupBackupClass

INCLUDE /TSM4SBR/LV/* LogicalVolumeBackupClass

INCLUDE /TSM4SBR/FS/* FilesystemBackupClass

INCLUDE /TSM4SBR/FD/* FileDirectoryBackupClass

These include statements bind an entire backup type to a management class. For example, the Full System Backup is comprised of a table of contents image and several logical volumes images that represent the data of raw logical volumes and logical volumes that have mounted file systems. Each and every image created by a single backup operation, whether it be five or 20 images, will be bound to the same management class. Backup images are grouped by TSM so that all components of a single backup operation will expire at the same time based on the Management Class attributes.

The following screen in Figure 4-15 is displayed as an example of binding backup to another Management Class called mc.sysback.monthly.

Figure 4-15 example of /usr/tivoli/tsm/client/api/bin/dsm.sys (Include)

Rebinding Management Class to another Management ClassRebinding is a TSM term that refers to reassigning a backup to a different Management Class. When a backup type is rebound to a different management class, only the currently active backup, and all future backup operations after the Management Class is changed will be rebound.

Note: Make sure you do the validate/reactivate on any policy set, which you added another Management Class to, then you add the INCLUDE option into /usr/tivoli/tsm/client/api/bin/dsm.sys. The SysBack client does not see any new Management Class if you do not validate and reactivate the policy set.


For example, let us assume that you performed full system backups on Monday, Tuesday, and Wednesday using the default Management Class. Then on Thursday you assigned a new Management Class to the full system backup using an include statement. When the Thursday backup is initiated, the Thursday backup and the Wednesday backup will be rebound to the new Management Class.

SysBack EXCLUDE setupThe purpose of EXCLUDE regarding SysBack BMR will relate to what you are going to exclude from our SysBack’s system backup images. Make sure that anything you exclude from the SysBack’s system backup images is not used for the operating system. Otherwise, you cannot startup the operating system after you complete the SysBack BMR restoration.

In order to exclude specified files, directories, logical volumes, or file systems from backup processing, you must create an exclude list. The exclude list is created from within SysBack. TSM exclude statements located in a dsm.sys file will not be processed by SysBack backup commands.

You can exclude a single file, a directory (and all files beneath that directory), a filesystem, or a logical volume from all SysBack backups.

You cannot use the following characters in the exclude list because they have special meaning to some AIX commands:

$

*

+

?

^

Although some of these characters can be used in a file or directory name in AIX, those files or directories cannot be properly excluded when entered in the exclude list. Only the asterisk (*) character can be used in the exclude list, but this character represents a wildcard, allowing groups of files or directories with similar names to be excluded.

The following are examples of using wild cards in the exclude list:

/*test* All files in the system containing the word test

/*old All files on the system ending with old

/home/b* All files under /home starting with a b

/home/t*y All files under /home starting with t and ending with y

Note: If a directory name is excluded, all files below that directory are also excluded. This includes any files that might be required for the system to operate properly, and might parse into different filesystems. Use discretion when excluding directories to prevent creating a system backup that cannot be used as system installation media.

Note: Any entry starting with /* includes all directories on the system, not just the root (/) directory.


To create an exclude list:


2. Type smitty sb_exclude then press Enter.

3. Select Add a File, Directory, or Logical Volume to Exclude List then press Enter.


Figure 4-16 Add a File, Directory or Logical Volume to Exclude List

Exclude List File Name [ ] --> Press F1 for help.

Default file is /usr/lpp/sysback/.exclude_list --> If you do several kinds of SysBack’s backup you will have to create several exclude list files, one for each type of SysBack’s backup.

File or directory name to add [ ] --> Press F1 for help.

OR

Logical Volume name to add [ ] --> Press F1 for help.

4. Fill in the parameters then press Enter to create exclude list file.

5. You need to specify the exclude list file name on the field Exclude List File Name every time you start any SysBack backup (This also include SysBack’s system backup).

4.2 SysBack’s Bare Machine Recovery operationThis section describes the steps to do SysBack’s Bare Machine Recovery using network boot. The network boot will initiate from the AIX client machine to send bootp requests to the network boot server. This network boot server may or may not be the same as the TSM Server machine. The network boot server must be an AIX machine because it needs to support and respond to bootp requests. This SysBack BMR may need to be done due to a system hard disk crash, AIX operating system crash, or if you want to clone an AIX OS image from one machine to another.

To restore application data you should follow the TSM files backup/restore procedure or any Tivoli Data Production (TDP) backup/restore procedure for those application data restorations after the SysBack’s Bare Machine Recovery has completed.


Most of RS/6000 machines and all of IBM eServer, pSeries machines support network boot by setting up a System Management Service Menu (SMS Menu). The procedure or steps to go into the SMS menu may be different on each model of RS/6000 or IBM eServer, pSeries. Please consult an IBM Service Engineer on how to set up the SMS menu for certain RS/6000 or IBM eServer, pSeries machines to do network boot installation.

The following steps are based on the IBM eServer, pSeries Machine Type 7028 Model 6C4, and describe how to do an AIX network boot. After you finish the network boot, the AIX system will come up with SysBack’s system restore menu.

Steps to do a network boot and SysBack BMR restore, read the following section.

4.2.1 Initiate the network bootHere are the steps:

1. Power on IBM eServer pSeries.

2. Wait until the LED shows E1F1. Press key 1 on keyboard immediately. (Do not use numeric key pad.)


Figure 4-17 Network boot screen (Graphic Adapter Screen)

Or, see Figure 4-18.

Memory Keyboard network SCSI Speaker

PowerPC


Figure 4-18 Network Boot Screen (Dumb Terminal)

3. Then wait until the SMS screen comes up.

The following screen is the SMS Menu screen shown in Figure 4-19.

Figure 4-19 SMS Menu

4. Press the 4 key then press Enter to select Setup Remote IPL (Initial Program Load).



Figure 4-20 Network Parameter Menu

5. Type the 1 key then press Enter. To select 1. IP Parameter.


Figure 4-21 IP Parameter Menu (Network Boot)

6. Type the 1 key then press Enter. To select 1. Client IP address.



Figure 4-22 IP Parameter Menu

7. Type in Client IP address then press Enter.


Figure 4-23 IP Parameters Menu (Client IP Address)

8. Type the 2 key then press Enter, then select 2. Server IP Address.



Figure 4-24 IP Parameters Menu (Server IP Address)

9. Type in the Network Boot Server IP address as the previous screen then press Enter.


Figure 4-25 IP Parameters (Server IP Address)

10.If you have Gateway IP Address, do the same procedure as the previous steps.

11.Type the 4 key then press Enter, then select 4. Subnet Mask.



Figure 4-26 IP Parameters Menu (Subnet Mask)

12.Type in Subnet Mask, you are using for this Client IP Address then press Enter.


Figure 4-27 IP Parameters Menu (Subnet Mask)

13.Press ESC key to return to previous screen then press the 2 key to select 2. Adapter Parameters then press Enter.



Figure 4-28 Adapter parameters

14.Select the network adapter using for this network boot. e.g. In this example press the 1 key then press Enter to select 10/100 Mbps Ethernet PCI Adapter, location U0.1 P1/E2.


Figure 4-29 Adapter Parameters Menu

15.Select the one that match the network adapter then press Enter. In this example, press 5 to select ethernet, 100 Mbps, rj45, full duplex.

16.Press the ESC key until you reach the Network Parameters menu in Figure 4-30.


Figure 4-30 Network parameters menu

17.Press the 3 key to select 3. Ping Test then press Enter.


Figure 4-31 Adapter parameters menu (ping test)

18.Select the network adapter that matches the network adapter that you used for the Network Boot. In this example, press 1 key to select 1. 10/100 Mbps Ethernet PCI adapter then press Enter.



Figure 4-32 Adapter Parameters (Ping Test)

19.Select the Ethernet adapter that you used for the network boot. In this example, press 5 key to select 5. ethernet, 100, rj45, full then press Enter.

Figure 4-33 Adapter Parameters (Ping Test)

20.Press the 6 key on previous screen to select 6. Continue with Ping then press Enter.



Figure 4-34 Ping Test Menu

21.If the parameters above are all correct, then press the 5 key to select 5. Execute Ping Test then press Enter.


Figure 4-35 Ping test menu (starting ping)


Figure 4-36 Ping Success screen

22.Press Enter then press the M key to go back to the SMS main menu.

The following screen displays SMS Main Menu.

Figure 4-37 SMS Main Menu

23.Press the 7 key to select 7. Select Boot Options then press Enter.



Figure 4-38 Select boot options menu

24.Press the 1 key to select 1. Select Install or Boot Device then press Enter.


Figure 4-39 Select Device Type Menu (Select Boot Options)

25.Press 6 key to select 6. Network boot options to boot from network, then press Enter.



Figure 4-40 Select Device Menu (Select Boot Options)

26.Select the network adapter that matches our network boot adapter. In this example, press the 1 key then press Enter.


Figure 4-41 Select task menu (select boot options)

27.Press the 2 key to select 2. Normal Mode Boot then press Enter.



Figure 4-42 SMS menu

28.Press the 1 key then press Enter.

Figure 4-43 Network boot screen 1




29.From the previous screen press the 2 key to select this screen as system console.


Figure 4-46 Select Terminal Type Screen

30.Type in our terminal type then press Enter (such as vt100 or ibm3151).


Figure 4-47 Select terminal type screen


Figure 4-48 Select terminal type screen

31.Press the y key if the message on the screen is displayed correctly. If not, press n then go back to select new terminal type which matches our terminal.

After press the Y key. The following screen is displayed in Figure 4-49.

Figure 4-49 Tivoli Storage Manager for System Backup and Recovery Menu

This menu is Sysback restoration menu from the network boot.


4.2.2 Bare Machine Recovery for SysBack’s system restoreContinue from the previous step. After you get the previous screen from network boot, you have to do the following:

� Change installation device� Change volume group and logical volume information� Install the system with the current settings

You may need another two options if there is something wrong with the network boot.

� Utilities menu� Reboot the system

Figure 4-50 Tivoli Storage Manager for System Backup and Recovery (SysBack)

32.Select Change Installation Device then press Enter.



Figure 4-51 Change installation device menu

33.Select tsmdev TSM Virtual Device (ent0) as our restoration device then press Enter.


Figure 4-52 Change network interface menu

34.Select the network adapter that matches our installation. This network is the network connected to our TSM Server. Then press Enter.



Figure 4-53 Change TSM network settings menu

35.Fill in the parameters then press ESC key three times to go back to Sysback main menu. The following are examples of the required parameters:

Client IP Address 9.1.38.92 --> This AIX machine IP address.

Client Node Name sb_atlantic --> SysBack Client Node name which you registered on the TSM Server.

TSM Admin Name admin --> TSM Server administrator ID.

Server IP Address 9.1.38.95 --> This is the IP address of the TSM Server which kept images of the SysBack’s system. This IP address may or may not be the same as IP address of the network boot server.

Gateway IP Address 9.1.38.95 --> IP address of the Gateway incase your Client IP address is on different subnet to the TSM Server.

Subnet Mask 255.255.254.0 --> Client subnet mask.

Port Number 1500 --> TSM Server port, if you do not know, you can check from the /usr/tivoli/tsm/server/bin/dsmserv.opt file of the TSM Server.

Node/Admin Password admin --> Type in only the password of administrative user ID or password of SysBack’s Client Node, which you put above and already registered on the TSM Server. Do not put both passwords. In this example, you used admin as administrator user ID and password for admin ID is also admin.

36.When you are at Sysback Main Menu, select Change Volume Group & Logical Volume Information then press Enter.





The previous screen is displayed only if the SysBack program can contact the TSM Server that you set up in the previous step, and can get this information from the TSM Server. If you do not see the previous screen and get an error, please check and make sure that all parameters that you input in the previous step are correct. See A.0.5, “Wrong TSM API version in error recovery” on page 104 for more information.

37.Move cursor to the desired SysBack’s system backup images then press Enter.



Figure 4-56 Tivoli Storage Manager for System Backup and Recovery Menu (Select images)

38.Select backup images to be restored (previous step) and then press the ESC key.


Figure 4-57 Change volume group & logical volume information menu

39.Select Select Physical volumes for Volume Groups then press Enter.



Figure 4-58 Select Physical Volumes for “rootvg” Volume Group

From the previous screen, The hdisk2 shows rootvg because SysBack detected and found that hdisk2 used to be our rootvg before. If your old rootvg on hdisk0 was destroyed, and you replaced it with new a physical hard disk, you must restore the AIX OS. You will see Free on hdisk0 as the previous screen only. Move the cursor bar over the target hdiskx then press Enter; the status of each hard disk will be changed.

40.Select hdisk0 and hdisk1 for our rootvg, then press Enter.


Figure 4-59 Select physical volumes for “rootvg” volume group


On the previous screen, you select hdisk0 and hdisk1 for “rootvg” because you want to do mirroring after you restore the AIX OS. The rootvg on SysBack’s system backup images did mirror before; the SysBack feature supports changing the mirror or un-mirror option during restoration.

41.Press the ESC key then you will go back to Change Volume Group & Logical Volume Information Menu.



42.Select Change Volume Group Attribute the press Enter. This selection will only be needed if you need to change parameters regarding Volume Group Attribute, otherwise, press the ESC key to go back to the SysBack Main Menu.



Figure 4-61 Change “rootvg” volume group attributes

This screen is presented to give us the opportunity to alter the default parameters. If no changes are required, press the ESC key to go back to Change Volume Group & Logical Volume Information Menu.



43.Select Physical Volumes for Logical Volume then press Enter. This selection is only needed if you want change parameters regarding the physical volume and volume group, otherwise, press the ESC key to go back to SysBack Main Menu.



Figure 4-63 Select physical volumes for a logical volume

44.Change parameters as needed, then press the ESC key to go back to Change Volume Group & Logical Volume Information Menu.



45.Select Change Logical Volume Attributes then press Enter. This selection is only needed if you want to change parameters here, otherwise, press the ESC key to go back to SysBack Main Menu.



Figure 4-65 Change logical volume attributes menu

Figure 4-66 Change “hdx” Logical Volume Attributes Menu

46.Change parameters as needed then press the ESC key to go back to Change volume Group & Logical volume Information Menu.



Figure 4-67 Change Volume Group & Logical Volume Information Menu

47.Select Change Filesystem Attributes then press Enter. This selection is only needed if you want to change filesystem attributes parameters, otherwise, press the ESC key to go back to SysBack Main Menu.


Figure 4-68 Change filesystem attributes menu


Figure 4-69 Change Filesystem Attributes for “hdx” LV menu

Change parameters as needed then press the ESC key to go back to Change Volume Group & Logical Volume Information Menu.


Figure 4-70 Change Volume Group & Logical Volume Information Menu

48.Select Change Physical volume Attributes then press Enter. This selection is only needed if you want to change parameters regarding physical volume attributes, otherwise, press the ESC key to go back to SysBack Main Menu.



Figure 4-71 Change Physical Volume Attributes

Figure 4-72 Change Physical Volume Attributes

This will change Hot Spare status of hard disk. The Hot Spare feature is supported on AIX 5L. If you change this parameter, make sure this change will not conflict with other parameters such as mirroring.

Change parameter as need then press the ESC key twice to go back to SysBack Main Menu.



Figure 4-73 Tivoli Storage Manager for System Backup and Recovery

49.Select Install the System with Current Settings then press Enter.


Figure 4-74 Install the System

50.Press the Y key if you wish to continue the installation.



Figure 4-75 BMR for SysBack ‘s System Restore Start screen 1

Figure 4-76 BMR for SysBack ‘s System Restore Start screen 2

51.The LED in front of machine will show 0c46. Wait until the restoration is successful. After successfully restored, the AIX rootvg machine will reboot itself twice. This finishes the Bare Machine Recovery process.


Chapter 5. Performance considerations and tuning

This chapter discusses performance considerations and tuning of BMR for ITSM for System Backup and Recovery (SysBack) when integrated with the TSM Server.

The SysBack’s system backup or system restore times depend on the amount of data you need to back up or restore, the network speed, performance of hard disk being accessed to have access or store the data. The SysBack’s system backup times are almost equal to restoration times. Normally, if rootvg (root volume group) includes only the AIX system’s filesystems, then system backups or restores will not take a very long time to finish.

You can do some performance tuning for SysBack’s system backup and SysBack’s system restore. This chapter discusses the following topics:

� Exclude unnecessary files or directories from SysBack’s system backup� Network parameter tuning� SysBack’s parameter tuning� Storage pools and tape drives being use as backup/restore devices

5


5.1 Exclude unnecessary files or directories from SysBack’s system backup

Try to exclude the unnecessary files or directories on rootvg from SysBack’s system backup images which you create. For example, exclude database filesystem on rootvg from SysBack’s system backup because the data in the database filesystem cannot be used after SysBack’s system restore due to the data not being consistent. Database backups should always be done from the database software to ensure that they are synchronized and verifiable. Otherwise, you need Tivoli Data Protection (TDP) to do online backups, or you need to shut down the database manager before doing the database backup.

Figure 5-1 SysBack exclude

5.2 Network parameter tuningSince BMR for SysBack integrated with TSM Server can do system backup and restore only via TCP/IP protocol, the network parameters: tcp_sendspace and tcp_recvspace on AIX will have some negative effect if not properly set up.

To set up the tcp_sendspace and tcp_recvspace parameters:

� Use the no -o command to set up this parameter in the /etc/rc.net file.

� Use SysBack’s utilities, type smitty sb_chgsettings then press Enter.


rootvg

hdisk1

hdisk2

=

rootvg

//usr/var/tmp/home/opt/proc

/database

Sysback Exclude /database filesystem from rootvg(/usr/lpp/sysback/.exclude_list)

//usr/var/tmp/home/opt/proc

SysBack's system backup image

Exclude list


Figure 5-2 SysBack Change Program Defaults

Then change the following parameter and press Enter. The default value for this parameter is 16384:

TCP Send Buffer size (in bytes) [65536]

TCP Receive Buffer size (in bytes) [65536]

5.3 SysBack’s parameter tuningThe BMR for SysBack’s system backup and restore does have some parameters that you can set up during the backup time to enhance the backup performance:

� Create a Power Backup parameter when starting to do SysBack’s system backup using smitty sb_sysback

The default of no should be used to create a regular system backup that is fully customizable, and from which any type of data may be restored.

A power backup is one in which all the filesystem data is backed up as “raw” logical volumes. In many cases, this will provide better performance during the backup and during restoration from this backup, but provides some limitations on customizing the restoration as it is not possible to restore select files or directories.

5.4 Storage Pool and Tape drive being used as backup and restore devices

The backup times and restoration times also depend on where the SysBack’s system backup images go to reside on the storage pool of TSM Server such as the tape drive or hard disk;

Note: Also, logical volumes are backed up in their entirety, even if the filesystems are only half full. This could, therefore, decrease the backup and restore performance as you would be backing up “dead” space. Please be careful when you change this parameter. If not sure, leave this parameter as the default (no).

Chapter 5. Performance considerations and tuning 99

also, the speed of the tape drive being used on the TSM Server for doing SysBack’s system backup.

If possible, try to set up a disk storage pool and migrate to a tape drive storage pool. This will also help enhance the backup and restore performance.


Appendix A. Troubleshooting, hints, and tips

This appendix provides information about troubleshooting with some hints and tips for the SysBack backup and SysBack restore.

This appendix provides the following topics:

� Problem determination and troubleshooting� Error recovery� Hints and tips

A


5.5 Problem determinationUnderstanding basic SysBack and TSM problem determination tools may help you resolve minor problems without the need to contact support. In those situations where you would like to contact support for assistance, understanding the tools that support use may be helpful as well.

There are three primary items that you should monitor or review periodically to ensure that all of our backup processes are functioning properly. They are:

� The SysBack command output� The SysBack activity log� The SysBack error log for the 32-bit TSM API

A.0.1 The SysBack command outputThe most effective way to ensure that our backup operations are completing without error is to save the output from the backup operation. Sometimes, a backup completes with a status of successful but may also have warning messages. In order to determine what exactly caused the warnings, you will need to look at the output from the command. There have been scenarios where an overall backup process completed successfully, but due to an unforeseen operating system issue, much of the data was not actually backed up. In order to capture the output of the SysBack backup operations, you must redirect the standard output and the standard errors to a file. This may be achieved by issuing our command in a manner like this:

/usr/sbin/sysback -ftsm0 -I06181622 -i -x -p > /tmp/sysback_backup.log 2>&1

If you would like to monitor the backup process on the screen and save the output to a file, you can issue a command like the following:

/usr/sbin/sysback -ftsm0 -I06181622 -i -x -p | tee -a /tmp/sysback_backup.log 2>&1

There are several different methods for capturing the standard output (stdout) and standard error (stderr) from a command. There are also several ways to rotate our backup logs or to dynamically created the log name. Simply choose the method that is appropriate to our environment.

A.0.2 The SysBack activity logSysBack provides a basic activity log that indicates the start date and time of all backup, restore, and verify operations. It also includes the command issued, and if the command was successful, failed, and had warnings. For more information regarding the SysBack activity log, please refer to: Chapter 19, “Activity Logging”, on page 19-1 of SysBack Version 5.6 Installation and User’s Guide, GC32-9076. By default, the SysBack activity log is /var/adm/ras/sysback.log and the size is equal to 4 KB.

A.0.3 SysBack error log for the 32-bit TSM APIThe 32-bit TSM API error log specific to the SysBack initiated communications is located at /usr/lpp/sysback/sbtsmerror.log. You should periodically review this file for issues related to TSM server communications. Only “ANS” error messages are stored in this file. The BMR messages will only be displayed to the stderr and will not log into this file.

Note: You can override this location by setting the DSMI_LOG environment variable in our profile or .kshrc file.


A.0.4 Debug optionsOccasionally, more detailed information is needed for diagnosis; these primary options are available:

� Putting the SysBack programs into debug� Putting SysBack’s system restore into debug� Putting SysBack 32-bit TSM API programs into debug� Tracing the 32-bit TSM API programs

Please contact support for detailed information with using any of these debug options. The following are some examples to set up the debug options.

A.0.4.1 Putting the SysBack programs into debugTo debug SysBack programs you need to set the SBDEBUG parameter to 1 in the user profile and then start the SysBack programs or activity. The output includes detailed debugging information and will be put to /tmp/output.log file:

# export SBDEBUG=1# /usr/sbin/sysback -ftsm0 -I06181622 -i -x -p > /tmp/output.log 2>&1

or

# /usr/sbin/mkvgback -ftsm0 datavg > /tmp/output.log 2>&1

The previous command will do a SysBack’s volume group backup. The verbose output and detailed log will be put to /tmp/output.log

A.0.4.2 Turn on the debug mode for BMR for SysBack’s system restoreThere are two procedures to turn on the debug mode for the SysBack’s system restoration:

1. At the Set Network Install Client Defaults setup step (smitty sb_cfginstclient)

You can change Debug Logging? parameter to be yes. The SysBack’s system restoration will log detailed output into the /tmp/debug.out.mmddyy file during restore process. This file can be used to help troubleshoot the problems encountered during the Sysback’s system restoration.

Appendix A. Troubleshooting, hints, and tips 103

2. After you successfully do a network boot and come up with the SysBack’s system restoration menu, press the Shift-D keys on the keyboard. The word DEBUG will be shown at lower right corner of the screen. The debug output will be saved in /tmp/debug.out.mmddyy.

A.0.5 Wrong TSM API version in error recovery

Figure 5-3 libApiDS.a error

The previous screen displays a TSM API error, SysBack cannot locate /usr/tivoli/tsm/client/api/bin/libApiDS.a on system. This error is due to the fact that there is no 32-bit TSM API installed on system or you have installed the 64-bit TSM API. The 64-bit TSM API is located in the /usr/tivoli/tsm/client/api/bin64 directory (this directory does not contain the required “libApiDS.a” file). The 32-bit TSM API is located in the /usr/tivoli/tsm/client/api/bin directory this directory contains the “libApiDS.a” file. As state previously, SysBack requires the 32-bit TSM API.

A.0.6 Wrong passwordWhen you access the Change Volume Group & Logical Volume Information menu from SysBack’s network boot menu in an attempt to verify the Logical Volume Manager (LVM) informations on the SysBack’s system backup images, you may encounter the following screen in Figure 5-4, or the Unable to open the LVM information file message.


Figure 5-4 Verifying LVM Information error

This error will occur if the wrong TSM admin password or SysBack’s client password was used in the previous step.

A.0.7 NIM problem: /dev/ram0 (/) filesystem 100% fullWhen you successfully do a NIM Network Boot, then go to setup the SysBack’s installation device. Try to select Tsmdev then press Enter, after that the list will disappear from the screen. You cannot change or update any of the “Installation devices” once you have pressed Enter.

The following screen displays Change Installation Device. When you select Tsmdev then press Enter, the list previously available will have disappeared from the screen.


Figure 5-5 Change Installation Device menu

Figure 5-6 Change Network Interface menu (error)

The previous error occurs if the /dev/ram0 (/) created by NIM boot file was too small. The SysBack program tried to update information into /tmp which was located on /dev/ram0 (/) when changing the network interface.

You can check the status of the /dev/ram0 (/) filesystem by going to Utilities Menu then select Start Maintenance shell then run the df command.

The following screen in Figure 5-7 displays the df command output.


Figure 5-7 output from the df command

To solve this problem, you need to edit the /usr/sbin/mksbnetboot file on the NIM network boot server. Search for ramfs and copy this line to the next line (our advice is to comment out the original line and modify the newly created line). This ramfs parameter defines the minimum size of /dev/ram0 (/) to be created when you do a NIM Network Boot. The default value is “26624 Blocks of 512 Bytes ” (13 MB). You may change this to be “51200” (25 MB) if our system still has enough physical memory (32 MB or more). You also need to change the “value” number on the line after the ramfs variable line, the “awkprog3=" \$1 !~ /<noboot>/ { print \$0 } \$1 ~ /<noboot>/ { print \$1 \" 51200 \" \$3 } /rc\.boot/ { print \"\tcomp.kext ---- 777 0 0 /sbin/comp.kext\"; print \"\tcomp.uext ---- 777 0 0 /sbin/comp.uext\"} " ”, to be the same value as ramfs variable. Then recreate the boot images by using the smitty sb_cfgnetboot menu of the SysBack’s program on the NIM Network Boot Server. The /usr/sbin/mksbnetboot is used to create the Network Boot image file (e.g. /tftpboot/azov --> /usr/lpp/sysback/netinst/bootimages/spot1.chrp.mp.ent).

The following example displays part of the /usr/sbin/mksbnetboot file:

Example 5-1 /usr/sbin/mksbnetboot file

+516 # awk program substitute fs size in first line and adds two lines right after+517 # sbin/rc.boot+518 #ramfs=26624 # 13MB+519 ramfs=51200 # 25MB+520 #awkprog3=" \$1 !~ /<noboot>/ { print \$0 }+521 #\$1 ~ /<noboot>/ { print \$1 \" 26624 \" \$3 } \+522 #/rc\.boot/ { print \"\tcomp.kext ---- 777 0 0 /sbin/comp.kext\"; print \"\tcomp.uext ---- 777 0 0 /sbin/comp.uext\"} "+523 awkprog3=" \$1 !~ /<noboot>/ { print \$0 }+524 \$1 ~ /<noboot>/ { print \$1 \" 51200 \" \$3 } \+525 /rc\.boot/ { print \"\tcomp.kext ---- 777 0 0 /sbin/comp.kext\"; print \"\tcomp.uext ---- 777 0 0 /sbin/comp.uext\"} "

Note: Please be careful when you edit /usr/sbin/mksbnetboot. This is an executable shell script file. Please make a copy of original file before doing modification.


+526+527 function custproto+528 { # input : proto file to customize+529 $XSET

A.0.8 LPAR machine installationFor eServer pSeries machines which support Logical Partitions (LPARs). You can set up BMR for SysBack on each LPAR like you are setting it up on an individual machine. You use vterm on the Hardware Management Console (HMC) as a console for each partition. For more details related to reinstalling LPAR capable systems, please refer to the IBM Redbook The Complete Partitioning Guide for IBM eServer pSeries Servers, SG24-7039-00 located at:http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg247039.pdf

A.0.9 Volume group to includeYou can include other volume groups into the SysBack’s system backup images when you do the SysBack’s system backup. But this volume group should contain the programs which are not dynamically updated. For example; the db2 programs (not database) which are never to be changed after the install. The BMR for AIX with SysBack will restore the AIX’s system and application programs together and at the same time.

A.0.10 No prompt installationYou can set up the “no prompt” installation for SysBack’s system restoration. This will allow the network boot client machine to do the SysBack’s system restoration without any user intervention.

For further information, Please see Section 3.3, “Setup and customizing SysBack and 32-bit TSM API” on page 20.

A.0.11 Install additional Device DriversThe new machine to which you restore an AIX image may have different hardware e.g. new type of Ethernet network adapter, so, this machine will need additional device drivers to be installed after successfully restoring the AIX image. For further information on this See “Set Network Install Client Defaults” on 3.3.3, “AIX Network Boot Server setup” on page 29.


http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg247039.pdf

Figure 5-8 Set Network Install Client Defaults Menu

The “Set” parameter at the “Utilities” Menu of the SysBack menu is available after successfully doing a network boot. Review the following several screens to follow the process.

Figure 5-9 Utilities menu, network boot menu (network boot)


Figure 5-10 Post Install Configuration Options Menu (Network Boot)

Figure 5-11 Install Additional Device Support Menu (Network Boot)


Figure 5-12 Change Installation Device Menu (Network Boot)

Figure 5-13 Install Additional Device Support

A.0.12 Restore files from SysBack’s system backup images You can restore particular files or directories from the SysBack’s system backup image. If you accidentally delete some system files and the system still works you still can do a SysBack restoration.

To do this restoration, the parameter “create a Power Backup” must have been set to “no” at SysBack’s system backup.


A.0.13 Restore files from another SysBack’s client backup imageYou can utilize the files stored in the SysBack’s backup images from other AIX machines if you need a particular files or directories on another AIX machine that may have been corrupted or deleted on this machine. You can do this by:

1. Edit /usr/tivoli/tsm/client/api/bin/dsm.opt and /usr/tivoli/tsm/client/api/bin/dsm.sys file on the target machine that you want to restore the files to. Add the source SysBack’s client name into these two files.

2. Add a new TSM virtual device (e.g. TSM1) which corresponds to the source SysBack’s client name.

3. Then, you can restore the source SysBack’s client files using the new TSM virtual device to the target machine.

Note: Please be careful because the restored files may overwrite local files. Make sure that the restored files will go to temporary directory.


Appendix B. Sample parameter and log files

This appendix provides the following samples of parameter files and log files:

� /usr/tivoli/tsm/client/api/bin/dsm.sys� /usr/tivoli/tsmclient/api/bin/dsm.opt� /usr/lpp/sysback/.settings� /usr/lpp/sysback/.exclude_list� /usr/lpp/sysback/sbscripts/monthly_system_backup� /usr/lpp/sysback/tsm/dsm.opt.tsm0� /usr/lpp/sysback/sbtsmerror.log� /var/adm/ras/sysback.log� /tmp/debug.out.mmddyy� /tmp/output.log� SysBack’s files after Network Boot up

B


/usr/tivoli/tsm/client/api/bin/dsm.sysExample 5-2 /usr/tivoli/tsm/client/api/bin/dsm.sys on atlantic.almaden.ibm.com

************************************************************************* Tivoli Storage Manager ** Sample Client System Options file for AIX and SunOS (dsm.sys.smp)

************************************************************************** This file contains the minimum options required to get started using TSM. Copy the ** dsm.sys.smp to* If your client node communicates with multiple TSM servers, be sure to add a stanza, ** beginning *

************************************************************************************SErvername sb_atlanticNODename sb_atlantic COMMMethod TCPIPTCPPort 1500TCPServeraddress baltic.almaden.ibm.comPASSWORDAccess generate

* The following TSM Client Options are allowed with IBM Tivoli Storage Manager* for System Backup and Recovery:* COMMMethod* COMMRESTARTDuration* COMMRESTARTInterval* COMPRESSAlways* COMPRESSIon* FROMNode* INCLexcl

**Note: Only 5 Include statements are supported in this file. Please see the section**“Binding and Rebinding Backups to TSM Management Classes” on**page 15-17 of GC32-9076, SysBack Version 5.6: installation and User Guide for details.* INCLUDE

**Note: Only 5 Include statements are supported for backup processing. Please see**the section “Binding and Rebinding Backups to TSM Management**Classes” on page 15-17 of GC32-9076, SysBack Version 5.6: installation and User Guide**for details for details.

* MAILprog* NODename* PASSWORDAccess

**Note: Only the generate value is supported with this option

* PASSWORDDIR* SErvername* TCPBuffsize* TCPNodelay* TCPPort* TCPServeraddress* TPCPWindowsize


**Note: For more detailed information on configuring the dsm.sys and dsm.opt files,**and an explanation of the uses for each of the referenced options, please**refer to the IBM Tivoli Storage Manager for Unix: Backup - Archive Clients**Installation and User’s Guide (GC32-0789)

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

************************************************************************* Tivoli Storage Manager ** ** Sample Client User Options file for AIX and SunOS (dsm.opt.smp) *

************************************************************************* This file contains an option you can use to specify the TSM* server to contact if more than one is defined in your client* system options file (dsm.sys). Copy dsm.opt.smp to dsm.opt.* If you enter a server name for the option below, remove the* leading asterisk (*).

************************************************************************* SErvername A server name defined in the dsm.sys fileSErvername sb_atlantic

/usr/lpp/sysback/tsm/dsm.opt.tsm0Example 5-4 /usr/lpp/sysback/tsm/dsm.opt.tsm0 file

SErvername sb_atlantic

/usr/lpp/sysback/.settingsExample 5-5 /usr/lpp/sysback/.settings file

READCNT 50SYNCCNT 50RETRYCNT 2000PADERRS 1BACKEND BSNDBUF 65536RCVBUF 65536

Appendix B. Sample parameter and log files 115

/usr/lpp/sysback/.exclude_listExample 5-6 /usr/lpp/sysback/.exclude_list file

/fixes

/usr/lpp/sysback/sbscripts/monthly_system_backupExample 5-7 /usr/lpp/sysback/sbscripts/monthly_system_backup file

#!/bin/ksh# Command filename: /usr/lpp/sysback/sbscripts/monthly_system_backup# Description: System Backup

sysback -ftsm0 -I06181622 -i -x -p > /tmp/monthly_sysback.log 2>&1

exit $?

/usr/lpp/sysback/sbtsmerror.logExample 5-8 /usr/lpp/sysback/sbtsmerror.log file

06/30/03 11:54:28 ANS0101E NLInit: Unable to open message repository 'dsmclientV3.cat'.

/var/adm/ras/sysback.logThis file is alog format file. You need to run alog command to display information:

# alog -f /var/adm/ras/sysback.log -o | pg

or

# alog -f /var/adm/ras/sysback.log -o > /tmp/sysback.log

Then open /tmp/sysback.log to check the log.

Example 5-9 alog -f /var/adm/ras/sysback.log -o

perform an incremental level 1 backup becausethere is no record of a prior-level backup for the/tmp filesystem.Backup will now continue...

WARNING: Skipping /var filesystem.You cannot perform an incremental level 1 backup becausethere is no record of a prior-level backup for the/var filesystem.Backup will now continue...

There are no more filesystems or logical volumes leftto process. The backup was not performed!

Backup failed at Fri Jun 27 09:45:53 PDT 2003FAILURE: Volume Group backup failed to complete.


Command: /usr/sbin/mkjfsback -ftsm0 -v /varDate: Fri Jun 27 09:47:35 PDT 2003Backup ended Fri Jun 27 09:47:38 PDT 2003SUCCESS: Filesystem backup completed successfully.

Command: /usr/sbin/mkvgback -ftsm0 -l1 -v rootvgDate: Fri Jun 27 09:49:06 PDT 2003

WARNING: Skipping / filesystem.You cannot perform an incremental level 1 backup becausethere is no record of a prior-level backup for the/ filesystem.Backup will now continue...

WARNING: Skipping /usr filesystem.You cannot perform an incremental level 1 backup becausethere is no record of a prior-level backup for the/usr filesystem.Backup will now continue...

WARNING: Skipping /home filesystem.

/tmp/debug.out.mmddyyThis file is the debuging file. You need to set the parameter Debug Logging = Yes when you set SysBack parameter, set Network Install Client Defaults on the network boot server. Or, press Shift-D at the SysBack console after successfully doing a network boot on the SysBack client machine.

Example 5-10 /tmp/debug.out.062603

------------ [sysinstall runshell: Thu Jun 26 21:27:22 2003] --------------+ typeset -i numpvs+ rm -f /tmp/inst_error+ MAXPPS=1016+ KSH=/bin/ksh------------ [sysinstall setupfiles: Thu Jun 26 21:33:34 2003] --------------+ typeset -i numpvs+ rm -f /tmp/inst_error+ MAXPPS=1016+ KSH=/bin/ksh+ set -x+ cd /+ [ -z ]+ [ ! -f /usr/lib/methods/devices.cat -a 5 != 5 -a -z ]+ [ 5 = 3 -a ! -f /tmp/cd.extract ]+ [ ! -z ]+ 1> /tmp/pvinfo+ getlvminfo -PN+ VGname=+ getlvminfo -VN+ [ -z ]+ VGname=(free)+ + getlvminfo -P hdisk0 -iIPVid=0009cd9aea9f4324+ + getlvminfo -P hdisk0 -iXLocation=1S-08-00-8,0


+ [ -z 1S-08-00-8,0 ]+ + lsdev -Cl hdisk0 -F descriptiondesc=16 Bit LVD SCSI Disk Drive+ print hdisk0 (free) 0009cd9aea9f4324 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive+ VGname=+ getlvminfo -VN+ [ -z ]+ VGname=(free)+ + getlvminfo -P hdisk1 -iIPVid=0009cd9af71db2c1+ + getlvminfo -P hdisk1 -iXLocation=1S-08-00-9,0+ [ -z 1S-08-00-9,0 ]+ + lsdev -Cl hdisk1 -F descriptiondesc=16 Bit LVD SCSI Disk Drive

/tmp/output.logThis file contains the debugging output when you set environmental parameter SBDEBUG=1 the next time you issue a SysBack command the output will be redirected to a file.

The following example uses the following command:# export SBDEBUG=1# /usr/sbin/sbtsmlist -l -n'tsm0' > /tmp/output.log1 2>&1

Example 5-11 /tmp/output.log file

***************************************************Program: “sbtsmlist” in Function: “Main”***************************************************

+ getoptions -l -ntsm0

***************************************************Program: “sbtsmlist” in Function: “getoptions”***************************************************

+ unset action list_type id manage+ getopt maorlg:n:t: -l -ntsm0+ 2> /dev/null+ set -- -l -n tsm0 --+ [ 0 -ne 0 ]+ [ -l != -- ]+ action=l+ shift+ [ -n != -- ]+ devname=tsm0+ shift+ shift+ [ -- != -- ]+ func_end getoptions

******************************************* Function “getoptions” has ended.*******************************************

+ check_flags


***************************************************Program: “sbtsmlist” in Function: “check_flags”***************************************************

+ [ -z l ]+ [ l = r ]+ [ l = l ]+ [ -z tsm0 ]+ [ ! -z ]+ [ ! -z ]+ func_end check_flags

******************************************* Function “check_flags” has ended.*******************************************

+ list_tsmbackups

***************************************************Program: “sbtsmlist” in Function: “list_tsmbackups”***************************************************

+ [ ! -z ]+ [ ! -z ]+ [ ! -z ]+ [ ! -z ]+ get_tsmdev tsm0

***************************************************Program: “sbtsmlist” in Function: “get_tsmdev”***************************************************

+ tsm_dev=tsm0+ tsmvirdevfile=/usr/lpp/sysback/tsm/dsm.opt.tsm0+ [ ! -f /usr/lpp/sysback/tsm/dsm.opt.tsm0 ]+ export DSMI_CONFIG=/usr/lpp/sysback/tsm/dsm.opt.tsm0+ func_end get_tsmdev

******************************************* Function “get_tsmdev” has ended.*******************************************

+ sbtsm query Backup ID Type Active? Open? Management Class Backup Date------------ ---- ------- ------- ---------------- ------------------- 0.1334 FS Yes No MC.SYSBACK.MONTHLY 06/27/2003 09:47:09 0.1369 SB Yes No MC.SYSBACK.MONTHLY 07/01/2003 03:59:34 0.1353 SB No No MC.SYSBACK.MONTHLY 06/30/2003 03:59:37 0.1361 SB No No MC.SYSBACK.MONTHLY 06/30/2003 11:55:39+ func_end list_tsmbackups

******************************************* Function “list_tsmbackups” has ended.*******************************************

+ cancel 0

***************************************************Program: “sbtsmlist” in Function: “cancel”


***************************************************

+ rm -f /tmp/16694*+ 2> /dev/null+ exit 0

SysBack’s files after Network Boot upAfter you successfully do a network boot and come up with the SysBack restoration menu, you choose Utilities then choose Start Maintenance shell to see the following files.

/tmp/tsminfoExample 5-12 /tmp/tsminfo

ent0 9.1.38.89 9.1.38.95 255.255.254.0 0 9.1.38.95 0 en0 0

/tmp/instdevinfoExample 5-13 /tmp/instdevinfo file

/dev/cd0 IDE CD-ROM Dirve (650 MB) 1G-19-00/dev/ent0 10/100 Mbps Ethernet PCI adapter II 1L-08/dev/ent1 IBM 10/100/1000 Base-T Ethernet PCI 1n-08/dev/ent2 10/100 Mbps Ethernet PCI adapter II 14-08Tsmdev TSM Virtual Device (ent0) 1L-08

/tmp/device.pkgsExample 5-14 /tmp/device.pkgs

devices.chrp.basedevices.chrp.pcidevices.chrp_lpar.basedevices.fcp.tapedevices.ide.cdromdevices.isa_sio.8042devices.isa_sio.chrp.8042devices.isa_sio.chrp.ecpdevices.isa_sio.fdcdevices.isa_sio.paralleldevices.isa_sio.pnpPNP.400devices.isa_sio.pnpPNP.501devices.isa_sio.pnpPNP.700devices.isa_sio.serialdevices.pci.00100010devices.pci.00100f00devices.pci.00102100devices.pci.14100401devices.pci.14103302devices.pci.1410ff01devices.pci.2b102505devices.pci.86802912devices.pci.MTRX.G450


/tmp/dsm.opt.tsm0Example 5-15 /tmp/dsm.opt.tsm0

SErvername tsmserver

/tmp/dsm.sysExample 5-16 /tmp/dsm.sys

SErvername tsmservercommmethod tcpiptcpserveraddress 9.1.39.148tcpport 1500

/tmp/instdevExample 5-17 /tmp/instdev

/dev/ent0

/tmp/instdevdescExample 5-18 /tmp/instdevdesc

Network [ent0]

/tmp/instdevinfoExample 5-19 /tmp/instdevinfo

/dev/cd0 IDE CD-ROM Drive I (650 MB) 1G-19-00/dev/ent0 10/100 Mbps Ethernet PCI Adapter II 1L-08/dev/ent1 IBM 10/100/1000 Base-T Ethernet PCI 1n-08/dev/ent2 10/100 Mbps Ethernet PCI Adapter II 14-08tsmdev TSM Virtual Device (ent0) 1L-08

/tmp/netinfoExample 5-20 /tmp/netinfo

ent0 9.1.38.89 9.1.38.95 255.255.254.0 9.1.38.95 0 en0 0

/tmp/netstatExample 5-21 /tmp/netstat

ent0

/tmp/nfsdevExample 5-22 /tmp/nfsdev

/export/lpp_source/lpp_source1


/tmp/nfsdevfileExample 5-23 /tmp/nfsdevfile

/dev/cd0 IDE CD-ROM Drive I (650 MB) 1G-19-00/export/lpp_source/lpp_source1 LPP Source Directory

/tmp/nfsinfoExample 5-24 /tmp/nfsinfo

ent0 9.1.38.89 9.1.38.95 255.255.254.0 9.1.38.95 0 en0 0

/tmp/pvinfoExample 5-25 /tmp/pvinfo

hdisk0 (free) 0009cd9aea9f4324 1S-08-00-8,0 16 Bit LVD SCSI Disk Drivehdisk1 (free) 0009cd9af71db2c1 1S-08-00-9,0 16 Bit LVD SCSI Disk Drivehdisk2 (free) 0009cd9ab922cb5c 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive

/tmp/tsm_clientExample 5-26 /tmp/tsm_client

NODE 9.1.38.89PASSWORD abcdeTSM_ADMIN_ID admin

/tmp/tsminfoExample 5-27 /tmp/tsminfo

ent0 9.1.38.89 9.1.39.148 255.255.254.0 9.1.38.95 0 en0 0

/tmp/tsmnetdevsExample 5-28 /tmp/tsmnetdevs

/dev/ent0 10/100 Mbps Ethernet PCI Adapter II 1L-08/dev/ent1 IBM 10/100/1000 Base-T Ethernet PCI 1n-08/dev/ent2 10/100 Mbps Ethernet PCI Adapter II 14-08


®

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

Redpaper

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

This Redpaper describes the use of IBM Tivoli Storage Manager (ITSM) V5.2 or above, to perform Bare Metal Restoration of AIX using SYSBACK.

SYSBACK provides facilities to perform Bare Machine Recovery from tape. The purpose of this paper is to show how SYSBACK may be integrated with IBM Tivoli Storage Manager to protect your systems from catastrophic server failures.

Back cover


