Teradata Extension for Tivoli Storage Manager. Administrator Guide

Transcription

1 Teradata Extension for Tivoli Storage Manager Administrator Guide Release B A April 2010

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/os are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a collective membership mark and a service mark of Unicode, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as Feedback ) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata Corporation. All Rights Reserved.

3 Preface Purpose This book provides information about Teradata Extension for Tivoli Storage Manager, which is a Teradata Tools and Utilities product. Teradata Tools and Utilities is a group of products designed to work with the Teradata Database. Chapter 2 Teradata TARA Installation and Uninstallation provides information about installing Teradata Extension for Tivoli Storage Manager. Teradata Extension for Tivoli Storage Manager is supported by ARCMAIN as an interface for backing up and restoring objects in a Teradata Database. Teradata Extension for Tivoli Storage Manager manages the input/output (I/O) interfaces between the Teradata ARCMAIN client utility and IBM Tivoli Storage Manager (TSM). In the framework of Teradata Extension for Tivoli Storage Manager is Teradata Tiered Archive Restore Architecture (TARA). TARA is composed of three components: TARA server, TARA GUI, and the backup application extension, TIVBAR. Audience This book is intended for use by: System administrators System operators Users who are responsible for backing up data and restoring tasks Supported Releases This book supports the following releases: IBM Tivoli Storage Manager 6.1 and 5.5 Teradata Tools and Utilities or later Teradata Extension for Tivoli Storage Manager Note: Open Teradata Extension for Tivoli Storage Manager s GUI. Click Teradata Tiered Archive/Restore Architecture>Help>About to display the Teradata Extension for Tivoli Storage Manager version number. Teradata Extension for Tivoli Storage Manager Administrator Guide 3

4 Preface Prerequisites To locate detailed supported-release information: 1 Go to 2 Under Online Publications, click General Search. 3 Type 3119 in the Publication Product ID box. 4 Under Sort By, select Date. 5 Click Search. 6 Open the version of the Teradata Tools and Utilities ##.##.## Supported Platforms and Product Versions spreadsheet associated with this release. The spreadsheet includes supported Teradata Database versions, platforms, and product release numbers. Prerequisites The following prerequisite knowledge is required for this product: Computer technology and terminology Teradata system hardware Relational database management (RDBMS) systems IBM Tivoli Storage Manager (TSM) IBM Backup/Archive Client Basic concepts and facilities of the Teradata Database and the Teradata server Teradata Backup and Storage procedures Microsoft Windows 2003 and XP operating systems SUSE Linux 9 and 10 operating systems Changes to This Book The following changes were made to this book in support of the current release. Changes are marked with change bars. For a complete list of changes to the product, see the release definition associated with this release. 4 Teradata Extension for Tivoli Storage Manager Administrator Guide

5 Preface Additional Information Date and Release April August Description Added support for Tivoli Storage Manager 6.1 The maximum length of the of the job names in the archive and restore scripts is 220 characters. The Java heap size can be increased. Uninstallation instructions for Linux are included. A job can be created just to back up the dictionary. A different port number may be selected for the TARA Server. An Analyze option as a part of the Restore process has been added. There are file extensions for archive and restore jobs. They are.arc and.res. A Logon feature is provided to the TARA server for the TARA user interface and utilities. There are two new CopyScript options. TARA nodes have to run with the same version of ARC on all nodes. There is a utility that provides problem and remedy details for any ARC or Teradata Extension for Tivoli Storage Manager errors when a TARA job is run. The installations scripts have been changed. The TARALaunch returns the TARA JobFile name. After configuration, TARA clients can access images from other TARA clients. Added support for Tivoli Storage Manager 5.5. Added GUI support for Teradata Extension for Tivoli Storage Manager. Reorganized book into different sections: for the new GUI and the legacy command line product. Added online help to the new GUI. Added export to html functionality in the TARA GUI. Added SUSE Linux 9 and 10 support for the TARA server. Dropped Windows 2000 support. Added the taratddsmc command-line utility. Added the ability to specify the size of the log file. Added the ability to selectively back up and restore individual objects, described in Selecting Individual Objects to Archive or Restore on page 71. Additional Information Additional information that supports this product and Teradata Tools and Utilities is available at the web sites listed in the table that follows. In the table, mmyx represents the publication date of a manual, where mm is the month, y is the last digit of the year, and x is an internal publication code. Match the mmy of a related publication to the date on the cover of this book. This ensures that the publication selected supports the same release. Teradata Extension for Tivoli Storage Manager Administrator Guide 5

6 Preface Additional Information Type of Information Description Access to Information Release overview Late information Additional product information CD-ROM images Ordering information for manuals Use the Release Definition for the following information: Overview of all of the products in the release Information received too late to be included in the manuals Operating systems and Teradata Database versions that are certified to work with each product Version numbers of each product and the documentation for each product Information about available training and the support center Use the Teradata Information Products web site to view or download specific manuals that supply related or additional information to this manual. Access a link to a downloadable CD-ROM image of all customer documentation for this release. Customers are authorized to create CD-ROMs for their use from this image. Use the Teradata Information Products web site to order printed versions of manuals. 1 Go to 2 Under Online Publications, click General Search. 3 Type 2029 in the Publication Product ID box. 4 Click Search. 5 Select the appropriate Release Definition from the search results. 1 Go to 2 Select Data Warehousing under Browse by Category. 3 Do one of the following: For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities and then select a release or a specific title. Select Open Teradata Backup for a specific title relating to a Backup Application Software product. Select a link to any of the data warehousing publications categories listed. Specific books related to Teradata Extension for Tivoli Storage Manager are as follows: Teradata Archive/Recovery Utility Reference B mmyx Teradata Tools and Utilities Installation Guide for Microsoft Windows B mmyx 1 Go to 2 Under the Online Publications subcategory, Browse by Category, click Data Warehousing. 3 Click CD-ROM List and Images. 4 Follow the ordering instructions. 1 Go to 2 Under Print & CD Publications, click How to Order. 3 Follow the ordering instructions. 6 Teradata Extension for Tivoli Storage Manager Administrator Guide

7 Preface Additional Information Type of Information Description Access to Information General information about Teradata The Teradata home page provides links to numerous sources of information about Teradata. Links include: Executive reports, case studies of customer experiences with Teradata, and thought leadership Technical information, solutions, and expert advice Press releases, mentions, and media resources 1 Go to Teradata.com. 2 Select a link. Teradata Extension for Tivoli Storage Manager Administrator Guide 7

8 Preface Additional Information 8 Teradata Extension for Tivoli Storage Manager Administrator Guide

9 of Contents Preface Purpose Audience Supported Releases Prerequisites Changes to This Book Additional Information Chapter 1: Introduction Component Overview Migration from Legacy Product Older Version of Teradata Extension Discontinued Chapter 2: Teradata TARA Installation and Uninstallation System Requirements Linux Windows User Account Requirements Linux Windows Teradata TARA Installation Overview of Installation Packages Installation Location Installation Order Installation of Teradata TARA Components on Linux Installation of Teradata TARA Components on Windows The xinetd Process on Linux Installed Components Teradata Extension for Tivoli Storage Manager Administrator Guide 9

10 of Contents TARA Server Package Teradata TARA GUI Package Teradata Extension for Tivoli Storage Manager Package Uninstallation on Windows Uninstallation on Linux Chapter 3: TSM and Teradata TARA Configuration Configure TSM for Teradata Backups TSM Server Configuration TSM Client Options Configure the TARA Server GUI TARA Server Port Increasing the Java Heap Size Configure the TARA Server Step 1 - Configure the Teradata Database System Step 2 - Configure the Client Systems Step 3 - Configure the Client Groups Step 4 - Configure Tivoli Information Step 5 - Configure ARC Options Step 6 - Configure Logging Configure the Log File Chapter 4: Backup and Restore Using the GUI Starting the Teradata TARA GUI Archiving a Database Object Dictionary Only Archive TSM Parameters Overwrite at Run Time Selecting Individual Objects to Archive or Restore Restoring a Database Object Dictionary Only Restore Analyze Option CopyScript Options Rename and Copy into Same Database Copy into New Database Viewing Job History Teradata Extension for Tivoli Storage Manager Administrator Guide

11 of Contents Extensions for Job Files Chapter 5: Taratddsmc Command-Line Utility Overview of taratddsmc Installation Command Line Parameters Syntax Conventions Format Specifiers Taratddsmc Help Command Query TSM Command Prompt Off Command Query Backup and Query Object Commands Delete Backup and Delete Object Commands Batch Mode Inactivate Backup and Inactivate Object Commands Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery Sample Lines of Code Sample List Option Output Sample Query Option Output - Traditional View Sample Query Option Output - Hierarchical View TARALaunch Sample Lines of Code Output TARASetCfg Sample Lines of Code Output TARAJobRM Teradata Extension for Tivoli Storage Manager Administrator Guide 11

12 of Contents Chapter 7: Troubleshooting for the TARA Overview of Error Messages Teradata Extension for Tivoli Storage Manager Debug Log ARCMAIN Outlog TSM Log Messages TSM Server Activity Log TSM Client Log Error Conditions and Recovery Data Connector Error Messages Vendor-Independent Error Messages TSM Error Messages Troubleshoot Utility TARA Server Stop and Restart Use of the Command Line to Obtain Information Teradata TARA GUI on Java Runtime Extension States for Archive Jobs Job Stream Connection Failure Symptom Step 1: Verify that ARC Output Files are Being Created Step 2: Examine the Script that Launches Teradata ARC TARA Job Output Errors Symptom Remedy Unresponsive TARA Server Symptom Step 1: Add ulimit Step 2: Change Verbosity of TARA Server Log Appendix A: Installation and Configuration: Command Line Utility Configuration Requirements Hardware Software Local Area Network (LAN) Connections and Platforms Installation Installed Files Teradata Extension for Tivoli Storage Manager Administrator Guide

13 of Contents Additional Directories Removal of the Teradata Access Module Configuration of TSM for Teradata Backups TSM Server Configuration TSM Client Options LAN Configuration Multiple Network Cards and TDPID Addressing Teradata Database Connections Network Settings for a Single Card Preparation for Production Appendix B: Storage of Backup Data: Command Line Utility Overview of Backup Data Storage Object Names DataSetName in ARCMAIN Backups and Restores Backup Generations Functional Restrictions No RESTART During Write ARCHIVE Statement Recommendation Per Script No Dual Backup Support Interoperability Collocation IOPARM Parameters Syntax Rules Parameter Definitions Security Security for Files that Contain Passwords Control of Access to Backup Images Stored in TSM Default Files for ARCMAIN and the Access Module Environment Variables Appendix C: The TDDSMC Administrative Utility Overview of the TDDSMC Utility Command Line Parameters Syntax Conventions Teradata Extension for Tivoli Storage Manager Administrator Guide 13

14 of Contents Format Specifiers TDDSMC Help Command Query TSM Command Prompt Off Command Query Backup and Query Object Commands Delete Backup and Delete Object Commands Inactivate Backup and Inactivate Object Commands Appendix D: Troubleshooting: Command Line Utility Overview of Error Messages Teradata Access Module for Tivoli Debug Log ARCMAIN Outlog TSM Log Messages TSM Server Activity Log TSM Client Log Error Conditions and Recovery Data Connector Error Messages Vendor-Independent Error Messages TSM Error Messages Glossary Index Teradata Extension for Tivoli Storage Manager Administrator Guide

15 List of Figures Figure 1: Overview of a Teradata Extension for Tivoli Storage Manager Backup Teradata Extension for Tivoli Storage Manager Administrator Guide 15

16 List of Figures 16 Teradata Extension for Tivoli Storage Manager Administrator Guide

17 List of s 1: User Accounts and Permissions for Linux Environment : User Accounts and Permissions for Windows Environment : Location of Installation Packages : Actions Taken when TARA Server Package Installed : Subdirectories of taraserver_postinstall.sh : Files in bin Subdirectory : Folders and Registry Entries : Fields to Consider for the Backup Copy Group : TSM Server Options : TSM Client Options File Characteristics : Object Icons : Metadata Fields : Parameters for TARAJobQuery : Parameters for TARALaunch : TARALaunch Return Codes : Parameters for TARASetCfg : Parameters for TARAJobRM : TARAJobRM Return Codes : Types of Messages : Log File Levels : Error Conditions and Recovery Options : Data Connector Error Codes : Vendor Independent Error Messages : TSM Error Messages : States for Archive Jobs : Files Created at Installation : Additional Directories Created at Installation : Tasks to Uninstall Complementary Components : Fields to Consider for the Backup Copy Group : TSM Server Options : TSM Client Options : Specifying Backup Image Names Teradata Extension for Tivoli Storage Manager Administrator Guide 17

18 List of s 33: Configuration for Examples : Parameter Definitions : Security Features : Environment Variables : Metadata Fields : Types of Messages : Log File Levels : Error Conditions and Recovery Options : Data Connector Error Codes : Vendor Independent Error Messages : TSM Error Messages Teradata Extension for Tivoli Storage Manager Administrator Guide

19 CHAPTER 1 Introduction Teradata Extension for Tivoli Storage Manager is an access module that is supported by ARCMAIN as an interface for backing up and restoring objects in a Teradata Database. Teradata Extension for Tivoli Storage Manager manages the input/output (I/O) interfaces between the Teradata ARCMAIN client utility and IBM Tivoli Storage Manager (TSM). The same ARCMAIN executable code can communicate with a variety of access modules. This guide provides information about the installation and configuration of Teradata Extension for Tivoli Storage Manager, and how to perform backup and restore jobs. A troubleshooting section provides guidance for resolving error conditions and error messages. Note: This book changes the product name to Teradata Extension for Tivoli Storage Manager. The prior product name, Teradata Access Module for Tivoli, is used in the appendixes to describe the legacy Teradata Access Module for Tivoli product. The legacy product was accessed with a command line utility. The chapters use the term Teradata Extension for Tivoli Storage Manager for the new product, which is accessed through a Graphical User Interface (GUI). Component Overview ARCMAIN retrieves data from a Teradata Database server for tape storage, or retrieves data from tape storage to insert into a Teradata Database. Figure 1 illustrates how Teradata Extension for Tivoli Storage Manager interfaces with ARCMAIN through use of the Data Connector to store backups onto TSM. Teradata Extension for Tivoli Storage Manager Administrator Guide 19

20 Chapter 1: Introduction Migration from Legacy Product Figure 1: Overview of a Teradata Extension for Tivoli Storage Manager Backup Teradata Server ARCMAIN Single Process with Shared Library Calls TARA High-Speed LAN Connection Recommened When ARCMAIN Process Runs On a Remotely- Connected Node Data Connector Teradata Extension for Tivoli Storage Management Tivoli Client API Library LAN-mode Tivoli Client API Library TSM Server LAN-Free Mode Managed Storage TSM Database 2444C001 ARCMAIN does not call Teradata Extension for Tivoli Storage Manager directly. Instead, access is through a Data Connector component that dynamically loads the module and standardizes the interfaces. The Data Connector and ARCMAIN software must be installed before using Teradata Extension for Tivoli Storage Manager. For more about hardware and software requirements, see System Requirements on page 23. Migration from Legacy Product Use the legacy Teradata Access Module for Tivoli to restore backups that were created by Teradata Access Module for Tivoli. It is not possible to use Teradata Extension for Tivoli Storage Manager s GUI to restore those backups. Older Version of Teradata Extension Discontinued Teradata Extension for TSM with TIVBAR x has reached end-of-life. Teradata Extension 13.0 for TSM which uses TARA 13.0 is the replacement for TIVBAR 1.0.2x. TSM 5.5, TTU 13.0, and Teradata DBMS 13.0 are the final release versions supported by TIVBAR x. TSM users are encouraged to switch to Teradata Extension 13.0 for TSM when they upgrade to Teradata DBMS 12.0 or All Teradata DBMS archives created with Teradata Extension for TSM - TIVBAR can not be restored with Teradata Extension 13.0 for TSM. They can only be restored with Teradata Extension for TSM with TIVBAR. In addition, the final Teradata DBMS release for which TIVBAR archives can be restored is Teradata Therefore, TSM users who want to retain these archives post Teradata DBMS 20 Teradata Extension for Tivoli Storage Manager Administrator Guide

21 Chapter 1: Introduction Migration from Legacy Product 13.0 must restore them to their Teradata DBMS using Teradata Extension for TSM - TIVBAR. They will also have to be archived using Teradata Extension 13.0 fortsm. Teradata Extension for Tivoli Storage Manager Administrator Guide 21

22 Chapter 1: Introduction Migration from Legacy Product 22 Teradata Extension for Tivoli Storage Manager Administrator Guide

23 CHAPTER 2 Teradata TARA Installation and Uninstallation This chapter describes installing Teradata TARA for SUSE Linux and Windows hosts: System Requirements User Account Requirements Teradata TARA Installation Installed Components Uninstallation on Windows Uninstallation on Linux System Requirements Linux The next sections list the required software for Teradata TARA on Linux or Windows operating systems. Operating System Use one of the following for the TARA GUI, TARA server, and Teradata Extension for Tivoli Storage Manager: SUSE Enterprise Server 9 Linux SUSE Enterprise Server 10 Linux Non-Teradata Software Use Java Runtime Environment 1.5.0_06, or later. Teradata Tools and Utilities Software Use the version, or later, of the following software: Shared ICU Libraries for Teradata Teradata Archive and Recovery Utility (ARC) Teradata Call-Level Interface (CLI) V2 Teradata Data Connector (PIOM) Teradata GSS Teradata Extension for Tivoli Storage Manager Administrator Guide 23

24 Chapter 2: Teradata TARA Installation and Uninstallation User Account Requirements Note: To ensure consistent results, the same versions of the Teradata Tools and Utilities software set must be installed on each of the client nodes. Windows Operating System For the TARA GUI, use one of the following: Microsoft Windows 2003 Microsoft Windows XP For the TARA server and the Teradata Extension for Tivoli Storage Manager, use Microsoft Windows 2003 SP1 or later. Non-Teradata Software Install Microsoft Windows Script Host, version 5.6. If you are installing the Teradata TARA GUI package, also install Java Runtime Environment 1.5.0_06 or later. Teradata Tools and Utilities Software Use the version, or later, of the following software: Shared ICU Libraries for Teradata Teradata Archive and Recovery Utility (ARC) Teradata Call-Level Interface (CLI) V2 Teradata Data Connector (PIOM) Teradata GSS Client nt-i386 Note: To ensure consistent results, the same versions of the Teradata Tools and Utilities software set must be installed on each of the client nodes. User Account Requirements Teradata TARA requires specific user accounts and permissions for proper operation. Refer to 1 for Linux information and 2 for Windows information. Linux 1: User Accounts and Permissions for Linux Environment Linux User Account Required Permission Description taraserver 755 User Read/Write/Execute Group Read/Execute baruser 755 Other Read/Execute 24 Teradata Extension for Tivoli Storage Manager Administrator Guide

25 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation Windows 2: User Accounts and Permissions for Windows Environment Windows User Account Required Permission Description taraserver Local Administrators This account and permission is required to start the TARA server. The TARA server uses the LocalSYSTEM account for the TCS communication mechanism. baruser Local Administrators This account is necessary to launch TARA jobs. Teradata TARA Installation Overview of Installation Packages There are three TARA-related installation packages for Linux and Windows: TARA server install package Teradata TARA GUI install package Teradata Extension for Tivoli Storage Manager package 3 lists the installation package locations on the Teradata Extension for Tivoli Storage Manager (TARA ) CD. 3: Location of Installation Packages Operating System TARA Server Teradata TARA GUI Teradata Extension for Tivoli Storage Manager Linux Linux/taraserver-<version>- <release>.i386.rpm Linux/taragui-<version>- <release>.i386.rpm Linux/tivbar-<version>- <release>.i386.rpm Windows Windows\TARA Server\setup.exe Windows\TARA GUI\setup.exe Windows\TIVBAR\setup.exe The TARA server runs on a node called the TARA server host, which contains the Job Information Repository, the Script Repository, the TARA server logs, and the default configuration file. The TARA server is the executable that manages the data stored in the different repositories and controls the flow of data between the TARA server, the Teradata TARA GUI, and the Teradata Extension for Tivoli Storage Manager. On this host, the TARA server executable runs as a service. The Teradata TARA GUI can run on any node connected to the TARA server; such a node is called the TARA GUI host. The Teradata TARA GUI acts as the user interface to the TARA system. The Teradata Extension for Tivoli Storage Manager runs on a node called the TIVBAR host. The TIVBAR host must also be a BAR server node. The Teradata Extension for Tivoli Storage Teradata Extension for Tivoli Storage Manager Administrator Guide 25

26 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation Manager is a Teradata-provided library file that interfaces with the ARCMAIN module, which is installed on the BAR server node during a Tivoli backup or restore job. Installation Location Install all three packages on a single server, each package on a different server, or any combination in between. Base the decision about where the TARA components are installed on the availability of servers and the anticipated usage and load on those servers. For installation in a multiple BAR server environment, these recommendations apply: Install the TARA server on only one of the BAR servers. Install the Teradata Extension for Tivoli Storage Manager on every BAR server that is part of the Tivoli and TARA configuration. Install the Teradata TARA GUI on either or both of the sets of components that will be used as the administrative interface to TARA: BAR servers Workstations Installation Order There are restrictions on the order of installation: Install the TARA server before the Teradata Extension for Tivoli Storage Manager. Install any product dependencies before installing the required TARA package (dependencies are noted in the next sections). Installation of Teradata TARA Components on Linux To install the TARA server On the Linux server where you want the TARA server to run: 1 Install the TARA server package with the rpm utility. For example: rpm -ih taraserver i386.rpm 2 Manually execute the post-installation script. The post-installation script, taraserver_postinstall.sh, is usually located in /opt/teradata/tara/server/bin. Execute the post-installation script by typing one of the following: /var/opt/teradata/tara/server/bin/taraserver_postinstall.sh cd /var/opt/teradata/tara/server/bin./teraserver_postinstall.sh 3 At the command-line prompt for the name of the Backup Application, type t for Tivoli. 4 Enter the user name for the owner of the TARA server service. The default is taraserver, which can be selected by clicking Enter. 26 Teradata Extension for Tivoli Storage Manager Administrator Guide

