SQL-BackTrack™ Module for IBM Tivoli Storage Manager Installation and User Guide Version 3.1.00

March 29, 2018 | Author: dillonr01 | Category: 64 Bit Computing, Backup, Portable Document Format, Operating System, Server (Computing)
Share
Report this link


Comments



Description

SQL-BackTrack™ Module for IBM Tivoli Storage Manager Installation and User GuideVersion 3.1.00 July 25, 2003 Copyright 2003 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. IBM and DB2 are registered trademarks of International Business Machines Corp.; Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corp. All other registered trademarks or trademarks belong to their respective companies. THE USE AND CONTENTS OF THIS DOCUMENTATION ARE GOVERNED BY THE SOFTWARE LICENSE AGREEMENT ENCLOSED AT THE BACK OF THIS DOCUMENTATION. Restricted Rights Legend U.S. GOVERNMENT RESTRICTED RIGHTS. UNPUBLISHED–RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in FAR Section 52.227-14 Alt. III (g)(3), FAR Section 52.227-19, DFARS 252.227-7014 (b), or DFARS 227.7202, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address. Contacting BMC Software You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC Software, Inc. 2101 CityWest Blvd. Houston TX 77042-2827 713 918 8800 or 800 841 2031 713 918 8000 Outside United States and Canada Telephone Fax (01) 713 918 8800 (01) 713 918 8000 Telephone Fax Customer Support You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see “Before Contacting BMC Software.” Support Web Site You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home.html. From this Web site, you can • • • • • • • read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers Support by Telephone or E-mail In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and e-mail contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at www.bmc.com/support.html. Before Contacting BMC Software Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately: • product information — — — • product name product version (release number) license number and password (trial or permanent) operating system and environment information — — — — — machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level BMC Software, Inc., Confidential and Proprietary Information iii • • • sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) — — — product error messages messages from the operating system.. Inc. such as file system full messages from related software BMC Software. Confidential and Proprietary Information iv SQL-BackTrack Module for IBM TSM Installation and User Guide . . . . . . . . . . . 1-6 Password Access . . . . . . 1-2 LAN Configuration . . . . . . . . . . . . . . . . . . . . . . 1-8 Accessing Documentation on the Product CD . . . . . . . . . . . . . . . . . . . . . 1-7 Media Mount Wait Time . . . . . . . . . . . . . 1-10 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Chapter 1 Introducing the SQL-BackTrack Module for IBM TSM Overview . . . . . . . . . 2-2 Supported Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Installation Procedures . . . . . . . . . . . . . Confidential and Proprietary Information Contents v . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Chapter 2 Installing the SQL-BackTrack Module for IBM TSM Overview . 1-2 SAN Configuration . . . . . . . . . . . . . . . Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Installing the SQL-BackTrack Module on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 How IBM TSM and the SQL-BackTrack Module Work Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Upgrading the SQL-BackTrack Module for IBM TSM . . . . . . . . . . . . . . . 1-5 Nodename Verification . . . . .. . . . . . . . . . . 1-9 Viewing the SQL-BackTrack Module Documentation . . . . . . . . . . . . . . 2-8 Installing the SQL-BackTrack Module on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 BMC Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Installing the Acrobat Reader from the Product CD . . . . . .Contents Contents About This Book . . . . . . . . . . . . . . . . . 2-5 Installation Account Requirements . . . . . . . . . . . . . . 1-7 Filespace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Software and Hardware Requirements . . . . . . . . . . . . . . . . . . 1-6 Management Classes and Storage Pools . . . . . 1-7 LAN-Free Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10 COMMTIMEOUT Setting . . . . . . . . . . . .3-9 Compression Setting . . .Setting Environment Variables . . . . . . . .2-22 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4 IBM TSM Server Name . . . .3-14 Configuring the IBM TSM Server Settings . . . . . . . . . . . . .3-28 Running the adsmpw Utility . . . . . . . . . . . . .3-25 Editing the Storage Agent Options Files . . . . . . . . . . . . . .3-18 Editing the IBM TSM Client User Options File (dsm. . . . . . . . . . . . . . . . . . . . . . . .3-8 LAN-free Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14 Setting Unix Environment Variables During Post-Installation . .3-30 Validating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-19 Setting Optional Environment Variables . . . . . . . . . . . . . . . . . . . . . . . .. .3-2 IBM TSM Options . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Adding the SQL-BackTrack Module to SQL-BackTrack on Unix . . . . .3-13 Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . .3-11 Storage Pools . . . . . . . Confidential and Proprietary Information vi SQL-BackTrack Module for IBM TSM Installation and User Guide . .2-16 Setting Windows Environment Variables During Post-Installation . . .sys) on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 Validating the IBM TSM Configuration . . . . . . . . . . . . . . . . . . . . . . . .3-6 IBM TSM Node Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38 Chapter 4 Configuring SQL-BackTrack for Use with IBM TSM Overview . . . . . . . .3-11 Management Class . . . . . . . . . . . . . . . . . . . . . .3-33 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 Configuring the IBM TSM Client . . . . . . . . . . . . . . . . . . . .3-7 Filespace Tag . . . . . . . . . . . . . . . . . . . . . . . . .3-17 Editing the Client System Options File (dsm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9 Communication Method .2-24 Chapter 3 Configuring IBM TSM for Use with SQL-BackTrack Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22 Editing the IBM TSM Client Options File (dsm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12 Include-Exclude List . . . . . . . . Inc. . . . . . . . . . . . . . . . . . . . . . .4-4 BMC Software. . . . . . . . . . . . . . . . .3-6 Password Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .opt) on Windows . . . . . . . . . . . . . . . . . . . . . . . .3-10 MOUNTWAIT Setting . . . . . . . . . . . . . . . . . .opt) on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Prerequisites for On-Demand and Unattended Backups . . A-2 BMC Software. . . . 6-3 Recovering from an Alternate Host . . . . . . . . . . . . . . 5-11 Expiring Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27 Improving Your Backup Performance . 5-10 Monitoring Backups Using SQL-BackTrack Utilities . 5-16 Chapter 6 Recovering Data Using SQL-BackTrack to Recover . . . . . 5-13 Improved Expiration (Expiration Retry Feature) . . . . . 5-4 Running On-Demand Backups with SQL-BackTrack . . 4-31 Using Multiple IBM TSM Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Alternate Host Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inc. . . . . . . . 5-14 Manually Deleting SQL-BackTrack Objects . . . . . . . 4-32 Chapter 5 Backing Up Data Overview . . . 5-14 Troubleshooting Object Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Using IBM TSM Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Adding Environment Variables to Backup Scripts . . . . . . . . . . . . . . . . . .Adding the SQL-BackTrack Module to SQL-BackTrack on Windows . . . . . . . . 5-5 Scheduling Unattended Backups . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Overriding IBM TSM Options . . . . 4-16 Defining a Backup Pool . . . . . . . . . . . . Confidential and Proprietary Information Contents vii . . . . . . . . . . . . . . . . . . . . 6-4 Appendix A Error Messages On Unix and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Using cron . . . . 5-10 Monitoring Backups . . . . . . . . . . . . . . . . . . . . . . 4-31 Using Memory Mapped I/O for SQL-BackTrack for Oracle . . . . . . . . . . . . . . . . . . . . . . 4-11 Defining a Backup Pool for the SQL-BackTrack Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Using the Windows Scheduler . A-2 On Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23 Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 Defining a Backup Pool (Oracle Parallel Server Users) . . . . . 5-10 Monitoring Backups Using IBM TSM Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Software. Confidential and Proprietary Information viii SQL-BackTrack Module for IBM TSM Installation and User Guide .. Inc. . . . . . . . . . . . . . . . . . . . .Figures Figures Figure 1-1 Figure 1-2 Figure 3-1 Figure 3-2 Figure 5-1 Configuration for Backing Up and Recovering Over a LAN . . . . . 1-3 1-4 3-3 3-4 5-3 BMC Software. . Task Map for Configuring IBM TSM (part 2 of 2) . .. Task Map for Backing Up Data . . Configuration for Backing Up and Recovering Across a SAN . . . . Inc. . . . Confidential and Proprietary Information Figures ix . . . . Task Map for Configuring IBM TSM (part 1 of 2) . . . . . . . . BMC Software. Confidential and Proprietary Information x SQL-BackTrack Module for IBM TSM Installation and User Guide .. Inc. . . . . . . . . . . . . . . . .sys file on Unix . Unix Environment Variables for Post-Installation . . . . . PASSWORDAccess Options . . . . . . . . Confidential and Proprietary Information Tables xi . . . . .. . . . . . . . . . . . . . . . . . . . . . Settings for dsm. . .Tables Tables Table 2-1 Table 2-2 Table 2-3 Table 2-4 Table 2-5 Table 2-6 Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 4-1 Installation Tasks . . . . . . . . . . Supported IBM TSM API Client Versions . . . . . . . . . . . . . . . . . . . . Optional Environment Variables . . . Inc. . . . . . . . . . . Overriding IBM TSM Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Environment Variables for Post-Installation . . . . . . . . . . .opt file on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM TSM Options . . . . Settings for the dsm. . . 2-2 2-4 2-6 2-16 2-19 2-22 3-5 3-8 3-20 3-26 4-12 BMC Software. . . . . . . . . . . . . . . . . . IBM TSM Library Link Commands (Unix Only) . . . . . . . . . . . . . . BMC Software. Confidential and Proprietary Information xii SQL-BackTrack Module for IBM TSM Installation and User Guide . Inc.. Confidential and Proprietary Information About This Book xiii . and other users of SQL-BackTrack. database administrators (DBAs). “Configuring SQL-BackTrack for Use with IBM TSM” Chapter 5. this book contains a glossary of terms and an index.. How This Book Is Organized This book is organized as follows. “Backing Up Data” BMC Software. “Configuring IBM TSM for Use with SQL-BackTrack” Chapter 4. Inc. About This Book This book provides information about installing and configuring the SQL-BackTrack Module for IBM Tivoli Storage Manager (TSM). .About . In addition. . This document is intended for system administrators. Chapter/Appendix Chapter 1. “Installing the SQL-BackTrack Module for IBM TSM” Chapter 3. “Before You Begin” Description discusses information you need to know before you begin to install the SQL-BackTrack Module for IBM TSM presents the tasks necessary to install the SQL-BackTrack Module for IBM TSM presents the tasks necessary to configure IBM TSM for use with SQL-BackTrack presents the tasks necessary to configure SQL-BackTrack for use with IBM TSM presents the tasks necessary to submit SQL-BackTrack backups to IBM TSM Chapter 2. the following documents are available: Document SQL-BackTrack Module for IBM Tivoli Storage Manager Release Notes SQL-BackTrack user documentation IBM TSM documentation Purpose explains the latest updates to the SQL-BackTrack Module for IBM TSM describes how to use the SQL-BackTrack backup and recovery software for various database types describes how to install and use IBM TSM Online and Printed Books The books that accompany BMC Software products are available in online and printed formats.Chapter/Appendix Chapter 6. Inc. Some online books are also formatted as HTML files.. BMC Software. Online books are formatted as Portable Document Format (PDF) files. In addition to the SQL-BackTrack Module™ for IBM Tivoli Storage Manager Installation and User Guide. “Error Messages” Related Documentation The product documentation consists of two SQL-BackTrack Module for IBM TSM publications and a number of other SQL-BackTrack and IBM TSM documents. Confidential and Proprietary Information xiv SQL-BackTrack Module for IBM TSM Installation and User Guide . “Recovering Data” Description presents the task necessary to recover SQL-BackTrack backups that are managed by IBM TSM describes error messages that you might encounter and provides the recommended user response Appendix A. go to http://www.bmc. visit the Customer Support page of the BMC Software Web site at http://www. Inc.com. In some cases.bmc. if you do not follow instructions carefully.. Confidential and Proprietary Information About This Book xv .com/support_home. installing the Acrobat Reader and downloading the online books is an optional part of the product-installation process. such as loss of data. Conventions The following conventions are used in this book: • This book includes special elements called notes.adobe. To Request Additional Printed Books BMC Software provides some printed books with your product order.To Access Online Books To view any online book that BMC Software offers. go to the Adobe Systems site at http://www. BMC Software. Example An example clarifies a concept discussed in text. Use the free Acrobat Reader from Adobe Systems to view. print. and examples: Note Notes provide additional information about the current subject. To request additional books. For information about downloading the free reader from the Web. Warning Warnings alert you to situations that can cause problems. warnings. or copy PDF files. You can also access PDF books from the installation compact disc (CD) that accompanies your product.com/support_home. as shown in the following examples: The table <tablename> is not available.• All syntax. angle brackets (<>) represent a variable. path names. Web addresses. or system messages. boldface type highlights information that you enter. File names. Actions => Create Test instructs you to choose the Create Test command from the Actions menu. and literal examples are presented in this typeface. Confidential and Proprietary Information xvi SQL-BackTrack Module for IBM TSM Installation and User Guide . operating system terms. and names of GUI elements also appear in boldface type.. directories. In instructions. system/<instance>/<filename> BMC Software. e-mail addresses. The symbol => connects items in a menu sequence. In syntax. For example. Inc. The symbol • • • • » denotes one-step instructions. . . . . . . . . . . . . Inc. . . . . . . . . . . . . . 1-10 Where to Go from Here . . . . . 1-5 Accessing Documentation on the Product CD . . . . . . . . . . . 1-8 Installing the Acrobat Reader from the Product CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Viewing the SQL-BackTrack Module Documentation . . . . . . . . . . . . . . . . . 1-2 LAN Configuration . . . . . . . . . . . . . . . . .. . . . . . . . 1-2 SAN Configuration . . . . . . . . .1 Introducing the SQL-BackTrack Module for IBM TSM This chapter discusses the following topics: 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 How IBM TSM and the SQL-BackTrack Module Work Together . . . . . . . . . . . Confidential and Proprietary Information Introducing the SQL-BackTrack Module for IBM TSM 1-1 . . . . 1-10 BMC Software. . . . . . . . . . . . . . . . . . . . Microsoft SQL Server. BMC Software. Inc. This chapter provides information on how the products interface and communicate. and LAN-free environments. Confidential and Proprietary Information 1-2 SQL-BackTrack Module for IBM TSM Installation and User Guide . This enterprise-wide storage management application provides automated storage management services to workstations. local area network (LAN) file servers. This section contains a technical overview of using SQL-BackTrack with IBM TSM to back up and recover across a local area network (LAN) and across a storage area network (SAN).” LAN Configuration Figure 1-1 on page 1-3 shows the major components in a configuration for backing up and recovering over a LAN using SQL-BackTrack and the SQL-BackTrack Module for IBM TSM. The SQL-BackTrack Module for IBM TSM provides an interface between SQL-BackTrack and IBM TSM and enables you to submit SQL-BackTrack database backups directly to IBM TSM. Sybase. DB2 Universal Database. The term used in this book to refer to backing up and recovering across a SAN is “LAN-free.Overview The SQL-BackTrack product from BMC Software is the leading backup and recovery tool for Oracle.. and Informix. It improves backup performance and simplifies recovery. The SQL-BackTrack Module for IBM TSM extends the capabilities of SQL-BackTrack by integrating its sophisticated backup and recovery features with the storage management features of the IBM TSM product. exchanges control information (such as policy information and data about the objects) with the IBM TSM Server.Figure 1-1 Configuration for Backing Up and Recovering Over a LAN Database SQL-BackTrack Host and IBM TSM Client LAN Tape or Optical Device IBM TSM Server The database host serves as both the IBM TSM client host and the SQL-BackTrack host. 4. Confidential and Proprietary Information Introducing the SQL-BackTrack Module for IBM TSM 1-3 . 3. In the LAN environment. BMC Software. The following backup scenario outlines the flow of data across the LAN: 1. 2. the storage devices are accessible to the IBM TSM server. The SQL-BackTrack Module for IBM TSM. 5. through the IBM TSM API client. Inc. SQL-BackTrack initiates a database backup and sends the data to the SQL-BackTrack Module for IBM TSM. which stores it on a storage device or backup media.. through IBM TSM API client. The IBM TSM server database is updated. The SQL-BackTrack Module for IBM TSM. SQL-BackTrack stores history information pertaining to the backup. sends the data to the IBM TSM server. For a recovery. Confidential and Proprietary Information 1-4 SQL-BackTrack Module for IBM TSM Installation and User Guide . Figure 1-2 Configuration for Backing Up and Recovering Across a SAN Database SQL-BackTrack Host (IBM TSM Client/Storage Agent Host) LAN SAN IBM TSM Server Tape or Optical Device As in the LAN configuration. Inc. and the data is retrieved from the IBM TSM server. the steps are reversed. BMC Software. the database host serves as both the IBM TSM client and the SQL-BackTrack host. SAN Configuration The example network below shows the major components in a configuration for backing up and recovering over a SAN using SQL-BackTrack and the SQL-BackTrack Module for IBM TSM.. the storage devices are accessible to the IBM TSM storage agent. In this configuration. the SQL-BackTrack Module communicates with IBM TSM and enables SQL-BackTrack to use the storage management features of IBM TSM. which writes to the tape library using the SAN.The following backup scenario outlines the flow of data in a SAN environment: 1. Confidential and Proprietary Information Introducing the SQL-BackTrack Module for IBM TSM 1-5 . through the IBM TSM API client. Inc. The SQL-BackTrack Module takes advantage of the following IBM TSM configuration parameters and features: • • • • • • • controlled access (nodename verification) password access management classes storage pools filespace management media mount wait time LAN-free operations The following sections provide more detail on each point of integration. 4. The IBM TSM Server database is updated. SQL-BackTrack initiates a database backup and sends the data to the SQL-BackTrack Module for IBM TSM. BMC Software. 2.. 5. SQL-BackTrack stores history information pertaining to the backup. sends the data to IBM TSM Storage Agent. 3. The SQL-BackTrack Module for IBM TSM. How IBM TSM and the SQL-BackTrack Module Work Together Through the IBM TSM API client. The SQL-BackTrack Module for IBM TSM. exchanges control information across the LAN with the IBM TSM Server. through the IBM TSM API client. or to another client.. If the server is configured to verify the node name passwords at the time the IBM TSM client contacts the server. the client can be enabled to generate the password automatically or to prompt the user each time the server is accessed. If you configure the client to prompt the user for a password each time the server is accessed. BMC Software. Inc. for unattended backups. The password is assigned to the node name at the time that the node name is registered with the IBM TSM server. Confidential and Proprietary Information 1-6 SQL-BackTrack Module for IBM TSM Installation and User Guide . Password Access Password access enables the IBM TSM server to authenticate the communications between the IBM TSM client (SQL-BackTrack host) and IBM TSM server.Nodename Verification A single IBM TSM client can be registered with the IBM TSM server under one or more node names. and one for database backups) enables SQL-BackTrack backups and IBM TSM file system backups to be stored on the same IBM TSM server. SQL-BackTrack can also be configured to store the password and provide it at the time of the prompt. If you use a cluster environment. Using two different node names for each client (one for file system backups. use the same nodename across all the clients for the SQL-BackTrack backups. This authentication allows data to be recovered to the same IBM TSM client that initially transferred it. which determines how the IBM TSM server manages backup versions or archive copies of the object. an archive copy group. Each IBM TSM client has a default management class. and there are multiple management classes available for each client.. recovery. The copy groups determine the number of backup versions to be maintained and the amount of time that the backups will be maintained. You can specify the filespace tag prefix that you want to use in the backup pool or backup destination definition. Inc. BMC Software. Filespace Management A filespace is a logical space on the IBM TSM server that contains a group of files. IBM TSM uses the filespace to identify the file system or disk drive on which the data is located. this feature is not applicable to SQL-BackTrack. with parameters that can differ from the default management class. and though the IBM TSM backup copy group feature enables object versioning. or one of each. recovery. or expiration. Each management class contains a backup copy group. You can configure SQL-BackTrack to wait the amount of time specified in the IBM TSM device class attribute or to skip the backup. Each object that is backed up has a management class associated with it. Confidential and Proprietary Information Introducing the SQL-BackTrack Module for IBM TSM 1-7 .Management Classes and Storage Pools Management classes define how IBM TSM stores and manages objects. or expiration operation if a backup device is not available. Each object that SQL-BackTrack generates during backup operations has a unique name. Media Mount Wait Time The mount wait period is a device class attribute that specifies how long the IBM TSM server waits for a tape to be mounted before it cancels the backup. SQL-BackTrack requires a separate management class. the IBM TSM storage agent is installed on the IBM TSM client host and the IBM TSM client is enabled for LAN-free operations.LAN-Free Operations SQL-BackTrack takes advantage of the LAN-free enablement provided by IBM TSM and allows LAN-free backups and recoveries. You can use the free Acrobat Reader from Adobe Systems to view or print the documents.. The following topics tell you how to • • install the Acrobat Reader view the documents using the Acrobat Reader BMC Software. Confidential and Proprietary Information 1-8 SQL-BackTrack Module for IBM TSM Installation and User Guide . In a LAN-free backup and recovery environment. Accessing Documentation on the Product CD Online documentation for the SQL-BackTrack Module for IBM TSM is included on the product CD as Portable Document Format (PDF) files. Inc. For Windows. Confidential and Proprietary Information Introducing the SQL-BackTrack Module for IBM TSM 1-9 . Mount the product CD (Unix) or insert it in the CD-ROM drive (Windows).txt for more help on installing Acrobat Reader. follow these instructions to install version 4.0 or 4.com. and execute the ar405eng. Alternatively.exe file by double-clicking it. and run the install script: % cd /cdrom/Acrobat4/<platform_dir> % . Step 3 Follow the instructions as they appear on your screen. BMC Software. you can download the free Acrobat Reader from the Adobe Systems site at http://www. Inc../INSTALL Step 1 Step 2 Replace <platform_dir> with the subdirectory for your platform. change to the appropriate directory for your platform.Installing the Acrobat Reader from the Product CD Summary: If you do not have Acrobat Reader 3.adobe. For Unix. contact your system administrator. in Windows Explorer.0.0 from the product CD. If you need help. See the file instguid. navigate to the Acrobat4\NT directory on the installation CD. After you have installed Acrobat Reader.. BMC Software. Double-click one of the documents listed above to view it. Change to the Acrobat Reader application directory and run the program: % cd /<Acrobat_install_dir>/bin % acroread Step 2 Step 3 Select File => Open. Inc. For more information about Acrobat Reader. “Installing the SQL-BackTrack Module for IBM TSM”. and then select one of the documents listed above. Step 2 Where to Go from Here Proceed to verifying that your system meets the minimum installation requirements before you install the product. Confidential and Proprietary Information 1-10 SQL-BackTrack Module for IBM TSM Installation and User Guide . For Windows Step 1 Copy all of the PDF files from the Doc directory on the product CD to your hard drive. follow these instructions to view the PDF files: For Unix Step 1 Copy all of the PDF files from the Doc directory on the product CD to your hard drive. See Chapter 2.Viewing the SQL-BackTrack Module Documentation The SQL-BackTrack Module for IBM Tivoli Storage Manager Installation and User Guide is provided on the product CD. choose Help => Reader Online Guide. . . . . . .2 Installing the SQL-BackTrack Module for IBM TSM 2 This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Installing the SQL-BackTrack Module on Unix . . . . . . . . . . . . . . . . . . . . 2-9 Installing the SQL-BackTrack Module on Windows. . . . . . . . . . . 2-4 Software and Hardware Requirements . . . . . . . . . 2-5 Installation Account Requirements . . . . . . . . . . . . . . . . . . . . . 2-22 Where to Go from Here . . . . . . . . . . . . 2-12 Setting Unix Environment Variables During Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 BMC Software. . . . . . . . . . . . 2-7 Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Setting Windows Environment Variables During Post-Installation . . . . . . . . . . . . . 2-3 Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 Setting Optional Environment Variables . . . . Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-1 . . . . . .. . . . . Inc. . . . 2-2 Supported Environments . . . . . . . . . . . see “Setting Windows Environment Variables During Post-Installation” on page 2-19 When you complete the installation. you must perform the complete installation process on all the nodes. Table 2-1 Installation Tasks Step 1 Task Verify that the system and installation account requirements are met. For Windows. the host on which you have installed the SQL-BackTrack Module for IBM TSM will contain the following products and components: • • • • SQL-BackTrack IBM TSM API Client IBM TSM Storage Agent (for LAN-free) SQL-BackTrack Module for IBM TSM BMC Software. Set the environment variables. Install the SQL-BackTrack Module for IBM TSM on each host. see “Setting Unix Environment Variables During Post-Installation” on page 2-16. Note If you are installing the SQL-BackTrack Module for IBM TSM in a cluster environment.Overview This chapter describes installation requirements and provides installation procedures that apply to both new installations and upgrade installations. The process is the same for new installations and upgrades.. Confidential and Proprietary Information 2-2 SQL-BackTrack Module for IBM TSM Installation and User Guide . Inc. Table 2-1 guides you through the installation process. Reference “Installation Requirements” on page 2-4 2 “Installation Procedures” on page 2-8 3 For Unix. Inc. see the SQL-BackTrack installation documentation.. For information on installing the IBM TSM components. see the IBM TSM documentation. BMC Software.For information on installing SQL-BackTrack. Supported Environments The SQL-BackTrack Module for IBM TSM is supported for operating systems and the IBM TSM API client versions listed in Table 2-2. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-3 . Table 2-2 Supported IBM TSM API Client Versions Operating System Hewlett-Packard Tru64 UNIX 5.1, 5.1a (64-bit) HP-UX 11.0 (32-bit and 64-bit), 11.11 (32-bit and 64-bit) IBM AIX 4.3.3 (32-bit and 64-bit), 5.1 (32-bit and 64-bit), 5.2 (32-bit and 64-bit) Linux RedHat Advanced Server 2.1 (Intel) Kernel 2.4.18, SuSe 7.3 Kernel Level 2.4.7 Solaris 2.6 (32-bit), Solaris7 (32-bit and 64-bit), Solaris8 (32-bit and 64-bit), Solaris9 (32-bit and 64-bit) Microsoft Windows NT Server, Enterprise Server 4.0 Microsoft Windows 2000 Server, Advanced Server, Professional, DataCenter IBM TSM API Client 4.2x and 5.1x (32-bit and 64-bit) 4.2x and 5.1x (32-bit and 64-bit) 4.2x and 5.1x (32-bit and 64-bit) 4.2x and 5.1x (32-bit and 64-bit) 4.2x and 5.1x (32-bit and 64-bit) 4.2x and 5.1x (32-bit) 4.2x and 5.1x (32-bit) Note If you are using a 64-bit operating system, BMC Software recommends that you install the 64-bit SQL-BackTrack Module for IBM TSM. The 64-bit SQL-BackTrack Module version requires a 64-bit IBM TSM API Client, and the 32-bit SQL-BackTrack Module version requires a 32-bit IBM TSM API Client. The SQL-BackTrack Module for IBM TSM does not support LAN-free backup and recovery on Linux or Tru64 UNIX. Installation Requirements Before you install the SQL-BackTrack Module for IBM TSM, ensure that the requirements addressed in this section have been met. BMC Software, Inc., Confidential and Proprietary Information 2-4 SQL-BackTrack Module for IBM TSM Installation and User Guide Software and Hardware Requirements The host on which SQL-BackTrack is installed must have a minimum of 50 MB of free disk space. The following software must be installed: • SQL-BackTrack must be installed, and you must verify that backups and recoveries using the SQL-BackTrack Module for Tape or the SQL-BackTrack Module for Disk are successful. These Modules are installed with your SQL-BackTrack product. For instructions on using these Modules, see the SQL-BackTrack documentation. The IBM TSM Server that is compatible with the IBM TSM API client must be installed and operational and configured for use with the IBM TSM client. If you are planning to perform LAN-free backups and recoveries, the IBM TSM storage agent must be installed (for the versions of the storage agent that are compatible with the IBM TSM API client versions supported by the SQL-BackTrack Module, see the IBM TSM documentation). The IBM TSM API client must be installed, and backups to the IBM TSM server must be successful. (For supported versions, see “Supported Environments” on page 2-3.) If you are installing on Unix, you must verify that the links to the IBM TSM library exist. The library file libApiDS.x or libApiDS64.x should be linked to libApiDS.x or libApiDS64.x file (respectively) in the /usr/lib directory (The x variable represents a platform-dependent extension.) If you need to create or modify the links, use the commands for your operating system, as shown in Table 2-3, on page 2-6. Note • • • These are the typical directories where IBM TSM API client libraries are found. They could vary if you installed the IBM TSM API client in a different directory. BMC Software, Inc., Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-5 . Table 2-3 IBM TSM Library Link Commands (Unix Only) Operating System AIX Version all versions (32-bit) 4.3 (64-bit) Commands % cd /usr/lib % ln -s /usr/tivoli/tsm/client/api/bin/libApiDS.a libApiDS.a % cd /usr/lib % ln -s /usr/tivoli/tsm/client/api/bin64/libApiDS64.a libApiDS64.a % cd /usr/lib 5.1 (64-bit) % ln -s /usr/tivoli/tsm/client/api/bin64/libApiTSM64.a libApiTSM64.a 5.2 (64-bit) % cd /usr/lib % ln -s /usr/tivoli/tsm/client/api/bin64/libApiTSM64.a libApiTSM64.a Tru64 UNIX HP-UX all versions % cd /usr/lib % ln -s /usr/tivoli/tsm/client/api/bin/libApiDS.so libApiDS.so all versions (32-bit) % cd /usr/lib % ln -s /opt/tivoli/tsm/client/api/bin/libApiDS.sl libApiDS.sl all versions (64-bit) % cd /usr/lib % ln -s /opt/tivoli/tsm/client/api/bin64/libApiDS64.sl libApiDS64.sl BMC Software, Inc., Confidential and Proprietary Information 2-6 SQL-BackTrack Module for IBM TSM Installation and User Guide 1 all versions (64-bit) Linux all versions Installation Account Requirements Ensure that your installation account has the appropriate permissions to perform the installation tasks. • BMC Software. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-7 .) On Windows.so libApiDS.so.so libApiDS.1 % cd /usr/lib % ln -s /opt/tivoli/tsm/client/api/bin/libApiDS. the DTBASE directory is /opt/bmc/SQL-BackTrack or /usr/datatools. you will must be logged in as the database user..so % ln -s libApiDS.so /usr/lib/libApiDS. Inc.so /usr/lib/libApiDS64. You must have read/write/execute permission in the DTBASE directory to run the installation script.so libApiDS64.so.Table 2-3 IBM TSM Library Link Commands (Unix Only) Operating System Solaris Version all versions (32-bit) Commands % cd /usr/lib % ln -s /opt/tivoli/tsm/client/api/bin/libApiDS. • On Unix. (By default.so.so /usr/lib/libApiDS. you must be logged in as a member of the local Administrators group.1 % cd /usr/lib % ln -s /opt/tivoli/tsm/client/api/bin64/libApiDS64.so % ln -s libApiDS.so % ln -s libApiDS64. refer to the installation procedure for your platform: Platform Unix Windows Procedure “Installing the SQL-BackTrack Module on Unix” on page 2-9 “Installing the SQL-BackTrack Module on Windows” on page 2-12 BMC Software. Inc..Installation Procedures To install the SQL-BackTrack Module for IBM Tivoli Storage Manager. Confidential and Proprietary Information 2-8 SQL-BackTrack Module for IBM TSM Installation and User Guide . Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-9 . you can copy between the same operating systems only. the installation on the HP-UX system will fail. you must create a link in your DTBASE directory for SQL-BackTrack that points to the SQL-BackTrack Module for IBM TSM. if you attempt to copy the binaries from a computer that is running Solaris to a computer that is running HP-UX. Change the working directory to the mount point noted in Step 1 using the following command: % cd /cdrom Step 2 BMC Software. you run the installation script. using the same value for the DTBASE environment variable). Before You Begin BMC Software recommends that you install the SQL-BackTrack Module for IBM TSM in the same location as SQL-BackTrack (that is. which installs the product in the DTBASE directory.. before validating the installation. BMC Software also recommends that you install this software on each system using the CD. Otherwise. Inc. For example.Installing the SQL-BackTrack Module on Unix Summary: In this procedure. If you choose to install this software on one computer and then copy the binaries from the first computer to other computers. To Install the SQL-BackTrack Module for IBM TSM Software Step 1 Mount the SQL-BackTrack Module for IBM TSM CD-ROM and note the mount point. /install Note On most systems. and then run the install script. Inc.1. The installation process performs the following operations: • adds the obsi.00 directory for 32-bit installations and obsi. For example: % ls INSTALL install install % . used if the PASSWORDAccess option is set to generate. Step 5 Read and accept the license agreement information to complete the installation process. Confidential and Proprietary Information 2-10 SQL-BackTrack Module for IBM TSM Installation and User Guide . On systems that do not fully support the Rock Ridge extensions to ISO 9660 and on HP-UX platforms. This directory contains the following: — the adsmpw utility for seeding or changing the password for the IBM TSM nodename.adsm-3. the installation script might be named INSTALL.1. Note Install the 64-bit version of the Module if you have a 64-bit operating system..00-64bit directory for 64-bit installations where the SQL-BackTrack Module for IBM TSM software resides in the DTBASE directory.Step 3 Verify the script name with the ls command. the name of the installation script on the CD-ROM is install.adsm-3. — the adsmrc utility for verifying the IBM TSM API client message files and accessing error codes BMC Software. Step 4 Respond to the prompt for installing the 32-bit or 64-bit version of the SQL-BackTrack Module for IBM TSM. adsm-3. Inc. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-11 . BMC Software. adds the mls directory for internationalization in $DTBASE/obsi.00-64bit directory.adsm link pointing to the obsi.00 directory or obsi.adsm-3.1.1.adsm-3. • Where to Go from Here Proceed to “Setting Unix Environment Variables During Post-Installation” on page 2-16..00-64bit directory in the DTBASE directory.00 directory or $DTBASE/obsi.adsm-3.1.1.— the adsm_del utility for expiring residual SQL-BackTrack objects — the obsitest utility for validating the SQL-BackTrack Module for IBM TSM configuration • adds an obsi. you need to install the SQL-BackTrack Module for IBM TSM in the same location as SQL-BackTrack (that is. The installation program is finished when the Setup Complete screen appears. At the beginning of the installation. To Install the Software Step 1 Insert the CD-ROM containing the SQL-BackTrack Module for IBM TSM software into the CD-ROM drive. Read each screen carefully before clicking Next. and then execute the setup. and it is where the SQL-BackTrack Module for IBM TSM will be installed. you are prompted for DTBASE. use the same DTBASE directory).Installing the SQL-BackTrack Module on Windows Summary: In this procedure. The account that you use to install the product must be a member of the local Administrators group. you use the InstallShield program to install the software. This is the SQL-BackTrack installation directory. Inc.exe file by double-clicking it. Step 2 Step 3 BMC Software. Before You Begin For all SQL-BackTrack products.. Confidential and Proprietary Information 2-12 SQL-BackTrack Module for IBM TSM Installation and User Guide . The default value for this directory is C:\Program Files\BMC Software\SQL-BackTrack or C:\Program Files\BMC Software\datatools (for SQL-BackTrack for Microsoft SQL Server). If the setup program does not launch automatically. use Windows Explorer to navigate to the \NT\TSM directory on the installation CD. adsm-3. This directory contains the following: — the adsmpw utility for seeding or changing the password for the IBM TSM nodename.The installation process performs the following operations: • adds the obsi.opt DSMI_CONFIG • adds the mls directory for internationalization in %DTBASE%\obsi. Inc.1. BMC Software.txt and any NLS message files) %DSMI_DIR%\dsm. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-13 . by default.. C:\Program Files\Tivoli\TSM\api (the path containing dscameng. Where to Go from Here Proceed to “Setting Windows Environment Variables During Post-Installation” on page 2-19.00 directory.1. — the adsmrc utility for verifying the IBM TSM API client message files and accessing error codes — the adsm_del utility for expiring residual SQL-BackTrack objects — the obsitest utility for validating the SQL-BackTrack Module for IBM TSM configuration • updates the registry with the following values for the DSMI_DIR and DSMI_CONFIG variables: Variable DSMI_DIR Default value Location of the IBM TSM API Client. used if the PASSWORDAccess option is set to generate.adsm-3.00 directory where the SQL-BackTrack Module for IBM TSM software resides in the DTBASE directory. Confidential and Proprietary Information 2-14 SQL-BackTrack Module for IBM TSM Installation and User Guide . BMC Software.Upgrading the SQL-BackTrack Module for IBM TSM Summary: Use this procedure to upgrade your existing SQL-BackTrack Module for IBM TSM installation. if you have stored the variable in the backup or recovery script. Use the following table to locate the procedure: Platform Unix Windows Procedure “Installing the SQL-BackTrack Module on Unix” on page 2-9 “Installing the SQL-BackTrack Module on Windows” on page 2-12 Note If you are updating any of the environment variables.. See “Validating the Configuration” on page 3-33. Where to Go From Here Proceed to verifying the IBM TSM configuration using the obsitest utility. To Upgrade the Module » Install the product just as you would for a new installation. following installation. Setting Environment Variables This section contains procedures for setting environment variables that are required for Unix and Window. ensure that the value is also updated in the backup or recovery script. Inc. See “Adding Environment Variables to Backup Scripts” on page 5-5. in case you want to override some of the options that are set for IBM TSM.This section also contains procedures for setting additional environment variables that are optional.. BMC Software. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-15 . Inc. you need to add environment variables specific to IBM TSM before this backup script can be used. Note If you use SQL-BackTrack to generate a backup or recovery script for on-demand or unattended backups or recoveries. Inc. dsmtca. and any other national language support (NLS)a AIX (32-bit) AIX (64-bit) Tru64 UNIX HP-UX (32-bit) HP-UX (64-bit) Solaris (32-bit) Solaris (64-bit) Linux BMC Software. set the environment variables using the following syntax: Unix Shell C shell Bourne or Korn shells Command Syntax setenv <environment variable> <value> <environment variable>=<value> export <environment variable> Table 2-4 Unix Environment Variables for Post-Installation (Part 1 of 2) Variable DTBASE Description specifies the SQL-BackTrack Module for IBM TSM installation directory.Setting Unix Environment Variables During Post-Installation Summary: After you install the product.. Operating System All versions (32-bit and 64-bit) Recommended Value /usr/datatools (SQL-BackTrack for Sybase) or /opt/bmc/SQL-BackTrack (SQL-BackTrack products for Oracle and DB2/UDB) /usr/tivoli/tsm/client/api/bin /usr/tivoli/tsm/client/api/bin64 /usr/tivoli/tsm/client/api/bin /opt/tivoli/tsm/client/api/bin /opt/tivoli/tsm/client/api/bin64 /opt/tivoli/tsm/client/api/bin /opt/tivoli/tsm/client/api/bin64 /opt/tivoli/tsm/client/api/bin DSMI_DIR specifies the TSM API client installation. the path containing dsm. the en_US subdirectory. Confidential and Proprietary Information 2-16 SQL-BackTrack Module for IBM TSM Installation and User Guide .sys. you can set several environment variables for the SQL-BackTrack Module for IBM TSM. To Set Environment Variables on Unix » Using the information in Table 2-4. 00-64bit/bin % adsmrc 0 You should get the following response: % adsmrc 0 0: ANS0302I (RC0) Successfully done.1. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-17 .log file is created to record some of the IBM TSM errors Operating System All versions (32-bit and 64-bit) All versions (32-bit) All versions (64-bit) Recommended Value $DSMI_DIR/dsm.. This value depends on the location where you want the Module to look for the dsm.adsm-3.optb $DTBASE/obsi.opt) on Unix” on page 3-22 for more information.adsm-3.opt (user options) file specifies the directory where the dsierror. Inc.cat. See “Editing the IBM TSM Client User Options File (dsm.1.adsm-3.1.00/dsm $DTBASE/obsi.00/bin % adsmrc 0 For the 64-bit version of the Module: % cd $DTBASE/obsi.Table 2-4 Unix Environment Variables for Post-Installation (Part 2 of 2) Variable DSMI_CONFIG Description specifies the fully qualified file name for the dsm.adsm-3.opt file. To Verify that the Environment Variables are Set Correctly » Validate that the DSMI_DIR and DSMI_CONFIG environment variables are set correctly by using the following commands: For the 32-bit version of the Module: % cd $DTBASE/obsi.00-64bit/dsm DSMI_LOG a b The en_US subdirectory must contain dsmclientv3. BMC Software.1.opt or $DTBASE/dsm/dsm. • BMC Software. “Configuring IBM TSM for Use with SQL-BackTrack”. you have not set the DSMI_DIR and DSMI_CONFIG environment variables correctly: % adsmrc 0 FATAL: DSMI_DIR environment variable not set If you receive any other error message. To begin configuring IBM TSM. contact your IBM TSM administrator to find out the correct value for DSMI_DIR and DSMI_CONFIG.If you receive the following message. Inc. Confidential and Proprietary Information 2-18 SQL-BackTrack Module for IBM TSM Installation and User Guide .. proceed to “Setting Optional Environment Variables” on page 2-22. Where to Go From Here Proceed to the following procedures: • If you would like to set the additional. proceed to Chapter 3. optional environment variables. the value of the environment variable is valid only for as long as the command prompt session is active. Table 2-5 Windows Environment Variables for Post-Installation Variable DTBASE Description specifies the location for the SQL-BackTrack Module for IBM TSM specifies the directory where the dsierror. choose Start => Settings =>Control Panel => System.1.00\dsm DSMI_LOG BMC Software.. Recommended Value C:\Program Files\BMC Software\SQL-BackTrack or C:\Program Files\BMC Software\ datatools (SQL-BackTrack for Microsoft SQL Server) %DTBASE%\obsi. enter the environment variables and their values using the information provided in Table 4-3 on page 4-19. Inc. To Set Windows Environment Variables from the MS–DOS Command Prompt » At the command prompt. SET <variable_name>=<value> Note If you set an environment variable using this method. see Table 2-5. set the environment variable using the following syntax.Setting Windows Environment Variables During Post-Installation Summary: Use the following procedure to set the Windows environment variables DTBASE and DSMI_LOG. For a list of environment variables.adsm-3.log file will be created to record some of the errors generated by IBM TSM. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-19 . Step 2 From the System Properties dialog. To Set the Windows Environment Variables from the Windows Control Panel Step 1 From the Windows desktop. and any NLS message files specifies the fully qualified file name for the dsm. DSMI_DIR is added to the Windows registry but can be overridden at any time.opt a b During installation.adsm-3. you have not set the DSMI_DIR and DSMI_CONFIG environment variables correctly: % adsmrc 0 FATAL: DSMI_DIR environment variable not set If you receive any other error message.Table 2-5 Windows Environment Variables for Post-Installation Variable DSMI_DIRa (optional) Description specifies the IBM TSM API client installation.00\bin adsmrc 0 You should get the following response: adsmrc 0 0: ANS0302I (RC0) Successfully done.1. If you receive the following message. Confidential and Proprietary Information 2-20 SQL-BackTrack Module for IBM TSM Installation and User Guide .opt (user options) file Recommended Value C:\Program Files\tivoli\tsm\api DSMI_CONFIGb (optional) %DSMI_DIR%\dsm.. BMC Software. DSMI_CONFIG is added to the Windows registry but can be overridden at any time. » Validate that the DSMI_DIR and DSMI_CONFIG environment variables are set correctly by using the following command: cd %DTBASE\obsi. During installation.txt. Inc. contact your IBM TSM administrator to find out the correct value for DSMI_DIR and DSMI_CONFIG. the path containing dscameng. To begin configuring IBM TSM. optional environment variables. • BMC Software.Where to Go From Here Proceed to the following procedures: • If you would like to set the additional. proceed to Chapter 3. proceed to “Setting Optional Environment Variables” on page 2-22. Inc. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-21 . “Configuring IBM TSM for Use with SQL-BackTrack”.. Setting Optional Environment Variables Summary: Use this procedure to set the optional environment variables on Unix or Windows. to override the values that are set for some of the IBM TSM parameters and some of the values that are in the SQL-BackTrack backup pool or backup destination. use the instructions provided in “Setting Windows Environment Variables During Post-Installation” on page 2-19. Possible values are SERVER and CLIENT. Confidential and Proprietary Information 2-22 SQL-BackTrack Module for IBM TSM Installation and User Guide . see “Overriding IBM TSM Options” on page 4-11. use the syntax provided in “Setting Unix Environment Variables During Post-Installation” on page 2-16. Table 2-6 Optional Environment Variables (Part 1 of 3) Variable DT_ADSM_DEBUG Description This environment variable enables debugging information from the SQL-BackTrack Module for IBM TSM.log). To Set the Optional Environment Variables » Use the information in Table 2-6 to set the optional environment variables.. Inc. To help you decide whether you need to set these variables. or both. Value 1 DT_ADSM_FILESPACE /<filespace_tag_prefix> DT_ADSM_LOG <SERVER or CLIENT> BMC Software. For Windows. Not all the variables that are listed have to be set. and the variables can be set at any time. the IBM TSM client log file (dsierror. This environment variable defines whether backup and recovery events are logged in the IBM TSM server activity logs. For Unix. Any other value specifies that log data is recorded in both files. This environment variable defines the filespace tag prefix assigned to SQL-BackTrack backups. unless otherwise specified. Do not set this variable if the client passwordaccess is set to generate. the owner used during recovery and expiration must be the same as the owner used during backup. Inc. Confidential and Proprietary Information Installing the SQL-BackTrack Module for IBM TSM 2-23 . This value must match the name of a registered node on the IBM TSM Server.Table 2-6 Optional Environment Variables (Part 2 of 3) Variable DT_ADSM_MGMTCLASS Description This environment variable defines the IBM TSM management class to override the default management class. Set this variable to y to wait for media mounts during backup and recovery. or it can be root. Note: On Unix.. This environment variable defines the owner of the SQL-BackTrack backup. The value assigned to this variable is case-sensitive. the owner used during recovery and expiration must be the same as the owner used during backup. This variable should be used at the time of recovery and expiration. only if you want to use a user ID different from the user ID used during the backup. This environment variable defines whether to wait for IBM TSM media mounts. This environment variable defines the IBM TSM client node name that will be used with SQL-BackTrack. Do not set this variable if the client PASSWORDAccess option is set to generate. Value <management_class_name> DT_ADSM_MOUNTWAIT <y or n> DT_ADSM_NODE <IBM_TSM_client_node_name> DT_ADSM_OWNER <owner> Should be user ID used at time of backup or NULL. On Windows. BMC Software. This environment variable defines the IBM TSM copy group of the management class to which SQL-BackTrack backups belong. Define this variable to BACKUP to use the backup copy group. Confidential and Proprietary Information 2-24 SQL-BackTrack Module for IBM TSM Installation and User Guide . “Configuring IBM TSM for Use with SQL-BackTrack”. Inc. or to ARCHIVE to use the archive copy group. Do not set this variable if the client passwordaccess option is set to generate.Table 2-6 Optional Environment Variables (Part 3 of 3) Variable DT_ADSM_PASSWORD Description This environment variable defines the IBM TSM node password (not encrypted). This environment variable defines the IBM TSM server name that will be used with SQL-BackTrack. BMC Software. Value <IBM_TSM_node_name_passwor d> DT_ADSM_SERVER <IBM_TSM_server_name> DT_ADSM_STORAGEPO OL <BACKUP or ARCHIVE> Where to Go from Here Proceed to Chapter 3.. . . . . 3-16 Editing the Client System Options File (dsm. . . 3-18 Editing the IBM TSM Client User Options File (dsm. . . . . . . . . . . . . . . . . . . . . . . . . . .opt) on Windows 3-25 Editing the Storage Agent Options Files . . . . 3-14 Configuring the IBM TSM API Client . . . . . . . 3-15 Configuring the IBM TSM Storage Agent Options Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Include-Exclude List . . . . . . . . . . . . . . . Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 3-9 Compression Setting . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 IBM TSM Node Name. . . . . . . . . . . . . . . . . . . . 3-6 Password Authentication . . . . . . . . 3-13 Configuration Procedures . . . . . . . . . . . . . . . .sys) on Unix . . . . . . . . . . . . . . . . . . . . . . . . 3-8 LAN-free Option . . . . . . . . . . . . . . . . . . . . . . . 3-2 IBM TSM Options . . . . . . . . . . . . . 3-10 MOUNTWAIT Setting. . . . . . . . .opt) on Unix 3-22 Editing the IBM TSM Client Options File (dsm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 BMC Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-1 . . . . . . 3-11 Management Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28 Running the adsmpw Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 COMMTIMEOUT Setting. . 3-7 Filespace Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Configuring IBM TSM for Use with SQL-BackTrack This chapter contains the following topics: 3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Communication Method . 3-4 IBM TSM Server Name. . . . . . . . . . . 3-11 Storage Pools . . . . . . . . . . . . . . . . . . . Depending on your access rights. . .Validating the Configuration . . .. you should be able to perform many of the tasks in this section. . . . . . . . . . . . . . . . . . . . . .3-33 Where to Go From Here . . . . . Inc. . This chapter also includes configuration and verification procedures. . . BMC Software. .3-38 Overview This chapter provides information about the IBM TSM server and client options that you might need to configure for use with SQL-BackTrack. . . . . . . . . If you do not have all of the required access rights. you might need to coordinate the configuration effort with the IBM TSM administrator. . . . . . . . Confidential and Proprietary Information 3-2 SQL-BackTrack Module for IBM TSM Installation and User Guide . . Figure 3-1 on page 3-3 shows the steps for configuring IBM TSM for use with SQL-BackTrack. “Editing the Storage Agent Options Files” on page 3-28 A BMC Software. Inc.opt) on Unix” on page 3-22 “Editing the IBM TSM Client Options File (dsm.opt file.opt file “Editing the Client System Options File (dsm.sys) on Unix” on page 3-18 “Editing the IBM TSM Client User Options File (dsm.Figure 3-1 Task Map for Configuring IBM TSM (part 1 of 2) Configuration begins Review IBM TSM options 1 Review the IBM TSM options with the IBM TSM administrator “IBM TSM Options” on page 3-4 Configure the IBM TSM server 2 Modify the IBM TSM server options. “IBM TSM Options” on page 3-4 Configure the IBM TSM client 3 Are you configuring a Unix Unix or Windows client? Windows Configure the dsm.. as appropriate.sys file Configure the dsm.opt) on Windows” on page 3-25 Are you performing yes LAN-free operations? no Configure the storage agent options files. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-3 . Configure the dsm. expire. The sections that follow this table describe each option in more detail. For more information on the options and on commands for setting the options in Table 3-1. The IBM TSM administrator and the database administrator must review these options and their current settings to ensure that SQL-BackTrack can communicate with IBM TSM and that SQL-BackTrack can successfully back up. Confidential and Proprietary Information 3-4 SQL-BackTrack Module for IBM TSM Installation and User Guide . Table 3-1 contains a list of the IBM TSM options that you might need to configure. see the IBM TSM documentation.Figure 3-2 Task Map for Configuring IBM TSM (part 2 of 2) A Is yes PASSWORDAccess set to generate? no Run the adsmpw utility “Running the adsmpw Utility” on page 3-30 Validate the IBM TSM configuration 4 Validate the configuration “Validating the Configuration” on page 3-33 Configuration is complete IBM TSM Options This section addresses the IBM TSM options that you might need to configure for use with SQL-BackTrack. and recover using IBM TSM. Inc.. BMC Software. presenting the options for configuring and overriding the values for these settings. A separate management class for SQL-BackTrack backups is recommended. Reference “IBM TSM Server Name” on page 3-6 “IBM TSM Node Name” on page 3-6 “Password Authentication” on page 3-7 “Filespace Tag” on page 3-8 “LAN-free Option” on page 3-9 “Communication Method” on page 3-9 “Communication Method” on page 3-9 “Communication Method” on page 3-9 “Compression Setting” on page 3-10 “MOUNTWAIT Setting” on page 3-10 “COMMTIMEOUT Setting” on page 3-11 “Management Class” on page 3-11 BMC Software.. Inc.Table 3-1 IBM TSM Options (Part 1 of 2) Option IBM TSM server name IBM TSM node name password authentication filespace tag prefix LAN-free option communication method TCP/IP port address TCP/IP internet address COMPRESSION setting MOUNTWAIT setting COMMTIMEOUT setting management class Description the name of the server(s) that SQL-BackTrack can contact for services the IBM TSM session node name that will be used with SQL-BackTrack backups to the IBM TSM server whether the IBM TSM server is enabled for password authentication the filespace tag prefix designated for SQL-BackTrack backups whether IBM TSM is configured for LAN-free operations specifies the communication method between the IBM TSM server and IBM TSM API client the TCP/IP port address that the IBM TSM API client uses to communicate with the IBM TSM server the TCP/IP internet address that the IBM TSM API client uses to communicate with the IBM TSM server whether the IBM TSM server is set to compress backups the time that the IBM TSM server waits for a storage volume to be mounted before IBM TSM API client operations are terminated the time that the IBM TSM server waits for communication from the IBM TSM API client before it terminates operations the management class that is to be used by the IBM TSM API client. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-5 . Table 3-1 IBM TSM Options (Part 2 of 2) Option Storage Pools (Copy groups) Description the backup or archive copy group that is available for the specified management class and that the database administrator wants to use in the backup pool an additional option that IBM TSM can use to associate the SQL-BackTrack filespace tag prefix with the appropriate management class Reference “Storage Pools” on page 3-12 Include-Exclude List “Include-Exclude List” on page 3-13 IBM TSM Server Name SQL-BackTrack needs to know which IBM TSM server it can contact for backup and recovery operations. If you have a cluster environment. By default. The IBM TSM server name is specified in the dsm. Inc. it is the name returned by the Unix host name command.. See “Overriding IBM TSM Options” on page 4-11.out.opt file (Unix and Windows) and dsm. it is the computer name. Confidential and Proprietary Information 3-6 SQL-BackTrack Module for IBM TSM Installation and User Guide . use the backup pool or backup destination to store the server name. BMC Software recommends that the node name that you use for SQL-BackTrack backups be different from the node name that you use for file system backups. or use the an environment variable. To enable SQL-BackTrack to override the server that is specified by IBM TSM. The node name can be any name that you want to use.sys file (Unix only) and in the storage agent configuration files dsmsta. SQL-BackTrack can contact one or more servers.opt and devconfig. or for Windows. you should use the same node name across multiple IBM TSM clients for SQL-BackTrack backups. BMC Software. IBM TSM Node Name The IBM TSM node name is the session node name that will be used with SQL-BackTrack backups. Note BMC Software recommends that you configure the IBM TSM client to generate the password automatically.sys file (Unix) and the dsm. you can configure SQL-BackTrack to store the passwords so that you can perform unattended backups. or SQL-BackTrack operations will fail. Inc. you can configure the IBM TSM client to generate and use the stored password automatically or to prompt the user each time the server is accessed. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-7 . especially for unattended backups.opt file (Windows). If the password is configured to prompt the user and you have stored the password in the backup pool or backup destination.The IBM TSM node name is configured in the dsm. Password Authentication You can enable the IBM TSM server to authenticate the node name passwords each time that the client accesses the IBM TSM server. you will need to update the stored password when the password is updated. If the server is enabled to authenticate the node name passwords.. use the backup pool or backup destination to specify a different node name. To enable SQL-BackTrack to override the node name that is specified by IBM TSM. BMC Software. See “Overriding IBM TSM Options” on page 4-11. or use the an environment variable. If you configure the client to prompt the user each time the server is accessed. Note Prompt is the default mode that IBM TSM uses if the client is enabled for password authentication and no PASSWORDAccess option is specified in the dsm. See “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 for more information. use the PASSWORDAccess option in the dsm. Confidential and Proprietary Information 3-8 SQL-BackTrack Module for IBM TSM Installation and User Guide . SQL-BackTrack cannot override the PASSWORDAccess option that is set in the dsm. Use either of the following values: Table 3-2 PASSWORDAccess Options Option setting prompt Result Options for Storing Passwords Options for Updating Passwords Update within the SQL-BackTrack product.sys file or the dsm.To configure the client to generate the password or prompt the user. generate Each time the client attempts to access the IBM TSM server. SQL-BackTrack is required to provide the node password Store the encrypted backup password in the SQL-BackTrack backup pool or backup destination.sys (Unix) file or the dsm. See the SQL-BackTrack user documentation for more information.opt (Windows) file. Each time the client attempts to access the IBM TSM server.opt (Windows) file. See “Running the adsmpw Utility” on page 3-30 for more information. the client uses a stored password.. Use the adsmpw utility. Filespace Tag The IBM TSM server uses the filespace tag to determine where backup files will be stored. Run the adsmpw password utility to store the encrypted password on the client.opt file. BMC Software. See “Running the adsmpw Utility” on page 3-30 for more information.sys (Unix) file or the dsm. Inc. the LAN-free option can be enabled on the IBM TSM client.opt and devconfig.. This option is enabled in the dsm. each backup pool can use a unique filespace tag prefix. Inc. Alternatively. • • • LAN-free Option If IBM TSM is configured for storage area network (SAN) operations. dsmsta. Filespace tag prefixes are case-sensitive and must be entered exactly as they are known to the IBM TSM server. Note the following considerations about filespace names: • If the filespace name does not exist on the IBM TSM server. it will be created by the SQL-BackTrack Module. See “Overriding IBM TSM Options” on page 4-11. A filespace can be deleted with a single IBM TSM delete command. You can specify the filespace tag prefix when creating a SQL-BackTrack backup pool or by using the DT_ADSM_FILESPACE environment variable. which might be useful for testing or for cleaning up unwanted data.If the filespace name does not exist on the IBM TSM server. it is created by the SQL-BackTrack Module. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-9 .out. SQL-BackTrack backup pools can share a filespace.sys (Unix) file or the dsm. the server name of the IBM TSM client is stored in the storage agent options files. BMC Software.opt file (Windows). Communication Method The communication method option specifies the protocol between the IBM TSM server and client. In addition. you must specify the following information: • the port number through which to communicate with the IBM TSM server the IP address of the IBM TSM server. or it can be configured to allow the IBM TSM client to specify whether the data should be compressed. If the mount request is not satisfied within the specified amount of time.sys (Unix) file or dsm. the mount request is canceled and the SQL-BackTrack session is terminated. To enable IBM TSM compression.opt file (Windows). SQL-BackTrack also provides a compression option. To enable SQL-BackTrack compression. jupiter. Confidential and Proprietary Information 3-10 SQL-BackTrack Module for IBM TSM Installation and User Guide . When you enable SQL-BackTrack compression. or catalog. Inc.com • Compression Setting The IBM TSM server can be configured to compress the data from the IBM TSM clients. BMC Software.bmc.sys file for Unix or in the dsm. If TCP/IP is used. control directory.The communication method is specified in the dsm.opt file for Windows and disable SQL-BackTrack compression.. MOUNTWAIT Setting You can define the IBM TSM server to wait for storage devices to be mounted. specify that option when you create a backup profile. See “Editing the Client System Options File (dsm.opt) on Windows” on page 3-25 for more information on setting the IBM TSM compression option for use by SQL-BackTrack.sys) on Unix” on page 3-18 or “Editing the IBM TSM Client Options File (dsm. for example. set compression to yes in the dsm. IBM TSM compression is automatically disabled. BMC Software recommends that you use the SQL-BackTrack compression option rather than the IBM TSM compression option as it provides a better compression ratio for database backups. For most SQL-BackTrack operations. COMMTIMEOUT Setting You can configure the IBM TSM server to wait during client operations for a particular length of time before the client operation times out. BMC Software. If such an operation exceeds the COMMTIMEOUT value. You can also set the environment variable DT_ADSM_MOUNTWAIT. there can be significant periods of time when there is no activity apparent to IBM TSM. the recommended COMMTIMEOUT value is at least 600 seconds (10 minutes). Inc. See “Overriding IBM TSM Options” on page 4-11. You can configure this option only on the IBM TSM server. including file system backup. Note You need to define a separate management class to set the following parameters since changing the parameters for STANDARD management class might impact other IBM TSM operations. the SQL-BackTrack backup pool can be configured to specify whether SQL-BackTrack should wait for IBM TSM media mounts. You can override this backup pool setting using the DT_ADSM_MGMTCLASS environment variable. You can configure the IBM TSM client to override the default management class by specifying the separate management class in the SQL-BackTrack backup pool. IBM TSM terminates the SQL-BackTrack backup or recovery operation. During certain SQL-BackTrack operations. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-11 ..On the IBM TSM client. Management Class The IBM TSM server defines the management class for each IBM TSM client. if you are using archive copy groups). This permits IBM TSM to delete from the IBM TSM server the archives that SQL-BackTrack expires. Use the DEFINE COPYGROUP or UPDATE COPYGROUP command (for type=archive) to set the RETVER value for the archive copy group. archives will be deleted automatically by IBM TSM when the number of days for retention has expired. • • • BMC Software. The SQL-BackTrack backup pool can be configured to specify which storage pool (copy group. the object cannot be archived. Confidential and Proprietary Information 3-12 SQL-BackTrack Module for IBM TSM Installation and User Guide . Set the RETVER (Retain Version) value for the archive copy group to NOLIMIT so that SQL-BackTrack can control expiration of the objects. if the SQL-BackTrack backups are archived (that is. The default RETVER value for archive copy groups is 365 days. you should set ARCHDEL to YES. Otherwise. Similarly.. If an object is bound to a NULL backup copy group. For expiration to work properly. backup or archive) to use.Storage Pools The IBM TSM server can specify the storage pools (copy groups) that are available in each management class. The IBM TSM administrator should note the following restrictions and recommendations when creating or modifying copy groups: • The backup or archive copy group in a management class cannot be empty (NULL). if an object is bound to a NULL archive copy group. that object cannot be backed up. Inc. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-13 . Instead. or a file that is accidentally deleted could be expired from the IBM TSM server the same day. Use DEFINE COPYGROUP or UPDATE COPYGROUP command (for type=backup) to set the value for backup copy group. Include-Exclude List The IBM TSM server may use an include-exclude list that associates the SQL-BackTrack filespace names with the appropriate management classes. Note If you do not set the RETONLY and VERDELETED values to 0.. If you have an include-exclude file.• Set the RETONLY and VERDELETED values for backup copy group to 0 so that SQL-BackTrack can control the expiration of the objects. The following example shows an include statement using /BACKTRACK as the filespace prefix and BTMGMT as the name of the management class: Unix example: include /BACKTRACK*/*/* BTMGMT Windows example: include ?:/BACKTRACK*/*/* BTMGMT BMC Software. add a line below the EXCLUDE * line for SQL-BackTrack backups that contains the filespace tag prefix and the management class.opt (Windows) file contains the INCLEXCL parameter. the dsm. Inc. create a separate management class and backup copy group for SQL-BackTrack backups.sys (Unix) file or dsm. Warning Do not set RETONLY to 0 on a backup copy group containing file system backups. If the IBM TSM server uses an include-exclude list. the objects that SQL-BackTrack creates will not be expired since they are considered by IBM TSM to be active objects. as in the following examples: • The following Unix include statement will match only the test backup done by the obsitest utility: include /BACKTRACK:tmp-control-dir/*/* Configuration Procedures This section contains information and procedures for configuring the IBM TSM server and client. For information on modifying this file. the IBM TSM administrator might need to modify the settings on the IBM TSM server. Configuring the IBM TSM Server Settings After reviewing the options listed in “IBM TSM Options” on page 3-4 with the IBM TSM administrator. Inc..opt file found in the IBM TSM server installation directory. BMC Software. Confidential and Proprietary Information 3-14 SQL-BackTrack Module for IBM TSM Installation and User Guide . you might want to use separate include statements for different databases. see the IBM TSM documentation. the IBM TSM storage agent file. if you are planning to perform LAN-free operations. Configuring the IBM TSM client involves configuring the IBM TSM API Client and the IBM TSM storage agent options files. Configuring the IBM TSM Client Configuring the IBM TSM client involves editing the IBM TSM API Client and. These options are stored in the dsmserv.If you are using the include-exclude file to control management classes. edit the dsm. and communications options for each server. communication method.sys. space management operations.Configuring the IBM TSM API Client For Unix. This file can also include authorization.opt. the SQL-BackTrack Module for IBM TSM connection to the IBM TSM server is controlled by the client user options file dsm. On Windows. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-15 .sys file Reference “Editing the Client System Options File (dsm. The dsm. • For Windows. and archive processing options.opt file • To specify the server parameters.. backup and archive options.opt) on Windows” on page 3-25 Windows • To specify the server parameters. the SQL-BackTrack Module for IBM TSM connection to the IBM TSM server is controlled by the client system options file dsm. the dsm. edit the dsm. edit the dsm.sys file specifies one or more servers to contact for services. backup.sys) on Unix” on page 3-18 and “Editing the IBM TSM Client User Options File (dsm. Edit the files in the following scenarios: Platform Unix File to Edit • To specify the server to use with SQL-BackTrack backups.opt file BMC Software.sys file).sys file does not exist. Inc.opt. and the SQL-BackTrack Module environment variables that you have set. the client user options file dsm. options specified in SQL-BackTrack backup pool or backup destination. options specified in SQL-BackTrack backup pool. and the SQL-BackTrack Module environment variables that you have set: • The dsm.opt file specifies the server (which is included in the dsm. and scheduling options.opt) on Unix” on page 3-22 “Editing the IBM TSM Client Options File (dsm. 8. A sample devconfig. Confidential and Proprietary Information 3-16 SQL-BackTrack Module for IBM TSM Installation and User Guide .opt file follows: DEVCONFIG devconfig. The following example shows the command with variables for the command options. you must configure the dsmsta. usually the SQL-BackTrack host. Inc.opt file and the devconfig. cd /usr/tivoli/tsm/StorageAgent/bin (For AIX) cd /opt/tivoli/tsm/StorageAgent/bin (For Solaris or HP-UX) BMC Software.19.192.out file. which are installed with the Tivoli Managed System for SAN product. commonly known as the storage agent.out SERVERNAME SQLBT The devconfig. A sample dsmsta..out file is created by the DSMSTA SETSTORAGESERVER command executed during the installation and configuration of the IBM TSM storage agent.86 LLADDRESS=1502 SERVERPA=1896e688f446 The content of the devconfig.out file follows: SET STANAME STAKE_AGENT SET STAPASSWORD 182372e3d32cefd5457d26e2 SET STAHLADDRESS 172. you might need to modify this file. The subsequent example shows the command with values instead of variables.out file is the device configuration file for the storage agent and includes information about the storage agent and the IBM TSM server with which the storage agent communicates.Configuring the IBM TSM Storage Agent Options Files If you are planning to perform LAN-free backup and recovery operations using SQL-BackTrack.19. The dsmsta. If your SQL-BackTrack host changes.192 DEFINE SERVER SQLBT HLADDRESS=172.opt file is the storage agent options file that contains the name of the server with which the storage agent communicates. see “Editing the Storage Agent Options Files” on page 3-28./dsmsta setstorageserver myname=<storage agent> mypassword=<storage agent passwd> myhladdress=<IP address of storage agent> servername=<TSM server name> serverpassword=<TSM server passwd hladdress=<IP address of TSM server> lladdress=<port no. you can use the obsitest utility that is installed with the SQL-BackTrack Module. To edit these files.. which stores information about the backup device (IBM TSM./dsmsta setstorageserver myname=stake_agent mypassword=stake_agent myhladdress=172.19. BMC Software.19. To validate the IBM TSM configuration. a file normally created by your SQL-BackTrack program. see “Validating the Configuration” on page 3-33. Validating the IBM TSM Configuration To verify that the IBM TSM server and client are properly configured for SQL-BackTrack backups. in this case) and its characteristics.192 servername=SQLBT serverpassword=SQLBT hladdress=172. Inc.8. The obsitest utility prompts you to create a backup pool. of TSM server> ..86 lladdress=1500 See the IBM TSM storage agent documentation for more information.192. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-17 . .sys file if your IBM TSM administrator requests that SQL-BackTrack backups be submitted under a different client node name. To Edit the IBM TSM Client System Options File dsm.sys file. but they will be registered against a different node name. BMC Software.sys file than the ones discussed here. Note You might want to set more options in the dsm. If there is not a separate server stanza. Configure the options in the server stanza according to the guidelines presented in this procedure. Confidential and Proprietary Information 3-18 SQL-BackTrack Module for IBM TSM Installation and User Guide . Step 2 Ensure that the dsm. you can copy an existing server stanza to the end of the file and modify the options according to this procedure. Contact your IBM TSM administrator for information about other options that you can set in this file. Also.sys file.sys file includes a server stanza for the server that you will use with SQL-BackTrack operations and the options for that server.Editing the Client System Options File (dsm. By default. add a separate server stanza in the dsm.sys file.sys Step 1 Locate the dsm. it is found in the DSMI_DIR directory. You must have root access to edit the dsm. Inc.sys) on Unix Summary: On Unix. Ensure that the node name that you are using with SQL-BackTrack backups has been registered with the IBM TSM server. Use the REGISTER NODE command to perform this task. Before You Begin Read “IBM TSM Options” on page 3-4. see the IBM TSM client user documentation for more information about editing the dsm. The backups will then go to the same server. bmc.com TCPPort 1500 NODENAME ADSM_CLIENT_NODE PASSWORDAccess GENERATE COMPRESSIon no Step 3 If you copied the server stanza.Typically. change the name on the SERVERNAME parameter. BMC Software.. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-19 . the server stanza begins with the line SErvername <name>. choosing any name that can easily identify the stanza as being for SQL-BackTrack. as shown in the following stanza from a sample dsm. Inc.sys file: SERVERNAME REGCLNT enablelanfree yes COMMMethod tcpip TCPServeraddress jupiter. Step 4 Set the options as appropriate, using the following information for guidance:. Table 3-3 Settings for dsm.sys file on Unix Option enablelanfree Description Setting this option to yes enables this feature if the IBM TSM client is configured for LAN-free operations. For this required option, specify your network’s communication method, for example, tcpip. For this required option, specify the TCP/IP port used to communicate with the IBM TSM Server. The default value is 1500. For this required option, specify the IP address for the IBM TSM Server, for example, jupiter.bmc.com. Specify the IBM TSM client node name registered with the IBM TSM server. Setting the value to no is recommended. Setting value to generate is recommended. Note: If prompt is used, you will need to update the password that is stored by SQL-BackTrack whenever the password changes, or SQL-BackTrack operations will fail. Reference “LAN-free Option” on page 3-9 “Communication Method” on page 3-9 “Communication Method” on page 3-9 “Communication Method” on page 3-9 “IBM TSM Node Name” on page 3-6 “Compression Setting” on page 3-10 “Password Authentication” on page 3-7 COMMMethod TCPPort TCPServeraddress NODENAME COMPRESSIon PASSWORDAccess Note: Uppercase letters indicate the abbreviation for each option. Note To facilitate recovery from an alternate host, the NODENAME, SERVERNAME, and PASSWORDAccess values should be the same in each dsm.sys file on each host. When you have finished editing the dsm.sys file, it might contain two stanzas similar to the following stanzas. (The new stanza is shown in bold.) BMC Software, Inc., Confidential and Proprietary Information 3-20 SQL-BackTrack Module for IBM TSM Installation and User Guide SERVERNAME REGCLNT enablelanfree yes CommMethod TCPip TCPServeraddress jupiter.bmc.com TCPPort 1500 NODENAME TSM_CLIENT_NODE PASSWORDAccess GENERATE COMPRESSIon no SERVERNAME SQLBT enablelanfree yes CommMethod TCPip TCPServeraddress jupiter.bmc.com TCPPort 1500 NODENAME BT_NODE PASSWORDAccess GENERATE COMPRESSIon no Where to Go from Here Proceed to either of the following procedures: • Repeat this procedure on each IBM TSM client. If you are using a cluster environment or plan to recover data backed up on another host, you should ensure that the NODENAME, SERVERNAME, and PASSWORDAccess values are the same in each dsm.sys file on each host. Proceed to “Editing the IBM TSM Client User Options File (dsm.opt) on Unix” on page 3-22. • BMC Software, Inc., Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-21 Editing the IBM TSM Client User Options File (dsm.opt) on Unix Summary: Use this procedure to edit the dsm.opt file if more than one IBM TSM server stanza is listed in the dsm.sys file. Before You Begin Read “IBM TSM Options” on page 3-4. Also, see the IBM TSM client user documentation for more information about editing the dsm.opt file. Use a text editor to modify this file. Determine which dsm.opt file that you want to edit: • You can edit the existing client options file that was created during the IBM TSM client installation. You can create a separate dsm.opt file for use by the SQL-BackTrack Module for IBM TSM by using the sample file, dsm.opt.smp, that is installed with the SQL-BackTrack Module for IBM TSM. This file is located in $DTBASE/obsi.adsm-3.1.00/dsm or $DTBASE/obsi.adsm-3.1.00-64bit/dsm. To use this file, you must rename it and place it in a location different from the dsm.opt file that was created during the IBM TSM client installation. Note • The dsm.opt file can be stored in any location. It does not have to reside in the same directory as the dsm.sys file or in the location of the IBM TSM API client installation. BMC Software, Inc., Confidential and Proprietary Information 3-22 SQL-BackTrack Module for IBM TSM Installation and User Guide sys file and you do not want SQL-BackTrack to connect to the first server listed in the dsm.sys) on Unix” on page 3-18.To Edit the dsm. Inc. The following example shows a sample entry: SErvername SQLBT Note The server name that you use should match the name used in the server stanza created for SQL-BackTrack in the task “Editing the Client System Options File (dsm. If you are performing LAN-free operations.opt File Step 1 If there are multiple servers listed in the dsm.opt file on each host. See “Overriding IBM TSM Options” on page 4-11. if appropriate.opt file. you should ensure that the SErvername values are the same in each dsm. Step 2 Ensure that the environment variable DSMI_CONFIG specifies the fully qualified file name of the dsm.sys file. Where to Go from Here You can proceed with any of the following procedures: • Repeat this step on each host. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-23 . If you are using a cluster environment or plan to recover data backed up on another host.. Server names can be up to eight characters and are not case-sensitive. provide the name of the server to which you want SQL-BackTrack to connect. you can provide the server name in the backup pool or use the SQL-BackTrack Module environment variable. To override the server name specified here. see “Editing the Storage Agent Options Files” on page 3-28 • BMC Software. . see “Running the adsmpw Utility” on page 3-30 To verify the IBM TSM configuration. Inc. see “Validating the Configuration” on page 3-33 • BMC Software.sys file is set to generate.• If PASSWORDAccess in the dsm. Confidential and Proprietary Information 3-24 SQL-BackTrack Module for IBM TSM Installation and User Guide . 00\dsm. Before You Begin Read “IBM TSM Options” on page 3-4. If your IBM TSM administrator requests that SQL-BackTrack backups be submitted under a different client node name. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-25 . Ask your IBM TSM administrator to register the new client node name on the IBM TSM server. see the IBM TSM client user documentation for more information on editing the dsm. Use a text editor to modify the dsm. rename it using Windows Explorer and place it in a location separate from the dsm.opt on Windows Step 1 Add the nodename parameter.1.opt file. Specify the options in the dsm. dsm. providing the node name that the IBM TSM administrator requested.opt. The sample dsm..opt file to specify IBM TSM server options for SQL-BackTrack operations. Also. Step 2 Step 3 BMC Software.opt) on Windows Summary: Edit the dsm.smp that is installed with the SQL-BackTrack Module for IBM TSM. create a different dsm.opt file. using the information in Table 3-4 for guidance. To use this file.opt file.adsm-3.opt file installed during the IBM TSM client installation.opt file for the SQL-BackTrack Module for IBM TSM by using the sample file. To Edit the IBM TSM Client Option File dsm.opt file is located in %DTBASE%\obsi. See the IBM TSM documentation for information on the dsmadmc command. Inc.Editing the IBM TSM Client Options File (dsm. Confidential and Proprietary Information 3-26 SQL-BackTrack Module for IBM TSM Installation and User Guide . specify the IP address for the IBM TSM Server. For this required option. Setting the value to no is recommended.Table 3-4 Settings for the dsm.. The default value is 1500. Reference “IBM TSM Server Name” on page 3-6 enablelanfree COMMMethod “LAN-free Option” on page 3-9 “Communication Method” on page 3-9 “Communication Method” on page 3-9 “Communication Method” on page 3-9 “Compression Setting” on page 3-10 “Password Authentication” on page 3-7 TCPPort TCPServeraddress COMPRESSIon PASSWORDAccess Setting the value to generate is recommended. or SQL-BackTrack operations will fail. Server names can be up to eight characters and are not case-sensitive.com enablelanfree yes PASSWORDAccess generate COMPRESSIon no BMC Software. tcpip. specify your network’s communication method. jupiter. specify the TCP/IP port used to communicate with the IBM TSM Server.com.opt file on Windows Option SErvername Description Specify this required option if you are using a separate node name for SQL-BackTrack backups. Note: If prompt is used. For this required option. For this required setting. Inc. Setting this option to yes enables this feature if IBM TSM is configured for LAN-free operations. for example. Note: Uppercase letters indicate the abbreviation for each option. The dsm.opt file for Windows contains all the IBM TSM client options and looks similar to the following example: SErvername SQLBT COMMMethod TCPip NODENAME BT_NODE TCPPort 1500 TCPServeraddress jupiter. you will need to update the password that is stored by SQL-BackTrack whenever the password changes. for example.bmc.bmc. ensure that the NODENAME. SERVERNAME. To verify the IBM TSM configuration.. If the PASSWORDAccess option is set to generate. you need to override the environment variable DSMI_CONFIG to point to the fully qualified file name of the dsm. Inc. If you are using a cluster environment or plan to recover data backed up on another host. • • • BMC Software. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-27 . See “Setting Windows Environment Variables During Post-Installation” on page 2-19 for more information. see “Validating the Configuration” on page 3-33. If you are performing LAN-free operations. see “Running the adsmpw Utility” on page 3-30. Where to Go From Here You can proceed with any of the following procedures: • Repeat this procedure on each IBM TSM client.opt file on each host. see “Editing the Storage Agent Options Files” on page 3-28.opt file to a different location. the DSMI_CONFIG variable is updated in the registry with %DSMI_DIR%\dsm.opt file. If you have copied the dsm.opt as the default.Note During the installation. and PASSWORDAccess values are the same in each dsm. Inc. which is found in the storage agent installation directory.out SERVERNAME SQLBT Step 3 Locate the devconfig.opt file in the storage agent installation path.opt file (Windows)).opt file contains the name of the server that you will use with SQL-BackTrack backups.out file. (This is the same server name that appears in the dsm. Operating System AIX Solaris and HP Windows Step 1 Directory /usr/tivoli/tsm/StorageAgent/bin /opt/tivoli/tsm/StorageAgent/bin C:\Program Files\tivoli\tsm\storageagent Step 2 Ensure that the dsmsta. Confidential and Proprietary Information 3-28 SQL-BackTrack Module for IBM TSM Installation and User Guide . The default paths are as follows: Operating System AIX Solaris and HP Windows Directory /usr/tivoli/tsm/StorageAgent/bin /opt/tivoli/tsm/StorageAgent/bin C:\Program Files\tivoli\tsm\storageagent BMC Software. Locate the dsmsta.sys file (Unix) or the dsm.opt file and the devconfig. A sample dsmsta.opt file follows: DEVCONFIG devconfig.Editing the Storage Agent Options Files Summary: Use this procedure to ensure that the server name of the server that you will use for SQL-BackTrack backups is found in both the dsmsta..out file. The default paths are as follows:. .86 LLADDRESS=1502 SERVERPA=1896e688f446 Where to Go from Here Proceed with running the adsmpw utility.) A sample devconfig.out file contains the server name of the SQL-BackTrack host.19. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-29 .19. See “Running the adsmpw Utility” on page 3-30. (This server name is the same server name that appears in the dsmsta.192.out file follows: SET STANAME STAKE_AGENT SET STAPASSWORD 182372e3d32cefd5457d26e2 SET STAHLADDRESS 172.192 DEFINE SERVER SQLBT HLADDRESS=172.Step 4 Ensure that the devconfig. Inc.opt file.8. BMC Software. opt file for Windows. Inc. BMC Software. In addition. Use this procedure to seed the IBM TSM password on each host or update the password on each host when it changes. The adsmpw utility uses the environment variable DSMI_DIR to locate the IBM TSM API client installation and the -s option to determine which IBM TSM server to contact. Note If you set any of the optional environment variables. you must log in as root (Unix) or as a member of the local system administrator group (Windows). The following variables must be set: • • • • DTBASE DSMI_DIR DSMI_CONFIG DSMI_LOG See “Setting Unix Environment Variables During Post-Installation” on page 2-16 or “Setting Windows Environment Variables During Post-Installation” on page 2-19 for the recommended values. Confidential and Proprietary Information 3-30 SQL-BackTrack Module for IBM TSM Installation and User Guide . You should run this utility before creating a backup pool or backup destination. Before You Begin To run this utility.Running the adsmpw Utility Summary: The adsmpw utility seeds the node password in a password file (Unix) and in the registry (Windows) for the node name of the IBM TSM server so that subsequent passwords can be generated. SQL-BackTrack uses this stored password when it tries to access the IBM TSM server. the adsmpw utility ignores those values. this utility ignores backup pool or backup destination entries. if you have set the PASSWORDAccess option to generate in the dsm.sys file for Unix or in the dsm.. 00\bin Step 2 At the Unix or Windows system prompt.1.adsm-3. For example: • for Unix 32-bit Module % cd $DTBASE/obsi.adsm-3.00/bin for Unix 64-bit Module % cd $DTBASE/obsi. For <current_password>. • BMC Software.sys (Unix only) or use the fully qualified server name (Windows). Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-31 . type the following command: adsmpw -s <servername> -c <current_password> -p <new_password> • For <servername>.00-64bit/bin • for Windows C:\> cd %DTBASE%\obsi.1. enter the client password used when the node was registered. use the value assigned to the servername entry from the IBM TSM client system options file dsm. Inc.1. and the password has not yet been seeded if you are about to recover data to an alternate host and you have not yet seeded the password on the alternate host if the IBM TSM administrator removes the password file (Unix only) if the node password is manually changed. using an IBM TSM administrative utility. This option enables this utility to use a non-default IBM TSM server name.You will need to run adsmpw in the following cases: • if this is a first-time installation.. for example • • • To Run the adsmpw Utility Step 1 Change your working directory to the location of adsmpw.adsm-3. • For <new_password>, enter any new password. Note If you are using the adsmpw utility for the first time to seed the host with the password, use the same syntax. In this case, use the same values for <current_password> and <new_password>. Warning Do not forget the new password! If you forget the password, you cannot retrieve it. If a Problem Occurs If you have problems with the password, the IBM TSM administrator can reset it using the IBM TSM dsmadmc utility with the update NODE command. After the administrator resets the password, then you can update the password using the adsmpw utility. See the IBM TSM documentation for more information on the dsmadmc utility and the update NODE command. Where to Go From Here If you are in a cluster environment, run this utility on every host in the cluster. Proceed to “Validating the Configuration” on page 3-33. BMC Software, Inc., Confidential and Proprietary Information 3-32 SQL-BackTrack Module for IBM TSM Installation and User Guide Validating the Configuration Summary: To validate the IBM TSM configuration, you use the obsitest utility to create a backup pool and perform a test backup and recovery. Before You Begin Ensure that the following environment variables are set: • • • DTBASE DSMI_DIR DSMI_CONFIG See “Setting Unix Environment Variables During Post-Installation” on page 2-16 or “Setting Windows Environment Variables During Post-Installation” on page 2-19 for the recommended values. Ensure that you have read/write access to the $DTBASE/obsi.adsm-3.1.00/bin or $DTBASE/obsi.adsm-3.1.00-64bit/bin directory (Unix) or %DTBASE\obsi.adsm-3.1.00\bin (Windows) directory. Note For the purposes of this test, BMC Software recommends that you set the following options in the dsm.sys file (Unix) or the dsm.opt file (Windows): COMPRESSIon = no PASSWORDAccess = prompt (for first-time installation) or PASSWORDAccess=generate (for upgrading) If the PASSWORDAccess option is set to generate, you must run the adsmpw utility before you run the obsitest utility. See “Running the adsmpw Utility” on page 3-30 for more information. BMC Software, Inc., Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-33 To Run the obsitest Utility Step 1 Create a backup pool for the SQL-BackTrack Module for IBM TSM, using the following commands according to your platform: Platform Unix Commands % cd $DTBASE/obsi.adsm-3.1.00/bin % obsitest -msgfile ../msgs/obsitest.english adsm -pool or % cd $DTBASE/obsi.adsm-3.1.00-64bit/bin % obsitest -msgfile ../msgs/obsitest.english obsi/adsm -pool C:> cd %DTBASE%\obsi.adsm-3.1.00\bin C:>obsitest -msgfile ..\msgs\obsitest.english adsm -pool Windows Answer the prompts using the following table and the example of obsitest output on the following pages for guidance. In most cases, you should accept the default value by pressing Enter. Prompt TSM Server name Description Type the name of the IBM TSM server to be used for this session. The server name should be listed in the dsm.sys file (Unix) or the dsm.opt file (Windows). Specify whether the PASSWORDAccess mode is set to generate in the dsm.sys file. Default is y. If you respond n, you will be prompted for the password for the node name. Specify the IBM TSM client (SQL-BackTrack host) node name registered with the IBM TSM Server. This is the same name that is in the dsm.sys file (Unix) or the dsm.opt file (Windows). Specify the password for the node name used. Response <server name> n PASSWORDAccess mode set to generate? TSM session node name <node name> TSM session node password Note: This prompt will not appear if PASSWORDAccess is set to generate. <password > BMC Software, Inc., Confidential and Proprietary Information 3-34 SQL-BackTrack Module for IBM TSM Installation and User Guide The default value is n.0. Storing the password disables user prompting during the recovery operation. Inc. Version 4. serial number @@_SERIAL_NUMBER Licensed to: User *** started on 03/03/2003 10:10:18 Typing '?' at any prompt prints help information Enter TSM Server Name (return = none)? <tsm_server_name_for_this_session> Is Passwordaccess mode for TSM Server '<tsm_server_name>' is generate? (y/n) [y] <passwordaccess_for_tsm_server_name> BMC Software. The default value is y. Storing the password disables user prompting during the backup operation. BMC Software. Specify whether you want to be prompted if the media is not available.Prompt Please confirm Use stored password for backup? Description Password confirmation Specify whether you want to store the password just entered for the backup operation.0. The default value is y. Specify whether you want to use the default filespace name for the location where your SQL-BackTrack backup data is stored.. Specify the copy group (backup or archive) that you want to use that is associated with the management class specified above. Specify the IBM TSM management class that you want to override. if you want to direct your backups to a management class other than the default set by the IBM TSM administrator. Response <password > Press Enter Use stored password for recovery? y Wait for media mounts? Press Enter TSM filespace name? Press Enter TSM management class override? Press Enter Select TSM storage pool Press Enter The following sample shows the output from using the obsitest utility to create a backup pool on Unix: OBSI Test Program Utility (OBSITEST) Copyright (c) 1991-1998. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-35 . A backup or recovery operation could fail if the media is not available. Specify whether you want to store the password just entered for recovery operation. The default filespace tag prefix is /BACKTRACK. Inc. The default value is BACKUP. 00/bin/tmp-control-dir/. Confidential and Proprietary Information 3-36 SQL-BackTrack Module for IBM TSM Installation and User Guide .End of information ---------Is this correct(y/n) y Write pool file:/usr/datatools/obsi. BMC Software.Enter TSM session node name (return = default)? <nodename_for_SQL-BackTrack> Enter TSM session node password (return = none)? <node_password_for_SQL-BackTrack_nodename> Please confirm TSM session node password ? <node_password_for_SQL-BackTrack_nodename> Use stored password for backup operations(y/n) [y] Enter Use stored password for recover operations(y/n) [n] y Wait for media mounts? (y/n) [y] Enter Enter TSM filespace name (return = /BACKTRACK)? <Enter> Enter TSM management class override(return = none)? Enter Select TSM storage pool [BACKUP|ARCHIVE] (return = BACKUP)? Enter adsm POOL obsi test completed ---------.. such as jupiter.com.dtoptions(y /n) [y] <Enter> Note If you are performing this step on Windows.1. the output will be similar to the Unix output shown above.bmc. Inc. but the servername entry will contain a fully qualified IBM TSM server name.Control file information ---------begin backup_pool=default obsi=adsm server=SQLBT node=bt_node dumpepass=KLETZJDXKCB23T6VR5G5V43NE568766T loadepass=FJ42DQQRW62XPEUD59XA85UMZMP5XJYX mount-wait=y filespace=/BACKTRACK management_class storage-pool=backup end backup_pool ---------.adsm-3. 187MBs(0.00 secs)] [OBSIDump1 718] *** using: crc-check: 1.\msgs\obsitest.english adsm -in The following sample shows the output from using the obsitest utility to perform a test recovery on Unix: OBSI Test Program Utility (OBSITEST) Copyright (c) 1995-2002. Version 4.. BMC Software. Inc. serial number @@_SERIAL_NUMBER Licensed to: BMC Software.. Inc..status 0 *** OUT command completed *** Step 3 Perform a test recovery using the following command and the sample obsitest utility output for guidance: Platform Unix Windows Command % obsitest -msgfile . BMC Software. Confidential and Proprietary Information Configuring IBM TSM for Use with SQL-BackTrack 3-37 .english adsm -out The following sample shows the output from using the obsitest utility to create a test backup on Unix: OBSI Test Program Utility (OBSITEST) Copyright (c) 1995-2002../msgs/obsitest.english adsm -out obsitest -msgfile . BMC Software.0.\msgs\obsitest./msgs/obsitest.0. Inc. Inc *** started on 03/03/2003 10:10:04 Starting 1 dump stream(s) [OBSIDump1 718] *** OBSITEST Dump Completed on 03/03/2003 10:10:07 [OBSIDump1 718] *** 64. compression: 0.000K bytes of 64..Step 2 Perform a test backup using the following command and the sample obsitest utility output for guidance: Platform Unix Windows Command % obsitest -msgfile .000K bytes [%100 complete at 20. ipc: named pipe 10:10 OBSITEST Dump Completed OK .english adsm -in obsitest -msgfile . ipc: named pipe 10:12 OBSITEST Load Completed OK .0. Confidential and Proprietary Information 3-38 SQL-BackTrack Module for IBM TSM Installation and User Guide .Version 4.000K bytes [%100 complete at 51. Inc *** started on 03/03/2003 10:12:36 Starting 1 load stream(s) [OBSILoad1 758] *** OBSITEST Load completed on 03/03/2003 10:12:38 [OBSILoad1 758] *** 64.0. “Configuring SQL-BackTrack for Use with IBM TSM.000K bytes of 64.status 0 *** IN command completed *** This completes the configuration validation.. Where to Go From Here Proceed to Chapter 4. serial number @@_SERIAL_NUMBER Licensed to: BMC Software.” BMC Software. compression: 0.00 secs)] [OBSILoad1 758] *** using: crc-check: 1. Inc.188MBs(0. . . . . . . . . 4-2 Adding the SQL-BackTrack Module to SQL-BackTrack on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 4-31 Using Memory Mapped I/O for SQL-BackTrack for Oracle . . . 4-32 BMC Software. . . . . . . . . . . . . . . Inc. . . . . . . . . . . 4-31 Using Multiple IBM TSM Servers . . . . . .4 Configuring SQL-BackTrack for Use with IBM TSM 4 This chapter contains the following topics: Overview . 4-4 Adding the SQL-BackTrack Module to SQL-BackTrack on Windows4-7 Overriding IBM TSM Options . . . . . . . . . . . . . . 4-23 Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server . . . . . . . . 4-27 Improving Your Backup Performance . . . . 4-11 Defining a Backup Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 Defining a Backup Pool (Oracle Parallel Server Users). . Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-1 . . . . . . . . . . . . . . . DB2/UDB.Overview After you verify that you have properly configured IBM TSM. Task Ensure that the SQL-BackTrack Module is linked to SQL-BackTrack Create a backup pool Reference “Adding the SQL-BackTrack Module to SQL-BackTrack on Unix” on page 4-4 “Defining a Backup Pool” on page 4-17 BMC Software. or Informix on Unix only. do not delete the existing backup pools or destinations until the backups in the backup pools or destinations have expired. The chapter also contains the following topics that you might find useful during configuration: • • • • improving your backup performance memory mapped I/O using multiple IBM TSM servers updating backup profiles and control directories If you are upgrading from a previous version of the SQL-BackTrack Module for IBM TSM and you have existing backup pools. you can continue to use the existing backup pools or backup destinations.. Note If you create new backup pools or backup destinations. If you are using SQL-BackTrack for Oracle. Sybase. you will perform the tasks listed in the following table. Confidential and Proprietary Information 4-2 SQL-BackTrack Module for IBM TSM Installation and User Guide . you can configure SQL-BackTrack to work with IBM TSM. Inc. . you will perform the tasks listed in the following table.If you are using SQL-BackTrack for Oracle or DB2/UDB on Windows. Inc. Task Add the SQL-BackTrack Module to SQL-BackTrack Create a backup pool Reference “Adding the SQL-BackTrack Module to SQL-BackTrack on Windows” on page 4-7 “Defining a Backup Pool” on page 4-17 If you use SQL-BackTrack for Microsoft SQL Server. Task Add the SQL-BackTrack Module to SQL-BackTrack Create a backup destination Reference “Adding the SQL-BackTrack Module to SQL-BackTrack on Windows” on page 4-7 “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 BMC Software. you will perform the tasks listed in the following table. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-3 . The links must not contain program version numbers. as in the following example: % cd $DTBASE % ln -s . If your earlier version of the SQL-BackTrack Module for IBM TSM has a similar symbolic link that points to another location. Confidential and Proprietary Information 4-4 SQL-BackTrack Module for IBM TSM Installation and User Guide . If any of these links exist and point to the exact locations described in this step.1.adsm Note The SQL-BackTrack Module for IBM TSM installation automatically creates an obsi. SQL-BackTrack and the SQL-BackTrack Module for IBM TSM require symbolic links to the current program versions. Inc. You can determine whether these links already exist by typing ls -l at the Unix system prompt. Before You Begin Ensure that no SQL-BackTrack processes are running on the host on which you are adding the Module. you do not have to reestablish them.adsm-3. you must remove it and reestablish the link to the location given in this step.adsm link to point to the latest version of the SQL-BackTrack Module installed in the DTBASE directory. BMC Software. To Add the 32-bit SQL-BackTrack Module to SQL-BackTrack on Unix Step 1 Create or verify the versionless symbolic link for the SQL-BackTrack Module for IBM TSM../obsi.00 obsi.Adding the SQL-BackTrack Module to SQL-BackTrack on Unix Summary: Use these procedures to add the 32-bit or 64-bit SQL-BackTrack Module for IBM TSM to the SQL-BackTrack products that run on Unix by establishing symbolic links for the SQL-BackTrack Module. adsm obsi././.adsm The value of <x> depends on your SQL-BackTrack product..adsm obsi. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-5 .adsm64 link to point to the latest version of the SQL-BackTrack Module installed in the DTBASE directory./obsi. BMC Software.adsm64 Note The SQL-BackTrack Module for IBM TSM installation automatically creates an obsi./obsi. SQL-BackTrack Product SQL-BackTrack for Oracle SQL-BackTrack for Sybase SQL-BackTrack for DB2 Universal Database SQL-BackTrack for Informix <x> value o s u i The following example shows the commands for SQL-BackTrack for Oracle version 4.adsm To Add the 64-bit SQL-BackTrack Module to SQL-BackTrack on Unix Step 1 Create or verify the versionless symbolic link for the SQL-BackTrack Module for IBM TSM.00/links % ln -s ..adsm-3.Step 2 Use the following commands to create the symbolic links required by SQL-BackTrack: % cd $DTBASE % cd $DTBASE/<x>backtrack-<version>/links % ln -s .. as in the following example: % cd $DTBASE % ln -s ./obsi...1.0.00-64bit obsi. Inc.0: % cd $DTBASE % cd $DTBASE/obacktrack-4. Inc..adsm64 obsi. SQL-BackTrack Product SQL-BackTrack for Oracle SQL-BackTrack for Sybase SQL-BackTrack for DB2 Universal Database SQL-BackTrack for Informix <x> value o s u i For purposes of this example.Step 2 Use the following commands to create the symbolic links required by SQL-BackTrack.././obsi. see “Overriding IBM TSM Options” on page 4-11 To create a backup pool.adsm Where to Go From Here Proceed to either of the following: • To override the IBM TSM options../obsi. see “Defining a Backup Pool” on page 4-17.00/links % ln -s .adsm The value of <x> depends on your SQL-BackTrack product. % cd $DTBASE % cd $DTBASE/<x>backtrack-<version>/links % ln -s .0. we will use SQL-BackTrack for Oracle version 4./.0: % cd $DTBASE % cd $DTBASE/obacktrack-4.. Confidential and Proprietary Information 4-6 SQL-BackTrack Module for IBM TSM Installation and User Guide .adsm64 obsi. • BMC Software.. To Add the SQL-BackTrack Module to SQL-BackTrack for Oracle and SQL-BackTrack for DB2/UDB on Windows Step 1 Run the Configure utility by clicking Configure from the Start => Programs => SQL-BackTrack program folder..exe file should be found at %DTBASE%\obsi. enter the directory name of the SQL-BackTrack Module. Type the full path name of the SQL-BackTrack Module executable (adsm.Adding the SQL-BackTrack Module to SQL-BackTrack on Windows Summary: In the procedure provided. Note The adsm. You can search for the executable by clicking the Browse button. In the Add OBSI dialog box.adsm-3. In the SQL-BackTrack Configure dialog box.A 3. 3. The procedures are different depending on your SQL-BackTrack product. click Add OBSI. BMC Software. Inc. Before You Begin Ensure that no SQL-BackTrack processes are running on the host on which you are adding the Module. proceed as follows: 3.B Step 2 Step 3 Type adsm in the Name for OBSI module field.exe) in the Modules executable field.C In the Modules home path box. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-7 .1.00\bin directory. you add the SQL-BackTrack Module to SQL-BackTrack on Windows using the Configure utility. D Click Add to complete the operation. 3.E Step 4 Click Close to exit the Add OBSI dialog box. click Add. The Add OBSI dialog box is displayed.. Step 2 Step 3 BMC Software. In the SQL-BackTrack Configure dialog box.3. In the Add SQL-BackTrack Module dialog box. Click Done on the Configure dialog box to exit the utility. To Add the SQL-BackTrack Module for IBM TSM to SQL-BackTrack for Microsoft SQL Server Step 1 Run the Configure utility by clicking Configure from the Start => Programs => SQL-BackTrack for Microsoft SQL Server program folder. Inc. click Add Module. Confidential and Proprietary Information 4-8 SQL-BackTrack Module for IBM TSM Installation and User Guide . as seen in the following example: Step 6 Step 7 Click Close to exit the Add SQL-BackTrack Module dialog box.adsm entry is added to the list of Installed SQL-BackTrack Modules.. The obsi.exe file that is located at %DTBASE%\obsi. Note If you mistakenly select the adsm.1. see “Overriding IBM TSM Options” on page 4-11. which is located at %DTBASE%\obsi. Where to Go From Here Proceed to either of the following: • To override the IBM TSM options. the following error message is issued when you submit the backup: SQL-BackTrack Module is unable to initialize Message Manager.00\bin.adsm-3.adsm-3. Click Close on the SQL-BackTrack Configure dialog box to exit the utility. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-9 .exe.1. Inc.00\bin\obsi. navigate to adsm. Step 5 Select adsm.exe. BMC Software.Step 4 Using the Open dialog box. and click Open. Confidential and Proprietary Information 4-10 SQL-BackTrack Module for IBM TSM Installation and User Guide .• To create a backup pool or backup destination see “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27. BMC Software. Inc.. To override what is set in the dsm.Overriding IBM TSM Options Summary: Use the procedure provided to enable the SQL-BackTrack Module to override the IBM TSM options.. the node name is set in the dsm. on page 4-12 provides the following information: • • The hierarchy for overriding each of the IBM TSM options and the SQL-BackTrack backup pool or backup destination options. Scenario 2: The filespace tag prefix is stored in the SQL-BackTrack backup pool. you can set the DT_ADSM_FILESPACE variable to override what is stored. Note BMC Software recommends that you use the backup pool or backup destination to override the IBM TSM options.sys file (Unix) or the dsm.sys file (Unix) or dsm. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-11 . Inc.opt file (Windows). In this case. and the node name is not in the SQL-BackTrack backup pool or backup destination. BMC Software.opt file (Windows). References to procedures for overriding the IBM TSM options and the backup pool options. you can use the environment variable DT_ADSM_NODENAME. Example The following examples demonstrate how to use this table: Scenario 1: The PASSWORDAccess option is prompt. » Use the following table as a guide to override the IBM TSM options. Table 4-1. You can use this same procedure to override the SQL-BackTrack backup pool or backup destination settings. “Optional Environment Variables. Environment variable DT_ADSM_SERVER 2. Value of SErvername entry in dsm.Table 4-1 Overriding IBM TSM Options (Part 1 of 4) IBM TSM Option IBM TSM server name Override Hierarchy Unix 1. “Optional Environment Variables.” on page 2-22 “Overriding IBM TSM Options” on page 4-11 “Configuring the IBM TSM Client” on page 3-14 “Configuring the IBM TSM Client” on page 3-14 Table 2-6.opt) on Windows” on page 3-25 BMC Software. Confidential and Proprietary Information 4-12 SQL-BackTrack Module for IBM TSM Installation and User Guide . Inc. Value of first SErvername entry in dsm. Backup pool entry server=<servername> 3.. Windows 1. Value of TCPServeraddress entry in the dsm. 4. Environment variable DT_ADSM_SERVER 2. Backup pool or backup destination entry server=<servername> 3.opt file Reference Table 2-6.” on page 2-22 “Overriding IBM TSM Options” on page 4-11 “Editing the IBM TSM Client Options File (dsm.opt file.sys file. Value of nodename entry in dsm. If PASSWORDAccess is prompt 1.opt) on Windows” on page 3-25 N/A 3. Environment variable DT_ADSM_NODE 2. if PASSWORDAccess is generate 1.opt) on Windows” on page 3-25 N/A 2. Computer name BMC Software. if PASSWORDAccess if prompt 1. Name returned by the Unix host name command On Unix.opt file “Editing the IBM TSM Client Options File (dsm. Environment variable DT_ADSM_NODE 2. Value of nodename entry in dsm. “Optional Environment Variables.” on page 2-22 “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 “Editing the IBM TSM Client Options File (dsm. Name returned by the Unix hostname command On Windows PASSWORDAccess is generate 1.sys) on Unix” on page 3-18 N/A 2. Computer name On Windows. Value of nodename entry in dsm. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-13 . “Optional Environment Variables. Value of nodename entry in dsm.sys file Table 2-6. Inc.sys file Reference “Editing the Client System Options File (dsm.” on page 2-22 “Overriding IBM TSM Options” on page 4-11 “Editing the Client System Options File (dsm.. Backup pool or backup destination entry node=<adsm_client_nodename> Table 2-6.sys) on Unix” on page 3-18 N/A 4. Backup pool entry node=<adsm_client_nodename> 3.Table 4-1 Overriding IBM TSM Options (Part 2 of 4) IBM TSM Option IBM TSM client node name Override Hierarchy On Unix.opt file 4. Backup pool entry mount-wait=<y/n> IBM TSM filespace tag prefix for SQL-Backtrack 1. “Optional Environment Variables. Environment variable DT_ADSM_MOUNTWAIT=<y/n> 2. Reference Table 2-6.” on page 2-22 “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 Table 2-6.Table 4-1 Overriding IBM TSM Options (Part 3 of 4) IBM TSM Option IBM TSM node name password Override Hierarchy If PASSWORDAccess is prompt 1. Confidential and Proprietary Information 4-14 SQL-BackTrack Module for IBM TSM Installation and User Guide . Environment variable DT_ADSM_FILESPACE=/<filespace_nam e> 2. Environment variable (not encrypted) DT_ADSM_PASSWORD 2. “Optional Environment Variables.” on page 2-22 “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 N/A Table 2-6. Backup pool entry filespace=/<filespace_name> BMC Software. Inc.. Backup pool entries (encrypted) loadepass=<encrypted_adsm_ client_password_for_backup_or_expirati on> or dumpepass=<encrypted_adsm_ client_password_for_recovery> If PASSWORDAccess is generate No overrides are available. “Optional Environment Variables.” on page 2-22 “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 storage device mount wait 1. ” on page 2-22 “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 “Editing the Client System Options File (dsm. “Optional Environment Variables. “Optional Environment Variables.” on page 2-22 “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27 IBM TSM storage pool (copy group) 1. Inc. Default management class Reference Table 2-6. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-15 .sys) on Unix” on page 3-18 or “Editing the IBM TSM Client Options File (dsm. Backup pool entry management_class=<ibm_tsm_manage ment_class_for_SQLBackTrack 3. BMC Software.opt) on Windows” on page 3-25 Table 2-6. Backup pool entry storage-pool=<backup/archive> Where to Go From Here To create a backup pool or backup destination see “Defining a Backup Pool” on page 4-17 or “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27. Environment variable DT_ADSM_MGMTCLASS 2.Table 4-1 Overriding IBM TSM Options (Part 4 of 4) IBM TSM Option IBM TSM management class for SQL-BackTrack Override Hierarchy 1.. Environment variable DT_ADSM_STORAGEPOOL=<BACKUP or ARCHIVE> 2. or backup catalog directory. Confidential and Proprietary Information 4-16 SQL-BackTrack Module for IBM TSM Installation and User Guide . start the backup pool definition process. backup profile. Using SQL-BackTrack. Backups are directed to IBM TSM by a SQL-BackTrack backup pool that resides in the SQL-BackTrack directory that contains other backup configuration information. Inc.Defining a Backup Pool for the SQL-BackTrack Module Note If you are using SQL-BackTrack for Microsoft SQL Server. A backup pool stores information about a backup device and any options associated with that device. You can do this as a separate operation (depending on your SQL-BackTrack version) or as part of creating a configuration directory. refer to “Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server” on page 4-27. This chapter explains how to define the backup pool options for the SQL-BackTrack Module for IBM TSM.. BMC Software. control directory. Refer to your SQL-BackTrack documentation for more details. and Informix. DSMI_DIR. When you are prompted to enter a backup pool. (It might look different than the one shown in this procedure. and DSMI_LOG before defining a backup pool. initiate the process of creating a backup pool. Sybase. To Define a Backup Pool Step 1 Using SQL-BackTrack. the driver specific information includes BMC Software. Inc. If you are using SQL-BackTrack for Oracle with OPS/RAC. as in the following example: Enter backup pool name (return='default')? TSM.) DEFINE BACKUP POOL INFORMATION The backup pool definition contains the name of the OBSI driver (typically. See “Running the adsmpw Utility” on page 3-30.pool1 The Define Backup Pool Information prompt is displayed. Make sure you have set DTBASE. the adsmpw utility must have been run to seed the password on the IBM TSM client. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-17 . provide a name for the backup pool. DSMI_CONFIG. DB2/UDB. For disk. depending on your SQL-BackTrack product. See your SQL-BackTrack user documentation for more information. "tape" or "disk") and other driver specific information. use the procedure documented in “Defining a Backup Pool (Oracle Parallel Server Users)” on page 4-23.Defining a Backup Pool Summary: Use this procedure to define a backup pool for the SQL-BackTrack products for Oracle. Before You Begin If the PASSWORDAccess option is set to generate. Be familiar with the procedure for creating a backup pool.. Backup pool name is 'TSM. For tape. tape Enter the OBSI backup device type? Step 2 Enter adsm for the SQL-BackTrack Module backup device type to specify that this backup pool will direct backups to IBM TSM. or press Enter to accept the default value.sys file (Unix) or dsm. No backup pool information has been defined. adsm. Confidential and Proprietary Information 4-18 SQL-BackTrack Module for IBM TSM Installation and User Guide . either the SQL-BackTrack Module for IBM TSM versionless symbolic links are not created properly or the SQL-BackTrack Module for IBM TSM is not properly installed.. Inc.the name of the file system directory where new backup data files are created. See the installation information in this book. Enter TSM Server Name (return = none) BMC Software. answer n to the following prompt: Run SQL-BackTrack Module on node other than local node? (y/n) [n] n Step 4 Enter a value for the IBM TSM server name if you want to override the IBM TSM server name specified in the dsm. the driver specific information includes the device name for the tape drive and tape label information. Step 3 If you are using SQL-BackTrack for Oracle and are not running an Oracle Parallel Server/Real Application Cluster (OPS/RAC) database. SQL-BackTrack prompts you for IBM TSM backup pool options.pool1' Available OBSI backup devices: disk. Note If adsm is not on the list of available SQL-BackTrack Module backup devices.opt file (Windows). as follows: • If the IBM TSM passwordaccess option is generate. the nodename parameter in dsm.opt file (Windows) is recommended to facilitate the alternate host recovery and failover scenario. If the mode prompt. If the IBM TSM node passwordaccess option is prompt.sys file (Unix) or dsm. Step 6 Enter a value for the IBM TSM session node name.opt file (Windows) and respond accordingly: • • If the mode is generate. If the IBM TSM PASSWORDAccess option is prompt and the IBM TSM administrator has registered the node name under the Unix hostname or the Windows computer name. If PASSWORDAccess is set to generate. you will not be prompted for a password.sys file (Unix) or dsm. BMC Software. enter the node password. a non-NULL node name is recommended. Inc.. see “Password Authentication” on page 3-7. Step 7 Enter a value for the IBM TSM node password. • For more information on IBM TSM client passwordaccess.Step 5 Determine the setting for the PASSWORDAccess mode by consulting the IBM TSM administrator or by examining the entry in the dsm. press Enter and proceed to Step 11. as appropriate: • If the IBM TSM PASSWORDAccess option is prompt (the default) and the IBM TSM administrator has registered the node name under a name other than the hostname on Unix or the computer name on Windows. press Enter. enter the node name. enter n and proceed to Step 6. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-19 . Note • If PASSWORDAccess option is prompt. Step 8 If you entered a node password in Step 6. or press Enter to use the default management class configured on the IBM TSM server. Enter TSM filespace name (return = /BACKTRACK)? BMC Software. Use stored TSM password for recover operations (y/n)? [n] Step 10 To be prompted for the node password during recovery. enter y. If you do not want to be prompted for the client password during recovery. Specify whether or not SQL-BackTrack should wait for IBM TSM media mounts: Wait for media mounts (y/n)? [y] Note Step 11 Yes (y) is the recommended option. Confidential and Proprietary Information 4-20 SQL-BackTrack Module for IBM TSM Installation and User Guide . If you enter n. press Enter for the default n. Step 12 Enter an IBM TSM management class to override the default. This specifies that SQL-BackTrack will wait for offline IBM TSM media to be mounted during backup and recovery operations. Inc.. enter n. Enter TSM management class override (return = none)? Step 13 Enter the filespace tag prefix. as appropriate. SQL-BackTrack operations terminate if IBM TSM media is not mounted. enter y. If you want to be prompted for the node password during backups and expiration. the following prompts are displayed: Use stored TSM password for backup operations (y/n)? [y] Step 9 To perform unattended backups. Step 14 Enter the IBM TSM storage pool type. default values are shown in the following examples: Unix begin backup_pool=default obsi=adsm server=SQLBT mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup end backup_pool Is this correct (Y/N)? Windows begin backup_pool=default obsi=adsm server=jupiter. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-21 . Select TSM storage pool [BACKUP|ARCHIVE]? (return = BACKUP) SQL-BackTrack displays the backup pool options you selected and gives you the option to accept them. (backup or archive) depending on which copy group you want to use. Inc..com mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup end backup_pool Is this correct (Y/N)? BMC Software.bmc. You can specify different values for the server option when you create multiple pools or poolgroups. Confidential and Proprietary Information 4-22 SQL-BackTrack Module for IBM TSM Installation and User Guide . on page 4-12 for more information. Inc. as follows: • • y to accept the options displayed. To use multiple IBM TSM servers. See Table 4-1. If you want to override the settings that are stored in the backup pool. you may be able to use a Module environment variable. you might want to use multiple IBM TSM servers for cloning backups. See the SQL-BackTrack user documentation for more information. you must either use multiple backup pools or pool groups.Step 15 Enter the appropriate response to confirm. BMC Software. or edit the output.. See also “Improving Your Backup Performance” on page 4-31. n to reenter the backup pool options. Is this correct (Y/N)? y Where to Go From Here You can repeat this procedure to create additional backup pools for striped backups. Refer to “Using Multiple IBM TSM Servers” on page 4-32 for more information. In addition. change. adsm.Defining a Backup Pool (Oracle Parallel Server Users) Summary: Use this procedure to create a backup pool if you are using SQL-BackTrack for Oracle with Oracle Parallel Server. Before You Begin Make sure you have set DTBASE. poolgroup Enter the OBSI backup device type: poolgroup Define first pool in this poolgroup by selecting an existing pool or creating a new one. (Your prompts might be different than the ones shown in this procedure. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-23 . TSM. initiate the process to create a pool group: Enter backup pool or poolgroup name: mypoolgroup Available OBSI backup devices: disk. See “Setting Unix Environment Variables During Post-Installation” on page 2-16 for more information. DSMI_DIR. For example. To Define a Backup Pool (OPS Users) Step 1 In SQL-BackTrack for Oracle. Then enter a name for the backup pool.pool1. Inc.pool1 The Define Backup Pool Information prompt is displayed. See the SQL-BackTrack for Oracle documentation for more information.) BMC Software. depending on your version of SQL-BackTrack. tape. Enter backup pool name: TSM. and DSMI_LOG before defining a backup pool. indicate that you want to define a new one. DSMI_CONFIG.. Backup pools defined within group: mypoolgroup Step 2 When you are asked to choose a backup pool. Be familiar with the process of creating a backup pool and pool group. poolgroup Enter the OBSI backup device type: adsm Note If adsm is not on the list of available backup devices.Step 3 Enter adsm as the OBSI backup device type to specify that this backup pool will direct backups to IBM TSM. Available OBSI backup devices: disk. answer y to the following prompt. Confidential and Proprietary Information 4-24 SQL-BackTrack Module for IBM TSM Installation and User Guide . either the SQL-BackTrack Module for IBM TSM versionless symbolic links are not created properly or the SQL-BackTrack Module for IBM TSM is not properly installed. SQL-BackTrack prompts you for IBM TSM backup pool options. BMC Software. and other backup pool options as discussed in “Defining a Backup Pool” on page 4-17. tape. Inc. Run OBSI on node other than local node? (y/n) [n] y Enter node on which to run OBSI (hit return to run dynamically with dump): Step 5 Enter an IBM TSM node name.. adsm. Then enter the cluster node name when prompted. or press Enter to run the SQL-BackTrack Module for IBM TSM on the same node where the SQL-BackTrack dump process is running. Step 4 Since you are going to be using the SQL-BackTrack Module for IBM TSM with a SQL-BackTrack for OPS database. password. The value used in the nodename parameter on each OPS node must be the same. The node name used in the dsm.. Is this info correct? (y/n) y BMC Software.sys file for each OPS node must be the same in each corresponding server stanza. Inc. Enter n to reenter the backup pool options.If IBM TSM PASSWORDAccess option is set to prompt in the dsm. the nodename parameter in dsm.sys will be used. If PASSWORDAccess is set to generate in dsm. the nodename parameter in the dsm. a non-NULL node name is recommended. Warning If the PASSWORDAccess mode is set to prompt and the node name is not provided in the backup pool. After you enter values for all prompts. you might not be able to recover your data automatically. as follows: • • Enter y to accept what you entered.sys file must be set. If you do not follow these guidelines.sys. begin backup_pool=default obsi=adsm server=SQLBT mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup end backup_pool Is this info correct? (y/n) Step 6 Enter the appropriate response to accept or reenter the output. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-25 .sys file. SQL-BackTrack displays the backup pool options that you selected and gives you the option to accept them. pool1 Enter backup pool name: TSM. Step 7 If you want to add one or more pools to the existing poolgroup. Inc. Confidential and Proprietary Information 4-26 SQL-BackTrack Module for IBM TSM Installation and User Guide ..pool2 Step 8 Repeat the procedure starting with Step 3 on page 4-24. BMC Software.SQL-BackTrack returns the following message: The poolfile has been updated to reflect your changes. answer y to the next question: Would you like to define another pool in this poolgroup:(Y/N) [y] y Backup pools defined within group: mypoolgroup TSM. Click New on the Backup Destination Settings dialog box.Defining IBM TSM as a Backup Destination for SQL-BackTrack for Microsoft SQL Server Summary: If you use SQL-BackTrack for Microsoft SQL Server. Select IBM TSM on the New Backup Destination dialog. Note Step 2 Step 3 If IBM TSM is not available for selection. To Define IBM TSM as a Backup Destination Step 1 From the SQL-BackTrack for Microsoft SQL Server console. as shown on the next page. See “Adding the SQL-BackTrack Module to SQL-BackTrack on Windows” on page 4-7. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-27 . choose Administration => Modify Settings => Backup Destinations. See the installation information in this book. Before You Begin Make sure that you have added the SQL-BackTrack Module for IBM TSM to SQL-BackTrack for Microsoft SQL Server. either the SQL-BackTrack Module for IBM TSM has not been properly added to SQL-BackTrack or the SQL-BackTrack Module for IBM TSM is not properly installed. The dialog box expands to allow you to enter definitions.. Inc. use this procedure to define IBM TSM as a backup destination. BMC Software. create an include-exclude file that associates the SQL-BackTrack Module for IBM TSM filespace tag prefixes with the appropriate management classes. If you want to override the default management class.Step 4 In the Name box. Inc. for example. no entry needs to be made in the management class field. Note Step 6 Step 7 • If you create a special management class for SQL-BackTrack backups. a backslash (\). BMC Software. IBM_TSM1. Confidential and Proprietary Information 4-28 SQL-BackTrack Module for IBM TSM Installation and User Guide . or a colon (:) in the name. Note Do not include a blank. Specify the management class: • If you want to use the default management class. enter the name in the management class field.. Step 5 Accept /BACKTRACK as the default filespace tag prefix or type a name of your choice. enter a name for the IBM TSM destination. Select Backup or Archive for the storage pool that you want to use. Note If PASSWORDAccess is set to generate in the dsm. Note If you store the node name and password. BMC Software. you will not be prompted for the IBM TSM node name password during the backup or recovery. Step 10 In the Store Password box. complete Step 9 and Step 10.. Inc. locate the . Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-29 . select Yes and enter the node name that you plan to use with SQL-BackTrack. you can store the node name and password.Step 8 Specify whether you want to wait for the IBM TSM media to be mounted.opt file. a non-NULL node name is recommended. If this is the case. Step 9 In the Include IBM TSM Node Name box. Step 12 To override the IBM TSM server. proceed to Step 11 on page 4-29.dtoptions file in <SQL-BackTrack_installation_directory>\mbacktrack\catalog. Step 11 Click OK. The Backup Destinations dialog box is displayed and the IBM TSM destination is included in the backup destinations list. SQL-BackTrack terminates the operation. In this case. If PASSWORDAccess is set to prompt. If you select No and the IBM TSM media are unavailable when an operation starts. If these options are not available. the fields for the IBM TSM node name and password are not available. Note BMC Software recommends that you store a node name and password in the backup destination when the PASSWORDAccess option is prompt. specify whether you want to store the password for the IBM TSM node name entered in Step 9 for backups or recoveries and enter the password that you would like to store. Once you have completed creating the backup destinations.bmc. Inc. Confidential and Proprietary Information 4-30 SQL-BackTrack Module for IBM TSM Installation and User Guide . See Table 4-1. See “Backing Up Data” on page 5-1.Step 13 Add the following line to the IBM TSM backup destination definition using a text editor: server=<IBM_TSM_servername> An example of an updated IBM TSM destination definition follows: begin backup_pool=IBMTSM01 obsi=adsm server=jupiter. If you want to override the settings that are stored in the backup pool.com mount-wait=y filespace=/BackTrack management_class=BTMGMT storage-pool=backup end backup_pool Where to Go from Here Proceed to any of the following: • You can create additional backup destination definitions if you want to stripe backups across multiple IBM TSM destinations. See also “Improving Your Backup Performance” on page 4-31. you may be able to use a Module environment variable. on page 4-12 for more information. you can begin backing up data to IBM TSM. See the SQL-BackTrack for Microsoft SQL Server user documentation for more information. • • BMC Software.. SQL-BackTrack asks you if you want to use pool groups (Oracle). If you are creating a physical backup profile (Oracle). Currently. Inc. Warning If you are using pool groups. dump striping (Sybase). each backup pool should direct the backup to a different storage device on IBM TSM. Using Memory Mapped I/O for SQL-BackTrack for Oracle The SQL-BackTrack Module for IBM TSM supports the memory mapped I/O for IPC (Inter-Process Communication) mode for data transfer between SQL-BackTrack and the SQL-BackTrack Module. or a backup catalog (DB2 Universal Database and Microsoft SQL Server). This IPC mode is supported only when the SQL-BackTrack Module for IBM TSM and SQL-BackTrack processes are running on the same system. you might not be able to recover your database.. which can improve performance. a control directory for physical backups (Sybase). or stripes (DB2 UDB). you can specify multiple backup destinations for your backup. add the following entry in every backup pool: ipc=mmap BMC Software. See your SQL-BackTrack documentation for more information. To use the memory mapped I/O mode. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-31 .Improving Your Backup Performance You can improve backup performance by writing to multiple backup streams simultaneously. Otherwise. only SQL-BackTrack for Oracle supports the memory mapped I/O mode. If you are backing up a SQL Server instance. or striping. dump striping. and expire to and from multiple IBM TSM servers from a single client host. This feature is especially convenient for cloned backups. Confidential and Proprietary Information 4-32 SQL-BackTrack Module for IBM TSM Installation and User Guide . Inc.For example. Unix Here is a sample POOLS file with multiple pools (pool1 and pool2). To enable this feature. Note BMC Software does not recommend that you stripe your backups to two different IBM TSM servers.sys file. specify a different server name for each backup pool while you are creating new backup pools. The server names provided below match the server names used in two different server stanzas in the dsm. refer to the SQL-BackTrack user documentation. See the examples below for more information. BMC Software. For details on how to clone your database.pool1 obsi=adsm server=SQLBT mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup ipc=mmap end backup_pool Using Multiple IBM TSM Servers SQL-BackTrack Module for IBM TSM enables you to back up. after you add the entry your backup pool might look like this: begin backup_pool=TSM. recover. In the following example. note that the server entry is different for each pool.. You must use multiple pools or pool groups to use multiple IBM TSM servers. In the following example.bmc.bmc. note that the server entry is different for each pool.. Confidential and Proprietary Information Configuring SQL-BackTrack for Use with IBM TSM 4-33 . The server names provided below are two IBM TSM servers that are available for use.com mount-wait=y filespace=/BACKTRACK management_class=BTMGMT BMC Software. begin backup_pool=pool1 obsi=adsm server=jupiter.begin backup_pool=pool1 obsi=adsm server=SQLBT1 mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup end backup_pool begin backup_pool=pool2 obsi=adsm server=SQLBT2 mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup end backup_pool Windows Here is a sample POOLS file with multiple pools (pool1 and pool2).com mount-wait=y filespace=/BACKTRACK management_class=BTMGMT storage-pool=backup end backup_pool begin backup_pool=pool2 obsi=adsm server=grandbay. Inc. storage-pool=backup end backup_pool BMC Software. Inc.. Confidential and Proprietary Information 4-34 SQL-BackTrack Module for IBM TSM Installation and User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 Improved Expiration (Expiration Retry Feature). . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Manually Deleting SQL-BackTrack Objects. . . . . . . . . . . . . . . . . . . . . 5-14 Troubleshooting Object Expiration . . . 5-9 Using the Windows Scheduler . . . . . . . . . . . . . . . . . . . 5-7 Setting Schedule Parameters . . . . . . 5-5 Scheduling Unattended Backups . . . . . . 5-5 Adding Environment Variables to Backup Scripts . . . . . . . . . . . . . Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 BMC Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 The adsm_del Utility . . . . . . . . . . . . . . . 5-10 Monitoring Backups . . . . . . . . . . . . . . . . .5 Backing Up Data This chapter discusses the following topics: 5 Overview . . . . . . . . . 5-2 Prerequisites for On-Demand and Unattended Backups . . . . . . . . . 5-7 Starting the Client Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Monitoring Backups Using IBM TSM Programs . . . . . 5-11 Expiring Backups . . . . . 5-9 Using cron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Using IBM TSM Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Running On-Demand Backups with SQL-BackTrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confidential and Proprietary Information Backing Up Data 5-1 . . . . . . 5-10 Monitoring Backups Using SQL-BackTrack Utilities. . . . . . . . . . . . . . . . . . . . . Do not attempt to use SQL-BackTrack to recover a backup defined and created by any other database backup utility. Schedule unattended backups with the IBM TSM Scheduler. Confidential and Proprietary Information 5-2 SQL-BackTrack Module for IBM TSM Installation and User Guide . but this chapter provides information on additional backup tasks you might want to perform. Inc. BMC Software. Create the backup script following the instructions in your SQL-BackTrack user documentation. The figure provides the minimum steps required to back up data.. Schedule backups with a scheduling utility. then go to “Scheduling Unattended Backups” on page 5-6.Overview There are three methods of performing backups to IBM TSM: • Run on-demand backups with the SQL-BackTrack programs. See your SQL-BackTrack user documentation for instructions on how to do this. such as the Unix cron utility or the Windows scheduler. Note • • SQL-BackTrack can recover using backups or backup scripts generated by SQL-BackTrack only (though the backup script may have been executed using IBM TSM scheduler or any scheduling utility). Figure 5-1 provides a map of tasks required to back up data using SQL-BackTrack and IBM TSM. Inc. SQL-BackTrack user documentation. Run the backup 2 Do you want to run the backup right away? no yes Submit the backup using SQL-BackTrack. SQL-BackTrack user documentation. Confidential and Proprietary Information Backing Up Data 5-3 .Figure 5-1 Task Map for Backing Up Data Backup definition begins Create the backup 1 Define the backup using SQL-BackTrack. 3 “Monitoring Backups” on page 5-10 Backup ends BMC Software. “Adding Environment Variables to Backup Scripts” on page 5-5 no Schedule the backup to run using a scheduling utility. Do you want to run the backup unattended? yes Generate a backup script using SQL-BackTrack. “Scheduling Unattended Backups” on page 5-6 or the SQL-BackTrack user documentation Monitor the backup Monitor the backup.. SQL-BackTrack user documentation. Add the IBM TSM Module environment variables to the backup script. Inc. backup profile. or backup catalog directory (covered in your SQL-BackTrack user guide) created a backup pool (covered in “To Define a Backup Pool” on page 4-17) Before you can perform unattended backups..Prerequisites for On-Demand and Unattended Backups Before you can perform both on-demand and unattended backups. you must set the following environment variables and add them to your backup script: Windows: • • • • • PATH DTBASE DSMI_DIR DSMI_CONFIG DSMI_LOG • • On Unix: • • • • DTBASE DSMI_DIR DSMI_CONFIG DSMI_LOG Warning If these variables are not set at the time that the backup runs. you must have completed the following: • created a configuration directory. control directory. the backup will fail. BMC Software. Confidential and Proprietary Information 5-4 SQL-BackTrack Module for IBM TSM Installation and User Guide . However.opt 3. export DSMI_DIR DSMI_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm. On Windows. The following Unix example shows three variables added: DSMI_DIR=/opt/tivoli/tsm/client/api/bin.00/log. you may not need to add them to the backup script. if you want to override the values that are set in the environment.1. If you generate a backup script. export DSMI_CONFIG DSMI_LOG=/usr/datatools/obsi.Running On-Demand Backups with SQL-BackTrack To run on-demand backups with the SQL-BackTrack programs. if these variables are set at the time that the backup is to be run. refer to the SQL-BackTrack documentation.1.00. Inc.adsm-3.. you can add the variables to the backup script with the new values. you need to add environment variables specific to IBM TSM before this backup script can be used. export DSMI_LOG BMC Software. make sure to add the environment variables discussed in “Adding Environment Variables to Backup Scripts.” Adding Environment Variables to Backup Scripts If you have used SQL-BackTrack to generate a backup script for on-demand or unattended backups. Confidential and Proprietary Information Backing Up Data 5-5 . #!/bin/sh # SQL-BackTrack Module for IBM Tivoli Storage Manager environment variables DSMI_DIR=/opt/tivoli/tsm/client/api/bin.0. export DTBASE DT_OBACKTRACK_HOME=/usr/datatools/obacktrack-4.0.00/log.adsm-3.00/dsm/dsm. export DTTEMPDIR # SQL-BackTrack product-specific backup command status=/usr/datatools/obacktrack-4. export DSMI_DIR DSMI_CONFIG=/usr/datatools/obsi.. export DSMI_CONFIG DSMI_LOG=/usr/datatools/obsi. Inc. export DSMI_LOG # SQL-BackTrack product-specific environment variables DTBASE=/usr/datatools. If you add # anything to the script after the backup command you should be # sure to exit with the current status. exit $status Scheduling Unattended Backups Note Even if you have done a backup through a scheduler.The following is an example of a backup script from SQL-BackTrack for Oracle that has been modified with additional environment variables. Confidential and Proprietary Information 5-6 SQL-BackTrack Module for IBM TSM Installation and User Guide . \ export DT_OBACKTRACK_HOME DTTEMPDIR=/dttmp.1. the recovery must be initiated by the SQ-BackTrack interface.0/bin/dtobackup\ /usr/datatools/oracle/SONOMA -cold -full -quiet -noprompt # Be sure to exit the script with exit status.1. BMC Software.opt.0.adsm-3. Contact IBM TSM support if you need help running file system backups with the scheduler. BMC Software. the IBM TSM administrator must set the OBJECTS parameter in the DEFINE SCHEDULE command to the appropriate SQL-BackTrack backup command. Refer to your SQL-BackTrack user guide for instructions on creating a backup script. Confidential and Proprietary Information Backing Up Data 5-7 . Refer to “Adding Environment Variables to Backup Scripts” on page 5-5. Do not attempt to run SQL-BackTrack backups with the scheduler until you have successfully run file system backups with the scheduler. Inc. To schedule unattended SQL-BackTrack backups.. Setting Schedule Parameters The IBM TSM administrator can use the DEFINE SCHEDULE (or UPDATE SCHEDULE) and DEFINE ASSOCIATION commands to schedule SQL-Backtrack backups through IBM TSM. and the ACTION parameter must be set to COMMAND. Set other IBM TSM schedule parameters as desired. SQL-BackTrack backup commands are described in the next two sections. and that it directs the backup to the SQL-BackTrack Module for IBM TSM. Added the environment variables specific to SQL-BackTrack Module for IBM TSM to the backup script. • Using IBM TSM Scheduler Requirements If you are not already using the IBM TSM Scheduler for file system backups.These instructions assume that you have: • Created a backup script for the database or databases you want to back up. schedule a test file system backup to verify that the IBM TSM Scheduler is working correctly. but SQL-BackTrack for Oracle must be run as user oracle. the fully qualified file name is /usr/datatools/script/my_backup_script. Confidential and Proprietary Information 5-8 SQL-BackTrack Module for IBM TSM Installation and User Guide . /usr/datatools/script/orafull is the fully qualified file name of the backup script that was generated by SQL-BackTrack: DEFINE SCHEDULE STANDARD ORAFULL \ DESCRIPTION=”Submit SQL-BackTrack backup from TSM server” \ ACTION=COMMAND \ OBJECTS=”/usr/datatools/obsi. Because it will contain a space.You must use the DEFINE ASSOCIATION command to associate a schedule with the client node that runs your database. The script must be owned by oracle. SQL-BackTrack for Oracle The IBM TSM Scheduler can only run jobs as root. which will run a backup script as the owner of the script.. set the DEFINE SCHEDULE OBJECTS parameter to the fully qualified file name of the backup script that was generated by SQL-BackTrack. followed by a space and the full path name of the script. the OBJECTS= parameter must be enclosed in quotes and must be entered on a single line. In the following example.00/bin/unroot /usr/datatools/script/orafull” \ STARTTIME=22:00:00 Other SQL-BackTrack Products For all other SQL-BackTrack products. In the following Unix example using a 32-bit version of the SQL-BackTrack Module.adsm-3. BMC Software.1. Inc. the SQL-BackTrack Module for IBM TSM includes the unroot program. do the following: % chown oracle <name_of_backup_script> The OBJECTS= parameter of the DEFINE SCHEDULE command should contain the full path name of the unroot program. The DEFINE SCHEDULE and DEFINE ASSOCIATION commands are described in the IBM TSM Administrator’s Reference manual. To change the ownership of the backup script to user oracle. Therefore. and that the script directs the backup to the SQL-BackTrack Module for IBM TSM. • Use the Unix cron utility to schedule the backup. BMC Software. see your Unix documentation and man pages. For more information about the cron syntax.DEFINE SCHEDULE STANDARD FULL \ DESCRIPTION=”Submit SQL-BackTrack backup from TSM server” \ ACTION=COMMAND \ OBJECTS=”/usr/datatools/script/my_backup_script” \ STARTTIME=22:00:00 Starting the Client Scheduler After the IBM TSM administrator has created a schedule and associated it with the SQL-BackTrack host. Refer to “Adding Environment Variables to Backup Scripts” on page 5-5. use the dsmc SCHEDULE command to start the IBM TSM client scheduler on the SQL-BackTrack host. Inc. The IBM TSM client scheduler must be running before work scheduled by the IBM TSM administrator can be initiated.. Refer to your SQL-BackTrack user guide for instructions on creating a backup script. Using cron These instructions assume that you have: • Created a backup script for the database or databases you want to back up. Confidential and Proprietary Information Backing Up Data 5-9 . See the IBM TSM documentation for more information. Added the environment variables specific to the SQL-BackTrack Module for IBM TSM to the backup script. as described in the following sections. this utility is accessible through My Computer. Use the Windows Scheduled Tasks utility to schedule automatic backups during low usage times. the recovery must be initiated by the SQL-BackTrack interface. Monitoring Backups You can monitor backups in two ways.. this utility is accessible through Start => Programs => System Tools => Scheduled Tasks. For Windows 2000.Using the Windows Scheduler Note Even if you have done a backup through a scheduler. BMC Software. Confidential and Proprietary Information 5-10 SQL-BackTrack Module for IBM TSM Installation and User Guide . Monitoring Backups Using SQL-BackTrack Utilities Use one of the following SQL-BackTrack utilities: • • • dtwatch (Unix) dtwwatch (Windows) Watch utility (SQL-BackTrack for Microsoft SQL Server) Refer to your SQL-BackTrack documentation for more information on these utilities. Inc. For Windows NT. Generate a backup script using SQL-BackTrack that directs the backup to the IBM TSM destination. See the SQL-BackTrack documentation for more information. Note Ensure that the appropriate user account is included in the task that is set up. Confidential and Proprietary Information Backing Up Data 5-11 . enter: dsmc> query backup “/BACKTRACK:oracatalog/*/*” • To query all backup files in the archive copy group under filespace name /BACKTRACK:oracatalog from the command line. The examples below show /BACKTRACK as the filespace prefix used in the backup pool or backup destination. Use the following commands as an example. enter q filespace at the dsmc prompt: dsmc> query filespace • To query all backup files in the backup copy group under filespace name /BACKTRACK:oracatalog from the command line. Refer to the IBM TSM user documentation for more information on the IBM TSM commands. Unix • To see all files on a filespace. Inc. enter: dsmc> query archive “/BACKTRACK:oracatalog/*/*” • To query all backup files in the backup copy group under filespace name /BACKTRACK:oracatalog and for the node BT_NODE from the command line. start the IBM TSM client prompt by entering: % dsmc • After you see copyright and version information for IBM TSM.. enter: BMC Software. and C:/BACKTRACK:oracatalog is example filespace name created for Windows by SQL-BackTrack Module for IBM TSM. Filespace /BACKTRACK:oracatalog is an example filespace name created for UNIX.Monitoring Backups Using IBM TSM Programs You can use IBM TSM commands to view your database backups. enter: dsmc> query backup -fromnode=BT_NODE "{C:/BACKTRACK:oracatalog}\*\*" • To query backup files from a specified IBM TSM server.. Confidential and Proprietary Information 5-12 SQL-BackTrack Module for IBM TSM Installation and User Guide .dsmc> query backup -fromnode=BT_NODE "/BACKTRACK:oracatalog/*/*" • To query backup files from a specified IBM TSM server. enter: %dsmc -servername <servername> For example: %dsmc -servername sqlbt Windows • To query all backup files in the backup copy group under filespace name C:/BACKTRACK:oracatalog from the command line. Inc. enter: dsmc> -servername <servername> For example: dsmc> -servername sqlbt BMC Software. from the command line. enter: dsmc> query backup “{C:/BACKTRACK:oracatalog}\*\*” • To query all backup files in the archive copy group under filespace name C:/BACKTRACK:oracatalog from the command line. enter: dsmc> query archive “{C:/BACKTRACK:oracatalog}\*\*” • To query all backup files in the backup copy group under filespace name C:/BACKTRACK:oracatalog and for the node BT_NODE. Otherwise. SQL-BackTrack expects all objects that it has stored on the IBM TSM server to remain there until it deletes them. Always use the same user ID to do your backups. Confidential and Proprietary Information Backing Up Data 5-13 . the next EXPIRE INVENTORY process will remove the object from the server. you should set ARCHDEL to YES.” For expiration to work properly. so if it were in control of expiration.Expiring Backups Expiration of database backups should be controlled by SQL-BackTrack. VEREXISTS. SQL-BackTrack might get errors on recovery if objects are unexpectedly deleted. called RETVER (Retain Version). The response from IBM TSM to this delete request depends on whether the object is in a backup or archive copy group. It specifies the number of days to keep an archive copy. it sends a request to IBM TSM to delete the object. After the number of days specified in the RETONLY parameter. If the object is in a backup copy group: IBM TSM responds to the delete request by marking the object “inactive”. VERDELETED and RETEXTRA parameters of a backup copy group do not affect expiration processing of SQL-BackTrack objects. Furthermore. Inc. If the object is in an archive copy group: An archive copy group has only one parameter to set. BMC Software recommends that you set RETVER to “unlimited. IBM TSM does not know which objects correspond to which database components. See “Storage Pools” on page 3-12 for more information on the settings that you should use for expiring SQL-BackTrack backups. BMC Software. When the SQL-BackTrack Module for IBM TSM expires backups. your database objects might not be expired from IBM TSM (as you do not have permission) but will be deleted from the SQL-BackTrack backup history. it could inadvertently expire the latest copy of a backup and render the database unrecoverable.. The FREQUENCY. (At this time.Improved Expiration (Expiration Retry Feature) The SQL-BackTrack Module for IBM TSM has improved expiration. IBM TSM object names take the form: ADSM:<poolname>/<filespace>/<highlevel>/<lowlevel> where <filespace> = filespace name <highlevel> = high level name <lowlevel> = low level name The adsm:<poolname> part is added by SQL-BackTrack. If. SQL-BackTrack can then choose to expire this object at a later point in time. review the SQL-BackTrack backup history before a backup and find the oldest generation of a backup. Confidential and Proprietary Information 5-14 SQL-BackTrack Module for IBM TSM Installation and User Guide . for any reason. • For backup copy group: dsmc> query backup /<filespace>/<highlevel>/<lowlevel> -inactive BMC Software.) Troubleshooting Object Expiration To verify that objects are being deleted properly. You can log in as the user who backed up the database or as root.. This feature will be enabled only if the SQL-BackTrack version you are using supports SQL-BackTrack Module Protocol 6. the SQL-BackTrack Module for IBM TSM reports the failure to SQL-BackTrack. expiration of any object fails. only SQL-BackTrack for Oracle supports this protocol. The name on the IBM TSM server is: /<filespace>/<highlevel>/<lowlevel> Step 1 Enter the following command in the dsmc program. Inc.0 or above. dsmc> query archive /BACKTRACK:oracatalog/*/* The above examples show /BACKTRACK as the filespace name used in the backup. enter the following command: For Unix dsmc> query backup /<filespace>/<highlevel>/<lowlevel> -inactive for example. dsmc> query backup /BACKTRACK:oracatalog/*/* -inactive or dsmc> query archive /<filespace>/<highlevel>/<lowlevel> for example. dsmc> query backup {C:/BACKTRACK:oracatalog}\*\* -inactive or dsmc> query archive /<filespace>\<highlevel>\<lowlevel> BMC Software. Confidential and Proprietary Information Backing Up Data 5-15 . Step 2 After SQL-BackTrack completes the backup expiration. <highlevel>.. For Windows dsmc> query backup /<filespace>\<highlevel>\<lowlevel> -inactive for example. Inc.• For archive copy group: dsmc> query archive /<filespace>/<highlevel>/<lowlevel> The values for <filespace>. and <lowlevel> are taken from the backup history. Inc.adsm-3.1. When processing completes.adsm-3. or if you have other questions about how to run EXPIRE INVENTORY. the inactive object should be gone (assuming RETONLY=0).adsm-3. check to see whether the item has been removed from the SQL-BackTrack backup history. you can: • Delete the entire filespace Warning Make sure that SQL-BackTrack no longer references this backup in the backup history. expiration is working properly. which is in $DTBASE/obsi..00/bin or $DTBASE/obsi.00\bin directory on Windows. Step 3 See if the object has had its status changed to “I”. Make a text file with all of the SQL-BackTrack objects that you want to delete from the IBM TSM server. If an inactive object is not deleted by EXPIRE INVENTORY. and then run the program using that file as input. The IBM TSM administrator can run EXPIRE INVENTORY after the item becomes inactive. See the following section for more information on this utility. and that no critical data is on the filespace! • Use the adsm_del utility.00-64bit/bin on Unix and the %DTBASE%\ obsi. If it has.1. BMC Software. Confidential and Proprietary Information 5-16 SQL-BackTrack Module for IBM TSM Installation and User Guide . and C:/BACKTRACK:oracatalog is the example filespace name created on Windows by SQL-BackTrack Module for IBM TSM. refer to the IBM TSM Administrator’s Reference manual.for example. If it has not. Manually Deleting SQL-BackTrack Objects If SQL-BackTrack objects need to be manually deleted. Filespace /BACKTRACK:oracatalog is the example filespace name created on UNIX. dsmc> query archive {C:/BACKTRACK:oracatalog}\*\* The above examples show /BACKTRACK as the filespace tag prefix used in the backup pool.1. where there is one entry for each • • file to be deleted in the following format: /<filespace> /<highlevel> /<lowlevel> • <node_password> .Specifies the type of files in the • <filename>.The adsm_del Utility If SQL-BackTrack Module for IBM TSM objects are not getting expired but are being left on the IBM TSM tape or IBM TSM disk storage pool. To use this utility.Name of the node. This utility submits a request to the IBM TSM server to remove the files that you indicate without updating the SQL-BackTrack catalog. (This is not required if PASSWORDAccess is set to generate. if not specified. default node name is used..Name of the server that manages the files you want to delete. Confidential and Proprietary Information Backing Up Data 5-17 . The value can be backup or archive (the default is backup). Inc.Name of input file. nor any environment variables. <nodename> . This utility is not affected by any options set in the backup pool. (This is not required if PASSWORDAccess is set to generate.Password to be used for the node name. perform the following: BMC Software. The format of the utility is as follows: adsm_del -s <servername> -n <nodename> -f <filename> -p <node_password> -t <storage_pool_type> • <servername> .) <filename> . use the adsm_del utility to expire the objects.) <storage_pool_type> . Unix • If the backup file that you want to delete has the following value in the SQL-BackTrack backup history: file=adsm:tsmpool/backup_pool/BACKTRACK:oracat alog/ORA817DB/datafile_1-07-10-2003.1. There should be a blank space before the end-of-line separator between each of these.00:26:09-2 9142<1> The input file would look like the following /BACKTRACK:oracatalog /ORA817DB /datafile_1-07-10-2003. create the input file containing all of the SQL-BackTrack entries you want to mark as expired.. From the IBM TSM Server prompt.02:13:59-6 856<5> Your input file would look like BMC Software. do a “q con” of the volume name where the SQL-BackTrack backups that you want to delete reside. This could be one entry in your input file: /BACKTRACK:oracatalog /DBNAME /tmp-0. It will show: /<filespace>/<highlevel>/<lowlevel> 2.09:46:35-18825<5> The following examples show how to create an input file. and each of these strings should start with “/”. Confidential and Proprietary Information 5-18 SQL-BackTrack Module for IBM TSM Installation and User Guide .00:26:09-29142-0 • If the backup file that you want to delete has the following value in the SQL-BackTrack backup history: file=adsm:tsmpool/backup_pool/BACKTRACK:oracat alog/ORA817DB/datafile_1-07-10-2003.31-03-2002. Using a text editor. Inc. 00:26:09-29142 • If the backup file that you want to delete has the following value in the SQL-BackTrack backup history: BMC Software. use the following examples.02:13:59-6856-2 /BACKTRACK:oracatalog /ORA817DB /datafile_1-07-10-2003. Confidential and Proprietary Information Backing Up Data 5-19 .02:13:59-6856-0 /BACKTRACK:oracatalog /ORA817DB /datafile_1-07-10-2003.02:13:59-6856-1 /BACKTRACK:oracatalog /ORA817DB /datafile_1-07-10-2003./BACKTRACK:oracatalog /ORA817DB /datafile_1-07-10-2003. Inc. • If the backup file that you want to delete has the following value in the SQL-BackTrack backup history: file=adsm:tsmpool/backup_pool/BACKTRACK:oracat alog/ORA817DB/datafile_1-0-07-10-2003.02:13:59-6856-3 /BACKTRACK:oracatalog /ORA817DB /datafile_1-07-10-2003.00:26:09 -29142 Your input file would look like /BACKTRACK:oracatalog /ORA817DB /datafile_1-0-07-10-2003.02:13:59-6856-4 If your backup files were created using previous versions of the SQL-BackTrack Module.. Inc.02:13:59-6856 /BACKTRACK:oracatalog /ORA817DB /datafile_1-1-07-10-2003.12:42:13-4657 BMC Software.00:26:09-2 9142 Your input file would look like /BACKTRACK:oracatalog \ORA817DB \datafile_1-0-10-07-2003.02:13:59-6856+/BACKTRACK:oracat alog/ORA817DB/datafile_1-2-07-10-2003.file=adsm:tsmpool/backup_pool/BACKTRACK:oracat alog/ORA817DB/datafile_1-0-07-10-2003.02:13:59-6856+/BACKTRACK:oracat alog/ORA817DB/datafile_1-4-07-10-2003. Confidential and Proprietary Information 5-20 SQL-BackTrack Module for IBM TSM Installation and User Guide .02:13:59-6856 /BACKTRACK:oracatalog /ORA817DB /datafile_1-2-07-10-2003.02:13:59 -6856+/BACKTRACK:oracatalog/ORA817DB/datafile_ 1-1-07-10-2003.02:13:59-6856 /BACKTRACK:oracatalog /ORA817DB /datafile_1-3-07-10-2003.02:13:59 -6856+/BACKTRACK:oracatalog/ORA817DB/datafile_ 1-3-07-10-2003.02:13:59 -6856 Your input file would look like /BACKTRACK:oracatalog /ORA817DB /datafile_1-0-07-10-2003.02:13:59-6856 Windows • If the backup file that you want to delete has the following value in the SQL-BackTrack backup history: file=adsm:tsmpool\backup_pool/BACKTRACK:oracat alog\ORA817DB\datafile_1-07-10-2003..02:13:59-6856 /BACKTRACK:oracatalog /ORA817DB /datafile_1-4-07-10-2003. . Inc.• If the backup file that you want to delete has the following value in the SQL-BackTrack backup history: file=adsm:tsmpool\backup_pool/BACKTRACK:oracat alog\ORA817DB\datafile_1-07-10-2003.12:42:13-3764-1 /BACKTRACK:oracatalog \ORA817DB \datafile_1-10-07-2003.02:13:59-6 856<3> Your input file would look like /BACKTRACK:oracatalog \ORA817DB \datafile_1-10-07-2003.12:42:13-3764-2 BMC Software.12:42:13-3764-0 /BACKTRACK:oracatalog \ORA817DB \datafile_1-10-07-2003. Confidential and Proprietary Information Backing Up Data 5-21 . Confidential and Proprietary Information 5-22 SQL-BackTrack Module for IBM TSM Installation and User Guide .BMC Software. Inc.. . It covers this topic: 6 Using SQL-BackTrack to Recover. . . . . Inc. . 6-4 BMC Software. . . . . . . . . . . . . . . . . .6 Recovering Data This chapter discusses points to remember when you are using SQL-BackTrack to recover a database. . . . . . . . . . . . . . . . . . . . . . . . . . Confidential and Proprietary Information Recovering Data 6-1 . . . . . . . . . . . . . . . . . . . . . . . . .. 6-2 Alternate Host Recovery . . . . . . . . 6-3 Recovering from an Alternate Host . . . and DSMI_LOG environment variables before you start your recovery. SQL-BackTrack can recover backups that were submitted by SQL-BackTrack or by a scheduler. backup profile. you must recover a backup copy of it before you can recover database data. or backup catalog directory. control directory. Make sure you set your DTBASE. if the scheduler used a backup script generated by SQL-BackTrack. For recovery. Inc. The IBM TSM administrator can configure these setting. If you have lost this information. Note SQL-BackTrack recovery operations might require special COMMTIMEOUT and MOUNTWAIT settings. DSMI_CONFIG. BMC Software. You must use SQL-BackTrack to recover database data. you cannot recover databases directly from IBM TSM. make sure that you log in using the same user ID that was used when the backup was performed. Plan your recovery strategy carefully to prevent mistakes such as overwriting the wrong data. SQL-BackTrack provides you with complete control over the recovery process. Confidential and Proprietary Information 6-2 SQL-BackTrack Module for IBM TSM Installation and User Guide .. the recovery must be initiated by the SQL-BackTrack interface.Using SQL-BackTrack to Recover Note Even if you have done a backup through a scheduler. DSMI_DIR. To recover database data. Warning Database recovery should never be done in haste. you must have a current copy of the configuration directory. Refer to your SQL-BackTrack user guide or online Help for complete instructions on recovery operations. See page 3-11 and page 3-10. Inc. Confidential and Proprietary Information Recovering Data 6-3 .. This section assumes the following: • the backup files are available to the alternate host on the IBM TSM server the alternate host can access the same IBM TSM server to which the original backup was performed the user ID used for the recovery is the same as used for the backup • • BMC Software.Alternate Host Recovery This section contains prerequisites and procedures for using an alternate host to recover data that was backed up from a source host. Inc. Confidential and Proprietary Information 6-4 SQL-BackTrack Module for IBM TSM Installation and User Guide . This procedure assumes that the following values that were used for the backup on the source host and that are used for the recovery on the alternate host are the same: • • • IBM TSM node name IBM TSM server name password access Make sure you have performed the following on the alternate host before you attempt to recover using an alternate host: • • • • • Installed the IBM TSM API client Installed the IBM TSM storage agent. and DSMI_LOG environment variables Run the adsmpw utility to seed the IBM TSM password.Recovering from an Alternate Host Summary: Use this procedure perform a recovery of data backed up using another host. if the PASSWORDAccess option is set to generate Validated the IBM TSM configuration using obsitest Ensure that the SQL-BackTrack Module for IBM TSM has been properly linked or added to SQL-BackTrack • • • BMC Software. DSMI_CONFIG. DSMI_DIR. if appropriate Configured the client to access the IBM TSM server Installed the SQL-BackTrack Module for IBM TSM Set DTBASE. Before You Begin Review the alternate host recovery information in your SQL-BackTrack user documentation before you begin this task.. sys file for the backup on the source host matches the server stanza that exists in the dsm. perform the recovery. Using SQL-BackTrack. ensure that the server stanza used in the dsm. On Unix and Windows. Inc.opt file from the source host to the alternate host. copy the dsm. Step 2 Step 3 BMC Software.sys file on the alternate host.. Confidential and Proprietary Information Recovering Data 6-5 .• Ensure that the catalog directory or control files have been copied to the alternate host To Recover Using an Alternate Host Step 1 On Unix. Confidential and Proprietary Information 6-6 SQL-BackTrack Module for IBM TSM Installation and User Guide .BMC Software.. Inc. . To view the IBM Tivoli Storage Manager messages manual.com/support/public/Prodman/public_manuals/td/TD_PR OD_LIST. API-generated messages appear as ANSxxxx from the client and ANRxxxx from the server. go to http://www.tivoli.A Error Messages A This appendix documents the error messages that you might encounter during the SQL-BackTrack Module for IBM TSM installation and validation processes and suggests probable solutions. BMC Software. Confidential and Proprietary Information Error Messages A-1 .html This path reflects the IBM documentation Web site as of the printing of this guide. Inc. If you receive an error code that is not mentioned in this Error Messages section. you can visit the following IBM TSM Web sites to learn about more IBM TSM error codes. On Unix and Windows Message On dsmInit. Inc. It is possible that you have an owner or permission problem or a version incompatibility problem. Confidential and Proprietary Information A-2 SQL-BackTrack Module for IBM TSM Installation and User Guide . User Response: Check the owner and permissions in dsmtca of the IBM TSM client binary file. Explanation: You receive this message if the passwordaccess option is set to generate in the dsm. The owner should be root. BMC Software. type the following commands: chown root <filename> chmod 4755 <filename> This problem can also arise if the version of the dsmtca file is out of sync with /usr/lib/libApiDS. Unable to validate password.opt file (in Windows) and you have typed values for the IBM TSM node name and password. the node name is not allowed when PASSWORDACCESS=generate.x (where x is a platform-dependent extension). To change the file’s ownership and permissions. On Unix Message obsi/adsm: ADSM: dsmInit failed.. ANS0273E (RC138) The trusted agent execution/owner permissions are invalid. Explanation: You might see an error message similar to this during a Unix backup or recovery operation. User Response: Change the passwordaccess option to prompt. and the permissions should be set to 4755.sys file (in Unix) or the dsm. or leave passwordaccess=generate and remove the values for the IBM TSM node name and password in your backup pool. User Response: Verify that the entries in the dsm. or the password could be out of sequence with the IBM TSM Server. make sure that the filename dsm. check with your IBM TSM administrator. Also. User Response: Have the IBM TSM systems administrator check the password. The trusted agent module is used to identify the IBM TSM client to the IBM TSM server.opt and dsm. make sure that the DSMI_DIR and DSMI_CONFIG subdirectories are in the environment. Confidential and Proprietary Information Error Messages A-3 . User Response: Make sure that the trusted agent module is in the DSMI_DIR subdirectory. Inc. Message ANS1025E (RC137) Session rejected: Authentication failure Explanation: This failure indicates an IBM TSM node password problem. If it is not there. You might have entered an incorrect password. The name of this file is dsmtca. Check these files for valid parameters in valid syntax for IBM TSM.Message dsminit failed: unable to find trusted agent module Explanation: You can receive this message if IBM TSM is unable to find the trusted agent module. probably in the DSMI_CONFIG file. The program has encountered an invalid option.. which is used for IBM TSM client authentication.opt is part of the path specification in the DSMI_CONFIG variable. Also.sys are correct. BMC Software. Message ANS0220E (RC400) dsmInit failed Explanation: You receive this message when you install the SQL-BackTrack Module for IBM TSM and then run the obsitest program. sl not found (HP-UX users) Explanation: You might receive this message on an HP-UX host if you are missing a link from /usr/lib to the IBM TSM API library. User Response: To fix this.sl Note This text assumes that the IBM TSM API client is installed at /opt/tivoli/tsm/client/api/bin. If the IBM TSM API client is installed in a different location.sl). User Response: To fix this.a Note This assumes that the IBM TSM API client is installed at usr/tivoli/tsm/client/api/bin. If the IBM TSM API client is installed in a different location..a not found (AIX users) Explanation: You might receive this message on an AIX host if you are missing a link from /usr/lib to the IBM TSM API client library. create the following link: % ln -s /usr/tivoli/tsm/client/api/bin/libApiDS.Message libApiDS. Inc.a). create the following link: % ln -s /opt/tivoli/tsm/api/bin/libApiDS. If not. Message libApiDS. Confidential and Proprietary Information A-4 SQL-BackTrack Module for IBM TSM Installation and User Guide .sl /usr/lib/libApiDS. verify that the symbolic link exists from /usr/lib to the directory where the API library resides (libApiDS. verify that the symbolic link exists from /usr/lib to the directory where the API library resides (libApiDS. you must provide appropriate value in the link. If not. BMC Software.a /usr/lib/libApiDS. you must provide appropriate value in the link. status. and expiration of archive files. or IBM TSM) that is used as the backup destination for client files. A logical grouping of backup pools. destination.Glossary Glossary archive copy group A policy object containing the attributes that control the generation. date. See also backup pool. A named set of storage entities (such as disks.. and expiration of backup files. tapes. backup catalog backup copy group backup destination backup history backup pool backup pool group BMC Software. See also management class. A record of the backup operations that SQL-BackTrack has performed on a given database or object. See also management class. This information includes the time. A policy object containing the attributes that control the generation. and location of previous backups. Confidential and Proprietary Information Glossary 5 . destination. A logical device or group of devices to which backup data is written. Inc. See catalog directory. including: • • • backup and recovery instructions backup history backup device definitions backup type catalog catalog directory compression An option that encodes data to reduce its size before it is backed up. See catalog directory. See archive copy group and backup copy group. See catalog directory. Either a physical backup or a logical backup.. which write backup data in differing formats. Confidential and Proprietary Information 6 SQL-BackTrack Module for IBM TSM Installation and User Guide . backup script A sequence of commands that perform a backup operation when executed. configuration directory control directory control file copy group BMC Software. See catalog directory. including: • • • • what type of backup to perform what objects to back up where to write the backup data when previous backups occurred The catalog directory can contain multiple profiles: one for physical backups and several for export backups. Inc.backup profile A subdirectory of the catalog directory that contains physical and export backup instructions. See catalog directory. A directory that contains all the SQL-BackTrack configuration information. A backup operation that is performed periodically and without user interaction. A management class can contain a backup copy group. IBM TSM storage agent LAN-free management class parallel backup streams physical device primary node recovery script scheduled backup script BMC Software. An environment that enables movement of data outside of a LAN.expiration An event that causes all the records of a backup to be deleted from the backup history. an archive copy group. The actual backup files are deleted only if the SQL-BackTrack Module for IBM TSM supports file deletion operations. Confidential and Proprietary Information Glossary 7 . A sequence of commands that perform a recovery operation when executed. Contrast with logical device.. It is an instance of a specific device type. This component communicates directly with the storage devices in the SAN and enables LAN-free backups and recoveries. Common term for the Tivoli Managed System for SAN product. A policy object that is a named collection of copy groups. A backup operation that sends whole files to multiple devices simultaneously and writes data on a file-by-file basis. or neither of these. Users can bind backup and archive objects to a management class to specify how the IBM TSM server manages them. The first Oracle Parallel Server node that SQL-BackTrack tries to use for a backup or recovery of a specific file. This process reduces the time required to write backup data. A hardware component that communicates with the operating system by way of a device driver to process block device or character device files. A sequence of commands that perform a backup or recovery operation when executed. See also archive copy group and backup copy group. both of these. typically to a storage device attached to a SAN. See also striping. such as a tape drive or disk drive. Inc. (SQL-BackTrack for Sybase and SQL-BackTrack for Microsoft SQL Server terms.) To check for outdated or incorrect database login IDs and passwords. It may run on a node other than the node that extracts or loads data. See also parallel backup streams.. (SQL-BackTrack for Sybase term. Confidential and Proprietary Information 8 SQL-BackTrack Module for IBM TSM Installation and User Guide .) The interleaving of backup data across multiple backup devices. See scheduled backup. storage agent striping synchronize unattended backup BMC Software.SQL-BackTrack Module The component of the SQL-BackTrack program that handles reading from and writing to the backup media. Inc. See IBM TSM storage agent. and prompt the user to make any necessary changes. pdf files accessing on the product CD 1-8 installing the Acrobat Reader from the product CD 1-9 IBM TSM 3-7 recommendation for PASSWORDAccess 3-7 B backup adding environment variables to script 5-5 expiration troubleshooting 5-14 expiring 5-13 improved expiration 5-14 monitoring using SQL-BackTrack 5-10 monitoring with SQL-BackTrack 5-10 on-demand 5-5 stored IBM TSM password 4-20 unattended with IBM TSM 5-7 unattended with Unix cron 5-9 unattended with Windows scheduler 5-10 backup copy group 4-21. 4-16 OPS example 4-25 options 4-16 A Acrobat Reader installing 1-9 viewing online documentation 1-10 adding the SQL-BackTrack Module to SQL-BackTrack on Unix 4-4 on Windows 4-7 Administrators group 2-7 adsm 2-11 adsm_del 5-17 using 5-17 adsmpw 2-10 using 3-30 adsmrc utility 2-10 alternate host recovery 6-3 ARCHDEL 5-13 archive copy group 4-21. 5-11 backup destination 4-27 backup pool 3-15 creating on Unix 3-34 description 4-11.Index Index Symbols . Confidential and Proprietary Information Index 1 .. 5-11 authentication BMC Software. Inc. task map 3-3 LAN 1-2 SAN 1-4 SQL-BackTrack 4-2 task map 3-3 validating 3-17 configuration diagram (LAN-free) 1-4 Configure utility SQL-BackTrack for DB2/UDB 4-7 SQL-BackTrack for Microsoft SQL Server 4-8 SQL-BackTrack for Oracle 4-7 copy group backup and archive 4-21 cron 5-9 customer support iii launching on Windows. 3-25 dsm..sys explanation 3-15 BMC Software. 4-25 Unix example 4-21 Windows example 4-21 backup pool name 4-17 backup script changing ownership 5-8 generating (Unix) 5-5 sample (Unix) 5-6 BMC Software.smp.opt dsm. 2-12 changing IBM TSM password 3-30 client scheduler 5-9 cluster environment installation 2-2 commands INSTALL 2-10 install 2-10 COMMMethod 3-20.log 2-17 dsm.opt. contacting ii Bourne shell export syntax 2-16 C C shell setenv syntax 2-16 CD mounting for Unix 2-9 mounting for Windows installation configuring SQL-BackTrack to use multiple IBM TSM servers 4-32 IBM TSM server 3-14 IBM TSM. Inc. Confidential and Proprietary Information 2 SQL-BackTrack Module for IBM TSM Installation and User Guide . 3-26 compression 3-10 compression option 3-33 compression setting 3-10 configuration D DEFINE ASSOCIATION 5-7 DEFINE DEVCLASS 3-10 DEFINE SCHEDULE 5-7 DEFINE SCHEDULE OBJECTS parameter 5-8 devconfig explanation 3-16 documentation accessing on the product CD 1-8 dsierror.opt explanation 3-15 sample file (Unix) 3-23 sample file (Windows) 3-26 dsm.smp 3-22.options for OPS users 4-23. 3-26 COMMTIMEOUT and Sybase recovery 3-11 recommended value 3-11 recovery requirements 6-2 COMMTIMEOUT setting 3-11 communication method 3-9 COMPRESSIon 3-20.opt. See dsm. 5-16 F features 1-2 filespace name default 3-9 filespace tag 3-8 free disk space requirements 2-5 Index 3 E en_US subdirectory 2-17 BMC Software.sys. Inc.sys dsmc program 5-9 dsmclientv3.dsm. Confidential and Proprietary Information . 3-26 environment variable adding to backup script 5-5 DSMI_CONFIG (Unix) 2-17 DSMI_CONFIG (Windows) 2-13 DSMI_DIR (Unix) 2-16 DSMI_DIR (Windows) 2-13 DSMI_LOG (Windows) 2-19 DT_ADSM_DEBUG 2-22 DT_ADSM_FILESPACE 2-22 DT_ADSM_LOG 2-22 DT_ADSM_MGMTCLASS 2-23 DT_ADSM_MOUNTWAIT 2-23 DT_ADSM_NODE 2-23 DT_ADSM_OWNER 2-23 DT_ADSM_PASSWORD 2-24 DT_ADSM_SERVER 2-24 DT_ADSM_STORAGEPOOL 2-24 DTBASE (Unix) 2-16 DTBASE (Windows) 2-19 how to set on Unix 2-16 how to set on Windows 2-19 how to verify on Unix 2-17 optional variables 2-22 error messages IBM TSM A-1 SQL-BackTrack Module A-2 expiration adsm_del utility 5-17 improved 5-14 manually deleting objects 5-16 troubleshooting 5-14 EXPIRE INVENTORY 5-13.smp. See dsm.opt 3-14 DSMSTA SETSTORAGESERVER 3-16 dsmsta..opt explanation 3-16 dsmtca A-2 DT_ADSM_DEBUG 2-22 DT_ADSM_FILESPACE 2-22 DT_ADSM_LOG 2-22 DT_ADSM_MGMTCLASS 2-23 DT_ADSM_MOUNTWAIT 2-23 DT_ADSM_NODE 2-23 DT_ADSM_OWNER 2-23 DT_ADSM_PASSWORD 2-24 DT_ADSM_SERVER 2-24 DT_ADSM_STORAGEPOOL 2-24 DTBASE default value (Unix) 2-16 default value (Windows) 2-12 recommended value (Windows) 2-19 dtwatch 5-10 dtwwatch 5-10 enablelanfree 3-20.cat 2-17 DSMI_CONFIG default value (Windows) 2-13 recommended value (Unix) 2-17 verify setting (Unix) 2-17 DSMI_DIR default value (Unix) 2-16 default value (Windows) 2-13 verify setting (Unix) 2-17 DSMI_LOG default value(Unix) 2-17 recommended value (Windows) 2-19 dsmInit failed A-2 dsmserv. . copying the binaries 2-9 Windows permissions 2-7 introduction 1-2 ISO 9660.x 2-5 BMC Software. Inc.out 3-16 dsmsta. Rock Ridge extension 2-9 K Korn shell export syntax 2-16 L LAN configuration 1-2 backup scenario 1-3 diagram 1-3 LAN-free devconfig. Confidential and Proprietary Information 4 SQL-BackTrack Module for IBM TSM Installation and User Guide .G generate (PASSWORDAccess setting) 3-8 I IBM TSM filespace 4-28 management class 4-28 Passwordaccess mode 4-29 storage pool 4-28 storing passwords 4-29 IBM TSM API client library links 2-5 IBM TSM API client versions supported 2-3 IBM TSM Node Name 3-6 IBM TSM options for consideration 3-4 IBM TSM Scheduler requirements for using 5-7 sample commands 5-7 to 5-9 IBM TSM server installation requirements 2-5 IBM TSM Server Name 3-6 IBM TSM storage agent 3-16 include-exclude List 3-13 include-exclude list 3-13 installation 2-2 cluster environment requirements 2-2 DSMI_CONFIG variable to set after (Unix) 2-17 DSMI_DIR variable to set after (Unix) 2-16 DSMI_LOG variable to set after (Unix) 2-17 DSMI_LOG variable to set after (Windows) 2-19 DTBASE variable to set after (Unix) 2-16 DTBASE variable to set after (Windows) 2-19 how to install the Module on Unix 2-9 IBM TSM server requirement 2-5 list of all required components on host 2-2 list of tasks 2-2 of Acrobat Reader 1-9 process (Unix) 2-10 requirement for LAN-free operations 2-5 script 2-10 software and hardware requirements 2-5 supported environments 2-3 Unix install script 2-10 Unix library links 2-5 Unix permissions 2-7 upgrading 2-14 using a CD to install vs.opt 3-16 files to configure 3-16 LAN-free configuration 1-4 LAN-free option 3-9 libApiDS. libApiDS64.x 2-5 linking SQL-BackTrack Module to SQL-BackTrack Unix 4-4 Windows 4-7 Linux no SAN support 2-4 local area network configuration 1-2 P password changing 2-10 changing client 3-30 seeding 2-10 seeding with adsmpw 3-30 password authentication 3-7 PASSWORDAccess 3-20, 3-26 generate 3-8 prompt 3-8 performance, improving 4-31 platforms supported 2-3 pool options, for OPS users 4-23, 4-25 POOLS file sample 4-32, 4-33 product configuration 1-4 LAN 1-2 product features 1-2 product integration 1-5 filespace management 1-7 lan-free operations 1-8 management class and storage pools 1-7 media mount wait time 1-7 nodename verification 1-6 password access 1-6 product overview 1-2 product support iii program 3-30 programs adsmpw 2-10 Configure 4-7 obsitest 2-11 prompt (PASSWORDAccess setting) 3-8 M management class overriding default (Unix) 4-20 STANDARD 3-11 management class, configuring 1-7 media mounts 4-20 memory mapped I/O mode 4-31 mls directory 2-11 Module overview 1-2 mount CD-ROM 2-9 mount point 2-9 MOUNTWAIT and backup pools 4-20 and Sybase 3-10 recommended value 3-10 recovery requirements 6-2 MOUNTWAIT setting 3-10 multiple server support 4-32 O obsitest validating the configuration 3-17 obsitest utility 2-11 online documentation xiv accessing xiv operating systems supported 2-3 overview 1-2 BMC Software, Inc., Confidential and Proprietary Information R recovery commtimeout requirements 6-2 mountwait requirements 6-2 Index 5 Sybase COMMTIMEOUT requirements 3-11 to an alternate host 6-3 using SQL-BackTrack 6-2 related documentation xiv related publications xiv requirements free disk space 2-5 software and hardware 2-5 restore, stored IBM TSM password 4-20 RETVER 5-13 Rock Ridge extension 2-9 running adsmpw 3-30 S SAN storage agent requirement 2-5 SAN backup and recovery 3-16 SAN configuration 1-4 backup scenario 1-5 diagram 1-4 scheduled backups See unattended backup and backup, unattended 5-6 seeding client password 3-30 seeding password 2-10 SErvername 3-26 servername in dsm.opt file (Unix) 3-23 setup.exe 2-12 SQL-BackTrack backup pool 3-15, 4-11, 4-16 defining backup pool 4-16 defining backup pool (OPS users) 4-24 defining IBM TSM backup pool (OPS users) 4-25 recovery 6-2 SQL-BackTrack for Microsoft SQL Server, defining backup destination 4-27 6 SQL-BackTrack for Sybase, defining backup pool 4-18 SQL-BackTrack Module installing on Unix 2-9 SQL-BackTrack Module device type, choosing IBM TSM 4-18 SQL-BackTrack Module device type, choosing IBM TSM (OPS users) 4-24 SQL-BackTrack Module expiration retry feature 5-14 SQL-BackTrack Module for IBM TSM choosing backup device 4-18 features 1-2 introduction 1-2 storage agent devconfig.out 3-16 dsmsta.opt 3-16 storage area network configuration 1-4 storage pool. See copy group storage pools 3-12 backup or archive 3-12 stored IBM TSM password 4-20 support, customer iii Sybase recovery, COMMTIMEOUT requirements 3-11 Sybase, MOUNTWAIT requirements 3-10 symbolic links SQL-BackTrack programs 4-4, 4-5 versionless 4-4, 4-5 T tasks for installation 2-2 TCPPort 3-20, 3-26 TCPServeraddress 3-20, 3-26 technical support iii test backup (Unix) 3-37 test recovery (Unix) 3-37 Tru64 UNIX no SAN support 2-4 BMC Software, Inc., Confidential and Proprietary Information SQL-BackTrack Module for IBM TSM Installation and User Guide U unattended backup with IBM TSM 5-7 UPDATE DEVCLASS 3-10 upgrade 2-2 upgrading the Module 2-14 user ID for backups 5-13 utilities adsmpw 2-10 adsmrc 2-10 obsitest 2-11 W wait for media mounts 4-20 Watch utility 5-10 V variable DSMI_CONFIG (Unix) 2-17 DSMI_CONFIG (Windows) 2-13 DSMI_DIR (Unix) 2-16 DSMI_DIR (Windows) 2-13 DSMI_LOG (Unix) 2-17 DSMI_LOG (Windows) 2-19 DT_ADSM_DEBUG 2-22 DT_ADSM_FILESPACE 2-22 DT_ADSM_LOG 2-22 DT_ADSM_MGMTCLASS 2-23 DT_ADSM_MOUNTWAIT 2-23 DT_ADSM_NODE 2-23 DT_ADSM_OWNER 2-23 DT_ADSM_PASSWORD 2-24 DT_ADSM_SERVER 2-24 DT_ADSM_STORAGEPOOL 2-24 DTBASE (Unix) 2-16 DTBASE (Windows) 2-19 how to set on Unix 2-16 how to set on Windows 2-19 how to verify on Unix 2-17 optional variables 2-22 BMC Software, Inc., Confidential and Proprietary Information Index 7 BMC Software.. Confidential and Proprietary Information 8 SQL-BackTrack Module for IBM TSM Installation and User Guide . Inc. bmc. to You. Inc. "License Capacity" means the licensed capacity for the Software with the pricing and other license defining terms. lease. to do the following: (a) install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You acquired the license. outsourcing environment. DO NOT INSTALL OR USE THE PRODUCT. decompile or otherwise attempt to derive any Software from executable code. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS. maintenance modifications. enhancements. This Agreement ("Agreement") is between the entity or individual entering into this Agreement ("You") and BMC Software Distribution. up to the License Capacity. There is no additional warranty period or free support period for license upgrades. THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. . PRODUCT AND CAPACITY. The Product is deemed accepted by You. and error corrections. including any technical specifications. "You" includes you and your Affiliates. Subject to the terms of this Agreement. "Documentation" means all written or graphical material provided by BMC in any medium. gigabyte limit.END USER LICENSE AGREEMENT NOTICE BY OPENING THE PACKAGE. then you agree to only use such modifications or new software programs for Your internal purposes or otherwise consistent with the License. a Delaware corporation located at 2101 CityWest Blvd. is controlled by or shares common control with a party. LICENSE. upgrades. which is available at http://www. YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT. via delivery or electronic transmission. PROMPTLY RETURN THE PRODUCT TO BMC OR YOUR BMC RESELLER. PRESSING "AGREE" OR "YES" OR USING THE PRODUCT. OR (2) IF YOU DID NOT AGREE TO A WEB BASED LICENSE AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT AND YOU HAVE A WRITTEN LICENSE AGREEMENT WITH BMC. use in a service bureau. LICENSE UPGRADES. AND IF YOU ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF LICENSE FEES PAID. without BMC’s prior written approval.. 77042. USA or its affiliated local licensing entity ("BMC"). non-transferable. unless prohibited by local law.. THEN THAT WRITTEN AGREEMENT GOVERNS THE USE OF THE PRODUCT. Texas. For licenses based on the power of a computer. If the Software is designed by BMC to permit you to modify such Software. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such expanded usage and Your payment of applicable fees. or (c) provide a third party with the results of any functional evaluation or benchmarking or performance tests. THE ELECTRONIC AGREEMENT PROVIDED WITH THE PRODUCT AS PART OF THE INSTALLATION OF THE PRODUCT WILL NOT APPLY. reverse engineer. RESTRICTIONS: You agree to NOT: (a) disassemble. or sublicense). bug fixes.com or can be provided to You upon request. BMC grants You a non-exclusive. perpetual (unless a term license is provided on an order) license for each copy of the Software. You agree to use BMC’s current computer classification scheme. quantity of Software. such as tier limit. "Affiliate" is defined as an entity which controls. or for rental. relating to the functionality or operation of the Software. Houston. UNLESS (1) YOU AGREED TO A WEB BASED LICENSE AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT. (b) operate the Software solely for processing Your own data in Your business operations. (b) distribute or provide the Software to any third party (including without limitation. Software includes computer files. or processing the data of third parties. BMC grants You a license to use the Documentation solely for Your internal use in Your operations. and (c) make one copy of the Software for backup and archival purposes only (collectively a "License"). as well as Your payment of applicable fees. INSTALLING. "Software" means the object code version of the computer programs provided. THIS AGREEMENT WILL APPLY TO THE PRODUCT. In addition to the restrictions imposed under this Agreement. "Product" means the Software and Documentation. any other usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product. and/or other capacity limitations regarding the Software. IF YOU REJECT THIS AGREEMENT. total allowed users. ACCEPTANCE. IN WHICH CASE THAT WEB BASED LICENSE AGREEMENT GOVERNS THE USE OF THE PRODUCT. updates. including capacity restrictions. on the date that You received the Product from BMC. EXCLUSIVE REMEDY. WITHOUT LIMITATION. . This warranty shall not apply to any problems caused by software or hardware not supplied by BMC or to any misuse of the Software. Confidential Information means non-public technical and non-technical information relating to the BMC Products and Support. INDIRECT. for any reason. BMC may refuse to provide Support for any versions or releases of the Software other than the most recent version or release of such Software made available by BMC. BMC DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE. OWNERSHIP OF THE PRODUCT. SUPPORT. INCLUDING. ITS AFFILIATES AND LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. if not specified. Your right to use this Product automatically expires. BMC or its Affiliates or licensors retain all right. BMC may terminate for its convenience a Trial License upon notice to You. AND/OR THE PRODUCT (INCLUDING. WITHOUT LIMITATION. and (ii) BMC provides new releases or versions. and the structure and organization of the Software. AND IRRESPECTIVE OF ANY NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT LAW. Either party may terminate Your enrollment in Support upon providing notice to the other at least 30 days prior to the next applicable Support anniversary date. TERMINATION. ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL. IN NO EVENT IS BMC. THE PRODUCT IS PROVIDED "AS IS. and BMC. You must uninstall the Software. The BMC Products are and contain valuable confidential information of BMC ("Confidential Information"). LOST PROFITS. and industrial and intellectual property laws. SUPPORT." BMC. informational. FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT) AND HAVE NO LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL LICENSE ("Trial License"). WITHOUT LIMITATION. contact BMC to acquire a capacity-based license to the Product for a fee. and either certify the destruction of the Product or return it to BMC. title and interest to and in the BMC Product and all intellectual property. so long as such new releases or versions are furnished by BMC to all other enrolled Support customers without additional charge. BMC may charge You a reinstatement fee of 1. the Product is provided on a trial basis. BMC may change its prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date. DISCLAIMER. PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT. When the Trial Period ends. LOST COMPUTER USAGE TIME. or if BMC cannot remedy or replace such defective copy of the Software. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of supported versions of the Software. (b) Fees. including. copying. for any defect in the Software during the warranty period or breach of the warranty above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the warranty or replace the defective Software within a reasonable period of time. without limitation. Except for a Trial License. then BMC agrees to provide support (24 hours a day/7 days a week) ("Support"). BMC neither grants nor otherwise transfers any rights of ownership in the BMC Product to You. industrial property and proprietary rights therein. If You want to continue Your use of the Product beyond the Trial Period. There is a free support period during the one year warranty period. CONFIDENTIAL AND PROPRIETARY INFORMATION. If You re-enroll in Support. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE.5 times what You would have paid if You were enrolled in Support during that time period. LIMITS ON LIABILITY. trade secret. BMC warrants that the Software will perform in substantial accordance with the Documentation for a period of one year from the date of the order. BMC provides bug fixes. You may not disclose the Confidential Information to third parties. WARRANTY. OR THAT ALL DEFECTS CAN BE CORRECTED. DISCLAIMER OF DAMAGES. as part of the ordering process. THE IMPLIED WARRANTIES OF MERCHANTABILITY. AND NON-INFRINGEMENT. ITS AFFILIATES AND RESELLERS. and Your exclusive remedy. publication or dissemination of the Product. and (ii) Your use of the Product is on an AS IS basis without any warranty. AND DAMAGE OR LOSS OF USE OF DATA). This Agreement shall immediately terminate if You breach any of its terms. (a) Support Terms. patches or workarounds in order to cause that copy of the Software to operate in substantial conformity with its then-current operating specifications. trade secret and proprietary information. non-transferable evaluation license to operate the Software for the period of time specified from BMC or. then BMC shall refund the amount paid by You for the License for that Software. INCIDENTAL. then these terms apply: (i) this license consists solely of a non-exclusive. THE IMPLIED WARRANTIES OF MERCHANTABILITY. BMC reserves any rights not expressly granted to You herein. BMC’s entire liability. You agree to use all reasonable efforts to prevent the unauthorized use. FITNESS FOR A PARTICULAR PURPOSE.TRIAL LICENSE. The annual fee for Support is 20% of the Software’s list price less the applicable discount or a flat capacity based annual fee. BMC Products are protected by applicable copyright. AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES (INCLUDING. If Your order includes support for the Software. If. Upon termination. You will be automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You as provided below. BMC’s obligations in this section are conditioned upon Your providing BMC prompt access to the affected Software and full cooperation in resolving the claim. a 30 day time period ("Trial Period") only for evaluating whether You desire to acquire a capacity-based license to the Product for a fee. BMC’S AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE LICENSE TO THE PRODUCT. including. THE ARBITRATION SHALL BE HELD IN SINGAPORE. If the underpaid fees exceed 5% of the fees paid. at its expense. THE COSTS OF THE ARBITRATION SHALL BE BORNE EQUALLY PENDING THE ARBITRATOR’S AWARD. or transfer. This Agreement constitutes the entire agreement between You and BMC and supersedes any prior or contemporaneous negotiations or agreements. or Thailand (collectively. Special Administrative Region of Hong Kong. Republic of China. IF THE DISPUTE IS INITIATED IN A COUNTRY OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION.S. The Software under this Agreement is "commercial computer software" as that term is described in 48 C. THE ARBITRATION SHALL BE HELD IN NEW YORK. 227. SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. (c) in Singapore. written or displayed electronically. then You agree to also pay BMC’s reasonable costs of conducting the audit. if you acquired the License in Canada (subsections (a) and (b) collectively referred to as the "Americas Region"). This Agreement is governed by the substantive laws in force. use. UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL.227-7014(a)(1). or (d) in the Netherlands. MISCELLANEOUS TERMS. withholding. 12. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C. detailing Your use of the Software in accordance with this Agreement. or reimburse BMC.F. whether oral. BMC may. (b) in the Province of Ontario. If an audit reveals that You have underpaid fees. directly or indirectly. export. without regard to conflict of laws principles: (a) in the State of New York. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety. if you acquired the License in Japan. THE ARBITRATION SHALL BE HELD IN AMSTERDAM. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO PROTECT EITHER PARTY’S CONFIDENTIAL INFORMATION. Singapore.R. whether generated manually or electronically. AND THE PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS’ FEES AND NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY. You agree to pay such underpaid fees. If acquired by or on behalf of a civilian agency.212 (Computer Software) and 12. You may not assign or transfer this Agreement or a License to a third party without BMC’s prior written consent. duty. the U.S. Philippines.A. the U. re-export. Les parties exigent que la présente convention ainsi que les documents qui s’y rattachent soient rédigés en anglais. GOVERNMENT RESTRICTED RIGHTS.7202 of the DOD FAR Supplement and its successors. New Zealand. concerning the Product and related subject matter. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice. including sales.F. tariffs. the License Capacity. state or local taxes (other than taxes based on BMC’s net income) imposed in connection with the Product and/or the Support. unless otherwise provided on the order for the License to the Products. OWNERSHIP. U. 252. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C. ARBITRATION. for taxes of any kind.. if you acquired the License in any other country not described above. You agree not to import. OR ANY OTHER PROPRIETARY RIGHTS. customs. any part of the Product or any underlying information or technology except in full compliance with all United States. Puerto Rico. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH.S. or any country in Central or South America. RULES OF THE AMERICAN ARBITRATION ASSOCIATION.211 (Technical Data) of the Federal Acquisition Regulations ("FAR") and its successors. IF THE DISPUTE IS INITIATED IN THE AMERICAS REGION. EXPORT CONTROLS. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT. Should any provision of this Agreement be invalid or unenforceable. If acquired by or on behalf of any agency within the Department of Defense ("DOD").R.VERIFICATION. AND MAY BE ENFORCED IN ANY COURT OF COMPETENT JURISDICTION. If requested by BMC. India. SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. "Asia Pacific Region"). Indonesia. You agree to deliver to BMC periodic written reports. The parties have agreed that this Agreement and the documents related thereto be drawn up in the English language. Malaysia. and other similar federal. You will pay. property. No modification or waiver of any provision hereof will be effective unless made in a writing signed by both BMC and You.F. GOVERNING LAW. foreign and other applicable laws and regulations. audit Your use of the Software to confirm Your compliance with the Agreement.S. SW EULA Int 030102 . U. NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. South Korea. Australia. IF THE DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION.R. ALL ARBITRATION PROCEEDINGS SHALL BE CONDUCTED IN CONFIDENCE. Peoples Republic of China. if you acquired the License in the United States. value-added (VAT). without limitation. the remainder of the provisions will remain in effect. AS APPLICABLE. . Notes . *29721* *29721* *29721* *29721* *29721* .
Copyright © 2024 DOKUMEN.SITE Inc.