27 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 5 Enter the user home directory. The default is /home/taraserver, which can be selected by clicking Enter. At the conclusion of a taraserver install or upgrade, the TARA directories are: # ls -l /opt/teradata/tara total 0 drwxr-xr-x 4 root root 128 Sep 18 07:40 gui drwxr-xr-x 4 root root 96 Aug 25 16:38 nbubar lrwxrwxrwx 1 root root 29 Sep 3 12:20 server -> /var/opt/teradata/ tara/server # ls -l /etc/opt/teradata/tara/server total 0 lrwxrwxrwx 1 root root 45 Sep 3 12:20 defaults ->/var/opt/teradata/ tara/server/config/defaults # ls -l /var/opt/teradata/tara/server total 19 drwxr-xr-x 2 root root 528 Oct 12 06:09 bin drwx taraserver root 112 Oct 20 08:54 config drwx taraserver root Oct 20 08:43 jir drwx taraserver root 104 Oct 20 08:43 logs drwx taraserver root 656 Oct 20 08:42 sr To install the Teradata TARA GUI On the Linux server where you want the Teradata TARA GUI to run: 1 Install the rpm version of the Java runtime routines with the rpm utility. 2 Install the Teradata TARA GUI package with the rpm utility. For example: rpm -ih taragui i386.rpm The Teradata TARA GUI package has no post-installation script. Note: A dependency clause is included in the Teradata TARA GUI's rpm file to check for the existence of the Java runtime routines. The rpm utility only verifies that the Java runtime routines are installed if they were installed with the rpm utility. If the Java runtime routines have been installed without the rpm utility, the utility does not detect them. If this occurs, the installation of the Teradata TARA GUI will fail due to a dependency error. To correct this error, uninstall the Java runtime routines and then reinstall the rpm version of the Java runtime routines with the rpm utility. To install the Teradata Extension for Tivoli Storage Manager On the Linux server where you want the Teradata Extension for Tivoli Storage Manager to run: 1 Install the TTU packages for Teradata ICU, Teradata GSS, PIOM, CLIV2, and ARC with the rpm utility. 2 Install the Teradata Extension for Tivoli Storage Manager package with the rpm utility. For example: Teradata Extension for Tivoli Storage Manager Administrator Guide 27

28 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation rpm -ih tivbar i386.rpm 3 Execute the post-installation script by entering one of the following: /opt/teradata/tara/tivbar/bin/tivbar_postinstall.sh cd /opt/teradata/tara/tivbar/bin./tivbar_postinstall.sh The post-installation script, tivbar_postinstall.sh, is usually located in /opt/teradata/tara/ tivbar/bin. As the message indicates, the post-install script designates the local server as a BAR server and sets up the required TARA client elements. Verify the taraserver process is active in its designated BAR server, then: 1 Click Enter. 2 At the prompt, enter the machine name where the taraserver process is running. The default is localhost, which can be selected by clicking Enter. Installation of Teradata TARA Components on Windows The installation order of Teradata TARA components on Windows is: 1 TARA server 2 Teradata Extension for Tivoli Storage Manager and Teradata TARA GUI, in any order (installation instructions are given for the Teradata Extension for Tivoli Storage Manager first) To install the TARA server 1 Do one of the following: Download the TARA server (taraserver ) from the Teradata Software Server at: Save the file to your system. Go to Windows\TARA Server\setup.exe on the Teradata Extension for Tivoli Storage ManagerCD. 2 Double-click setup.exe. (If the Backup Application is not installed, an error message displays. Click Yes to continue with the installation.) 3 Do one of the following: If this is a new installation of the TARA server, proceed to step 6. If this is a reinstallation of taraserver , or taraserver was previously removed with the Windows Add or Remove Programs, select Remove when a screen displays the choice of modifying, repairing, or removing the program. Click Next. 28 Teradata Extension for Tivoli Storage Manager Administrator Guide

29 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 4 Click OK when asked to verify if the prior application should be removed. An Uninstall Complete dialog box verifies the removal of the TARA server. 5 Click Finish. 6 The TARA Server - InstallShield Wizard dialog box appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 29

30 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 7 Click Next. The license agreement appears. 8 To accept the agreement and install the TARA server, click Yes. The Choose Destination Location dialog box appears. For an installation location different than what is shown in Destination Folder, click Browse and select an alternate location. 9 Click Next. The Start Copying Files dialog box appears. 10 Click Next if the destination folder is correct. The Setup Status dialog box displays installation status, then displays that installation is complete. 11 Click Finish. 12 At the command-line prompt, type t to install Tivoli, then click Enter. 30 Teradata Extension for Tivoli Storage Manager Administrator Guide

31 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 13 Enter the password for the administrator. You will be prompted to re-enter it. That completes the TARA Server installation. Note: This password must be used for logging on to the TARA Server when using the TARA GUI. It also must be used with the utilities. See Chapter 6: Teradata TARA Command-Line Utilities. 14 Press any key to continue, as prompted. To install the Teradata Extension for Tivoli Storage Manager 1 Double-click setup.exe. If the TSM Backup-Archive Client is not installed, a warning message appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 31

32 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation Note: If the warning message appears, cancel installation and install TSM Client 5.5 before reinstalling the Teradata Extension for Tivoli Storage Manager. 2 Do one of the following: If this is a new installation of the Teradata Extension for Tivoli Storage Manager, proceed to step 3. If this is a reinstallation of tarativbar , or tarativbar was previously removed with the Windows Add or Remove Programs, select Remove when the screen displays the choice of modifying, repairing, or removing the program. InstallShield Wizard Completed verifies the removal of TARA TIVBAR. Go to step Click OK. The TARA TIVBAR welcome screen appears. 32 Teradata Extension for Tivoli Storage Manager Administrator Guide

33 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 4 Click Next. A license agreement appears. 5 If you agree with the terms of the license, select the radio button indicating consent, then click Next. Destination Folder appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 33

34 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 6 Accept the default destination, or click Change to browse for another folder. Click Next. Ready to Install the Program appears. 7 Click Install. Status of the installation is displayed. When installation is complete, a dialog appears indicating completed installation. 8 Click Finish. A command-line interface opens. 9 Choose the path for the baruser home directory, following these rules: Choose a folder that already exists. Include a drive letter, followed by a colon (:) at the beginning of the path. Include a backslash (\) at the end of the path. 34 Teradata Extension for Tivoli Storage Manager Administrator Guide

35 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation The script automatically appends the name baruser to the path. If no path is entered, the default path, C:\Documents and Settings\, is created. 10 Click Enter. The baruser directory is created. 11 At the prompt for the name of the TARA server host, enter the name of the BAR server where the TARA server is running. Click Enter. The default is localhost. 12 Click Enter to complete the postinstall script. A connection is made to the TARA server host. 13 Click any key to continue. InstallShield Wizard Completed appears. 14 Click Finish. The Teradata Extension for Tivoli Storage Manager has been successfully installed. To install the Teradata TARA GUI 1 From the Teradata Extension for Tivoli Storage Manager CD, double-click Windows\TARA GUI\setup.exe. Note: If this is a reinstallation of the TARA GUI, the prior copy will be removed. Click Finish to complete uninstallation, then double-click Windows\TARA GUI\setup.exe again. 2 The TARA GUI InstallShield Wizard welcome screen appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 35

36 Chapter 2: Teradata TARA Installation and Uninstallation Teradata TARA Installation 3 Click Next. The license agreement appears. 4 To accept the agreement and install the Teradata TARA GUI, click Yes. The Choose Destination Location dialog box appears. 5 For an installation location different than what is shown in Destination Folder, click Browse and select an alternate location. Otherwise, click Next. Start Copying Files is displayed with the specified destination. 6 Click Next if the destination folder is correct. The setup status is shown, then a message appears when installation is complete. 36 Teradata Extension for Tivoli Storage Manager Administrator Guide

37 Chapter 2: Teradata TARA Installation and Uninstallation Installed Components 7 To create a shortcut icon on the desktop, select that option. Then click Finish. The xinetd Process on Linux The xinetd process is similar in functionality to the inetd process, which starts programs that provide Internet services. The xinetd process is automatically disabled. To enable xinetd in SUSE: 1 Click Control Center>YAST>Network Services (inetd). 2 Click Enable. 3 Click Finish, then OK. The xinetd process is not necessary for Teradata TARA, however, it is vital for Tivoli software. Installed Components This section includes information on which items were installed and their location. The install path for the TARA directories and files is: /opt/teradata/tara for Linux \Program Files\Teradata\Teradata TARA for Windows The install path is referenced by install_path. There are three TARA-related install packages: TARA server install package Teradata TARA GUI install package Teradata Extension for Tivoli Storage Manager install package Teradata Extension for Tivoli Storage Manager Administrator Guide 37

38 Chapter 2: Teradata TARA Installation and Uninstallation Installed Components TARA Server Package The Windows install package and Linux taraserver_postinstall.sh script take the actions described in 4 upon installation of the TARA server package. 4: Actions Taken when TARA Server Package Installed Action Creates a new login account. Sets up the TARA server to run as a service on the TARA server host. Creates the TARA server install_path directory, /opt/teradata/tara/server. Details The user specifies the account name and home directory; the defaults are taraserver and /home/taraserver. Note: To install the TARA server on the same node as the Teradata Extension for Tivoli Storage Manager, do not change the TARA server's login information to baruser and /home/baruser. The packages cannot share the baruser account. Do not change the baruser account for the Teradata Extension for Tivoli Storage Manager. Instead, change the default taraserver account for the TARA server. None Under this directory, the taraserver_postinstall.sh script creates the bin, jir, sr, logs, and config subdirectories, which are described in 5. 5: Subdirectories of taraserver_postinstall.sh Subdirectory Name /bin /jir /sr /logs /config Description of Subdirectory Contains the TARA server executable file, plus the executable files for those programs that are needed to support the TARA server. The executable files provide these command-line utilities: taralaunch This utility launches a backup or restore job from the Script Repository on a specified TARA server. tarasetcfg This utility causes the TARA server to reset its configuration parameters by reading the defaults configuration file again. This is the Job Information Repository. These are binary files that contain the most current results of each backup or restore job that the TARA server controls. These files are a combination of binary and ascii, and should not be viewed and edited through a manual editor. This is the backup/restore script repository for the TARA server. Edit these scripts with the Edit feature of the Teradata TARA GUI. Contains the trace entries that the TARA server generates. Normally, the trace level is set to minimum, but can be increased in the event that troubleshooting becomes necessary. Contains the file named defaults. This file contains the default configuration parameters that the TARA server uses during initialization. Although this file is text-readable, it is advisable to modify it only through the Teradata TARA GUI, and not manually through a text editor. Note: Specifying the size of the log file must be done manually in defaults. 38 Teradata Extension for Tivoli Storage Manager Administrator Guide

39 Chapter 2: Teradata TARA Installation and Uninstallation Installed Components Teradata TARA GUI Package When the Teradata TARA GUI package is installed, the Teradata TARA GUI install_path directory, /opt/teradata/tara/gui, is created. Under this directory, the bin subdirectory is created. This subdirectory contains the files described in 6. 6: Files in bin Subdirectory File Teradata TARA GUI executable file Script file Details This file is called taragui.jar. The script file is called taragui and is located in /opt/teradata/tara/gui/bin. The user can launch the Java-based Teradata TARA GUI with the script file. Execute taragui by entering one of the following: export DISPLAY=<your_IP_address or host_alias> /opt/teradata/tara/gui/bin/taragui & cd /opt/teradata/tara/gui/bin./taragui & The command-line utilities are useful for field personnel who might not have access to the Teradata TARA GUI. Execute the command-line utilities by entering one of the following: /opt/teradata/tara/gui/bin/<utility name> <parameters> cd /opt/teradata/tara/gui/bin./<utility name> <parameters> Teradata Extension for Tivoli Storage Manager Package The Windows install package and the Linux tivbar_postinstall.sh script take these actions upon installation of the Teradata Extension for Tivoli Storage Manager package: Creates a new login account. The user cannot modify the account name and home directory. The login account is baruser and the home directory is /home/baruser. Note: To install the TARA server on the same node as the Teradata Extension for Tivoli Storage Manager, do not change the TARA server's login information to baruser and / home/baruser. The packages cannot share the baruser account. It is not possible to change the baruser account for the Teradata Extension for Tivoli Storage Manager, therefore change the default taraserver account for the TARA server. Copies runarctiv.bat to the baruser's home directory: /home/baruser. Sets up a path and symbolic link to allow access to the Teradata Extension for Tivoli Storage Manager's library file, libtivbar.so, which resides in /opt/teradata/tara/tivbar/lib. Teradata Extension for Tivoli Storage Manager Administrator Guide 39

40 Chapter 2: Teradata TARA Installation and Uninstallation Uninstallation on Windows Creates the Teradata Extension for Tivoli Storage Manager install_path directory, /opt/ teradata/tara/tivbar. Under this directory, the tivbar_postinstall.sh script creates the bin and lib subdirectories: Subdirectory Name /bin /lib /logs Description of Subdirectory Contains the executable files for those programs that are needed to support the Teradata Extension for Tivoli Storage Manager. Contains the Teradata Extension for Tivoli Storage Manager library file, libtivbar.so, which is used in conjunction with ARCMAIN during a Tivoli backup or restore job. Contains tivbar and taratddsmc log files. Uninstallation on Windows During installation, Teradata TARA creates folders and registry entries under Program Files\Teradata\Teradata TARA, then copies required files under the folders. When uninstalling Teradata TARA components, remove all of the folders and registry entries. This means, in some cases, that manual deletion is necessary in addition to using Windows Add or Remove Programs. 7 lists the folders that are created during installation, the associated registry entries, and information on manually removing files, folders, and registry entries. Typically, manual deletion is necessary if files were manually modified. 7: Folders and Registry Entries Folder Created During Installation Registry Entry Created During Installation Manual Deletion During Uninstallation gui HKEY_LOCAL_MACHINE\TERADATA\TARA Gui This folder and its registry entry are automatically removed during uninstallation. However, if any of the files under this folder were manually modified, the file is retained with the folder and the registry entry is not deleted. Manually delete the folder and the registry entry. 40 Teradata Extension for Tivoli Storage Manager Administrator Guide

41 Chapter 2: Teradata TARA Installation and Uninstallation Uninstallation on Linux 7: Folders and Registry Entries (continued) Folder Created During Installation Registry Entry Created During Installation Manual Deletion During Uninstallation server HKEY_LOCAL_MACHINE\TERADATA\TARA Server The uninstallation process does not automatically clear all folders and registry details. Manual deletion of files is necessary in some of the subfolders: bin This folder is automatically removed during uninstallation. However, if any of the files under this folder were manually modified, the file is retained with the folder. Manually delete the file and folder. config, jir, logs, sr These folders are not automatically deleted. Manually delete these folders and registry entries. tivbar HKEY_LOCAL_MACHINE\ TERADATA\tivbar This folder and its registry entry are automatically removed during uninstallation. However, if any of the files under this folder were manually modified, the file is retained with the folder and the registry entry is not deleted. Manually delete the folder and the registry entry. Other folders and files that require manual deletion are: \home\baruser the defaults file in \config Uninstallation on Linux To uninstall Teradata TARA components, run rpm -e <name_of_the_component> For example: rpm -e taragui rpm -e taraserver rpm -e tarativbar The uninstallation process does not delete all files. (Some files may be retained for specific reasons.) Also, if any of the files under the TARA component directory were manually modified, they are retained with the directory. Manual deletion of those files is necessary (if they are no longer needed). The list of directories and files not deleted after uninstallation are: config Teradata Extension for Tivoli Storage Manager Administrator Guide 41

42 Chapter 2: Teradata TARA Installation and Uninstallation Uninstallation on Linux jir logs sr the defaults file in /config /home/baruser 42 Teradata Extension for Tivoli Storage Manager Administrator Guide

43 CHAPTER 3 TSM and Teradata TARA Configuration Configure TSM before configuring Teradata TARA: Configure TSM for Teradata Backups Configure the TARA Server Configure the TARA Server GUI To configure the size of the log file, add an entry in the defaults file. See Configure the Log File. Configure TSM for Teradata Backups TSM Server Configuration A Teradata backup can be a backup of an entire Teradata Database, a selected database, or a selected table. To perform a Teradata backup, configure the TSM server first, the TSM client second, then set options for TSM. Before performing any Teradata backups, ensure that the TSM policy objects and TSM client nodes are properly configured in the TSM server. TSM Policy Objects TSM policy objects manage how data is stored, where client data is stored, the number of maintained versions, and the length of time those versions are stored. TSM allows a variety of configurations using TSM policy objects, but regardless of the configuration, Teradata Extension for Tivoli Storage Manager requires a backup copy group policy object. The backup copy group policy object can be preexisting or newly-created, but only TSM backup object types are supported. 8 lists TSM policy object fields that control the removal of inactive objects from storage. Objects become inactive when a backup is performed with the same name as an object that is already stored on the server. See Overview of Backup Data Storage on page : Fields to Consider for the Backup Copy Group Field Description Default Versions Data Deleted (VERDELETED) Number of inactive versions, if active versions do not exist. 1 Teradata Extension for Tivoli Storage Manager Administrator Guide 43

44 Chapter 3: TSM and Teradata TARA Configuration Configure TSM for Teradata Backups 8: Fields to Consider for the Backup Copy Group (continued) Field Description Default Versions Data Exist (VEREXISTS) Number of inactive versions, if active versions exist. 1 Retain Extra Versions (RETEXTRA) Retain Only Version (RETONLY) Number of days to keep the last inactive versions, if active versions do not exist. Number of days to keep the last inactive versions, if active versions do not exist TSM Client Node In the TSM software, by default, a client node can access only the backup storage objects that it creates. For instance, when a backup is performed on client node1, all ARCMAIN backups are registered in the TSM server catalog as belonging to node1 and all other nodes are prevented from accessing the storage objects created by node1. However, it is possible to grant authorization for nodes to access other backups by creating a pseudo node that is used by all clients performing backups. To create a pseudo node, use the TSM register node command that provides the node name and password. Then set the BACKDELETE option to YES. If this option is not set to YES, backup objects cannot be deleted with the TDDSMC utility. For more information, see Appendix C: The TDDSMC Administrative Utility. For information about the TSM register node command, refer to the Tivoli Storage Manager Administrators Guide on the IBM Web site at TSM Server Options Depending on site requirements, the TSM server option values for the TSM server (dsmserv.opt) and the TSM Storage Agent (dsmsta.opt) might need adjustment. 9 describes these options. 9: TSM Server Options TSM Server Option COMMTIMEOUT IDLETIMEOUT Description Specifies how long the server waits for an expected client message during an operation that causes a TSM database update. If a message does not arrive before the specified wait period, the server ends the session with the client. To prevent clients from timing out while backing up large files or during a heavy network load, increase the time-out value. Specifies the amount of time, in minutes, that a client session can be idle before the server cancels the session. To prevent clients from timing out due to a heavy network load in the environment, increase the time-out value. Note: If the time-out value is increased, a large number of idle sessions could prevent other users from connecting to the server. 44 Teradata Extension for Tivoli Storage Manager Administrator Guide

45 Chapter 3: TSM and Teradata TARA Configuration Configure TSM for Teradata Backups 9: TSM Server Options (continued) TSM Server Option RESOURCETIMEOUT TXNGROUPMAX Description Specifies the maximum number of minutes that a storage agent waits for a resource on the server. The default value is 60 minutes. The minimum value is 1 minute. Indicates the maximum number of logical files (client files) that a client can send to the server in a single transaction. The server might create multiple aggregates for a single transaction, depending on the size of the transaction. The TXNGROUPMAX option controls the number of files allowed in a transaction. Set this option to Although the maximum value allowed is 65000, TSM limits the number of objects restored at the same time to 4080 objects. Teradata Extension for Tivoli Storage Manager maps ARCMAIN backup files to a series of smaller storage objects or files segments with an object size of 2 GB. Therefore, the maximum size of a single backup cannot exceed 4080 * 2 GB, or approximately 8.1 TB. TSM Client Options Every time an archive or restore job is run, Teradata TARA creates an options file and sets DSMI_CONFIG to point to this file. Options provided through the Tivoli tab of the TARA Server Configuration dialog box (see Step 4 - Configure Tivoli Information on page 54) creates <job_id>.opt. However, when a job requires overriding the node name and password, or requires more parameters, click ManagementClass in the Script Options dialog box when archiving (see step 9 on page 65). The Management Class Selection dialog box appears, in which the node name, password, and user parameters can be changed. 10 describes client user and client system options files. 10: TSM Client Options File Characteristics Operating System TSM Client Options Files Description Directory or Folder Linux dsm.sys Specifies client system options: Servers to contact for services Communications options for each server Authorization options Archive processing options Scheduling options /opt/tivoli/tsm/client/api/bin/dsm.sys <job_id>.opt Specifies client user options. /home/baruser Windows <job_id>.opt Teradata Extension for Tivoli Storage Manager Administrator Guide 45

46 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server GUI The Linux Client System File Note: The TSM administrator gives the Teradata DBA write permission for dsm.sys, the client system file. Configuration choices made through the Tivoli tab of the TARA Server Configuration dialog box are appended to dsm.sys. If only the existing information in dsm.sys is needed (that is, no configuration information should be appended to that file) enter the Server Name only in the Tivoli tab of the TARA Server Configuration dialog box. Leave all other boxes in the dialog box blank. A <job_id>.opt file is also created, which contains the servername that points to the correct server stanza in dsm.sys. Teradata TARA sets DSMI_CONFIG to point to <job_id>.opt when a job runs. Configure the TARA Server GUI Use the Teradata TARA GUI for this procedure. After opening the Teradata Tiered Archive/Restore Architecture dialog box, use this procedure to configure the TARA server on which the Teradata TARA GUI is installed. To configure TARA server GUI 1 Click Settings>Graphical User Interface Configuration. The Graphic User Interface Configuration dialog box appears. 46 Teradata Extension for Tivoli Storage Manager Administrator Guide

47 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server GUI TARA Server Port 2 The localhost name is the default and appears in the TARA Server box when the GUI is first run. Enter another TARA server name if the server on which the Teradata TARA GUI is installed changes. 3 The TCP port on which the TARA server listens for GUI and ARC connections appears in the TARA Server Port Number box. The default is and appears when the GUI is first run. 4 Click Apply to apply changes. By selecting the TARA Server Port tab, the port number can be changed. (The default port number is ) Changing the Port Number 1 Verify the Tara Server is idle. No jobs can be running when you change the port number. (The port number will be used later by the GUIs.) 2 The TARA GUI has a panel in the TARA Server Configuration screen that allows you to change the port number. Select the TARA Server Port tab. 3 Enter the new TARA Server Port Number. Click OK. 4 From the Teradata Tiered Archive/Restore Architecture screen, select Settings>Graphical User Interface Configuration. Teradata Extension for Tivoli Storage Manager Administrator Guide 47

48 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server GUI 5 Enter the new Tara Server Port Number. Click OK. 6 Close all the existing TARA User Interface (UI) windows. 7 Restart the TARA Server and the TARA Client services. 8 Double-click or click Start>All Programs>Teradata Client>TARA GUI. 9 Logon to the TARA Server. Note: If the port is not changed on the client, change the port number in the config file in the home/baruser directory of the client. Note: For any of the TARA command line utilities, you must use the -P option to specify the correct TARA server port after changing the port number. Otherwise, the utilities will continue to use the default port number which is Increasing the Java Heap Size Increasing the Java heap size is necessary if the TARA GUI will monitor a job whose ARC output causes the GUI to exceed the default heap size of the Java Virtual Machine (JVM). A symptom of exceeding the default size is the GUI may freeze. If this happens, close the existing TARA GUI. For Linux, modify the script for the TARA GUI to include this JAVA heap size extension: -Xmx512m -jar "<path to Teradata taragui>\bin\taragui.jar" For Windows, modify the TARA GUI desktop icon to include the Java heap size extension: C:\WINDOWS\system32\java.exe -Xmx512m -jar "<path to Teradata taragui>\bin\taragui.jar" This increases the maximum heap size from 128 MB to 512 MB. 48 Teradata Extension for Tivoli Storage Manager Administrator Guide

49 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server Configure the TARA Server Use the Teradata TARA GUI for this procedure. There is a required order of configuration after a new installation of Teradata TARA. The first time after installation, define at least one of each of the following components before proceeding to the next definition. Follow the order given below: 1 Teradata Database system (refer to To configure the Teradata Database system on page 49) 2 Clients system (refer to To configure the client systems on page 51) 3 Client Groups (refer to To configure the client groups on page 53) 4 Tivoli information (refer to To configure Tivoli information on page 54) Click Refresh to populate the Client-Management Class Association and Available Management Classes columns. Note: Do not click Apply until you have completed these four steps. Applying these changes before defining the Tivoli information results in an external query failure. Step 1 - Configure the Teradata Database System After a new installation of Teradata TARA, the first step to configuring the TARA server is defining the Teradata Database system. Refer to Configure the TARA Server for information on the other steps of configuration. If this is not a new installation of Teradata TARA, there is no required order of configuration. To configure the Teradata Database system Click Teradata Tiered Archive/Restore Architecture>Settings>Server Configuration. The TARA Server Configuration dialog box appears with the Teradata tab selected by default. Teradata Extension for Tivoli Storage Manager Administrator Guide 49

50 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 1 Do one of the following: From the Teradata System list, select the Teradata Database system to configure for the TARA server. The list contains display names, not TDPID names. Click New to add a Teradata Database system name. To remove a name from the list, select the name, then click Remove. 2 In Display Name, type the name that should appear for this TDPID within the Teradata TARA GUI environment. Usually, the display name and the Teradata TDPID name are the same. 3 In Teradata TDPID, type the Teradata Database machine name. Usually, the display name and the Teradata TDPID name are the same. 4 Enter a Browse user name in Browse User and an associated password in Password; both must be valid within the target Teradata Database. The Browse user and password form the Teradata Database logon information that the TARA server uses to query the Teradata Database. 5 Enter an ARC user name in ARC User and an associated password in Password; you must have backup and restore privileges for the ARC User name that you specify. 50 Teradata Extension for Tivoli Storage Manager Administrator Guide

51 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 6 Click Single stream or Multi stream. For Multi stream, type the number of streams in the Multi stream box. The number of streams is essentially the number of BAR server tape drives that are configured. For example, if there are four BAR servers, each having two tape drives, enter eight streams. 7 In Default Session Count, the default for the selected database is set in the Teradata tab of the TARA Server Configuration dialog box. A general rule is to have one session per amp being archived in the stream. An adequate number of parallel ARC sessions per stream are necessary to keep data moving. Too few sessions cause ARCMAIN to be the bottleneck during archival. Too many sessions are a waste of resources as some of the sessions remain idle. Refer to Teradata Archive/Recovery Utility Reference for more detail. 8 Select the Clients tab of the TARA Server Configuration dialog box, then go to To configure the client systems. Step 2 - Configure the Client Systems After a new installation of Teradata TARA, the second step to configuring the TARA server is defining the client systems. Refer to Configure the TARA Server on page 49 for information on the other steps of configuration. If this is not a new installation of Teradata TARA, there is no required order of configuration. To configure the client systems Select the Clients tab of the TARA Server Configuration dialog box. Teradata Extension for Tivoli Storage Manager Administrator Guide 51

52 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 1 Do one of the following: Select a client system from the Client System list. Click New to indicate information for a new client system. To remove a client system from the configuration, select the client system from the Client System list, then click Remove. 2 Do one of the following: In Display Name, enter the client name that should appear for this client within the Teradata TARA GUI environment. (It is not necessary for the display name to match the system name.) Click New to change the client system information. The Display Name box now displays New Client Machine. Enter a new display name in the box. 3 Enter the system name of the client node in Client Machine Name. 4 Enter the maximum streams per job in Max Streams Per Job. Each stream is a portion of the entire backup job and consists of an ARCMAIN process sending to or receiving from Tivoli. 52 Teradata Extension for Tivoli Storage Manager Administrator Guide

53 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 5 Select the Client Groups tab of the TARA Server Configuration dialog box, then go to To configure the client groups. Step 3 - Configure the Client Groups After a new installation of Teradata TARA, the third step to configuring the TARA server is defining the client groups. Refer to Configure the TARA Server on page 49 for information on the other steps of configuration. If this is not a new installation of Teradata TARA, there is no required order of configuration. To configure the client groups Select the Client Groups tab of the TARA Server Configuration dialog box. 1 Do one of the following: From the Client Group list, select a client group. Click New to add a new client group to the configuration. To remove a client group from the configuration, select the group in the Client Group list, then click Remove. Teradata Extension for Tivoli Storage Manager Administrator Guide 53

54 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 2 In the Display Name box, type the client group name that should appear for this client group within the Teradata TARA GUI environment. It is not necessary for the display name to match the system name. 3 The Selected Clients column contains the clients that have been added to a client group. To remove a client from the group, highlight the client, then click Remove. The client name is then transferred to the Available Clients column. 4 The Available Clients column contains the clients that can be added to a client group. Highlight the client, then click Add. The client name appears in the Selected Clients column. 5 To move a client up in the order in which it is used for backup, highlight the client in the Selected Clients column, then click Move Up. If there are more clients than streams, the client that appears first will be used for backup. The first client defined becomes the ARC master in a multi-stream job. The remaining clients rely on the ARC master to provide direction on what and how to run the backup or restore operation. To move a client down in the order in which it is used for backup, highlight the client in the Selected Clients column, then click Move Down. 6 Select the Tivoli tab of the TARA Server Configuration dialog box, then go to To configure Tivoli information. Step 4 - Configure Tivoli Information After a new installation of Teradata TARA, the fourth step to configuring the TARA server is configuring Tivoli information. This configuration information will be included in <job_id>.opt, the TSM client options file that is dynamically created when a TARA job is launched. Refer to Configure the TARA Server on page 49 for information on the other steps of configuration. If this is not a new installation of Teradata TARA, there is no required order of configuration. To configure Tivoli information Select the Tivoli tab of the TARA Server Configuration dialog box. 54 Teradata Extension for Tivoli Storage Manager Administrator Guide

55 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 1 Do one of the following: Click ConfigureLANFree for LAN-free mode, which is recommended for TSM. The LAN Free dialog box appears. Proceed to step 2. Clear the Enable LAN Free button for LAN mode. Proceed to step 4. 2 Select the communication method between the storage agent and the client from CommMethod. Note: For Linux systems operating in LAN-Free mode, select TCPIP. The Shared Memory communication method is not supported. For more details, refer to IBM Tivoli Storage Manager 5.5 Administrator's Guide. Teradata Extension for Tivoli Storage Manager Administrator Guide 55

56 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 3 Depending on the communication method selected, in: TCPPort, enter the TCP port to be used for communication between a client and the storage agent SHMPort, enter the Shared Memory port to be used for processing between a client and the SAN-attached storage device NamedPipeName, enter the name of the named pipe to be used for communication between the client and the storage agent Click OK. 4 In Server Name, enter the name of the TSM server instance. If the TSM client is on Linux, the server name identifies the TSM server stanza, as listed in dsm.sys. 5 In TCPServer Address, the address of the TSM server is displayed. Or, enter another address. 6 Communication methods listed in the Communication drop-down list enable communication between the TSM server and the client: If LAN-free mode is enabled on Windows, TCPIP is the only allowed communication protocol. Port is the server s TCP/IP port address. The default value is If Sharedmem is selected (for Linux operating systems), Port is the port address where the TSM server establishes a Shared Memory connection. If Namedpipes is selected, Name becomes enabled. Enter the name of the named pipe. 7 Enter the TSM client node name in Node Name. The node name is in the TSM options file. The node name identifies the workstation to the TSM server. 8 Enter the password assigned to the TSM client node in Password. 9 (Optional) In User Parameters, enter any other TSM client options, for example tcpwindowsize 63 or diskbuffsize 64. Refer to TSM Client Options on page 45 and Tivoli documentation for other client options. 10 In the Client Group drop-down list, the client group that was configured using the Client Groups tab appears. Or, select another group from the drop-down list and click Refresh to refresh the list of available clients under Client-Management Class Association. Click Default to set the client group displayed in the Client Group drop-down list the default. 11 The Enter Management Class Name drop-down list contains management classes listed in Available Management Classes. To add or delete existing management classes, do one of the following: To add a management class, enter the name. Click to add the management class to the Available Management Classes list. To delete a management class, select it from Enter Management Class Name and click to delete it from the Available Management Classes list. 12 Client-Management Class Association lists the management classes that have been added to a client node. Expand the tree next to the client name to view the management class. 56 Teradata Extension for Tivoli Storage Manager Administrator Guide

57 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server 13 Do one of the following to add or delete a management class: To add a management class to the client node, highlight the: Client in Client-Management Class Association Management class in Available Management Classes Click Add. The management class is added to the client. To delete a management class from the client, highlight the management class listed under the client in Client-Management Class Association. Click Remove. 14 (Optional) Do one of the following to change the order in which a management class is used for a backup or restore job: To move a management class up, highlight it in the Client-Management Class Association list. Click Move Up. If there are more management classes than streams, the management class that appears first will be used for the backup or restore job. To move a management class down, highlight it in the Client-Management Class Association list. Click Move Down. 15 Click Apply to apply changes. Select the ARC Options tab of the TARA Server Configuration dialog box, then go to To configure ARC options. Step 5 - Configure ARC Options If this is a new installation of Teradata TARA, configure ARC options only after you have completed the first four steps described in Configure the TARA Server on page 49. If this is not a new installation of Teradata TARA, there is no required order of configuration. To configure ARC options Select the ARC Options tab in the TARA Server Configuration dialog box. Teradata Extension for Tivoli Storage Manager Administrator Guide 57

58 Chapter 3: TSM and Teradata TARA Configuration Configure the TARA Server Step 6 - Configure Logging 1 [Optional] Select Use Catalog to specify positioning data, so that when an object is restored, Tivoli can locate it without searching the entire tape. 2 [Optional] Select Use Checksum Verification to verify that what it is archiving or restoring is valid data. 3 [Optional] Select a character set other than ASCII in the Default Character Set list. ASCII is the default. Refer to Teradata Archive/Recovery Utility Reference for details on valid ARCMAIN command-line options. 4 [Optional] In Extra ARC Options, enter any ARCMAIN command-line options that are not part of the GUI ARC build flow. If this is a new installation of Teradata TARA, configure logging only after you have completed the first four steps described in Configure the TARA Server on page 49. If this is not a new installation of Teradata TARA, there is no required order of configuration. 58 Teradata Extension for Tivoli Storage Manager Administrator Guide

59 Chapter 3: TSM and Teradata TARA Configuration Configure the Log File The logging levels of the individual components of the TARA server are pre-set and cannot be changed from the GUI unless the Override Global Log Level check box is selected. When the box is selected, Global Log Setting is unavailable and logging for each TARA server component can be customized. Do not customize the logging settings unless Teradata Global Support recommends it. The Global Log level is pre-set to 0. This is the minimum, or normal, log level. The maximum level is 5. Increasing the Global Log level adds verbosity to the log for each of the TARA server components. Configure the Log File The default size of the Linux TARA server's logs file is 2GB. When this limit is reached, the TARA server resets the file to a length of 0 before writing more log entries. Adjust the logs file maximum length to a value less than 2GB by adding an entry within the [Defaults] stanza of the /opt/teradata/tara/server/config/defaults file: filesize=numofbytes Teradata Extension for Tivoli Storage Manager Administrator Guide 59

60 Chapter 3: TSM and Teradata TARA Configuration Configure the Log File For example, to set the log file size to exactly 500MB (500 * 1024): filesize= Do not set the value greater than 2GB. Doing so can cause the TARA server to become unresponsive. 60 Teradata Extension for Tivoli Storage Manager Administrator Guide

61 CHAPTER 4 Backup and Restore Using the GUI After completing installation and configuration, start Teradata backup and restore operations through the Teradata TARA GUI: For backup and restore operations, see these topics: Starting the Teradata TARA GUI Archiving a Database Object Restoring a Database Object Viewing Job History Extensions for Job Files Starting the Teradata TARA GUI To start the Teradata TARA GUI 1 To check the status of the TARA server service, type: /etc/init.d/tdtaraserver status 2 To start the TARA server service, type: /etc/init.d/tdtaraserver start 3 To start the Teradata TARA GUI: For Linux, type one of the following: /opt/teradata/tara/gui/bin/taragui & cd /opt/teradata/tara/gui/bin./taragui & For Windows, do one of the following: Double-click on if you installed the TARA GUI icon on your desktop. Click Start>All Programs>Teradata Client>TARA GUI. The Logon to TARA Server screen appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 61

62 Chapter 4: Backup and Restore Using the GUI Starting the Teradata TARA GUI The Teradata Tiered Archive/Restore Architecture dialog box appears. 62 Teradata Extension for Tivoli Storage Manager Administrator Guide

63 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object Archiving a Database Object To archive a database object Use the next procedure to run an archive operation. 1 Click Teradata Tiered Archive/Restore Architecture>Task>Archive. The Log on to Teradata DBS dialog box appears. 2 To log on to a Teradata Database, select it from the TDPID list. 3 Type a user account name for the Teradata Database in the UserID box. 4 Type the password for the user account in the Password box, then click Connect. The ARCHIVE object selection dialog box appears. 5 In the left and right panes are database objects that are available for archival. To archive a database, highlight or select the box next to the database in the left pane. The tables of the database to be archived appear in the right pane, as shown in the next screen capture. The screen capture shows a database example without a hierarchical view. If the database: Has a hierarchical view, go to step 6. Does not have a hierarchical view, skip to step 7. 6 This screen capture shows a database with a hierarchical view. Click on a level in the left pane. The database and tables appear in the right pane. Teradata Extension for Tivoli Storage Manager Administrator Guide 63

64 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object 7 Right-click on a table in the right pane, then click Options. A dialog box for Partitioned Primary Index (PPI) options appears for that table. 8 Under Partition selection, click on one of the radio buttons: Full table, which is the default, archives the entire table All Partitions option is not valid for archive operations 64 Teradata Extension for Tivoli Storage Manager Administrator Guide

65 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object Selected Partitions archives the specified partitions Other PPI Options is not valid for archive operations. 9 From the ARCHIVE object selection File menu, click Build ARC script or click. After the database objects are selected, the Selection... dialog box appears. When you click OK, the Script Options dialog box appears. 10 Select options: Teradata Extension for Tivoli Storage Manager Administrator Guide 65

66 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object Option Job Name Description Entries in Job Name are case-sensitive. A job name must not contain any spaces, or these characters: < > ~ " *,?. \ / The maximum length of the job name for Archive and Restore scripts is 220 characters. If this limit is exceeded, an error message requests that the job name be re-entered. Description TDPID User Name Password Single stream or Multi stream Default Group Assign Clients The entry in this box reflects the TDPID with which you logged on. It is not possible to change the TDPID. The user name with which you logged on appears. To create another job for the specified database, type a new user name. The password with which you logged on appears. To create another job for the specified database using another user name and password, type the new password. Click Single stream or Multi stream. For Multi stream, type the number of streams in the Multi stream box. The number of streams is essentially the number of BAR server tape drives that are configured. For example, if there are four BAR servers, each having two tape drives, enter eight streams. The list defaults to all clients, that is, no client group. If there are many clients, select a name from the list of available client groups. Using a client group reduces the amount of selections needed when building a new archive/restore job. Each stream is defaulted to All clients. Click Assign Clients to assign a specific client (or a specific client group) to each stream. Configure Protegrity Encryption (Optional) Select ProtegrityEncryption to encrypt the job. AES128 is the default encryption algorithm. Or, select AES256 or PANAMA from the drop-down list. 66 Teradata Extension for Tivoli Storage Manager Administrator Guide

67 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object Option QueryBanding Online Backup Sessions (per stream) Extra Options Backup Application Use Catalog Verify Checksum Character set Description (Optional) Select QueryBanding. In the QueryBanding box, specify one or more pairs of names with associated values to identify the source of a query. This allows setting different priorities for different requests, and the ability to make better use of system resources. For example, enter a name and value pair, ending with a semi-colon: aaa=bbb;ccc=ddd; Note: Teradata Tools and Utilities and later is required for the query banding feature. Additionally, the backup must be between two Teradata Tools and Utilities systems for the query banding feature to work correctly. See Teradata Archive/Recovery Utility Reference for more information on query banding. (Optional) Select Online Backup to archive rows from a table at the same time update, insert, or delete operations on the table are taking place. When an online archive is initiated on a table or a database, a log is created for the specified table or separate logs are created for each table in the specified database. The log, which contains all changes to the table, is saved as a part of the archive process. When the table is restored or copied, the changes recorded in the log are used to roll back those changes in the table. The table is rolled back to the point that was established when online archive logging was started on that table. Note: Teradata Tools and Utilities is required for the online backup feature. Additionally, backups must be between two Teradata Tools and Utilities systems. See Teradata Archive/Recovery Utility Reference for more information on online archive. The default for the selected database is set in the Teradata tab of the TARA Server Configuration dialog box. A general rule is to have one session per amp being archived in the stream. An adequate number of parallel ARC sessions per stream are necessary to keep data moving. Too few sessions cause ARCMAIN to be the bottleneck during archival. Too many sessions waste resources because some of the sessions remain idle. Refer to Teradata Archive/Recovery Utility Reference for more detail. (Optional) Enter any ARCMAIN command line options that are not part of the GUI ARC build flow. IOTRACE=5, a debug parameter that ARCMAIN uses to enable a level of tracing, is the default. The default is Tivoli. (Optional) Select Use Catalog to specify positioning data, so that when an object is restored, Tivoli can locate it without searching the entire tape. Note: Teradata Tools and Utilities and later is required for the catalog feature. (Optional) Verify Checksum verifies that what it is archiving or restoring is valid data. The checkbox is selected by default. The default is ASCII. Select another character set if appropriate. Teradata Extension for Tivoli Storage Manager Administrator Guide 67

68 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object Option Management Class Description Click to display the Management Class Selection dialog box. Select one of the following: A group from Use Configuration from Group A management class for a stream after selecting Manual Selection Other Buttons Save Launch Preview Close Click Save to accept the current script. Click Launch to launch the job. (Optional) Click Preview to open the Script Editor dialog box and display the job script. The job script can be edited, then saved. Click Launch to launch the job. Click Close to close the Script Options dialog box. 11 Click Save, then Launch. The Teradata Tiered Archive/Restore Architecture dialog box displays the launched job. Under the jobname, each of the job's streams appears. To view the ARC progress for the streams, double-click on one of the streams. In the next example, the State column indicates that Stream 1 has table data. The state conditions are: (B): Build phase (only for restore operations) (D): Dictionary (for archive and restore operations) (T): Data (for archive and restore operations) 68 Teradata Extension for Tivoli Storage Manager Administrator Guide

69 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object Dictionary Only Archive A job can be created for a dictionary only archive. The Script Options screen displays the Dictionary Only field. Teradata Extension for Tivoli Storage Manager Administrator Guide 69

70 Chapter 4: Backup and Restore Using the GUI Archiving a Database Object TSM Parameters Overwrite at Run Time TARA archive and restore jobs allow the use of Tivoli Storage Manager (TSM) options such as node name and password at run time. They overwrite the node name and password options provided globally in the TARA Server Configuration - Tivoli panel. If the node name and password are provided for the Archive Script during run time, ensure they are provided when the Restore Script is created. For an archive job, access the parameters from the Script Options dialog box by pressing the ManagementClass... button as in the screen example below. For a restore job, access the parameters from the Script Options dialog box by pressing the Options button. 70 Teradata Extension for Tivoli Storage Manager Administrator Guide

71 Chapter 4: Backup and Restore Using the GUI Selecting Individual Objects to Archive or Restore Selecting Individual Objects to Archive or Restore Beginning with Teradata Database 13.0, selecting an individual view, macro, procedure, or other Teradata object to archive or restore is valid. Prior to Teradata TARA 13.0, archiving and restoring was limited to databases and tables. The prerequisites for this feature are: TARA 13.0 Teradata ARC 13.0 Teradata Database 13.0 In the next screen example, the FindExRex function in the guest database is the only object selected for archive. Teradata Extension for Tivoli Storage Manager Administrator Guide 71

72 Chapter 4: Backup and Restore Using the GUI Selecting Individual Objects to Archive or Restore 11 lists the icons that represent the objects. 11: Object Icons Icon Object Database Function Index Join Index Journal Macro 72 Teradata Extension for Tivoli Storage Manager Administrator Guide

73 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object 11: Object Icons (continued) Icon Object Procedure Trigger View Restoring a Database Object To restore a database Use the next procedure to run a restore operation. 1 Click Teradata Tiered Archive/Restore Architecture>Task>Restore. The RESTORE object selection dialog box appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 73

74 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object In the left pane are datasets (jobs). The names underneath the Datasets icon are backup images and are listed in chronological order (earliest image to latest image). Click to the left of the dataset name to expand the tree further. 2 To restore a job, select the box next to it. The name of the specified object appears in the upper right pane, and the Backup Application name in the lower right pane under Details. The screen capture shows a database example without a hierarchical view. If the database: Has a hierarchical view, go to step 3. Does not have a hierarchical view, skip to step 4. Double-click on the icon to the left of the object name to expand the tree and show the specific tables to be restored. 3 This screen capture shows a database with a hierarchical view. Double-click to navigate to a level in the left pane. The job and its tables appear in the right pane. 74 Teradata Extension for Tivoli Storage Manager Administrator Guide

75 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object 4 Right-click on the database icon or table in the right pane. A dialog box for copy and Partitioned Primary Index (PPI) options appears. 5 The options for the COPY options tab are: Teradata Extension for Tivoli Storage Manager Administrator Guide 75

76 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object Option Rename Object Disable fallback on table (NO FALLBACK) Disable journaling on table (NO JOURNAL) Replace table creator value (REPLACE CREATOR) Specify different journal table APPLY TO list Description Gives the object in the archive a different name from the target object. Copies fallback tables into non-fallback tables. If the archived table is already non-fallback, this option has no effect. Copies all tables with journaling disabled, whether journaled in the archive or not. Replaces the LastAlterUID, creator name, and Creator ID of the tables in the target database with the user ID and the current user name, that is, the user name specified in the LOGON command. Specifies that a copied database has journaling for the specified database and journal table. Identifies the tables in the target system where the change images apply. Checking any of the boxes on this tab automatically selects the COPY script option of the Script Options dialog box for restore operations. 6 On the PPI options tab, under Partition selection, click on the radio button for one of these three options: Full table, which is the default, restores the entire table All Partitions restores all partitions Selected Partitions restores the specified partitions Under the Other PPI Options portion of the dialog box, select the LOG WHERE box to specify rows to be logged to an error table for manual insertion and deletion. Select the Error table name box to enter a table name other than the default name that is shown. Note: All PPI options are valid when restoring a table. Only the All Partitions option is valid when restoring a database. 7 Click RESTORE object selection>file>build ARC script. After the database objects are selected, the Selection... dialog box appears and the Archive object selection screen closes. When you click OK, the Script Options dialog box appears. 76 Teradata Extension for Tivoli Storage Manager Administrator Guide

77 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object Select options: Option Job Name Description Entries in the Job Name box are case-sensitive. A job name must not contain any spaces, or these characters: < > ~ " *,?. \ / Note: Scripts that are created or modified manually are not checked to see if the name contains spaces or the characters listed above. The maximum length of the job name for Archive and Restore scripts is 220 characters. If this limit is exceeded, an error message requests that the job name be re-entered. Teradata Extension for Tivoli Storage Manager Administrator Guide 77

78 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object Option Description Description TDPID User Name Password SingleStream or MultiStream Default Group Assign Clients This list reflects the TDPID with which you logged on. To restore a database or table from one Teradata Database to another Teradata Database, select another TDPID from the list of TDPIDs. The user name with which you logged on appears. To create another job for the specified database using another user name and password, type the new user name. The password with which you logged on appears. To create another job for the specified database using another user name and password, type the new password. Click SingleStream or MultiStream. For MultiStream, type the number of streams in the Multi stream box. The number of streams is essentially the number of BAR server tape drives that are configured. For example, if there are four BAR servers, each having two tape drives, enter eight streams. It is possible to specify fewer streams when restoring a job than were specified when the job was archived. The list defaults to all clients, that is, no client group. If there are many clients, select a name from the list of available client groups. Using a client group reduces the amount of selections needed when building a new archive/restore job. Each stream defaults to All clients. Click Assign Clients to assign a specific client to each stream. Configure RestoreScript CopyScript Analyze QueryBanding The RestoreScript radio button is automatically selected. To copy, instead of restore an object, click CopyScript. When this option is selected, all the records are validated to ensure the proper order and proper type of records are on the tape. (Optional) Select QueryBanding. In the QueryBanding box, specify one or more pairs of names with associated values to identify the source of a query. This allows setting different priorities for different requests, and the ability to make better use of system resources. For example, enter name and value pairs, ending with a semi-colon: aaa=bbb;ccc=ddd; Note: Teradata Tools and Utilities and later is required for the query banding feature. Additionally, the backup must be between two Teradata Tools and Utilities systems for the query banding feature to work correctly. 78 Teradata Extension for Tivoli Storage Manager Administrator Guide

79 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object Option Sessions (per stream) Extra Options Use Catalog Verify CheckSum Skip Build Steps CharacterSet Description The default for the selected database is set in the Teradata tab of the TARA Server Configuration dialog box. A general rule is to have one session per amp being archived in the stream. An adequate number of parallel ARC sessions per stream are necessary to keep data moving. Too few sessions cause ARCMAIN to be the bottleneck during archival. Too many sessions waste resources because some of the sessions remain idle. Refer to Teradata Archive/Recovery Utility Reference for more detail. (Optional) Enter any ARCMAIN command line options that are not part of the GUI ARC build flow. IOTRACE=5 is the default. (Optional) Select Use Catalog to specify positioning data so that when an object is restored, Tivoli can locate it without searching the entire tape. Note: Teradata Tools and Utilities and later is required for the catalog feature. (Optional) Select this check box to verify that what it is archiving or restoring is valid data. (Optional) Select this check box to skip the build steps, which Tivoli considers idle time. If you skip the build steps now, manually run the build step outside of Tivoli after all data is restored. The default is ASCII. Select another character set if appropriate. Extra Buttons Save Launch Preview Close Click Save to accept the script options that have been selected. Click Launch to launch the job. The job appears in the Teradata Tiered Archive/Restore Architecture dialog box. (Optional) Click Preview to open the Script Editor dialog box and display the job script. Make any corrections, then click Save in the Script Editor dialog box, then Launch to launch the job. Click Close, but do not click Save, to close the dialog box without saving any changes. 8 In the Script Options dialog box, click Save, then Launch. 9 The restore job status appears in the Teradata Tiered Archive/Restore Architecture dialog box. Teradata Extension for Tivoli Storage Manager Administrator Guide 79

80 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object To restore a multistream archive with fewer streams To restore a database or table from a multistream backup when one or more of the disk or tape storage devices is unavailable, divide the restore into two or more jobs. In the next example, the database BAR_AC backup was created using four streams. Only two storage devices are available, therefore streams 1 and 2 are restored in the first job, and streams 3 and 4 in the second job. 1 Click Teradata Tiered Archive/Restore Architecture>Task>Restore. The RESTORE object selection dialog box appears. 2 Select the object to restore, then File>Build ARC Script. The Script Options dialog box appears. 3 Type a job name. 4 In Multi stream, change the number of streams to the number of streams that are available. In this example, two streams are specified. 5 Select the Skip Build Steps check box. The build step must be done only by the last restore job for this database, or separately, after all restore jobs have completed. 6 Click Save, then Launch. 80 Teradata Extension for Tivoli Storage Manager Administrator Guide

81 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object To display information on the job progress, double-click the job or stream. A dialog box appears. Select a stream to display its information in the bottom pane of the dialog box. 7 Create a new job for the remaining streams by editing the script for the job that just completed. Click Teradata Tiered Archive/Restore Architecture>Options>Edit or Preview in the Script Options dialog box. The Script Editor dialog box appears. 8 Add the keyword STREAMNAME for each stream included in this job. The value of each STREAMNAME keyword is the name of each of the remaining streams. Teradata Extension for Tivoli Storage Manager Administrator Guide 81

82 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object In the following example, the job restores the remaining two streams of the database BAR_AC backup. Dictionary Only Restore Note: In the example, the NO BUILD statement is not removed from the script, therefore a separate ARCMAIN build will be required after job completion. If the NO BUILD statement were removed from this script, ARCMAIN would automatically perform the build step. 9 Save the job with a name different from the original job name, then click Launch. View the job in the Teradata Tiered Archive/Restore Architecture dialog box and the Job History dialog box. A job can be created for a dictionary only restore. The Script Options screen displays the Dictionary Only field. 82 Teradata Extension for Tivoli Storage Manager Administrator Guide

83 Chapter 4: Backup and Restore Using the GUI Restoring a Database Object Analyze Option An Analyze option is provided on the Script Options screen. When this option is selected, all the records are validated to ensure the proper order and proper type of records are on the tape. For more details, see the Teradata Archive/Recovery Utility Reference. Teradata Extension for Tivoli Storage Manager Administrator Guide 83

84 Chapter 4: Backup and Restore Using the GUI CopyScript Options CopyScript Options Supported with TARA and later, the CopyScript Option has added two options: Rename and Copy into Same Database Copy into New Database 84 Teradata Extension for Tivoli Storage Manager Administrator Guide

85 Chapter 4: Backup and Restore Using the GUI CopyScript Options Rename and Copy into Same Database Here is the procedure for renaming and copying database objects into the same database. 1 From the Teradata Tiered Archive/Restore Architecture screen, select Task>Restore. 2 The RESTORE object selection screen appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 85

86 Chapter 4: Backup and Restore Using the GUI CopyScript Options 3 From the left panel, select a database by clicking on it, but do not check it. 4 From the right panel, select database objects by checking them. 5 Right-click within the selected database objects. The CopyScript options appear. 86 Teradata Extension for Tivoli Storage Manager Administrator Guide

87 Chapter 4: Backup and Restore Using the GUI CopyScript Options 6 Select Rename and Copy into Same Database. 7 The Rename and Copy into Same Database screen appears. 8 Enter a new name for each database object. Click OK. Teradata Extension for Tivoli Storage Manager Administrator Guide 87

88 Chapter 4: Backup and Restore Using the GUI CopyScript Options 9 From the RESTORE object selection screen, select File>Build Arc Script. 10 The Selection... dialog box appears. Click OK to confirm the database object selections. 11 The Script Options screen appears. 12 Enter the job name in the Job Name field. 13 Click Preview. 14 The Script Editor screen appears displaying the renamed database objects. 88 Teradata Extension for Tivoli Storage Manager Administrator Guide

89 Chapter 4: Backup and Restore Using the GUI CopyScript Options 15 Save the job by clicking Save when the Save Script dialog box appears. Leave the script type as not available. 16 Launch the job. Copy into New Database Here is the procedure for copying database objects into a new database. 1 From the Teradata Tiered Archive/Restore Architecture screen, select Task>Restore. 2 The RESTORE object selection screen appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 89

90 Chapter 4: Backup and Restore Using the GUI CopyScript Options 3 From the left panel, select a database by clicking on it, but don t check it. 4 From the right panel, select database objects by checking them. 90 Teradata Extension for Tivoli Storage Manager Administrator Guide

91 Chapter 4: Backup and Restore Using the GUI CopyScript Options 5 Right-click within the selected database objects. The CopyScript options appear. 6 Select Copy into New Database. The Copy Into New Database screen appears. 7 Enter the new database name and then click OK. 8 From the RESTORE object selection screen, select File>Build Arc Script. 9 The Selection... dialog box appears. Click OK to confirm the database object selections. 10 The Script Options screen appears. 11 Enter the job name in the Job Name field. 12 Click Preview. Teradata Extension for Tivoli Storage Manager Administrator Guide 91

92 Chapter 4: Backup and Restore Using the GUI Viewing Job History 13 The Script Editor screen appears displaying the database objects that will be copied into the new database. 14 Save the job by clicking Save when the Save Script dialog box appears. Leave the script type as not available. 15 Launch the job. Viewing Job History To view job history, click Teradata Tiered Archive/Restore Architecture>Task>Job Viewer. There can be large amounts of job data, which is time-consuming to search. Export functionality, described in the next procedure, makes the task easier by placing the information into html table format. Then, a search can be quickly done for any value in the table. 92 Teradata Extension for Tivoli Storage Manager Administrator Guide

93 Chapter 4: Backup and Restore Using the GUI Extensions for Job Files To export job data in html format 1 Click Teradata Tiered Archive/Restore Architecture>Task>Job Viewer. The Job History dialog box opens. 2 Click Job History>File>Export list to html. The Save dialog box opens. Save the html file in any location. Extensions for Job Files Effective with this release, there are extensions for job files. They are.arc and.res. Archive jobs have the.arc extension. Restore jobs have the.res extension. Existing jobs can be renamed so that they have the extensions. From the Teradata Tiered Archive/Restore Architecture screen, click Options and select Rename. The Rename Script dialog box appears. Teradata Extension for Tivoli Storage Manager Administrator Guide 93

94 Chapter 4: Backup and Restore Using the GUI Extensions for Job Files Select the extension for renaming the file. The other options are Edit and Delete. Select Edit. The Script Editor screen appears. 94 Teradata Extension for Tivoli Storage Manager Administrator Guide

95 Chapter 4: Backup and Restore Using the GUI Extensions for Job Files Use this screen to edit your job file. Select Delete to delete a job file. A Warning message appears. Click OK to confirm the deletion of the job file. Teradata Extension for Tivoli Storage Manager Administrator Guide 95

96 Chapter 4: Backup and Restore Using the GUI Extensions for Job Files 96 Teradata Extension for Tivoli Storage Manager Administrator Guide

97 CHAPTER 5 Taratddsmc Command-Line Utility The taratddsmc command-line utility allows database administrators and TSM administrators to delete backup objects from TSM and: View Teradata backups in the TSM server catalog (the client node and file spaces associated with those backups are displayed, not the actual files in storage) Perform maintenance activities on backups Generate reports about specific backup images created by Teradata Extension for Tivoli Storage Manager For more information, see: Overview of taratddsmc Installation Command Line Parameters Syntax Conventions Format Specifiers Taratddsmc Help Command Query TSM Command Prompt Off Command Query Backup and Query Object Commands Delete Backup and Delete Object Commands Inactivate Backup and Inactivate Object Commands Overview of taratddsmc The Teradata Extension for Tivoli Storage Manager stores the generation number for each backup internally. That number can be displayed: In the Details pane of the RESTORE object selection dialog box With the TSM backup name and other details when a taratddsmc query command is issued on a backup (see Syntax Conventions on page 99 for details) When a backup job fails, Teradata TARA does not make an entry in the jir file and the job is not displayed in the Details pane of the RESTORE object selection dialog box. However, the job s backup name is listed in the TSM database with segment F0000. The job contains zero bytes. Teradata Extension for Tivoli Storage Manager Administrator Guide 97

98 Chapter 5: Taratddsmc Command-Line Utility Installation Use taratddsmc to delete the failed backup (segment F0000) and clear the TSM database of incomplete backups. Note: If taratddsmc or another TSM tool is used to delete a valid backup job (that is, a job that did not fail) in the TSM database, that job continues to be displayed in the RESTORE object selection dialog box. There is no mechanism to notify Teradata TARA of the deletion. Installation Taratddsmc and tarativadm.bat are installed at <destination_path>\teradata\tara\tivbar\bin. To run taratddsmc: 1 Run tarativadm.bat to correctly set the environment variables. 2 In tarativadm.bat, set the DSMI_CONFIG path to point to the correct options file (.opt). Set the DSMI_DIR path to point to the correct.sys file. 3 Modify other values in tarativadm.bat if necessary. 4 Start taratddsmc through batch mode or interactive mode by typing the following at the command line: taratddsmc [options] [command] 5 To run taratddsmc in batch mode, type: Echo y taratddsmc DEL BA <pathname> <generation> Example Echo y taratddsmc DEL BA B90G100A 1 In the example, the backup object, B90G100A, is deleted. Multiple backup objects can be specified for deletion. Interactive mode occurs when no command is included on the command line. In interactive mode, taratddsmc prompts for input until a quit command is entered. Each time taratddsmc is started, a TSM server session is opened. In interactive mode, a single session is used for all commands. In batch mode, a different session is opened and closed each time taratddsmc is started. The next example shows variations of command line options for batch and interactive mode. Taraddsmc query backup * Taraddsmc? Taraddsmc> query tsm Taraddsmc> query backup fin* Taraddsmc> quit Taraddsmc -noheader query backup dbl_???? sort /+30 /R >backup.txt The prompt in interactive mode is shown as taratddsmc>. The last line of the example shows how to override the default sort order of the QUERY BACKUP command by piping output to the Windows sort utility. 98 Teradata Extension for Tivoli Storage Manager Administrator Guide

99 Chapter 5: Taratddsmc Command-Line Utility Command Line Parameters Command Line Parameters All the IOPARM parameters that are described in the Parameter Definitions on page 177, can also be entered as command line parameters in taratddsmc. Adding a prefix to each field name with a leading hyphen (-) makes command line options easy to distinguish from taratddsmc commands. Use the IOPARM string specification from an ARCMAIN job as a command line option to taratddsmc. An example of an acceptable string specification is: taratddsmc -ioparm config=mydsm.opt,mgmtclass=mymgmtclass q ba * Syntax Conventions The taratddsmc utility uses these commands: DELete Backup <pathname> [generation] DELete OBJect <pathname> <generation> <segname> FORMAT <formatstring> HELP <command-type> INActivate BAckup <pathname> INActivate OBJect <pathname> <segname> PROMPT [ ON OFF ] QueRY BAckup <pathname> [generation] [formatstring] QueRY OBJect <pathname> [generation] [segname] [formatstring] QueRY TSM QUIT The commands follow the rules described in Syntax Rules on page 176, plus the following syntax and semantics: Uppercase letters denote the shortest acceptable abbreviation of a command. For example, express QueRY as QUERY, QRY, or Q. Commands that are entirely uppercase cannot be abbreviated. Formatstring means that a quoted string value is expected. Name means that a name value is expected using general syntax rules. Commands are not case-sensitive. In the next example, the user-supplied namepattern is required, but the gen and formatstring tokens are optional. The number of blanks or white space characters between keywords and tokens does not matter as long as the entire command is on a single line: QueRY BAckup namepattern [ gen ] [ formatstring ] Add comment lines in scripts by putting an asterisk (*) as the first non-blank character on a line. All-blank lines are echoed to the output stream. Teradata Extension for Tivoli Storage Manager Administrator Guide 99

100 Chapter 5: Taratddsmc Command-Line Utility Format Specifiers Format Specifiers Format string and format specifiers control the display output of the QUERY BACKUP and QUERY OBJECT commands. Any characters not contained within a format specifier are passed and displayed as is. For example, to produce Cr Time JJ BackupName, type: %crdate% JJ %name% Note: One exception to this rule is that the literal \t character sequences are translated to tab characters. To generate tab-delimited output files, type: %crdate%\t%name%\t%size%. Override the default field width of any of these metadata files by including a colon (:) and an integer width value inside the end delimiter. Positive width values are right-justified and negative width values are left-justified. 12 lists metadata fields, plus default widths, headings, and format specifiers. 12: Metadata Fields Field Default Width Heading Format Specifier Active/Inactive State -1 A/I %status% Backup name (high-level) -30 Backup Name %name% Compressed/Uncompressed -1 C/U %compress% Creation Date (YYYY-MM-DD format) -10 Cr Date %crdate% Creation Time (HH:MM:SS format) -8 Cr Time %crtime% Expiration Date (YYYY-MM-DD format) -10 Expire %exp% Filespace Id 9 FS ID %fsi% Filespace Name -30 FS Name %fs% Generation Number 4 Gen %gen% Management Class -30 Mclass %mc% Media Class (such as, library, fixed-disk, off-site) -12 Media Class %media% Number of file segments 4 # Seg %segcnt% Segment Name (low-level) -30 Seg Name %segname% Total size in MB 9 Size (MB) %size% 100 Teradata Extension for Tivoli Storage Manager Administrator Guide

101 Chapter 5: Taratddsmc Command-Line Utility Taratddsmc Help Command Examples The %name:15% specifier: Restricts the name field to 15 characters and right-justifies the string in the field. Has the same field width, but strings are left-justified in the field. Values longer than 15 characters are not truncated, but do skew the alignment on the line. The maximum field width is 255 characters. Next is an example of a command and the report it generates. The report shows that values longer than the specified width are not truncated, but the alignment is skewed. taratddsmc> q ba * * %crdate% %crtime% %name:-15% %gen% %status% Retrieved 17 records filtered to 8 backups Cr Date Cr Time Backup Name Gen A/I :01:14 new-multi_dstream A :34:50 new-multi_dstream I :01:56 new-multi_dstream A :35:27 new-multi_dstream I Taratddsmc Help Command The Help command causes taratddsmc to display syntax information for the defined command type. If no command is entered or an invalid command is entered, it is equivalent to HELP HELP. To access taratddsmc help, do one of the following: Start taratddsmc with a question mark character (?). On the command line, type: taratddsmc? When taratddsmc help is started with a question mark (?), the utility does not attempt to open a session with the TSM server. In interactive mode, type: TARATDDSMC> Help These Help commands are available: Help CMD displays syntax information for taratddsmc commands. Help FORMAT displays syntax information related to format strings. Help Help defines the various HELP commands that can be issued. Help TARATDDSMC displays information about the taratddsmc command line. Teradata Extension for Tivoli Storage Manager Administrator Guide 101

102 Chapter 5: Taratddsmc Command-Line Utility Query TSM Command Query TSM Command QUERY TSM displays information about the current session configuration settings. This is the same information that is written to the log file when diagnostic tracing is enabled. Sample output from the command is shown in the following report. DSMI_DIR - C:\Program Files\Tivoli\TSM\api DSMI_CONFIG - C:\Program Files\Tivoli\TSM\baclient\dsm.opt Note: This path can vary according to the value set in tarativadm. servername - SERVER1 commmethod - TCP/IP serveradrress nodename - NODE1 compress - 0 compressalways - 1 passwordaccess - PROMPT Server name - SERVER1 Server Host Server port Server type - Windows Servr Date/Time :22:08 Servr Release Client node type - Teradata Client filespace delimiter - : Client h1 and 11 delimiter - \ Client delete backup obj? - No Maximum objects in txn Client Node Name - PINOT Session Owner - API Config file - Policy Domain - STANDARD Management Class - STANDARD Backup retention grace period - 30 days The QUERY TSM command output is divided into three sections. The first section displays client-side options that connect the TSM server. For example, the first two lines indicate the environment variables currently in effect. The nodename field indicates the client node name that opens the TSM server connection. When using multiple node names to store Teradata backups, any QUERY BACKUP and QUERY OBJECT commands restrict access to only the backup created by this node. 102 Teradata Extension for Tivoli Storage Manager Administrator Guide

103 Chapter 5: Taratddsmc Command-Line Utility Prompt Off Command The other two sections of the QUERY TSM output describe the context of the TSM server session. Use this information to determine whether you are connecting to the correct TSM server, default management class, and so on. For more information about field display, refer to these IBM manuals: Tivoli Storage Manager for Windows: Administrator s Guide: Version 5, Release 5 Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and User s Guide, Version 5, Release 5 Prompt Off Command The PROMPT OFF command disables the taratddsmc> prompt. Using this prompt might make the taratddsmc output a bit more readable if I/O re-direction is used to pass an entire script of taratddsmc commands to the utility and save the results in a file. Re-enable the prompt with the PROMPT ON command. Query Backup and Query Object Commands The QUERY BACKUP and QUERY OBJECT commands print a formatted report about Teradata objects in storage that match an identified search pattern. The syntax is shown below. Note: QUERY OBJECT shows one record per storage object whereas the QUERY BACKUP command aggregates totals to have one record per Teradata backup generation. QueRY BAckup namepattern [ gen ][ formatstring ] QueRY OBJect namepattern [ gen ][ segnamepattern ][ formatstring ] The node name context is established at session logon. Tivoli API limitations cause casesensitive matching on the name patterns. The optional gen field filters output to specific backup file generations. The default value of zero for the gen field restricts output to only the most recent generation of a backup. An asterisk (*) character in the gen field qualifies for all versions of the qualified backups. Relative generation numbers, such as -1 for the second-to-last most recent backup, can also be indicated. The segname pattern refers to a segment number (F0000 through F9999). An asterisk (*) character in the segname pattern field returns all segments for a given object. For example, QRY OBJ span* 2 *1 returns segment F0001 for generation 2 of all objects matching the span pattern. If a format string is not specified in the command, the current default determined from the FORMAT command line option is used. For further explanation on format strings, see Format Specifiers on page 100. Teradata Extension for Tivoli Storage Manager Administrator Guide 103

104 Chapter 5: Taratddsmc Command-Line Utility Delete Backup and Delete Object Commands Delete Backup and Delete Object Commands The DELETE BACKUP and DELETE OBJECT commands expire, then remove the qualified objects from storage. DELete BAckup namepattern [ gen ] DELete OBJect namepattern [ gen ] segnamepattern Batch Mode To invoke taratddsmc in batch mode refer to this example: Echo y taratddsmc DEL BA B90G100A 1 This example accepts y (yes) as the standard input (stdin) and deletes the backup object, B90G100A. Inactivate Backup and Inactivate Object Commands The INACTIVATE BACKUP and INACTIVATE OBJECT commands change the qualified storage objects from an ACTIVE to an INACTIVE state. The syntax is shown below. INActivate BAckup namepattern INActivate OBJect namepattern segnamepattern These commands operate only on active storage objects; otherwise, the commands operate in a similar way to DELETE. Objects are not deleted, but the file retention rules for the backup copy group expire the object when it becomes inactive. Note: If the TSM server policy limits the number of inactive versions of a storage object, the oldest version might expire. For more details about the TSM storage management policies, refer to the Tivoli Storage Manager for Windows: Administrator s Guide: Version 5, Release Teradata Extension for Tivoli Storage Manager Administrator Guide

105 CHAPTER 6 Teradata TARA Command-Line Utilities This chapter contains information on Teradata TARA stand-alone command-line utilities: TARAJobQuery allows the display of job related information for completed TARA jobs without having to use the Teradata TARA GUI TARALaunch allows the execution of a TARA job without having to use the Teradata TARA GUI TARASetCfg allows the explicit request of a TARA server to reset its configuration parameters by re-reading the defaults configuration file TARAJobRM provides the DBA the ability to delete scripts from the script repository, or job files from the job information repository. Note: Job scripts created prior to TARA must be changed to include the TARA Administrator name and the associated password. The change will take the form of: TARALaunch -j <TARA_script_name> -u Administrator -p <password> [other optional TARALaunch parameters] or TARALaunch -j <TARA_script_name> -u Administrator -e <encoded_password filename> [other optional TARALaunch parameters]. Note: All command line utilities assume the TARA GUI and the TARA Server are running on the same system. If this is not the case, the TARA servername option is required. TARAJobQuery The TARAJobQuery utility allows the display of job-related information for all TARA jobs that have run (even those that have failed) without having to use the Teradata TARA GUI. TARAJobQuery is a stand-alone, command-line utility. The job information that TARAJobQuery accesses is stored in a Job Information file, which resides in the Job Repository (JIR directory) on a TARA server host. Only one Job Information file can be accessed at a time. TARAJobQuery provides two options for displaying job information: The List option allows the listing of summary job information for each Job Information file in the Job Repository. The information provided in this option allows the user to determine what data is stored in each Job Information file. The Query option allows the display of specific job information for a single Job Information file. Only one Job Information file can be accessed at a time. Teradata Extension for Tivoli Storage Manager Administrator Guide 105

106 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery A typical scenario is to run TARAJobQuery using the List option first to find the Job Information file that you want to query. Then, rerun TARAJobQuery using the Query option to display the job data from that Job Information file. Run the TARAJobQuery utility by using the following job specifications. The command-line parameter indicators are case sensitive, therefore use the correct case when specifying the individual parameters. Also, specify each parameter only once in the command-line. To query for a list of summary information from each Job Information file, use: TARAJobQuery -u <username to log onto TARA server> -p <password to log onto TARA server> or -e <path to encoded password file> -L[-s-P-f-v] -L <display summary list> -(required) -s <TARA servername> -(optional) -P <port> -(optional) -f<output file name> -(optional) -v<verbose level: 1 2 3> (optional) To query for specific job information from a single Job Information file, use: TARAJobQuery -u <username to log onto TARA server> -p <password to log onto TARA server> or -e <path to encoded password file> -j [-s -S -O -f -l -L -N -P -v] -j <jobid> - (required) -s <TARA servername> - (optional) -P <port> - (optional) -S <stream options> - (optional) -O <object options> - (optional) -f <output file name> - (optional) -l <output ARC logs> - (optional) -L <output NetBackup logs> - (optional) -N <output NetBackup job data> - (optional) -v <verbose level: 1 2 3> - (optional) 13 describes TARAJobQuery parameters, and indicates if the parameter is required. 13: Parameters for TARAJobQuery Mandatory Parameter Description Yes No Default -u <User Name> Specifies the User Name that the utility uses to connect to the TARA Server. Currently the user names allowed are administrator and user. The user just has the read-only privilege. Example TARAJobQuery -u administrator X Not Applicable 106 Teradata Extension for Tivoli Storage Manager Administrator Guide

107 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery 13: Parameters for TARAJobQuery (continued) Mandatory Parameter Description Yes No Default -p Specifies the password for the user name the utility uses to connect to the TARA Server. Example TARAJobQuery -u adminstrator -p xjmt9 X Not Applicable -e <path to encoded password file> Specifies the path to the file that contains the encoded password to the User Name. X Not Applicable Example TARAJobQuery -u administrator -e C:\Teradata\tara.pwd Note: The file containing the encoded password is created during the post-install of the TARA Server, and is located in the TARA server bin directory: \Teradata\TARA\server\bin). The name of the file is tara.pwd. If the utility is running on a machine different from the TARA server, tara.pwd can be copied to the machine, and the path to the file containing the encoded password can be specified. If you need to recreate a file with the encoded password, run the TARALogonGen executable located in the TARA server bin directory: \Teradata\TARA\server\bin. Enter the password and the tool creates a tara.pwd. This file contains the encoded password. -L This is the List option, which enables the listing of summary job information for each Job Information file in the Job Repository. The information provided for each Job Information file includes the file's associated jobid that is needed to execute TARAJobQuery using the Query option (see the -j parameter). There is no value specified with this parameter. Example -L Note: If you specify -L, you cannot use the -j <jobid> parameter. X Not Applicable Teradata Extension for Tivoli Storage Manager Administrator Guide 107

108 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery 13: Parameters for TARAJobQuery (continued) Mandatory Parameter Description Yes No Default -j <jobid> This is the Query option. This parameter enables the display of the job information stored in a single Job Information file. The jobid value specifies the Job ID of the Job Information file whose information is to be retrieved. The jobid value is typically a 16 digit number and is typically used as the name of the Job Information file. The names of the available Job Information files are in the Job Repository (JIR directory) on the specified TARA server host (see -s parameter). To determine what data is stored in a Job Information file (and its associated jobid), execute TARAJobQuery using the List option (see the -L parameter). Example -j 43c2ac Note: If you specify -j <jobid>, you cannot use the -L parameter. X Not Applicable -s <TARA servername> This parameter specifies the TARA server host where the Job Information file and Job Repository are stored. The TARA servername value can be a host name (for example, taraserver1 or localhost) or an IP address of a host (for example, ). Example -s localhost Example -s This parameter is valid with the List option and the Query option. X localhost -P <port number> Specifies the port number that the TARA server is running on. The default port is If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. Example TaraJobQuery -u administrator -p xflu7 -j MyBackupJob -P X Teradata Extension for Tivoli Storage Manager Administrator Guide

109 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery 13: Parameters for TARAJobQuery (continued) Mandatory Parameter Description Yes No Default -S <stream options> This parameter specifies the job's stream information that will appear. The stream options value is a string of characters in which each character specifies a type of stream information. The string value can include one or more of the following characters: c - Client machine name e - Exit code f - File type (Archive or Journal) g - Group name n - Dataset name s - Stream size t - Stream time to complete (displayed in HH:MM:SS format) Example -S cefgnst This parameter is valid only with the Query option. -O <object options> This parameter specifies the job's object information that will appear. The object options value is a string of characters in which each character specifies a type of object information. The string value can include one or more of the following characters: c - Object count h - Hierarchical view (defaults to Traditional view) o - Owner name s - Object size t - Object time (displayed in HH:MM:SS format) y - Object type ( or Journal) The job's object information can be displayed in a Traditional or Hierarchical view. In a Traditional view, the objects appear in alphabetical order without regard to parent/child relationship. In a Hierarchical view, the objects appear in alphabetical order according to their parent/child relationship. Example -O chosty This parameter is valid only with the Query option. X X cest sty Teradata Extension for Tivoli Storage Manager Administrator Guide 109

110 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery 13: Parameters for TARAJobQuery (continued) Mandatory Parameter Description Yes No Default -f <output file name> This parameter specifies the name to be used in creating files for the output that is generated by TARAJobQuery. If the List option is specified, the output file name value is the full name given to the output file. If the Query option is specified, the output file name value is the base name given to these output files: <output file name>_job.txt - Job information and stream info <output file name>_obj.txt - Object information <output file name>_log_%d.txt - Log file for stream %d (only if -l specified) This parameter is optional. If not specified, the output generated will be sent to stdout, which is usually the monitor. When sending output to the monitor, a permanent copy of the file is not kept. If a fully-qualified output file name is used, the files are created in the specified directory. If a fully-qualified output file name is not used, the files are created in the current directory. Log records stored in the <name>_log_%d.txt file are the output lines from the ARC job that the TARA job executes. In other words, the log file contains output from the ARC job. In a multi-stream job, each stream-specific log file contains the output from the corresponding stream in the ARC job. Example -f myname If the List option is used, a single file, myname, would be created to store the output from TARAJobQuery. If the Query option is used, these files would be created: myname_job.txt myname_obj.txt myname_log_1.txt (if there is one stream and -l is specified) Example If the name contains embedded spaces or special characters, enclose the entire name in double quotes: "my name" or "mydir/my Documents/myname" This parameter is valid with the List option and the Query option. X Not Applicable 110 Teradata Extension for Tivoli Storage Manager Administrator Guide

111 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery 13: Parameters for TARAJobQuery (continued) Mandatory Parameter Description Yes No Default -l This parameter enables the creation of a file(s) to store ARC log information. There is one file created for each stream that is defined for the job. There is no value specified with this parameter. If you specify -l, the -f <output file name> parameter is also necessary. Example -l The -f <output file name> parameter generates a file(s) for ARC output (for example, myname_log_1.txt). This parameter is valid only with the Query option. X If this parameter is not specified, the ARC output that the TARA job generates will not be stored in a userspecified file. -v <verbose level: 1 2 3> This parameter specifies the level of debug information to display. There are three valid debug levels (1, 2, and 3), with higher values providing more extensive debug information. More extensive information is typically only useful for utility developers when gathering information about a reported problem. X If this parameter is not specified, debug information will not display. Example -v 3 Specifying 3 results in the highest level of debug information. This parameter is valid with the List option and the Query option. Sample Lines of Code tarajobquery -u administrator -p xdmjk -L tarajobquery -u administrator -p xdmjk -L -s localhost tarajobquery -u administrator -p xdmjk -L -s f "my name" tarajobquery -u administrator -p xdmjk -L -s remotehostname -f myname -l -v 3 tarajobquery -u administrator -p xdmjk -j tarajobquery -u administrator -p xdmjk -j s Teradata Extension for Tivoli Storage Manager Administrator Guide 111

112 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery tarajobquery -u administrator -p xdmjk -j s remotehostname -S cest -O sty tarajobquery -u administrator -p xdmjk -j s S cest -O sty -f "my name" -l tarajobquery -u administrator -p xdmjk -j s localhost -S cefgnst -O chosty -f myname -l -v 3 Sample List Option Output This is output is generated by entering: tarajobquery -L List of summary Job information for all Job Files in the Job Information Repository on TARA Server ' '. File Name/Job ID Job Name Date Stream Cnt bkjob3-dbc_all :14: c2ac bkjob6-rec-ptrs :33: c2ac bkjob2_db-level_2streams :34: d526d bkjob6-rec-ptrs :57: d526d bkjob4_table_level :02:09 0 List of summary Job information completed. Sample Query Option Output - Traditional View This output is generated by entering: tarajobquery -j O oy Job "bkjob3-dbc_all" :14:31 (ID ) Operation: ARCHIVE TDPID: JKW2K Streams: 1 Stream Client Size Time Exitcode Jkw2k 680,532,117 :00:00 0 Object Type Owner ARCBARPPI_CATDB1 Database ARCBARPPI_CATU T1_PPI T2_PPI 112 Teradata Extension for Tivoli Storage Manager Administrator Guide

113 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery t3_ppi ARCBARPPI_CATDB2 Database ARCBARPPI_CATU T1_PPI T2_PPI t3_ppi ARCBARPPI_CATU Database DBC Dbase ARCUSER Database DBC ARPTEST Database ARCUSER INDEXTABLE LOBTABLE PPITABLE BARP_FAOCPU Database DBC BARP_FAOD Database BARP_FAOU BARP_PPI_SIBT006 BARP_PPI_SIBT008 BARP_FAOU Database DBC BARP_PPIT001 BARP_PPIT002 BARP_PPIT003 BARP_PPIT004 BARP_PPIT005 BARP_PPIT006 BARP_PPIT007 BARP_PPIT008 BARP_PPI_TOO_LONG_TABLE_NAME editdistance_u editdistance_u_opt tokenize_u tokenize_u_opt BARP_FAO_ERRDB Database DBC BARP_ERR_TBL COPY29CHARDBNAMEWWWXXXXXYYYYY Database dbnametest twentyninechartbnamexxxxyyyyy COPY30CHARDBNAMEWWWXXXXXYYYYYZ Database dbnametest thirtychartbnamewwwxxxxxyyyyyz COPYSMALLDBNAME Database dbnametest smalltbname CRASHDUMPS Database DBC DBC Database DBC AccessRights AccLogRuleTbl Accounts CollationTbl Dbase Hosts LogonRuleTbl Next OldPasswords Owners Parents Profiles RCConfiguration RCEvent RCMedia RepGroup RoleGrants Roles SysSecDefaults Teradata Extension for Tivoli Storage Manager Administrator Guide 113

114 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery Translation UDTCast UDTInfo UDTTransform DBNAMETEST Database DBC DRXXX13 Database DBC T1 SMALLDBNAME Database dbnametest smalltbname SYSADMIN Database DBC FastLog HelpSyntax SYSLIB Database DBC SYSTEMFE Database DBC CleanupQCF CreateQCF opt_cost_table Opt_DBSCtl_ opt_ras_table Temp_ReconfigSpace SYSUDTLIB Database DBC TPMP_POINT_T_04dc_C tpmp_point_t_fromsql tpmp_point_t_ordering UDTINT_04de_C SYS_CALENDAR Database DBC CALDATES TDPUSER Database DBC THIRTYCHARDBNAMEWWWXXXXXYYYYYZ Database dbnametest thirtychartbnamewwwxxxxxyyyyyz TWENTYNINECHARDBNAMEXXXXYYYYY Database dbnametest twentyninechartbnamexxxxyyyyy Sample Query Option Output - Hierarchical View This output is generated by entering: tarajobquery -j O hoy Job "bkjob3-dbc_all" :14:31 (ID ) Operation: ARCHIVE TDPID: JKW2K Streams: 1 Stream Client Size Time Exitcode Jkw2k 680,532,117 :00:00 0 Object Type Owner DBC Database DBC ARCBARPPI_CATU Database DBC ARCBARPPI_CATDB1 Database ARCBARPPI_CATU T1_PPI T2_PPI 114 Teradata Extension for Tivoli Storage Manager Administrator Guide

115 Chapter 6: Teradata TARA Command-Line Utilities TARAJobQuery t3_ppi ARCBARPPI_CATDB2 T1_PPI T2_PPI t3_ppi Dbase ARCUSER ARPTEST INDEXTABLE LOBTABLE PPITABLE BARP_FAOCPU BARP_FAOU BARP_FAOD BARP_PPI_SIBT006 BARP_PPI_SIBT008 BARP_PPIT001 BARP_PPIT002 BARP_PPIT003 BARP_PPIT004 BARP_PPIT005 BARP_PPIT006 BARP_PPIT007 BARP_PPIT008 BARP_PPI_TOO_LONG_TABLE_NAME editdistance_u editdistance_u_opt tokenize_u tokenize_u_opt BARP_FAO_ERRDB BARP_ERR_TBL CRASHDUMPS DBNAMETEST COPY29CHARDBNAMEWWWXXXXXYYYYY twentyninechartbnamexxxxyyyyy COPY30CHARDBNAMEWWWXXXXXYYYYYZ thirtychartbnamewwwxxxxxyyyyyz COPYSMALLDBNAME smalltbname SMALLDBNAME smalltbname THIRTYCHARDBNAMEWWWXXXXXYYYYYZ thirtychartbnamewwwxxxxxyyyyyz TWENTYNINECHARDBNAMEXXXXYYYYY twentyninechartbnamexxxxyyyyy DRXXX13 T1 SYSADMIN FastLog HelpSyntax SYSLIB SYSTEMFE CleanupQCF CreateQCF opt_cost_table Opt_DBSCtl_ opt_ras_table Temp_ReconfigSpace SYSUDTLIB Database ARCBARPPI_CATU Database DBC Database ARCUSER Database DBC Database DBC Database BARP_FAOU Database DBC Database DBC Database DBC Database dbnametest Database dbnametest Database dbnametest Database dbnametest Database dbnametest Database dbnametest Database DBC Database DBC Database DBC Database DBC Database DBC Teradata Extension for Tivoli Storage Manager Administrator Guide 115

116 Chapter 6: Teradata TARA Command-Line Utilities TARALaunch TPMP_POINT_T_04dc_C tpmp_point_t_fromsql tpmp_point_t_ordering UDTINT_04de_C SYS_CALENDAR CALDATES TDPUSER AccessRights AccLogRuleTbl Accounts CollationTbl Dbase Hosts LogonRuleTbl Next OldPasswords Owners Parents Profiles RCConfiguration RCEvent RCMedia RepGroup RoleGrants Roles SysSecDefaults Translation UDTCast UDTInfo UDTTransform Database DBC Database DBC TARALaunch The TARALaunch utility allows the execution of a TARA script without having to use the Teradata TARA GUI. TARALaunch is a stand-alone, command-line utility. The script(s) that TARALaunch executes must already exist and be stored in the Script Repository (SR directory) on a TARA server host. Only one script can be launched for execution at a time. Execute the TARALaunch utility by using the following job specification. The command-line parameter indicators are case sensitive, therefore use the correct case when specifying the individual parameters. Each parameter can only be specified once in the command-line. TARALaunch -u -p -j [-s -v -P -w] -j <jobname> - (required) -u <username> - (required) -p <password> - (required) or -e <path to encoded password file> - (required) -s <TARA servername> - (optional) -P <port> - (optional) -v <verbose level: > - (optional) -w <seconds-to-wait> - (optional) 116 Teradata Extension for Tivoli Storage Manager Administrator Guide

117 Chapter 6: Teradata TARA Command-Line Utilities TARALaunch If a seconds value is not specified, this job will wait indefinitely until the TARA job is completed. If a value is specified, this job will wait until the TARA job is completed OR that number of seconds has elapsed. 14 describes TARALaunch parameters, and indicates if the parameter is required. 14: Parameters for TARALaunch Parameter Description Mandatory Default Yes No -j <jobname> Specifies the Job Name of the job to be launched for execution. The jobname value must match the name of an existing job in the Script Repository on the specified TARA server host. When specifying the jobname value, do not include a path qualifier, spaces, or any of the following characters: < > ~ *,?. \ / Example -j MyBackupJob Note: Scripts that are created or modified manually are not checked to see if the name contains spaces or characters. If the job name contains embedded spaces, enclose the entire name in double quotes. Special characters, other than the characters listed above, are allowed. Example -j "My Backup Job" -u <User Name> Specifies the User Name that the utility uses to connect to the TARA Server. Currently the user names allowed are administrator and user. The user just has the read-only privilege. Example TARALaunch -u administrator X X Not Applicable Not Applicable Teradata Extension for Tivoli Storage Manager Administrator Guide 117

118 Chapter 6: Teradata TARA Command-Line Utilities TARALaunch 14: Parameters for TARALaunch (continued) Parameter Description Mandatory Default Yes No -p <password> Specifies the password for the user name the utility uses to connect to the TARA Server. Example TARALaunch -u adminstrator -p xjmt9 X Not Applicable -e <path to encoded password file> Specifies the path to the file that contains the encoded password to the User Name. X Not Applicable Example TARALaunch -u administrator -e C:\Teradata\tara.pwd Note: The file containing the encoded password is created during the post-install of the TARA Server, and is located in the TARA server bin directory: \Teradata\TARA\server\bin). The name of the file is tara.pwd. If the utility is running on a machine different from the TARA server, tara.pwd can be copied to the machine, and the path to the file containing the encoded password can be specified. If you need to recreate a file with the encoded password, run the TARALogonGen executable located in the TARA server bin directory: \Teradata\TARA\server\bin. Enter the password and the tool creates a tara.pwd. This file contains the encoded password. -P <port> Specifies the port number that the TARA server is running on. The default port is If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. Example TaraLaunch -u administrator -p xflu7 -j MyBackupJob -P X s <TARA servername> Specifies the TARA server host where the job to be launched is stored. The TARA servername value can be a host name (for example, taraserver1 or localhost) or an IP address of a host (for example, ). X localhost The launched job will be run on the specified TARA server host. Example -s taraserver1 Example -s localhost Example -s Teradata Extension for Tivoli Storage Manager Administrator Guide

119 Chapter 6: Teradata TARA Command-Line Utilities TARALaunch 14: Parameters for TARALaunch (continued) Parameter Description Mandatory Default Yes No -v <verbose level: > Specifies the level of debug information to display. There are four valid debug levels (0, 1, 2, and 3), with higher values providing more extensive debug information. More extensive information is typically only useful for utility developers when gathering information about a reported problem. Level 0 suppresses most debug information, with the exception of some parameter validation errors. This is useful when TARALaunch is used in a batch file (Windows) or shell script (Linux). In this case, the batch file checks the %errorlevel% (Windows) or $? (Linux) to obtain the return code of TARALaunch. Refer to 15 on page 120 for these return values. Level 1 is the default level if the -v option is not specified. This level displays a successful launch message or any error message that prevented the job launch, plus any errors that occurred during monitoring (when the -w option is used). Level 2 provides more detail in launching the job. It can be very useful when using TARALaunch interactively with the -w option. In this case, the TARA ARC job States and their associated elapsed time in seconds are displayed until the TARA job ends or the maximum wait time is exceeded. Some States might not be displayed if they transition to another State within 30 seconds. Level 3 is typically only useful for utility developers when gathering information about a reported problem. Example -v 3 Specifying 3 results in the highest level of debug information. Example -v 2 Specifying 2 results in state process level information. If this parameter is not specified, level 1 is used. X Level 1 Teradata Extension for Tivoli Storage Manager Administrator Guide 119

120 Chapter 6: Teradata TARA Command-Line Utilities TARALaunch 14: Parameters for TARALaunch (continued) Parameter Description Mandatory Default Yes No -w <seconds-to-wait> Enables the Wait-for-Completion option. If enabled, TARALaunch remains active until the TARA job it launched terminates. At that point, TARALaunch exits with the return value set to the severity code of the ARC job (0, 4, 8, 12, 16). If an external error occurs (for example, a network error), the return code represents the type of error. 15 documents all return codes. If the -w option is specified without a seconds-to-wait value, TARALaunch waits indefinitely for the TARA job to terminate. If a seconds-to-wait value is specified, TARALaunch waits for that period of time. If the seconds-to-wait value is exceeded, TARALaunch exits with a return code set to 126. The exit of TARALaunch in this situation does not affect the active TARA job. X TARALaunch exits after the TARA job is launched by the TARA server 15 lists TARALaunch return codes. 15: TARALaunch Return Codes 0-16 Code Number Description Return codes 0-16 indicate that the TARA job launched successfully and represent the severity code that is returned by the single-stream or multi-stream TARA job. 0 Successful ARC job termination 4 ARC job completed with warnings 8 ARC job completed with non-fatal errors 12 ARC job terminated with fatal errors 16 Internal ARC failure Return codes 100 through 119 are parameter validation errors. The TARA job is not launched in all cases. 101 Incorrect number of parameters given to TARALaunch. 102 Missing parameter (-j -s -v -w) and value is greater than 256 characters. 103 Parameters (-j -s -v -w) must begin with a hyphen. 104 The parameter value is more than one word. 105 The -j parameter is specified more than once. 106 The initial parameter is -j and is not followed by a value. 107 The -j value is longer than 255 characters. 120 Teradata Extension for Tivoli Storage Manager Administrator Guide

121 Chapter 6: Teradata TARA Command-Line Utilities TARALaunch 15: TARALaunch Return Codes 0-16 (continued) Code Number Description 108 The -j parameter is not followed by a value. 109 The -s parameter is specified more than once. 110 The initial parameter is -s and is not followed by a value. 111 The -s value is longer than 100 characters. 112 The -s parameter is not followed by a value. 113 The -v parameter is specified more than once. 114 The -v parameter is not followed by a value. 115 The -v value is too long. 116 The initial parameter is -v and is not followed by a value. 117 The -v value must be 1 character. 118 The -w value must be a non-zero decimal number. 119 The parameter is not -j, -s, -v or -w Return codes indicate that the TARA job was successfully launched with the Wait-for- Completion option, but TARALaunch could not continue monitoring the TARA job. 126 The seconds-to-wait time expired during the wait-for-job-completion monitoring. 127 Network error terminated the TARALaunch connection to the TARA server during the wait-for-job-completion monitoring. Return codes indicate that TARALaunch was unsuccessful in attempting to launch the TARA job. 201 TARALaunch could not make the initial connection to the TARA server. 202 Network error terminated the initial send to the TARA server. 203 Network error terminated the initial receive from the TARA server. 204 TARA server rejected the request. 205 Network error during job launch request transmission. 206 Network error waiting for response of job launch request. Sample Lines of Code taralaunch -u administrator -p fqn6t -j MyBackupJob -s localhost -v 3 taralaunch -u administrator -p fqn6t -j "My Backup Job" -s taralaunch -u administrator -p fqn6t -j MyBackupJob Teradata Extension for Tivoli Storage Manager Administrator Guide 121

122 Chapter 6: Teradata TARA Command-Line Utilities TARASetCfg Output Unless the verbosity is increased by the "-v option", TARALaunch will only display two messages. The first message displays the TARA Job Identifier (JobID) assigned to the job. The second message displays the success or failure of the launch process. For example: C:\Documents and Settings\Administrator>taralaunch -j Inventory_weekly.arc -u administrator -e encrypted.pwd JobID 4b033b returned in launch Job 'Inventory_weekly.arc' was successfully launched on TARA Server ' ' C:\Documents and Settings\Administrator> A by-product of the launched job is the Job Information file that is stored in the Job Repository (JIR directory) on the TARA server host. To view the output from the launched job, use the Teradata TARA GUI or the TARAJobQuery command-line utility. TARASetCfg The TARASetCfg utility allows the explicit request that a TARA server reset its configuration parameters by re-reading the defaults configuration file. Under normal conditions, a TARA server updates its configuration parameters only when it is first brought up, or restarted. However, there are scenarios when you might want to modify the configuration parameters in the TARA server's default configuration file, defaults, while the server is still running. TARASetCfg sends a message to the TARA server instructing it to immediately re-read the defaults configuration file and reset its configuration information. This avoids having to restart the TARA server. Run the TARASetCfg utility by using the following job specification. The command-line parameter indicators are case-sensitive, therefore use the correct case when specifying the individual parameters. Specify each parameter only once in the command line. TARASetCfg -u -p [-s -P -v] -u <username to logon to TARA server> - (required) -p <password to logon to TARA server> - (required) or -e <path to encoded password file> - (required) -s <TARA servername> - (optional) -P <port> - (optional) -v <verbose level: 1 2 3> - (optional) 16 describes TARASetCfg parameters, and indicates if the parameter is required. 122 Teradata Extension for Tivoli Storage Manager Administrator Guide

123 Chapter 6: Teradata TARA Command-Line Utilities TARASetCfg 16: Parameters for TARASetCfg Parameter Description Mandatory Default Yes No -u <User Name> Specifies the User Name that the utility uses to connect to the TARA Server. Currently the user names allowed are administrator and user. The user just has the read-only privilege. Example TARASetCfg -u administrator -p <password> Specifies the password for the user name the utility uses to connect to the TARA Server. Example TARASetCfg -u adminstrator -p xjmt9 X X Not Applicable Not Applicable -e <path to encoded password file> Specifies the path to the file that contains the encoded password to the User Name. X Not Applicable Example TARASetCfg -u administrator -e C:\Teradata\tara.pwd Note: The file containing the encoded password is created during the post-install of the TARA Server, and is located in the TARA server bin directory: \Teradata\TARA\server\bin). The name of the file is tara.pwd. If the utility is running on a machine different from the TARA server, tara.pwd can be copied to the machine, and the path to the file containing the encoded password can be specified. If you need to recreate a file with the encoded password, run the TARALogonGen executable located in the TARA server bin directory: \Teradata\TARA\server\bin. Enter the password and the tool creates a tara.pwd. This file contains the encoded password. -s <TARA servername> Specifies the TARA server host whose configuration information you want to reset. The TARA servername value can be a host name (for example, taraserver1 or localhost) or an IP address of a host (for example, ). Example -s taraserver1 Example -s localhost Example -s X localhost Teradata Extension for Tivoli Storage Manager Administrator Guide 123

124 Chapter 6: Teradata TARA Command-Line Utilities TARASetCfg 16: Parameters for TARASetCfg (continued) Parameter Description Mandatory Default Yes No -P <port> Specifies the port number that the TARA server is running on. The default port is If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. Example TaraSetCfg -u administrator -p xflu7 -j MyBackupJob -P X v <verbose level: 1 2 3> Specifies the level of debug information to display. There are three valid debug levels: 1, 2, and 3. Higher values provides more extensive debug information. This information is typically only useful for utility developers when gathering information about a reported problem. Example -v 3 results in the highest level of debug information The parameters can be specified in any order. X If this parameter is not specified, debug information will not appear. Sample Lines of Code tarasetcfg -u administrator -p xjmt9 tarasetcfg -u administrator -p xjmt9 -s localhost tarasetcfg -u administrator -p xjmt9 -s tarasetcfg -u administrator -p xjmt9 -v 1 tarasetcfg -u administrator -p xjmt9 -s localhost -v 2 tarasetcfg -u administrator -p xjmt9 -s v 3 Output TARASetCfg does not produce any output other than a message that the operation was a success or failure. To verify that the configuration information has been updated, open the Teradata TARA GUI s TARA Server Configuration dialog box and view the information under the various tabs. 124 Teradata Extension for Tivoli Storage Manager Administrator Guide

125 Chapter 6: Teradata TARA Command-Line Utilities TARAJobRM TARAJobRM To remove a TARA job file or a TARA script, use: TARAJobRM -u <username to logon to TARA server> -p <password to logon to TARA server> or -e <path to encoded password file> -s <taraserver> -P <port> -S [<script_name> : -f <input_file] [-v 0:1:2:3] or TARAJobRM -u <username to logon to TARA server> -p <password to logon to TARA server> or -e <path to encoded password file> -s <taraserver> -P <port> -J [<jobfile_name> : -f <input_file] [-v 0:1:2:3] -F TARAJobRM allows the DBA to remove script files or job files from the TARA server repository, using one of the following job specifications: Example Example 17: Parameters for TARAJobRM tarajobrm -u [ <username> ] -p [ <password> ] or -e [ <path to encoded file> ] -S [ <script_name> -f <input_filename> ] [ -s <TARAServer_name> ] [ -v ] [-P <Port>] tarajobrm -J [ <jobfile_name> -f <input_filename> ] [ -s <TARAServer_name> ] [ -v ] [-F] Mandatory Parameter Description Yes No Default -u <User Name> Specifies the User Name that the utility uses to connect to the TARA Server. Currently the user names allowed are administrator and user. The user just has the read-only privilege. Example TARAJobRM -u administrator -p <password> Specifies the password for the user name the utility uses to connect to the TARA Server. Example TARAJobRM -u adminstrator -p xjmt9 X X Not Applica ble Not Applica ble Teradata Extension for Tivoli Storage Manager Administrator Guide 125

126 Chapter 6: Teradata TARA Command-Line Utilities TARAJobRM 17: Parameters for TARAJobRM (continued) Mandatory Parameter Description Yes No Default -P <port> Specifies the port number that the TARA server is running on. The default port is If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. X Example TaraJobRM -u administrator -p xflu7 -j MyBackupJob -P e <path to encoded password file> Specifies the path to the file that contains the encoded password to the User Name. Example TARAJobRM -u administrator -e C:\Teradata\tara.pwd Note: The file containing the encoded password is created during the post-install of the TARA Server, and is located in the TARA server bin directory: \Teradata\TARA\server\bin). The name of the file is tara.pwd. If the utility is running on a machine different from the TARA server, tara.pwd can be copied to the machine, and the path to the file containing the encoded password can be specified. If you need to recreate a file with the encoded password, run the TARALogonGen executable located in the TARA server bin directory: \Teradata\TARA\server\bin. Enter the password and the tool creates a tara.pwd. This file contains the encoded password. X Not Applica ble -S <script_name> Specifies a script name, or the name of a file that has a list of script names to delete. If specifying a single file, the name of the file must immediately follow -S. If specifying a file that has a list of script names, precede the file name with -f (see the -f <input_filename> parameter). In the file containing the list: Each script name must be the first field in the line. Specify only one script name on each line. Spaces delimit the fields in a line. -f <input_filename> Specifies the name of a file that has a list of script or job names to delete. This parameter, or the -J <jobfile_name> parameter, is required. X 126 Teradata Extension for Tivoli Storage Manager Administrator Guide

127 Chapter 6: Teradata TARA Command-Line Utilities TARAJobRM 17: Parameters for TARAJobRM (continued) Mandatory Parameter Description Yes No Default -J <jobfile_name> Specifies a job name, or the name of a file that has a list of jobfile names to delete. If specifying a single file, the name of the file must immediately follow -J. If specifying a file that has a list of jobfile names, precede the file name with -f (see the -f <input_filename> parameter). In the file containing the list: Each jobfile name must be the first field in the line. Specify only one jobfile name on each line. Spaces delimit the fields in a line. Note: To obtain a list of all jobs in the TARA server repository, use tarajobquery -L. Then, copy those jobfiles to be deleted into a file for TARAJobRM. This parameter, or the -S <script_name> parameter, is required. -s <TARAServer_name> This option is not required if the TARA server resides on the same BAR server where this utility is launched. Otherwise, the TARAServer_name value is the name of the BAR server running TARAServer. X -v Specifies the verbosity of the utility after parameter validation. The range is 0 to 3. -F For a TARA JobFile only. Forces removal of the JobFile even if there is a valid image in the NetBackup image catalog. X 1 X When a single job or script is deleted, the deletion occurs after parameter validation, without verification of the file to be deleted. In contrast, when multiple scripts or jobs are deleted, the user is prompted by the following line: X files will be deleted. Is this correct? (y,n) Caution: Verify that X is the correct number of jobs or scripts. After the jobs or scripts are deleted, they cannot be recovered. 18 lists TARAJobRM return codes. 18: TARAJobRM Return Codes Return Code Description Return codes designate errors that can occur during a jobfile or script removal. 101 Unable to connect to the TARA server. 102 Network failure sending the file remove request to the TARA server. 103 Network failure receiving the file remove response from the TARA server. Teradata Extension for Tivoli Storage Manager Administrator Guide 127

128 Chapter 6: Teradata TARA Command-Line Utilities TARAJobRM 18: TARAJobRM Return Codes (continued) Return Code Description 104 Cannot open the Job list or Script list file. 105 Cannot read the Job list or Script list file. 106 The Job list or Script list file contains an unrecognizable line. 110 Cannot read the "y" or "n" response to the file verification message. 111 Job terminated. User answered "n" to the file verification message. Return codes designate parameter validation errors. 700 Incorrect number of parameters entered. 701 The parameter value is greater than the maximum size of 255 characters. 702 A parameter value is not preceded by a parameter key (-s, -S, -J, -f, or -v). 703 Unknown parameter key (not a -s, -S, -J, -f or -v). 705 The -J parameter key is specified twice. 706 The -J parameter key is specified, but no value or -f <filename> is specified. 707 The -J parameter key is specified with a value, but the value is not 16 characters in length. 709 The -s parameter key is specified twice. 710 The -s parameter key does not have a TARA server value following it. 711 The -s parameter key is specified with a value, but the value is greater than 100 characters in length. 713 The -S parameter key is specified twice. 714 The -S parameter key is specified, but no value or -f <filename> is specified. 715 The -S parameter key is specified with a value, but the value is greater than 255 characters in length. 738 The -f parameter key is specified twice. 739 The -f parameter key does not have a filename value following it. 740 The value associated with the -f parameter key is greater than 255 characters in length. 743 The -v parameter key is specified twice. 744 The -v parameter key must be followed by a value of 0, 1, 2 or Either the -S (script) or -J (Jobfile) parameter is required. 750 Both the -S and -J parameters are found. Only one can be specified. 751 The -f parameter is specified, but neither the -S or -J parameters, one of which is required, is found. 128 Teradata Extension for Tivoli Storage Manager Administrator Guide

129 Chapter 6: Teradata TARA Command-Line Utilities TARAJobRM 18: TARAJobRM Return Codes (continued) Return Code Description 753 Invalid level specified for -v (0, 1, 2 or 3). Teradata Extension for Tivoli Storage Manager Administrator Guide 129

130 Chapter 6: Teradata TARA Command-Line Utilities TARAJobRM 130 Teradata Extension for Tivoli Storage Manager Administrator Guide

131 CHAPTER 7 Troubleshooting for the TARA These topics discuss errors associated with Teradata Extension for Tivoli Storage Manager: Overview of Error Messages Teradata Extension for Tivoli Storage Manager Debug Log ARCMAIN Outlog TSM Log Messages Error Conditions and Recovery Data Connector Error Messages Vendor-Independent Error Messages TSM Error Messages For troubleshooting information on Teradata TARA components, see: Troubleshoot Utility TARA Server Stop and Restart Use of the Command Line to Obtain Information Teradata TARA GUI on Java Runtime Extension States for Archive Jobs Job Stream Connection Failure Unresponsive TARA Server Overview of Error Messages If errors occur with Teradata Extension for Tivoli Storage Manager during a Teradata backup, the extension and TSM generate debug logs that can be used for troubleshooting. Error messages reported by Teradata Extension for Tivoli Storage Manager can originate from several software components. Determining the root cause of an error depends on the application that reports the problem. 19 lists different types of messages that can occur. 19: Types of Messages Type of Message Description Reference Information ARCnnnn messages These messages are generated by ARCMAIN client code. None Teradata Extension for Tivoli Storage Manager Administrator Guide 131

132 Chapter 7: Troubleshooting for the TARA Teradata Extension for Tivoli Storage Manager Debug Log 19: Types of Messages (continued) Type of Message Description Reference Information BAMnnnn messages These messages are generated by Teradata Extension for Tivoli Storage Manager. Data Connector Error Messages on page 136 ANSnnnn messages These are TSM client messages. Refer to the version of IBM s Tivoli Storage Manager Messages that correlates to the version of TSM being used. See tdprodlist.html ANRnnnn messages These are TSM server messages. Refer to the version of IBM s Tivoli Storage Manager Messages that correlates to the version of TSM being used. See tdprodlist.html Messages with error numbers that range from - 50 to +50 Messages with error numbers that range from 1 to 50 Error messages in the form of "*** Failure nnnn:..." These error messages are associated with Teradata Extension for Tivoli Storage Manager or TSM. These ARCMAIN errors are associated with the Data Connector component. These are ARCMAIN errors that most likely originate with the Teradata Database. Refer to the version of IBM s Tivoli Storage Manager Messages that correlates to the version of TSM being used. See tdprodlist.html Data Connector Error Messages on page 136 Messages Note: Some error codes have multiple error messages, which are listed in the bullet lists in the Error Message Text column. Teradata Extension for Tivoli Storage Manager Debug Log Teradata Extension for Tivoli Storage Manager automatically writes diagnostic tracing information to a debug log file. Control the name and location of this log file and the level of tracing using the environment variables BARAMLOG and BARAMLOGLEVEL.For more information on these variables, see Environment Variables on page 181. By default, the debug log file is called baram_log.txt and is located in the current working directory where ARCMAIN runs. Diagnostic tracing in the debug log is available at the levels shown in Teradata Extension for Tivoli Storage Manager Administrator Guide

133 Chapter 7: Troubleshooting for the TARA ARCMAIN Outlog 20: Log File Levels Level Description 1 Defaults to 1 if a log level is not specified. Tracing at this level logs major events, such as opening/closing a file or shutdown. At shutdown, a summary report of I/O counts and number of bytes reads/writes from/to each file displayed. 2 Displays call trace information at the BAR_Session level for most functions, except the calls to read/write individual data blocks. 3 Logs TSM API function calls and includes more descriptive information about each read/write operation. 4 Includes information at trace level 3, in addition to memory buffer information. 5 Includes information at trace level 4, and Data Connector function codes and returns. ARCMAIN Outlog Always evaluate ARCMAIN output to ensure that each job runs successfully; all error messages (including the error code and message text) are displayed in the ARCMAIN outlog. Teradata Extension for Tivoli Storage Manager returns an error code and message text for ARCMAIN to output to its various log files. The message text and any additional debug information is also written to the debug log of Teradata Extension for Tivoli Storage Manager. TSM Log Messages The error codes in the 1200 to 1299 range originate in TSM, which logs diagnostic information in these log files: TSM Server Activity Log TSM Client Log TSM Server Activity Log Teradata Extension for Tivoli Storage Manager generates Teradata-specific messages in the TSM server activity log every time it opens and closes a backup file. These messages are strings that include TDB0nnn, where nnn is the message ID. The next example includes a command, plus the report it generates, of Teradata Extension for Tivoli Storage Manager messages that are associated with opening a Teradata backup file in WRITE mode: Query actlog search=tdb0002 Teradata Extension for Tivoli Storage Manager Administrator Guide 133

134 Chapter 7: Troubleshooting for the TARA Error Conditions and Recovery Date/Time 06/23/ :41:54 06/23/ :56:17 06/23/ :56:44 06/23/ :57:12 Message ANE4991I (Session: 4901, Node: MERLOT) Teradata TDB0002 System merlot Opening Teradata backup NS=Teradata, DSN-DATA0001 Generation=3 in write mode ANE4991I (Session: 4903, Node: MERLOT) Teradata TDB0002 System merlot Opening Teradata backup NS=Teradata, DSN-DATA0002 Generation=4 in write mode ANE 4991I (Session: 4905, Node: MERLOT) Teradata TDB0002 System merlot Opening Teradata backup NS=Teradata, DSN=DATA0001\Long_Path$#.DATA Generation=1 in write mode ANE4991I (Session: 4906, Node: MERLOT) Teradata TDB0002 System merlot Opening Teradata backup NS=Teradata, DSN=DATA0001.DSN Generation=1 in write mode TSM Client Log Query for all messages associated with a particular session or time period to see the server context of the operation, such as, device errors from mounting tapes. The default retention period for a TSM server activity log is only one day, so regular checks are recommended. Viewing older logs requires special procedures. For more information about the syntax of the QUERY ACTLOG command, refer to IBM s Tivoli Storage Manager for Windows: Administrator s Reference: Version 5, Release 5. Errors and abnormal conditions on the TSM client node are written to a client log file, typically named DSIERROR.LOG. The location of this file is controlled at runtime by the DSMI_LOG environment variable or is written to the local directory. The TSM client log file always opens in APPEND mode, therefore verify activity by checking the date/time stamp on all messages. View these log files in any text editor, such as Notepad. Error Conditions and Recovery The error messages that are displayed during ARCMAIN operations can originate from various software components. The error conditions shown in 21 can occur while starting Teradata Extension for Tivoli Storage Manager or while backing up data. Use this information to ensure that the installation process is successfully completed and that all recovery options are considered. 134 Teradata Extension for Tivoli Storage Manager Administrator Guide

135 Chapter 7: Troubleshooting for the TARA Error Conditions and Recovery 21: Error Conditions and Recovery Options Error Condition An invalid option was found during option parsing ANSnnnn or ANRnnnn TSM errors dsminitex -- Session rejected Errors that include a traceback Hung up on a tape mount Hung up on a Teradata Database lock Possible Recovery Option This is a dsmsetup error. The installation process attempted to read Windows registry settings to determine the paths to TSM. However, there was an invalid option found during option parsing, probably due to an invalid option specification in the TSM Client Options file. Refer to the DSIERROR.LOG file and determine which line of the options file is invalid. The path to this file is set with the DSMI_LOG environment variable or the path defaults to the local directory. For more information about TSM Client Options, refer to IBM s Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and User s Guide, Version 5, Release 2 documentation. Teradata Extension for Tivoli Storage Manager attempts to gather as much information as it can about the root cause of errors. Query the TSM server activity log for device errors or other messages that did not get conveyed to the client process. For information on the TSM server activity log, refer to TSM Server Activity Log on page 133. Alternately, check for DSIERROR.LOG file error messages on the client. This is an open session error from Teradata Extension for Tivoli Storage Manager, related to opening a TSM server connection. This is an authentication error, the most common source of open session errors. An invalid NODENAME or PASSWORD is defined in the TSM Client Options file. For more information about how settings need to match what is defined for the TSM server, see Configure TSM for Teradata Backups on page 43. Teradata Extension for Tivoli Storage Manager maintains an internal trace buffer that is dumped to stderr output when exceptional conditions occur, such as memory access or illegal instruction. This type of diagnostic output is a problem that can only be corrected by the Teradata Development organization, therefore: 1 Capture a complete output listing. For information about generating diagnostic traces, see Environment Variables on page 181 for details about the BARAMLOG and BARAMLOGLEVEL environment variables. These variables control the diagnostic tracing for Teradata Extension for Tivoli Storage Manager. 2 After collecting the trace information, contact the Teradata Global Support Center. File locking contention can occur when two jobs attempt to write to the same log file at the same time. Device messages often show up in the TSM server activity log. For more information on the TSM server activity log, refer to TSM Server Activity Log on page 133. Consult the Teradata QUERYSESSION and SHOWLOCKS console utilities for help. Teradata Extension for Tivoli Storage Manager Administrator Guide 135

136 Chapter 7: Troubleshooting for the TARA Data Connector Error Messages 21: Error Conditions and Recovery Options (continued) Error Condition Options file * not found The file cannot be found or is improperly formatted tivarc (tivadm) is not recognized as an internal or external command, operable program or batch file Unable to see backups in storage using TDDSMC Possible Recovery Option This is a dsmsetup error. The installation process attempted to read Windows registry settings to determine paths to TSM. However, the TSM Client Options file was not found. One or more of the DSMI environment variables are not properly set. Edit runarctiv.bat and: tarativadm.bat in Windows tarativadm.sh in Linux Locate the file and correct the format. The installation process should have created a TDBAR configuration file directory (which is usually C:\Program Files\Teradata\Teradata Client\TDBAR). The TIVARC.BAT file starts ARCMAIN with the sample ARCDFLT.TXT file as the ARCMAIN default command line option file. The %PATH% is wrong. The environment variable for %PATH% does not include the location of the TIVARC.BAT, ARCMAIN.EXE, and TIVBAR.DLL files. Usually this location is C:\Program Files\Teradata\Teradata Client\BIN. If the ARCMAIN process seems to be error-free, but verifying that the storage object was created on the TSM server is not possible, check the following: Is the TCPSERVERADDRESS field of the TSM Client Options file indicating the correct IP address? In other words, is Teradata Extension for Tivoli Storage Manager connected to the proper TSM server? Are you querying the TSM server for the correct node name? To see what node name was used to create the backup, execute the following command from the TSM Server Administrative Console: query activitylog search=tdb0002 Is the DATASETNAME pattern correctly entered? (TSM is case-sensitive.) The QUERY TSM command from the taratddsmc utility might provide additional information. Data Connector Error Messages The error messages shown in 22 correspond to Data Connector error codes that range from 0 to Teradata Extension for Tivoli Storage Manager Administrator Guide

137 Chapter 7: Troubleshooting for the TARA Data Connector Error Messages 22: Data Connector Error Codes Error Code Error Message Text Description and Remedy BAM0011 Access Module called by < > when expecting < > Teradata Extension for Tivoli Storage Manager is being called by a program other than ARCMAIN, but the extension can only be used for Teradata backup and restore. Remedy: Correct the software configuration and rerun the job. To determine the correct software version for the environment, refer to the release letter documentation or contact the Teradata Global Support Center. BAM0013 Invalid open mode < > requested Teradata Extension for Tivoli Storage Manager is being asked to open a file in an invalid mode. This error might indicate a software version incompatibility between Teradata Extension for Tivoli Storage Manager and the Data Connector. More likely, the error is related to some type of software corruption. Remedy: Contact the Teradata Global Support Center. BAM0018 Expected Data Connector Version (< > < >) but actually got (< > < >) The Data Connector version is incompatible with Teradata Extension for Tivoli Storage Manager. The Data Connector corresponds to the libpm.dll component on Windows and the libpm.so component on UNIX. Verify that the correct component is being loaded and the correct installation path is being used. Remedy: Correct the software configuration and rerun the job. To determine the correct software version for the environment, refer to the release letter documentation or contact the Teradata Global Support Center. Teradata Extension for Tivoli Storage Manager Administrator Guide 137

138 Chapter 7: Troubleshooting for the TARA Data Connector Error Messages 22: Data Connector Error Codes (continued) Error Code Error Message Text Description and Remedy BAM0020 Invalid token entered for Directory Delimiter Directory Delimiter must be single non-alphabetic No closing quote character < > value < > found after < > characters File path cannot exceed characters Name cannot exceed < > characters: < > Colon character < > in wrong place for a directory path Invalid substitution variable < > (need closing < > character) Unrecognized substitution variable < > Unrecognized character < > (value < >) at position < > < > is not a valid name value for < > field < > value cannot exceed < > characters < > field assignment must be a quoted string value < > is not a valid number for < > field < > field value cannot be a decimal < > value cannot exceed < > characters Unrecognized field name starting at: < > The IOPARM string or the command contains a syntax error. This error message can result from a number of causes, all related to the user-entered command syntax. Remedy: Correct the error and resubmit the job. BAM0024 Unsupported function code < > Teradata Extension for Tivoli Storage Manager is incompatible with the calling program. The extension can only be used for Teradata backup and restore. Your version of ARCMAIN software might be incompatible with the Teradata Extension for Tivoli Storage Manager software. Remedy: Correct the software configuration and rerun the job. To determine the correct software version for the environment, refer to the release letter documentation or contact the Teradata Global Support Center. BAM0033 < > Access Module currently does not support the < > file attribute < > Access Module currently does not support the < > function for < > file attribute Teradata Extension for Tivoli Storage Manager is incompatible with the calling program. Teradata Extension for Tivoli Storage Manager can only be used for Teradata backup and restore. This error suggests that a version of ARCMAIN software is being used that is not compatible with the extension s software level. Remedy: Correct the software configuration and rerun the job. To determine the correct software version for the environment, refer to the release letter documentation or contact the Teradata Global Support Center. 138 Teradata Extension for Tivoli Storage Manager Administrator Guide

139 Chapter 7: Troubleshooting for the TARA Vendor-Independent Error Messages Vendor-Independent Error Messages The error messages shown in 23 originate in the vendor-independent portions of Teradata Extension for Tivoli Storage Manager. These error codes range from 1000 to : Vendor Independent Error Messages Error Code Error Message Text Description and Remedy BAM1000 NULL file pointer passed to < > function of Access Module Unrecognized file pointer 0x< > passed to < > function of Access Module Write called with buffer length < > when max size is < > Access Module passed OBJNAME attribute < >. It is < > characters long when only < > characters supported Invalid object type < > passed on OBJNAME attribute Invalid CopyNum < > passed to BARFile Constructor Invalid File Open Mode < > when closing Write called when file not opened for writing NULL position pointer passed to SetPos Invalid position (< > < >) passed to SetPos SetPos position (< > < >) caused us to read past end of segment SetPos position (< > < >) reads past end of segment Reposition offset= < > when only < > bytes returned by read Unable to interpret Object Info. Format= < >, InfoLen= < > CloseWrite should have updated < > segments but only did < > CloseWrite File segment FS= < >, HL= < >, LL= < > does not match list An internal software error is detected. These messages correspond to BAR internal error codes. They indicate a severe, unexpected, or exceptional condition that can only be corrected by the Teradata Development organization, therefore: 1 Capture a complete output listing and all supporting text. 2 Contact the Teradata Global Support Center. Remedy: Contact a field engineer or the Teradata Global Support Center. Teradata Extension for Tivoli Storage Manager Administrator Guide 139

140 Chapter 7: Troubleshooting for the TARA Vendor-Independent Error Messages 23: Vendor Independent Error Messages (continued) Error Code Error Message Text Description and Remedy < > called when no active transactions EndCreateObj called when no open object FSeg Constructor passed invalid arguments: NS= < >, PATH= < >, GEN= < >, SEQ= < > Invalid pointer < > passed to rewind_input function Invalid File Name length < > passed to Open function Read function called when already flagged end-ofdata Invalid length < > passed for allocating temporary buffer Invalid length was returned from a call to dsmgetnextqobject BAM1001 NULL target buffer passed to esprintf routine Invalid message id < > passed to esprintf routine No message text stored for message id < > Call to esprintf routine exceeded < > number of inserts Invalid message id < > passed to escode routine The core error reporting routines cannot do their work. An internal software error/corruption is detected. Other error conditions might be hidden behind this error. Remedy: Contact a field engineer or the Teradata Global Support Center. BAM1002 BAM1003 BAM1005 The access module expects the Tivoli password access mode to be PASSWORD PROMPT Access Module currently does not support restarts in the WRITE mode Access Module cannot open more than < > files at same time Teradata Extension for Tivoli Storage Manager only functions in PASSWORD PROMPT mode. Remedy: Specify the PASSWORD mode as PROMPT in dsm.opt. Teradata Extension for Tivoli Storage Manager does not support restart processing when a backup file is opened in WRITE mode, which means that the extension rolls back and deletes all data written to TSM up to this point. Remedy: Do one of the following: Resubmit the job from the beginning of the current ARCMAIN step. Instead of resubmitting the job, issue a RELEASE LOCK statement on the Teradata server to remove any database locks set. More FILE= clauses are specified on the ARCMAIN backup statement than are supported by Teradata Extension for Tivoli Storage Manager. Remedy: Correct the ARCMAIN statement and resubmit the job. 140 Teradata Extension for Tivoli Storage Manager Administrator Guide

141 Chapter 7: Troubleshooting for the TARA Vendor-Independent Error Messages 23: Vendor Independent Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1006 Access Module detected multiple backups for NameSpace= < >, Path= < >, Segment= < > TSM qualified multiple backups for the indicated Namespace, Pathname, and Segmentname pattern. This is an error because a backup and restore needs to work with only one high-level name per ARCMAIN statement. The most likely reason for this error is that the Namespace or Pathname fields contain a wildcard character that qualifies multiple backup files from the TSM catalog. Test this by using the native API query tool to see what backup file names come back, making sure that you are logged on as the same user ID to the TSM server. Wildcard characters are acceptable for a low-level segment name because Teradata Extension for Tivoli Storage Manager reserves those names for its own purposes. Remedy: Correct the indicated name by removing the wildcard characters, and resubmit the job. BAM1007 No backup file(s) found with NameSpace= < >, Path= < >, Segment= < >, Generation= < > No backup file matched the indicated Namespace, Pathname, Segmentname pattern, and Backup File Generation number. The Namespace field defaults to Teradata. The Pathname is set by one of the following: The DATASETNAME field on the IOPARM string The external name of the FILEDEF parameter The value assigned on the FILE= clause of the ARCMAIN restore statement Segmentname is controlled only by Teradata Extension for Tivoli Storage Manager, but is shown in case you want to include it in an administrative query. The generation number is entered as an IOPARM field or defaults to zero. Relative numbers, such as -1 and -2, count backwards from the current active backup (gen=0). Remedy: Correct the indicated name and resubmit the restore job. Teradata Extension for Tivoli Storage Manager Administrator Guide 141

142 Chapter 7: Troubleshooting for the TARA Vendor-Independent Error Messages 23: Vendor Independent Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1008 Duplicate storage objects found with NameSpace= < >, Path= < >, Segment= < >, Generation= < > Teradata Extension for Tivoli Storage Manager creates storage object names with a particular format. Also, a non-negative generation number is stored in the Object Info portion of the storage catalog metadata. If duplicate storage objects were found with the same name/generation one of the following has happened: An existing ARCMAIN backup was copied or the Object Info field was corrupted. The storage catalog is corrupted or Teradata Extension for Tivoli Storage Manager has a bug. The extension relies on the generation number to distinguish between separate runs of the same backup job, so all file segments that correspond to a single backup job execution need to have the same generation number. Remedy: Verify the heritage of the pertinent storage objects and, if necessary, delete the corrupt objects or update the Object Info metadata with distinct generation numbers. Ensure that the backups are not creating new objects when the metadata is updated. If the remedy does not work, contact a field engineer or the Teradata Global Support Center. BAM1009 Access Module currently does not support repositioning when writing to backup files Teradata Extension for Tivoli Storage Manager does not support restart processing when a backup file is opened in WRITE mode because it is not possible to reposition to the exact point of failure inside TSM. This means that Teradata Extension for Tivoli Storage Manager rolls back and deletes all data written to TSM up to this point. Remedy: Do one of the following: Resubmit the job from the beginning of the current ARCMAIN step, Instead of resubmitting the job, issue a RELEASE LOCK statement on the Teradata server to remove any database locks set. 142 Teradata Extension for Tivoli Storage Manager Administrator Guide

143 Chapter 7: Troubleshooting for the TARA Vendor-Independent Error Messages 23: Vendor Independent Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1010 BAM1011 SetPos generation < > does not match current file generation of < > SetPos file segment number < > not found in retrieved list of backup segments When Teradata Extension for Tivoli Storage Manager creates a new backup file, it stores a unique generation number in the Object Info field of the storage object. This error occurs when a reposition operation detects that the position being requested is for a backup file with a different generation number from the one that is currently open. Normally, this condition indicates a corrupted position field managed by ARCMAIN. However, when using the CATALOG feature of ARCMAIN to get fast repositioning on a restore, ARCMAIN can pick up a position that is inconsistent with the backup files in storage. This condition can happen under the following circumstances: 1 Regularly running the same backup job, saving position information to the CATALOG database. 2 Creating additional backups without using the CATALOG option, so there is no position information saved. 3 Running a restore using the most recent backup image from storage. In this case, the most recent image in storage might correspond to generation 103, when the most recent backup image in the CATALOG database corresponds to generation 102. Remedy: Examine ARCMAIN listings and the storage catalog, and do one of the following: If a user error occurred, make corrections and resubmit the job. If no user error occurred, consult a field engineer or the Teradata Global Support Center. Teradata Extension for Tivoli Storage Manager cannot find the requested file segment number when a request was made to reposition the file within the backup set. Either the position information is corrupted, or a mismatch occurred between the backup set being requested and the position information. Remedy: Contact a field engineer or the Teradata Global Support Center. Teradata Extension for Tivoli Storage Manager Administrator Guide 143

144 Chapter 7: Troubleshooting for the TARA Vendor-Independent Error Messages 23: Vendor Independent Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1012 < > < > error < > < > Teradata Extension for Tivoli Storage Manager detects an unexpected error when starting a function of TSM. The nature of the error is indicated in the message by naming the TSM product, the API function being called, the error code, and the error message text. This type of error can be difficult to fix. Teradata Extension for Tivoli Storage Manager is customized to work with site-specific APIs, but configuration to work with TSM and ARCMAIN can be complex. Remedy: Correct the job or configuration settings. To run Teradata Extension for Tivoli Storage Manager with an option that is not recognized on the IOPARM of an ARCMAIN job, configure the TSM runtime environment to set the option as a default configuration option. To avoid resubmitting a job, issue a RELEASE LOCK statement on the Teradata Database to remove any database locks set and clean up the server. BAM1013 Storage object created on platform < > The backup file being restored was generated on a different operating system. The platform number identifies the operating system that created the backup. Remedy: Resubmit the job on the same platform that created backup. BAM1014 Invalid Segment name for NameSpace= < >, Pathname= < >, Segment= < >, CopyId= < >. Skipping. When querying the TSM storage catalog metadata, Teradata Extension for Tivoli Storage Manager found a storage object that qualified on the name pattern, but does not follow the proper naming convention. This is not a fatal error message, but the relevant object is omitted from processing because Teradata Extension for Tivoli Storage Manager cannot properly parse the segment name. Teradata Extension for Tivoli Storage Manager stores segment sequence numbers as part of the file segment name. For example, F0014 corresponds to the 15th file segment of a single ARCMAIN backup file. (File segment numbering starts at zero.) Remedy: Rename the segment name if NameSpace and PathName are too close to the name chosen for another storage process. If the skipped object was created by a Teradata backup operation, report the issue to a field engineer or to the Teradata Global Support Center. 144 Teradata Extension for Tivoli Storage Manager Administrator Guide

145 Chapter 7: Troubleshooting for the TARA TSM Error Messages 23: Vendor Independent Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1015 Unable to open diagnostic file < > because < >. Logging disabled. BAM1017 Unable to open DEFAULT file < > because < > Diagnostic logging is requested, but Teradata Extension for Tivoli Storage Manager is unable to open the file. This is a non-fatal error, but no diagnostic logging is captured. The cause of the file open error is indicated. Teradata Extension for Tivoli Storage Manager opens the log file in write-append mode. Periodic purging of this file is necessary. Remedy: Correct the problem, and resubmit the job. Teradata Extension for Tivoli Storage Manager is unable to open the command line DEFAULT file. The cause of the file open error is indicated. The DEFAULT file is specified with the BARAM_DEFAULT environment variable. Remedy: Specify a valid path to a DEFAULT file that is accessible to your user ID, then resubmit the job. BAM1018 Access Module is aborting the backup transaction Teradata Extension for Tivoli Storage Manager was called to close the backup file in an error condition. The write transaction is aborted and all storage objects created by this job are rolled back. This is an informational message rather than a report of the root cause of an error condition. ARCMAIN indicates the cause of the error or reports that the backup process is interrupted. Remedy: Correct the root cause of the error and resubmit the job. For further information, refer the output listing to the Teradata Global Support Center. BAM1019 Access Module is aborting due to Insufficient Memory This error occurs when Teradata Extension for Tivoli Storage Manager runs out of memory while attempting to allocate resources. A number of conditions can cause insufficient memory, including a lack of memory or swap space. Remedy: Correct the root cause of the error, then resubmit the job. TSM Error Messages Error messages that range from 1200 to 1299 (shown in 24) originate in the TSM portion of Teradata Extension for Tivoli Storage Manager. Note that some of the error codes have multiple error messages. Teradata Extension for Tivoli Storage Manager Administrator Guide 145

146 Chapter 7: Troubleshooting for the TARA TSM Error Messages 24: TSM Error Messages Error Code Error Message Text Description and Remedy BAM1200 Access Module needs Tivoli Version < > Release < > but client library is Version < > Release < > BAM1201 Tivoli dsmendtxn error < >, (reason < >): < > Teradata Extension for Tivoli Storage Manager detects an invalid software library release level. The path to the loaded extension is set with the IOMODULE command line parameter to ARCMAIN. Remedy: Correct the configuration issue and resubmit the job. Teradata Extension for Tivoli Storage Manager detects an unexpected error when starting a TSM End Transaction function. The error code, reason code, and error message text indicate the nature of the error. Reason codes usually correspond to numbers 1 through 50 of the API return codes. For more information on the API return codes, see IBM s TSM Messages manual. If this error occurs when writing backup files to the TSM, Teradata Extension for Tivoli Storage Manager rolls back and deletes all file segments written to TSM up to this point, except file segment 0 (F000). Remedy: For recommendations about correcting the cause of this error, refer to the TSM documentation. Do one of the following: To run Teradata Extension for Tivoli Storage Manager with an option that is not recognized on the IOPARM of the ARCMAIN job, configure the TSM runtime environment to set the option as a default configuration option. If you do not resubmit the job, issue a RELEASE LOCK statement on the Teradata Database to remove any database locks set, then clean up the Teradata server. BAM1202 Tivoli Backup Copy Group does not exist for object FileSpace= < >, HighLevel= < >, LowLevel= < > TSM is unable to assign a copy group for the backup object being created. This situation is the result of an API dsmbindmc call. The object name is listed as FileSpace, HighLevel name, and LowLevel name. Remedy: Consult the TSM administrator to determine the source of the problem. 146 Teradata Extension for Tivoli Storage Manager Administrator Guide

147 Chapter 7: Troubleshooting for the TARA TSM Error Messages 24: TSM Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1203 Tivoli Storage object FileSpace= < >, HighLevel= < >, LowLevel= < >, ID= < > is not recognized by Access Module. Skipping. Teradata Extension for Tivoli Storage Manager is unable to interpret the formatted metadata, which is usually stored with the storage object. The object is skipped and processing for the object stops, although processing continues for the balance of the job. This error is usually generated because a storage object exists in TSM that has a similar name to a Teradata backup created by Teradata Extension for Tivoli Storage Manager. The specified object name in the query is picking up more than it should. This warning message does not terminate processing because Teradata Extension for Tivoli Storage Manager cannot communicate a non-fatal warning condition to ARCMAIN. As a result, the return code indicator from ARCMAIN can be zero, even though this message is displayed. Remedy: Use the indicated diagnostic information to verify the status of the storage object. If the storage object is considered for Teradata backup and restore, contact the Teradata Global Support Center. If the object is being incorrectly qualified because the wildcard specification is too general, restate the query so it is correctly limited to the storage objects created by Teradata Extension for Tivoli Storage Manager. BAM1204 TDDSMC syntax error: < > The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error in the command. The message indicates the source of the error. Remedy: Correct the syntax and resubmit the job. For more details, issue the HELP command or refer to Taratddsmc Help Command. BAM1205 TDDSMC syntax error: < > field width cannot exceed < > The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on a FORMAT string. The field width override value for the indicated substitution variable is too long. Remedy: Correct the syntax and resubmit the job. For more details, issue the HELP FORMAT command or refer to Taratddsmc Help Command. Teradata Extension for Tivoli Storage Manager Administrator Guide 147

148 Chapter 7: Troubleshooting for the TARA TSM Error Messages 24: TSM Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1206 Tivoli server aborted transaction during < > call. Error < >, (reason < >): < > TSMserver aborted the client transaction for the noted reason code. For more information on the API return codes, see the TSM Messages manual. Reason codes usually correspond to numbers 1 through 50 of the API return codes. If this error occurs when writing backup files to the TSM, Teradata Extension for Tivoli Storage Manager rolls back and deletes file segments written to TSM up to this point, except file segment 0 (F000). If the text of the message indicates a zero value for the reason code, issue a QUERY ACTIVITYLOG command on the TSM server to determine the root cause of the abort. Remedy: For recommendations about correcting the cause of this error, refer to the TSM documentation. Do one of the following: To run Teradata Extension for Tivoli Storage Manager with an option that is not recognized on the IOPARM of the ARCMAIN job, configure the TSM runtime environment to set the option as a default configuration option. If you do not resubmit the job, issue a RELEASE LOCK statement on the Teradata Database to remove any database locks set, then clean up the Teradata server. BAM1207 BAM1208 TDDSMC syntax error: Expected quote string at >> ( ) << on command line TDDSMC syntax error: No matching and quote character on command line The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on the command line arguments used to start the utility. This error is the result of a quote string not being found at the specified position. Remedy: Correct the syntax and resubmit the job. For more details about command line syntax, issue the HELP command or refer to Taratddsmc Help Command. The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on the command line arguments used to start the utility. A quote string was detected, but no matching end-quote was found. The TDDSMC utility recognizes single- and double-quote characters, but sometimes the operating system strips quotes before passing the command line to the utility. After a quote character is detected, the utility will keep scanning the command line for a matching end-quote. Remedy: Correct the syntax and resubmit the job. For more details about command line syntax, issue the HELP command or refer to Taratddsmc Help Command. 148 Teradata Extension for Tivoli Storage Manager Administrator Guide

149 Chapter 7: Troubleshooting for the TARA Troubleshoot Utility 24: TSM Error Messages (continued) Error Code Error Message Text Description and Remedy BAM1209 TDDSMC syntax error: Extraneous information follows < > command starting at: < > The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on the command line arguments used to start the utility. A valid command was parsed, but non-blank trailing characters were detected. This error can occur when an unquoted name pattern contains embedded blanks. There are optional fields after the name pattern. Therefore, the actual source of the syntax error might be prior to the position indicated. Remedy: Correct the syntax and resubmit the job. For more details about command line syntax, issue the HELP command or refer to Taratddsmc Help Command. BAM1210 Access Module cannot backup more than 4080 objects. TSM limits the number of objects that can be retrieved at one time to DSM_MAX_GET_OBJ (4080). Therefore Teradata Extension for Tivoli Storage Manager does not back up more than 4080 object segments. The maximum size of one backup job cannot exceed approximately 8 TB. Remedy: Modify backup jobs to contain less data. Troubleshoot Utility There is a troubleshoot utility that provides problem and remedy details for any ARC or Teradata Extension for Tivoli Storage Manager errors for TARA jobs. From the Teradata Tiered Archive/Restore Architecture screen, select Help>Troubleshoot... Teradata Extension for Tivoli Storage Manager Administrator Guide 149

150 Chapter 7: Troubleshooting for the TARA TARA Server Stop and Restart The Troubleshoot screen appears. Enter the Error Code. Click Search. The description, problem, and remedy appear. Note: The error code can be an ARC or Teradata Extension for Tivoli Storage Manager (BAM) error. For example, it can be ARC0001 or BAM0001. TARA Server Stop and Restart The command line can be used to stop and restart the TARA server. To stop and restart the TARA server 1 Type: /etc/init.d/tdtaraserver stop 150 Teradata Extension for Tivoli Storage Manager Administrator Guide

151 Chapter 7: Troubleshooting for the TARA Use of the Command Line to Obtain Information Wait 60 seconds. If you attempt to start the tdtaraserver script immediately after stopping the service, the operation might fail. 2 Type: /etc/init.d/tdtaraserver start Use of the Command Line to Obtain Information Use the command line to: Query current and prior jobs launched through Teradata TARA Obtain launch times Obtain script names Type: /opt/teradata/tara/gui/bin/tarajobquery -L The output is similar to the following: File Name/Job ID Job Name Date Stream Cnt 469d frank :47: d42ff frank :33: d42ff frank :49:06 1 Teradata TARA GUI on Java Runtime Extension On Windows, the TARA GUI setup.exe installs a.jar file that allows the GUI to run under the Java Runtime Extension (JRE). The taragui.jar file is located at \Program Files\Teradata\TARA\gui\bin. On Linux, the TARA GUI.rpm package installs the.jar file. The taragui.jar file is located at /opt/teradata/tara/gui/bin. To run the GUI, download the file to a Windows or Linux machine with JRE and double-click the file. States for Archive Jobs When a Teradata archive job is started through Teradata TARA, the state of each cluster stream changes during the job launch process. The State column of the Teradata Tiered Archive/Restore Architecture dialog box displays the archive job states, which are shown in 25: Teradata Extension for Tivoli Storage Manager Administrator Guide 151

152 Chapter 7: Troubleshooting for the TARA Job Stream Connection Failure 25: States for Archive Jobs State Step in Job Launch Description Connecting 1 Each backup stream must connect to the MultiARC server. Logon 2 After the streams receive instructions from the ARC server, they log in their sessions to the Teradata Database. Tape Mount 3 After the ARC sessions are logged into the Teradata Database, the request for media is sent through Tivoli. Archive 4 After the media is made available by Tivoli, the archive process begins moving data to the media. In the Bytes Processed column of the Teradata Tiered Archive/Restore Architecture dialog box, the number of bytes should start increasing. Waiting 5 In a waiting state, one of the following happens: a child stream is waiting for instructions from the master stream (Stream 1) the master stream is waiting for a child stream to complete the current instruction Logoff 6 The stream is in the process of closing its ARC sessions; the job ends. Job Stream Connection Failure Symptom The job stream fails: in the TARA GUI, the job stream is shown trying to connect for some time before it fails. This occurs because of a MultiARC server time-out, and suggests that a problem has occurred before the ARC streams have connected to the MultiARC server. This symptom normally occurs after a recent installation or reconfiguration of Teradata TARA or Teradata ARC. The first step in investigating the problem is Step 1: Verify that ARC Output Files are Being Created. Step 1: Verify that ARC Output Files are Being Created On each media server, ARC output (.out) files are located in the /home/baruser account. These files are required when Teradata TARA launches Teradata ARC. If an ARC.out file with a matching timestamp of the attempted launch exists, open the ARC log and examine possible errors provided by the client utility. If no ARC.out file exists, or an.out file of 0 bytes exists, Teradata ARC is not being launched properly. This indicates that Teradata TARA cannot find the ARCMAIN binary or the permission on the script that launches Teradata ARC is not correct. Go to Step 2: Examine the Script that Launches Teradata ARC. 152 Teradata Extension for Tivoli Storage Manager Administrator Guide

153 Chapter 7: Troubleshooting for the TARA TARA Job Output Errors Step 2: Examine the Script that Launches Teradata ARC The script that launches Teradata ARC is called runarctiv.bat and is located in /home/baruser. The baruser account must be the owner of this file or Teradata ARC will not launch. To examine the script 1 Verify that runarctiv.bat has the proper permissions and owners assigned to it: -rwxr-xr-x 1 baruser root 2274 Jul 17 15:26 runarctiv.bat 2 Determine if runarctiv.bat can properly locate the ARCMAIN binary. The runarctiv.bat script that launches ARC (in /home/baruser) uses a variable called $INSTALLPATH. The variable is defined by executing an rpm -q command to determine where the ARC package is installed: rpm -q --queryformat '%{INSTALLPREFIX}\n' arc If the result of this command produces two outputs: (none) (none) ARC might not launch. As a result, jobs in the Teradata TARA GUI could remain in the Connecting phase, and the ARC.out file could remain a zero-length file. Workaround: Edit the /home/baruser/runarctiv.bat script and verify the path to the ARCMAIN executable is hardcoded. TARA Job Output Errors Symptom In a LAN-free environment, a system error can occur when COMMTIMEOUT is set to the default value of 60 seconds or less in dsmsta.opt (Storage Agent). The two error messages that are displayed when this occurs are: ANR0481W (Session: 207, Origin: BSRV1-AGENT) Session 288 for node AJ-BAR (Teradata) terminated - client did not respond within 60 seconds. (SESSION: 207) *** Failure ARC0805:Access Module returned error code 34: Error BAM1012: Tivoli dsmgetdata error -72: ANS1235E (RC-72) An unknown system error has occurred from which TSM cannot recover. Remedy Increase COMMTIMEOUT to a larger value. For more information, refer to 9 on page 44. Teradata Extension for Tivoli Storage Manager Administrator Guide 153

154 Chapter 7: Troubleshooting for the TARA Unresponsive TARA Server Unresponsive TARA Server Symptom The TARA server is not responding to job requests, although jobs have previously run successfully in the current configuration. To test if the TARA server is unresponsive, at the command line, type: /opt/teradata/tara/gui/bin/tarajobquery -L If the TARA server is not responding, there is no response to the command. A successful result returns a list of the current and previous jobs that have been launched through Teradata TARA. Verify that there is no filesize statement that exceeds 2GB in value. See Configure the Log File on page 59. Another area to investigate is to look at the core files. See Step 1: Add ulimit. Step 1: Add ulimit If the TARA server is unresponsive, add ulimit -c to the /etc/init.d/tdtaraserver script to produce core files. Doing so kills the process ID to obtain the core file: case "$1" in start) echo -n 'Starting taraserver ' ulimit -c if [ $KTYPE -eq 0 ]; then Core files are located in /opt/teradata/tara/server/config: For example: lussdgsc-bar00:/opt/teradata/tara/server/config # ls -l total 1690 drwx taraserver root 176 Aug 28 11:24. drwxr-xr-x 7 root root 168 Aug 9 15:13.. -rw taraserver users Aug 28 11:01 core rwxr-xr-x 1 taraserver root 901 Aug 13 14:57 defaults -rwxr-xr-x 1 root root 430 Aug 10 15:16 defaults_original Note: For the core ulimit setting to take effect, restart the TARA server. If core files do not provide an answer, look at the TARA server log. See Step 2: Change Verbosity of TARA Server Log. Step 2: Change Verbosity of TARA Server Log Change the verbosity of the TARA server log, logfile, located at /opt/teradata/tara/server/logs with the next procedure. 154 Teradata Extension for Tivoli Storage Manager Administrator Guide

155 Chapter 7: Troubleshooting for the TARA Unresponsive TARA Server To change the verbosity of the TARA server log Note: The TARA server does not have to be restarted before performing this procedure. 1 Start the Teradata TARA GUI. 2 Click Settings>Server Configuration>Logging. 3 Check the Override Global Log Level box. 4 Adjust the level of logging for the specific processes. 5 Click Apply, then close the dialog box. For example, when troubleshooting jobs that are launching, change the: Arc Log Setting to 48 Gui Log Setting to 48 Launch Log Setting to 63 Temporary workaround: Stop, then restart the TARA server to get the backup jobs operational in the meantime. Teradata Extension for Tivoli Storage Manager Administrator Guide 155

156 Chapter 7: Troubleshooting for the TARA Unresponsive TARA Server 156 Teradata Extension for Tivoli Storage Manager Administrator Guide

157 APPENDIX A Installation and Configuration: Command Line Utility This chapter discusses: Configuration Requirements Installation Removal of the Teradata Access Module Configuration of TSM for Teradata Backups LAN Configuration Configuration Requirements The following hardware, software, and LAN configurations are required before installing Teradata Access Module for Tivoli. Hardware Software The Teradata Access Module for Tivoli is certified for installation only for 32-bit Windows 2000 and 2003 platforms (Server or Professional). Before installing the Teradata Access Module for Tivoli, verify that the following products are already installed at the proper release levels: Note: NCR software is not certified to run with Unicode support enabled. IBM Tivoli Storage Manager Server or is a prerequisite, but does not need to be installed on the same hardware node as the Teradata Access Module for Tivoli software. IBM Tivoli Storage Manager Backup-Archive Client or must be installed on every node where ARCMAIN is run with Teradata Access Module for Tivoli. IBM Tivoli Storage Manager Storage Agent or (for LAN-free data movement only) must be installed on every node where ARCMAIN is run with Teradata Access Module for Tivoli. However, the Storage Agent cannot reside on the same node where the TSM server is installed. Windows versions of these Teradata Tools and Utilities components, version or later: Teradata Extension for Tivoli Storage Manager Administrator Guide 157

158 Appendix A: Installation and Configuration: Command Line Utility Installation ARCMAIN Data Connector Call-Level Interface version 2 (CLIv2) Shared ICU Libraries for Teradata (tdicu) Teradata GSS Client Local Area Network (LAN) Connections and Platforms The Teradata Access Module for Tivoli operates in LAN-attached or LAN-free modes. For optimal performance, install the Teradata Access Module for Tivoli on the same LAN where the Teradata Database is installed. Use private high-speed subnets with gigabit or better technology for all LAN connections that perform large-volume data transfers. To ensure optimal throughput, configure the gigabit adapter to support jumbo frames. An example of an optimized LAN connection is a link between MP-RAS and a Windows 2000 node that is running ARCMAIN and the Teradata Access Module for Tivoli. Follow these recommendations for running TSM in LAN or LAN-free mode: If TSM is running in LAN mode, the Teradata Access Module for Tivoli node sends all backup data to the TSM server node, which then writes the data to storage. A private high-speed LAN connection is recommended between the TSM client and the TSM server. If TSM is running in LAN-free mode, a high-speed LAN connection between the Windows 2000 node that runs the Teradata Access Module for Tivoli and the TSM server is not necessary because the link only has to accommodate metadata and control information. Installation The Teradata Access Module for Tivoli is released on the Teradata Tools and Utilities 8.0 Edition 2 CD, labeled Tape Storage Management Enablers. To install the Teradata Access Module for Tivoli 1 On the CD, locate the tivoliam\windows directory and click SETUP.EXE. The Install Configuration Files dialog box appears. 2 Specify the installation location for the BAR configuration files and customize the files as shown. 158 Teradata Extension for Tivoli Storage Manager Administrator Guide

159 Appendix A: Installation and Configuration: Command Line Utility Installation The options for this dialog box are: Option BAR Configuration Directory BAR Working Files Directory TSM Client Options File Copy TSM Client Options File to BAR Config Directory Replace existing configuration files Description This option specifies where the arcdflt.txt, tivdflt.txt, Tivoli.Readme.txt, and optional dsm.opt files are to be installed. For an explanation of these files, see Installed Files on page 160. This is an empty directory, which is recommended as the starting directory for all ARCMAIN and TDDSMC processes. This option specifies the location of the TSM Options file. If the TSM Backup/Archive Client is installed, the value shown is the actual location of the dsm.opt file. If the Backup/Archive Client is not installed, the value represents the default location of the file. This checkbox is selected if the Backup/Archive Client is installed; otherwise, it is blank. Note: If the dsm.opt file is copied over an existing file, any changes made to the existing file are lost. Select this checkbox to replace existing configuration files; otherwise, leave it blank. Note: If existing configuration files are replaced, any existing changes are lost. 3 Click OK to install the tddsmc.exe, tivbar.dll, tivadm.bat, and tivarc.bat files to the directory in which the ARCMAIN executable resides. This action creates a BAR configuration directory and BAR working files directory, and customizes the tivadm.bat and tivarc.bat files to contain the location and name of the TSM Client Options file and locations of the BAR configuration and BAR working files directories. Teradata Extension for Tivoli Storage Manager Administrator Guide 159