Teradata Extension for NetBackup Administrator Guide

Teradata Extension for NetBackup
Administrator Guide
Release 15.00
B035-2400-034K
March 2014
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo Marketing Studio, Aster, BYNET, Claraview,
DecisionCast, Gridscale, MyCommerce, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata
Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and
other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
Apache, Apache Hadoop, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation
in the United States and/or other countries.
Apple, Mac, and OS X all are registered trademarks of Apple Inc.
Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access,
Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum
Support are servicemarks of Axeda Corporation.
Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other
countries.
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 is a registered trademark 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.
NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries.
Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
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 registered trademark of Unicode, Inc. in the United States and other countries.
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 email: 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 © 2002-2014 by Teradata. All Rights Reserved.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Preface
Purpose
This book provides information on how to install, configure, and use Teradata® Extension for
NetBackup™ on Microsoft Windows® 2003 and SUSE™ Linux platforms. Teradata Extension
for NetBackup is used with Symantec™ NetBackup™ software.
Teradata Extension for NetBackup extends the capabilities of the Symantec NetBackup
product to include backing up and restoring Teradata Databases. The full functionality of the
NetBackup server and the multiple media servers is realized in Teradata Extension for
NetBackup.
Audience
This book is intended for use by:
•
Teradata system administrators responsible for configuring and using Teradata
•
NetBackup system administrators responsible for configuring Symantec NetBackup
Supported Releases
•
Teradata Database 12.0, 13.0, 13.10, 14.0, 14.10 and 15.0
•
Teradata Tools and Utilities 14.10 or later
Note: Teradata Tools and Utilities must be greater than or equal to the Teradata Database
version.
•
Symantec NBU 7.0.1 64-bit on SUSE Linux Enterprise Server 10
•
Symantec NBU 7.0.1 32-bit on Windows 2003 32-bit SP 2
•
Symantec NBU 7.0.1 64-bit on Windows 2003 64-bit SP 1 or Windows 2008 64-bit
•
Symantec NBU 7.1 64-bit on SUSE Linux Enterprise Server 10 or SUSE Linux Enterprise
Server 11
•
Symantec NBU 7.1 32-bit on Windows 2003 32-bit
•
Symantec NBU 7.1 64-bit on Windows 2003 64-bit or Windows 2008 64-bit
•
Symantec NBU 7.5.0.3 64-bit on SUSE Linux Enterprise Server 10 or SUSE Linux
Enterprise Server 11
•
Symantec NBU 7.5.0.3 32-bit on Windows 2003 32-bit
Teradata Extension for NetBackup Administrator Guide, Release 15.00
3
Preface
Prerequisites
•
Symantec NBU 7.5.0.3 64-bit on Windows 2003 64-bit or Windows 2008 64-bit
•
Symantec NBU 7.6
To locate detailed supported-release information:
1
Go to http://www.info.teradata.com/.
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:
•
A basic understanding of Windows 2003 system administration
•
A working understanding of the Symantec NetBackup for Windows 2003 server software
•
A familiarity with information covered in these Symantec NetBackup manuals:
•
•
NetBackup System Administrator’s Guide
•
NetBackup for Teradata on Windows System Administrator’s Guide
A thorough understanding of Teradata administration
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 Teradata BAR
Backup Application Software Release Definition associated with this release.
4
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Preface
Additional Information
Date and Release
Description
March 2014
• Clarified that a single stream must be specified when creating a
Dictionary Only backup job.
• Added information to step 1 of To synchronize job files.
• Added Linux information for User Account Requirements.
• New topics:
• Overriding the Existing NetBackup CLIENT_READ_TIMEOUT
Value
• Converting from OpenSSH to TCS
• Estimating the Size for the TARA Server Repositories
• TARA Server and TARA Client Log Files
15.00
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.
Type of Information
Description
Access to Information
Release overview
Use the Release Definition for the following
information:
1 Go to http://www.info.teradata.com/.
• 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
3 Type 2029 in the Publication Product ID box.
Late information
Teradata Extension for NetBackup Administrator Guide, Release 15.00
2 Under Online Publications, click General Search.
4 Click Search.
5 Select the appropriate Release Definition from
the search results.
5
Preface
Additional Information
Type of Information
Description
Access to Information
Additional product
information
Use the Teradata Information Products web
site to view or download specific manuals
that supply related or additional
information to this manual.
1 Go to http://www.info.teradata.com/.
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
NetBackup are:
• Teradata Archive/Recovery Utility Reference
B035-2412-mmyx
Provides a full description of the syntax used in
an Arcmain script.
• Teradata Tools and Utilities Installation Guide for
Microsoft Windows
B035-2407-mmyx
Provides information on how to install the
Teradata client products that are required by
NetBackup for Teradata:
• Teradata Call-Level Interface (CLI)
• Teradata ODBC Driver for Teradata (ODBC)
• Teradata Archive and Recovery Utility (ARC)
NetBackup manuals:
• NetBackup System Administrator’s Guide
Explains how to configure and manage
NetBackup for a Windows server system.
• NetBackup Media Manager System
Administrator’s Guide for Windows
Explains how to configure and manage the
storage devices and media for Windows
NetBackup servers. Media Manager is part of
NetBackup.
• NetBackup Troubleshooting Guide for Windows
Provides troubleshooting information for
Windows-based NetBackup products. Refer to
www.symantec.com/business/support/ to access
the Knowledge Base Search option and search
for TechNotes.
6
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Preface
Product Safety Information
Type of Information
Description
Access to Information
CD-ROM images
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.
1 Go to http://www.info.teradata.com/.
2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing.
3 Click CD-ROM Images.
4 Follow the ordering instructions.
Ordering
information for
manuals
Use the Teradata Information Products web
site to order printed versions of manuals.
1 Go to http://www.info.teradata.com/.
2 Under Print & CD Publications, click How to
Order.
3 Follow the ordering instructions.
General information
about Teradata
The Teradata home page provides links to
numerous sources of information about
Teradata. Links include:
1 Go to http://www.teradata.com/t/resources.
2 Select a link.
• Executive reports, case studies of
customer experiences with Teradata,
and thought leadership
• Technical information, solutions, and
expert advice
• Press releases, mentions, and media
resources
Product Safety Information
This document may contain information addressing product safety practices related to data or
property damage, identified by the word Notice. A notice indicates a situation which, if not
avoided, could result in damage to property, such as equipment or data, but not related to
personal injury.
Example:
Notice:
Improper use of the Reconfiguration utility can result in data loss.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
7
Preface
Product Safety Information
8
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Product Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Chapter 1:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Overview of Symantec NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetBackup Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administrator and User Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
24
NetBackup Features and Teradata Extension for NetBackup. . . . . . . . . . . . . . . . . . . . . . . . . . 24
Supported NetBackup Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Non-Supported NetBackup Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Overview of Teradata Extension for NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Teradata TARA Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
General Backup and Restore Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Creation of Backup and Restore Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
UTF-8 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 2:
Teradata TARA Installation and Uninstallation . . . . . . . . . . . . . . . . 29
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Teradata Extension for NetBackup Administrator Guide, Release 15.00
9
Table of Contents
Non-Teradata Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Teradata Tools and Utilities Software for 32-Bit and 64-Bit Linux . . . . . . . . . . . . . . . . . .30
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Non-Teradata Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Teradata Tools and Utilities Software for 32-Bit Windows . . . . . . . . . . . . . . . . . . . . . . . . .30
Teradata Tools and Utilities Software for 64-Bit Windows . . . . . . . . . . . . . . . . . . . . . . . . .31
User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Teradata TARA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Overview of Installation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
TARA Communication Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Installation Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Installation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Estimating the Size for the TARA Server Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
TARA Component Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Installation of Teradata TARA Components on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Installation of Teradata TARA Components on Windows . . . . . . . . . . . . . . . . . . . . . . . . .39
The xinetd Process on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
TARA Server Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Teradata TARA GUI Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
NetBackup Access Module Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Uninstallation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Uninstallation on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Chapter 3:
Teradata TARA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Start the NetBackup Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Configure the Media Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Set Maximum Jobs per Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Configure a NetBackup Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Add Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Add Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Configure an Application Backup Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Configure an Automatic Backup Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Specify Schedule Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Specify the Scripts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
10
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Table of Contents
Add Clients to a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Test Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configure Client Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Method #1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Method #2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Create Restore Userids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
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 ARC Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 5 - Configure NetBackup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 6 - TARA Server Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 7 - Password Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 8 - Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
64
66
67
69
70
71
72
74
Configure the TARA Server GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Increasing the Java Heap Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configure the Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 4:
Backup, Restore, and Migrate Operations . . . . . . . . . . . . . . . . . . . . . . . 77
Start the Teradata TARA GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Displaying Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Archive a Database Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Dictionary Only Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Automatic Scheduling by NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Select Individual Objects to Archive or Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Restore a Database Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Overriding the Existing NetBackup CLIENT_READ_TIMEOUT Value . . . . . . . . . . . . . 99
Dictionary Only Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Analyze Using Script Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Analyze Using Restore DBC Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
CopyScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restore Latest Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Restore a Multistream Archive Using Fewer Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Manually Restore a Multistream Archive Using Fewer Streams. . . . . . . . . . . . . . . . . . . . . . . 110
Restore the DBC Database Backup Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Valid Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Teradata Extension for NetBackup Administrator Guide, Release 15.00
11
Table of Contents
Validate Edited Job Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
No Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Permitted Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Stream Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Exclude Tables in Job Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Synchronize TARA JobFiles with NetBackup Catalog Images . . . . . . . . . . . . . . . . . . . . . . . . .117
Modified Job Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Extensions for Job Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
View Job History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Abort Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Delete Failed Jobs in Job History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Search for Strings in Job Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Migrate an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Migrate an Existing Dictionary Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Verify a Migrated Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Delete Temporary Files in baruser Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Chapter 5:
Retrieval of Teradata NetBackup Image
Names Using bplist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Extract all Teradata Extension for NetBackup Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Chapter 6:
Teradata TARA Command-Line Utilities . . . . . . . . . . . . . . . . . . . . . . . . . .135
TARAJobRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
TARAJobQuery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Code Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Sample List Option Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Sample Query Option Output - Traditional View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Sample Query Option Output - Hierarchical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Sample Query Option Output with NetBackup Job Information. . . . . . . . . . . . . . . . . . .150
TARALaunch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Guidelines and Parameters for Launching Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Parameters for Aborting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
TARALaunch Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
TARALaunch Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
12
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Table of Contents
Sample Lines of Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
TARAMigrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Sample Lines of Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
taraping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Sample Lines of Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
TARAScriptConv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Sample Lines of Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
TARASetCfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Sample Lines of Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Chapter 7:
Reference for Teradata TARA GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Teradata Tiered Archive/Restore Architecture Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . 176
ARCHIVE Object Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Assign Clients Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Auto Generate Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Graphic User Interface Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Job History Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Log on to Teradata DBS Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Migration Interface Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Migration Object Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Options Dialog Box for Archive Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Options Dialog Box for Restore Operations - Copy Options Tab . . . . . . . . . . . . . . . . . . . . . 189
Options Dialog Box for Restore Operations - PPI Options Tab . . . . . . . . . . . . . . . . . . . . . . 190
Policy Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Rename Script Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
RESTORE Object Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Save Script Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Script Editor Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Script Options Dialog Box for Archive Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Script Options Dialog Box for Restore Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
TARA Server Configuration Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TARA Server Configuration Dialog Box: Teradata Tab . . . . . . . . . . . . . . . . . . . . . . . . . .
TARA Server Configuration Dialog Box: Clients Tab . . . . . . . . . . . . . . . . . . . . . . . . . . .
TARA Server Configuration Dialog Box: Client Groups Tab . . . . . . . . . . . . . . . . . . . . .
Teradata Extension for NetBackup Administrator Guide, Release 15.00
205
206
207
208
13
Table of Contents
TARA Server Configuration Dialog Box: ARC Options Tab . . . . . . . . . . . . . . . . . . . . . . .210
TARA Server Configuration Dialog Box: NetBackup Tab . . . . . . . . . . . . . . . . . . . . . . . . .211
TARA Server Configuration Dialog Box: TARA Server Port Tab . . . . . . . . . . . . . . . . . . .212
TARA Server Configuration Dialog Box: TARA Logon Setup Tab. . . . . . . . . . . . . . . . . .213
TARA Server Configuration Dialog Box: Logging Tab . . . . . . . . . . . . . . . . . . . . . . . . . . .213
Chapter 8:
Teradata TARA Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Troubleshoot Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Creating a Diagnostic Bundle for Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
TARA Support Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
Script, Log, and .zip File Names and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
Support Bundle Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
TARA Server Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
TARA Server and TARA Client Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Teradata and NetBackup Debug Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Other NetBackup Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
TARA Server Repositories Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Client and Server System Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Client Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Server Heartbeat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Backup Jobs with the Same Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
TARA Server Stop and Restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
Command Line for Obtaining Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
States for Archive Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
Job Stream Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Symptom. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Step 1: Verify that ARC Output Files are Being Created . . . . . . . . . . . . . . . . . . . . . . . . . .223
Step 2: Examine the Script that Launches Teradata ARC. . . . . . . . . . . . . . . . . . . . . . . . . .223
Step 3: Test SSH Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
Step 4: Examine Directory Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
Step 5: Verify that Encryption Specifications Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226
Failure 8205 Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226
Unresponsive TARA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Symptom. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Step 1: Add ulimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Step 2: Change verbosity of TARA Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Recovery to a Different TARA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
Import Images to NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
14
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Table of Contents
Run an Analyze Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alternative Method for Moving Image and Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TARA Restore and Copy Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Errors After the Import Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . .
229
231
232
235
Appendix A:
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
TARA Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM0011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM0018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM0020 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM0024 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM0033 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM0013 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1015 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1017 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1019 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BAM1300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
241
241
241
242
242
242
242
243
243
243
244
244
244
245
245
245
246
246
247
247
248
248
248
249
249
Appendix B:
Methods to Obtain NetVault Capabilities in NetBackup . . . . . 251
NetVault Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Discard after “X” Full Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Teradata Extension for NetBackup Administrator Guide, Release 15.00
15
Table of Contents
Appendix C:
TVI Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
TVI Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
16
Teradata Extension for NetBackup Administrator Guide, Release 15.00
List of Figures
Figure 1: NetBackup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 2: Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 3: TARA Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 4: NetBackup Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 5: NetBackup Job Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 6: Task Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 7: Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Teradata Extension for NetBackup Administrator Guide, Release 15.00
17
List of Figures
18
Teradata Extension for NetBackup Administrator Guide, Release 15.00
List of Tables
Table 1: NetBackup Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 2: Administrator and Client User Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 3: TARA Command-Line Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 4: GUI Chapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 5: User Accounts and Permissions for Linux Environment . . . . . . . . . . . . . . . . . . . . . . 31
Table 6: User Accounts and Permissions for Windows Environment . . . . . . . . . . . . . . . . . . . 32
Table 7: CD Installation Packages and Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 8: Actions Taken when TARA Server Package Installed . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 9: Subdirectories of taraserver_postinstall.sh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 10: Files in bin Subdirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 11: Folders and Registry Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 12: Description of Policy Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 13: Description of Backup Types for Teradata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 14: Examples of Settings for an Application Backup Schedule. . . . . . . . . . . . . . . . . . . . 58
Table 15: Examples of Settings for an Automatic Backup Schedule . . . . . . . . . . . . . . . . . . . . 59
Table 16: Description of Schedule Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 17: NetBackup Job Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Table 18: Object Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 19: Keywords for Job Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Table 20: Parameters for TARAJobRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Table 21: TARAJobRM Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Table 22: Parameters for TARAJobQuery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Table 23: Parameters for TARALaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Table 24: TARALaunch Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table 25: Parameters for TARAMigrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Table 26: Taraping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 27: Taraping Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 28: Parameters for TARAScriptConv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 29: Parameters for TARASetCfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Table 30: Teradata Tiered Archive/Restore Architecture Dialog Box . . . . . . . . . . . . . . . . . . 177
Table 31: ARCHIVE Object Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Table 32: Assign Clients Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Teradata Extension for NetBackup Administrator Guide, Release 15.00
19
List of Tables
Table 33: Auto Generate Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Table 34: Graphic User Interface Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .183
Table 35: Job History Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
Table 36: Log on to Teradata DBS Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Table 37: Migration Interface Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
Table 38: Migration Object Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Table 39: Options Dialog Box for Archive Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Table 40: Options Dialog Box for Restore Operations - Copy Options. . . . . . . . . . . . . . . . . .189
Table 41: Options Dialog Box for Restore Operations - PPI Options . . . . . . . . . . . . . . . . . . .190
Table 42: Policy Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Table 43: Rename Script Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Table 44: RESTORE Object Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Table 45: Save Script Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Table 46: Script Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Table 47: Script Options Dialog Box for Archive Operations. . . . . . . . . . . . . . . . . . . . . . . . . .198
Table 48: Script Options Dialog Box for Restore Operation. . . . . . . . . . . . . . . . . . . . . . . . . . .202
Table 49: Buttons for TARA Server Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .206
Table 50: TARA Server Configuration Dialog Box: Teradata Tab . . . . . . . . . . . . . . . . . . . . . .206
Table 51: TARA Server Configuration Dialog Box: Clients Tab. . . . . . . . . . . . . . . . . . . . . . . .207
Table 52: TARA Server Configuration Dialog Box: Client Groups Tab . . . . . . . . . . . . . . . . .208
Table 53: TARA Server Configuration Dialog Box: ARC Options Tab . . . . . . . . . . . . . . . . . .210
Table 54: TARA Server Configuration Dialog Box: NetBackup Tab . . . . . . . . . . . . . . . . . . . .211
Table 55: TARA Server Configuration Dialog Box: TARA Server Port Tab . . . . . . . . . . . . . .212
Table 56: TARA Server Configuration Dialog Box: TARA Logon Setup Tab . . . . . . . . . . . . .213
Table 57: Script, Log, and .zip File Names and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
Table 58: Support Bundle Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
Table 59: Log Folders and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Table 60: States for Archive Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
Table 61: Information on nbubar and taraserver Postscripts . . . . . . . . . . . . . . . . . . . . . . . . . .225
Table 62: NetVault Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
20
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 1
Introduction
This chapter begins with an overview of Symantec NetBackup. For those familiar with the
product, skip to the sections that describe Teradata Extension for NetBackup, its operations,
and its graphical user interfaces for Windows and Linux platforms. To learn more about
Symantec NetBackup and Teradata Extension for NetBackup, see:
•
Overview of Symantec NetBackup
•
Overview of Teradata Extension for NetBackup
•
General Backup and Restore Information
•
Creation of Backup and Restore Scripts
•
Encryption
Overview of Symantec NetBackup
This section describes Symantec NetBackup’s main functions and defines Symantec
NetBackup terminology as it applies to Teradata Extension for NetBackup. Throughout the
remainder of this book, the terms NetBackup and Symantec NetBackup are interchangeable.
For more details on NetBackup operations, refer to Symantec NetBackup documentation at
http://www.symantec.com/netbackup.
Note: In this book, the Teradata term archive is synonymous with the NetBackup term
backup. Teradata terminology defines archive as storing Teradata Database data to media. The
term archive, as used in NetBackup for non-Teradata applications, denotes storing files to
media and removing them at their source upon successful completion. Teradata does not do
that.
Data Protection
NetBackup provides data protection. Administrators can schedule automatic, unattended
backups for client systems across a network. NetBackup users can also manually back up and
restore data from their computer.
NetBackup server software resides on the computer that manages storage devices. NetBackup
client software resides on the computer that contains data to back up. There is also a Media
Manager that manages tape and optical disk storage devices.
Multiple servers can work together under the administrative control of the NetBackup master
server. The master server manages backup and restore operations. It also directs media servers,
which control additional storage devices. A master server can also function as a media server.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
21
Chapter 1: Introduction
Overview of Symantec NetBackup
During a backup operation, the client sends backup data across the network to a NetBackup
server that manages the type of storage specified in the backup policy. During a restore
operation, users can select the data to recover. NetBackup restores the data to the disk on the
client system. Figure 1 illustrates a simple NetBackup configuration.
Figure 1: NetBackup Configuration
NetBackup Terminology
Table 1 lists NetBackup terms and definitions.
Table 1: NetBackup Terminology
22
Term
Definition
BAR Server
A NetBackup BAR Server contains media server and backup client
software. A BAR server is connected to the Teradata system(s) by a private
gigabit LAN. This enables BAR server's backup client, Teradata TARA, to
perform backup and restore operations to the Teradata system using
NetBackup.
Client or Backup Client
(used interchangeably)
A BAR server where NetBackup Client software is installed.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 1: Introduction
Overview of Symantec NetBackup
Table 1: NetBackup Terminology (continued)
Term
Definition
Master Server
A BAR server where NetBackup server software is installed that has been
explicitly configured to administer all the other NetBackup components.
The master server is also responsible for scheduling of archive and restore
operations.
Note: The NetBackup master server can reside on one of the media
servers, or it can be a separate BAR server from the media servers.
Master Server Domain
The combination of all nodes (clients and servers) that have NetBackup
server or NetBackup client software installed and that are configured to
point back to the same master server.
Media Server
A BAR server where NetBackup server software is installed and has been
explicitly configured to control one or both of the following:
• Library Changer Arms
• Tape Drives
A media server is under control of the master server.
NetBackup
Administration Console
The GUI, installed on the master server, that provides the administrative
interface to the NetBackup master server and its media server.
Policy
A NetBackup policy defines the backup criteria for a specific group of one
or more clients.
Remote Administration
Console
The GUI, installed on a separate workstation, that provides the
administrative interface to the NetBackup master server and its media
servers.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
23
Chapter 1: Introduction
NetBackup Features and Teradata Extension for NetBackup
Administrator and User Responsibilities
Table 2 shows the tasks that are required of the administrator, the operations that the
administrator and client user can perform, plus the NetBackup component that is required to
run the operation.
Table 2: Administrator and Client User Responsibilities
Administrator Responsibilities
Schedule automatic, unattended
backups (Windows and Linux
clients)
Administrator or Client User
Responsibilities
Component Used to Perform
the Task
Reference Information
NetBackup Administration
Console
Chapter 3: “Teradata TARA
Configuration”
Chapter 4: “Backup,
Run backup and restore jobs One of the following:
Restore, and Migrate
(Windows and Linux clients) • NetBackup GUI
Operations”
(Windows)
Note: The administrator
does not have to be involved • Teradata TARA GUI
if the client user is manually
(Linux or Windows)
backing up or restoring the
• tdbackex command-line
job.
utility (Windows)
• TARALaunch (Linux or
Windows)
Configure tapes or other storage
units for Teradata Extension for
NetBackup configurations
(Windows and Linux clients)
Media and Device
Management of the
NetBackup Administration
Console
Media Manager for
NetBackup System
Administrator’s Guide
Set the maximum jobs per client
(Windows and Linux clients)
One of the following:
“Set Maximum Jobs per
Client” on page 54
Configure NetBackup policies
One of the following:
• NetBackup
Administration Console
• Remote Administration
Console
• NetBackup
Administration Console
• Remote Administration
Console
“Configure a NetBackup
Policy” on page 55
NetBackup Features and Teradata Extension
for NetBackup
Teradata Extension for NetBackup does not support all NetBackup licensed features.
Supported and non-supported features are listed below.
24
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 1: Introduction
NetBackup Features and Teradata Extension for NetBackup
Supported NetBackup Features
•
Encryption
•
Inline tape copy
•
Library-based tape drives
•
OpsCenter
•
OpenStorage technology (with Data Domain plugin)
•
Robotic libraries
•
Robotic library sharing support
•
Shared storage
•
Storage Lifecycle Policies
•
Vault
•
Virtual tape
Teradata Extension for NetBackup also uses a NetBackup XBSA extension to initiate userdirected backup and restore jobs. The XBSA extension is not integrated into the NetBackup
core product.
Non-Supported NetBackup Features
•
Accelerator
•
Auto-image replication
•
Compression
Note: This feature is not made available for the Teradata Policy type.
•
Extensions: DB2, Informix, Lotus Notes, MS SQL, MS Exchange, Oracle, SAP, and Sybase
•
File system options, such as
•
Checkpointing
•
NFS mount points
•
Cross mount points
•
Bare Metal Restore
Note: BMR is certified for use in backing up BAR and Viewpoint TMSB servers and
Windows standalone BAR servers.
•
Flexible disk
•
NetBackup client/media server deduplication
•
Open file backup
•
PureDisk
•
Replication Director
•
SAN client
•
Snapshot
Teradata Extension for NetBackup Administrator Guide, Release 15.00
25
Chapter 1: Introduction
Overview of Teradata Extension for NetBackup
Overview of Teradata Extension for NetBackup
Teradata Extension for NetBackup extends the capabilities of NetBackup to include backing
up and restoring Teradata Databases. It supports parallel backups and restores that are
coordinated across multiple hosts contained in a single Teradata Database. Features include:
•
Full integration with the NetBackup master server and Media Manager
•
Support for parallel job launch using a single point of control
•
Backup and restore of databases and tables
•
Client operation monitoring through the NetBackup Client Job Monitor
•
Server monitoring is also available through the NetBackup master server
•
Job launch, which is supported through these options:
•
Immediate launch through the Teradata TARA GUI
•
Scheduled launch through the NetBackup scheduler
•
Command-line launch
Graphical User Interface
The GUI provides object browsing and selection, automatic script generation, and centralized
job monitoring. It runs on any Windows or Linux host that is a client to the NetBackup
master server and that has Teradata Extension for NetBackup installed. The GUI can be used
to coordinate NetBackup client operations for multiple Teradata Database data sources.
There is browsing capability for:
•
Teradata Databases and tables
•
Backup images stored by the NetBackup server
•
Backup, restore, and restart scripts
Other features include:
•
Graphical assistance for generating backup and restore scripts
•
Single-point progress monitoring for a parallel operation
Teradata TARA GUI
The Teradata Tiered Archive/Restore Architecture GUI supports Teradata Extension for
NetBackup for Linux and Windows. Throughout the rest of this book, the GUI is referred to
as the Teradata TARA GUI.
Launch the Teradata TARA GUI from any Linux or Windows host that is a client to the
NetBackup master and that contains defaults, the TARA server configuration file. The GUI
can also be used to manage multiple Teradata Database installations. The databases are
differentiated as distinct definitions within the TARA configuration file.
26
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 1: Introduction
General Backup and Restore Information
Teradata TARA Components
Teradata TARA consists of three components: the Teradata TARA server, the Teradata TARA
GUI, and the ARCMAIN NetBackup access module. The access module allows ARCMAIN
processes to work with NetBackup processes and is only active during NetBackup backup or
restore jobs. It is also transparent to the administrator.
There are also stand-alone, command-line utilities that Table 3 describes. Refer to Chapter 6
for more information on the utilities.
Table 3: TARA Command-Line Utilities
Utility
Description
TARAJobRM
Allows the Backup Administrator to remove a TARA job file or script file.
TARAJobQuery
Allows the display of job-related information for all TARA jobs that have run
(even jobs that have failed) without having to use the Teradata TARA GUI.
TARALaunch
Allows the execution of a TARA script without having to use the Teradata
TARA GUI.
TARAMigrator
Migrates images created under the legacy Teradata Extension for NetBackup
to a Teradata TARA Job Information file, allowing Teradata TARA to restore
data from a NetBackup image.
TARAScriptConv
Allows the conversion of ARC script files from Teradata Extension for
NetBackup for Windows script format (.bch and .scr) to the TARA format.
TARASetCfg
Allows the explicit request of a TARA server to reset its configuration
parameters by reading the defaults configuration file again instead of resetting
the server.
General Backup and Restore Information
The most convenient way to back up Teradata Databases is to set up Teradata policies and
schedules for automatic, unattended backups. To add a schedule or change an existing
schedule for automatic backups, follow the guidelines given in “Configure a NetBackup
Policy” on page 55.
The administrator on the master server can use the NetBackup Administration Console to
manually execute an Automatic Backup schedule for a Teradata policy. See the NetBackup
System Administrator’s Guide at http://www.symantec.com/business/products/allproducts.jsp
for instructions.
Note: Teradata Extension for NetBackup does not handle object names that contain any of
these special characters: a space, ^ , . , /, and \ .
Teradata Extension for NetBackup Administrator Guide, Release 15.00
27
Chapter 1: Introduction
Creation of Backup and Restore Scripts
Creation of Backup and Restore Scripts
Use the Teradata TARA GUI to create backup and restore scripts:
•
Teradata TARA GUI (Linux and Windows)
Refer to “Archive a Database Object” on page 79 and “Restore a Database Object” on
page 94 for instructions on creating scripts with the Teradata TARA GUI.
Table 4 references the chapter or appendix specific to the Teradata TARA GUI and the
NetBackup Database Extension - Graphical User Interface.
Table 4: GUI Chapters
GUI
Installation
Configuration
Using the GUI
Teradata TARA GUI
Chapter 2
Chapter 3
Chapter 4
Encryption
In the 13.10 release and later, Teradata Extension for NetBackup uses StorageTek Crypto Key
Management System (KMS) from Oracle® for encryption, replacing the Protegrity®
encryption module.
UTF-8 Support
The TARA 14.10 release and later supports UTF-8 database objects.
28
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 2
Teradata TARA Installation and
Uninstallation
This chapter describes installing Teradata TARA for SUSE Linux and Windows hosts:
•
Linux
•
Windows
•
User Account Requirements
•
Teradata TARA Installation
•
Installed Components
•
Uninstallation on Windows
•
Uninstallation on Linux
The next sections list the required software for Teradata TARA 15.00 on Linux or Windows
operating systems. To ensure consistent results, install the same versions of the Teradata Tools
and Utilities software set on each client node.
Note: For any updates in installation requirements, refer to the most recent version of the
Teradata BAR Backup Application Software Release Definition.
Linux
Operating System
Use SUSE Enterprise Server 10 Linux or SUSE Enterprise Server 11 Linux for:
•
Symantec NBU 7.0.1 64-bit (SUSE 10 or SUSE 11)
•
Symantec NBU 7.1 64-bit (SUSE 10 or SUSE 11)
•
Symantec NBU 7.5.0.3 64-bit (SUSE 10 or SUSE 11)
•
Symantec NBU 7.6.0.1 64-bit (SUSE 10 or SUSE 11)
Non-Teradata Software
Install the following or later versions:
•
Java Runtime Environment 1.6 or later
•
(Optional) Open Secure Shell (openssh) 4.2 or later
Note: If TARA Client Service (TCS) is used as the communication mechanism between
the TARA client and the TARA server, this package is unnecessary. See “TARA
Teradata Extension for NetBackup Administrator Guide, Release 15.00
29
Chapter 2: Teradata TARA Installation and Uninstallation
Windows
Communication Method” on page 33 for a description of differences between OpenSSH
and TCS.
Teradata Tools and Utilities Software for 32-Bit and 64-Bit Linux
For TARA 15.00, you must install:
•
Teradata Archive and Recovery Utility (ARC) 14.10 or later
Note: The ARC version must be equal to the ICU, CLI, PIOM and GSS versions.
•
Version 14.10 or later of the following software:
•
Shared ICU Libraries for Teradata
•
Teradata Call-Level Interface (CLI) V2
•
Teradata Data Connector (PIOM)
•
Teradata GSS (TeraGSS)
See the Teradata BAR Backup Application Software Release Definition for specific TARA and
TTU software compatibility.
Windows
Operating System
•
Microsoft Windows 2003 64-bit SP1 for Symantec NBU 7.0, 7.0.1, 7.1, and 7.5 64-bit
•
Microsoft Windows 2008 64-bit for Symantec NBU 7.0.1, 7.1, 7.5, and 7.6 64-bit
Non-Teradata Software
•
Install Microsoft Windows Script Host, version 5.6 or later.
•
If you are installing the Teradata TARA GUI package, also install Java Runtime
Environment 1.6 or later.
•
(Optional) Install OpenSSH for Windows 04.00.02.04 or later.
Note: If TARA Client Service (TCS) is used as the communication mechanism between
the TARA client and the TARA server, this package is unnecessary. See “TARA
Communication Method” on page 33 for a description of differences between OpenSSH
and TCS.
Teradata Tools and Utilities Software for 32-Bit Windows
Windows 32-bit Operating System is not supported by TARA 15.00.
30
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
User Account Requirements
Teradata Tools and Utilities Software for 64-Bit Windows
For TARA 15.00, you must install:
•
Teradata Archive and Recovery Utility (ARC) 14.10 or later
Note: The ARC version must be equal to or greater than the ICU, CLI, PIOM and GSS
versions.
•
Version 14.10 or later of the following software:
•
Shared ICU Libraries for Teradata
•
Teradata Call-Level Interface (CLI) V2
•
Teradata Data Connector (PIOM)
•
Teradata GSS Client nt-x8664
See the Teradata BAR Backup Application Software Release Definition for specific TARA and
TTU software compatibility.
User Account Requirements
Teradata TARA requires specific user accounts and permissions for proper operation. Refer to
Table 5 for Linux information and Table 6 for Windows information.
Linux
Table 5: User Accounts and Permissions for Linux Environment
Linux User
Account
Required Permission
Description
taraserver
755
baruser
755
• User Read/Write/Execute
• Group Read/Execute
• Other Read/Execute
The baruser account will not be recreated if it currently exists.
Note: The baruser account must use /home/baruser as its home directory.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
31
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
Windows
Table 6: 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 account, which must be local, provides
ownership for the TARA server service when OpenSSH is
selected as the communication mechanism. When TCS is
selected as the communication mechanism, the TARA server
uses the LocalSYSTEM account.
baruser
Local Administrators
This account is necessary to:
• Launch TARA jobs
• Run NetBackup commands such as bppllist, that are
hard-coded by the third-party vendor
sshd_server
Local Administrators
This account and permission is required to start the
OpenSSH service. This is a hard-coded user name from the
third-party software developer.
Teradata TARA Installation
Overview of Installation Packages
There are three TARA installation packages for Linux and Windows:
•
NetBackup Access Module install package (nbubar)
•
TARA GUI install package (taragui)
•
TARA server install package (taraserver)
The Teradata Extension for NetBackup (TARA 15.00.00) CD contains 32- and 64-bit
installation packages for nbubar, taragui, and taraserver.
Table 7: CD Installation Packages and Locations
OS
NetBackup Access Module
Package and Location
TARA GUI Package and Location
TARA Server Package and Location
Linux
32-bit
/LINUX/i386/
nbubar-15.00.00.00-1.i386.rpm
/LINUX/i386/
taragui-15.00.00.00-1.i386.rpm
/LINUX/i386/
taraserver-15.00.00.00-1.i386.rpm
Linux
64-bit
/LINUX/x8664/
/LINUX/x8664/
nbubar-15.00.00.00-1.x86_64.rpm taragui-15.00.00.00-1.i386.rpm
Note: The 32-bit TARA GUI package is
valid for use with the 64-bit NetBackup
Access Module and TARA server.
32
/LINUX/x8664/
taraserver-15.00.00.001.x86_64.rpm
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
Table 7: CD Installation Packages and Locations (continued)
OS
NetBackup Access Module
Package and Location
Windows \WINDOWS\i386\
32-bit
nbubar\setup.exe
TARA GUI Package and Location
TARA Server Package and Location
\WINDOWS\i386\
taragui\setup.exe
\WINDOWS\i386\
taraserver\setup.exe
Note: You must install the 32-bit GUI
on Windows 32-bit OS. The GUI is
valid for use with the 32- or 64-bit
versions of the NetBackup Access
Module and TARA server.
Windows \WINDOWS\x8664\
64-bit
nbubar\setup.exe
\WINDOWS\x8664\
taragui\setup.exe
\WINDOWS\x8664\
taraserver\setup.exe
Note: You must install the 64-bit GUI
on Windows 64-bit OS. The GUI is
valid for use with the 32- or 64-bit
versions of the NetBackup Access
Module and TARA server.
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 NetBackup Access Module. On this host, the TARA server executable runs
as a service. The TARA server package has no product dependencies.
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 NetBackup Access Module runs on a node called the NBUBAR host. The NBUBAR host
must also be a BAR server node. The NetBackup Access Module is a Teradata-provided library
file that interfaces with the ARCMAIN module that is installed on the BAR server node during
a NetBackup backup or restore job.
TARA Communication Method
Two methods are available for communication between the TARA server and TARA clients
using the TARA NetBackup Access Module (NBUBAR): OpenSSH and the TARA Client
Services (TCS). Beginning with TARA 13.10, OpenSSH use is deprecated.
Select only one method for the entire TARA environment. If TCS is selected during the
installation of the TARA server, select TCS for all of the client installations of NBUBAR. If SSH
is selected during the installation of the TARA server, select SSH for all of the client
installations of NBUBAR.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
33
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
OpenSSH
OpenSSH is a non-Teradata product that provides remote execution and remote copy
functions for the TARA environment. Install OpenSSH prior to installing the TARA server
and the TARA NetBackup Access Modules.
Converting from OpenSSH to TCS
The use of openssh as the communication method between the TARA server and the TARA
clients has been deprecated since TARA version 13.10. The conversion to TCS occurs as part of
upgrading the TARA server. However, the conversion can be done at any time by re-running
the post-install scripts of the server and client.
Changing to TCS on the TARA server
1
Ensure that no backup or restore jobs are active.
2
Run the TARA server post-install script:
Linux: /opt/teradata/tara/server/bin/taraserver_postinstall.sh
Windows: <INSTALL_PATH>\teradata\tara\server\bin\taraserver.bat
3
Select TCS as the communication service.
4
Complete the post-install.
Changing to TCS on the TARA server
1
Run the TARA client post-install script:
Linux: /opt/teradata/tara/nbubar/bin/nbubar_postinstall.sh
Windows: <INSTALL_PATH>\teradata\tara\nbubar\bin\nbubar.bat
2
Select TCS as the communication service.
3
Complete the post-install.
Note: All TARA clients and the TARA server must use the TCS. The use of both methods
between the TARA server and the TARA clients is not allowed.
TARA Client Service
TCS is integrated into the TARA server and the NBUBAR packages. TCS provides remote
execution and remote copy functions only for the TARA environment. No external packages
are required to use this communication method.
Note: TARA Client Service is the Teradata recommended communication method.
Installation Location
All three packages can be installed 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:
34
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
•
Install the TARA server on only one of the BAR servers.
•
Install the NetBackup Access Module on every BAR server that is part of the NetBackup/
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 NetBackup Access Module.
Note: If OpenSSH is used as the communication method, install it before installing the
TARA server.
•
Install any product dependencies before installing the required TARA package
(dependencies are noted in the next sections).
Estimating the Size for the TARA Server Repositories
The TARA server has JobFile and Script repositories that grow over time. It is important to
maintain them so that they do not contain obsolete information.
To initially estimate the size necessary to contain these repositories, you need to review your
backup strategy in terms of:
•
the backup jobs you will complete each week.
•
the number of objects (database names and tables) of the backup jobs.
•
the retention cycle of the images created by your backups.
JobFile Repository (jir)
For each backup job, estimate the JobFile size by the following formula:
((Number_of_objects * Number_of_streams * 2000) + 1000) * Number_of_retentions
The sum of the backup jobs is the estimated size needed for the JobFile Repository.
Script Repository (sr)
For each script that you will need to create for the backup jobs, estimate the size by the
following formula:
(Number_of_streams * 200) + (Number_of_objects * 60) + 800
The sum of the script sizes is the estimated size needed for the Script Repository
Logs Repository (logs)
The default maximum taraserver log file size is 2,147,483,648 (2GB). The taraserver retains
the currently-active logfile and one previous logfile. Maximum size necessary is 4,294,967,296
(4GB).
Teradata Extension for NetBackup Administrator Guide, Release 15.00
35
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
Note: You can reduce the maximum size by configuring the maximum file size limit. Refer to
“Configure the Log File” on page 75.
TARA Component Upgrade
When you are upgrading a TARA component from a prior release, remove the existing
package before installing the new package:
•
For Linux, use rpm -e <TARA_component_name>.
•
For Windows, use the Control Panel Add/Remove Programs.
Installation of Teradata TARA Components on Linux
You must install the correct version of the NetBackup Access module and TARA server for the
NetBackup version you are running.
For NetBackup 6.5.x, install the 32-bit TARA packages:
•
nbubar-15.00.00.00-1.i386.rpm
•
taraserver-15.00.00.00-1.i386.rpm
For NetBackup 7.x, install the 64-bit TARA packages:
•
nbubar-15.00.00.00-1.x86_64.rpm
•
taraserver-15.00.00.00-1.x86_64.rpm
If you do not install the correct version, you will receive error messages during the installation
process.
To install the TARA server
On the Linux server where you want the TARA server to run:
1
2
Install the TARA server package with the rpm utility. For example:
•
rpm -ih taraserver-15.00.00.00-1.i386.rpm
•
rpm -ih taraserver-15.00.00.00-1.x86_64.rpm
Run the post-installation script, which is usually located in /opt/teradata/tara/server/bin,
by typing one of the following:
•
/opt/teradata/tara/server/bin/taraserver_postinstall.sh
•
cd /opt/teradata/tara/server/bin
./teraserver_postinstall.sh
36
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
3
To verify that the TARA server service is running, type:
/etc/init.d/tdtaraserver status
The status should be “RUNNING”.
4
At the command-line prompt for the name of the Backup Application, type n for
NetBackup.
5
At the prompt for the communication services type, type s for SSH or t for TCS (TARA
Client Service) for the service that the NBUBAR TARA clients will use.
6
Enter an administrator password. Passwords must have at least:
•
Eight characters
•
One numeric character
•
One upper-case alphabetic character
•
One lower-case alphabetic character
Passwords cannot:
•
Have three consecutive identical characters
•
Be the reverse of the logon name
7
Enter the user name for the owner of the TARA server service. The default is taraserver,
which can be selected by pressing Enter.
8
Enter the user home directory. The default is /home/taraserver, which can be selected by
pressing Enter.
9
If SSH was selected as the communication service, the prompt asks for the name of the
security key file. Private and public security key files have the same name; the public key
file has a .pub extension. The default name is id_rsa, which can be selected by pressing
Enter.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
37
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
After taraserver is installed or upgraded, the TARA directories are:
# ls -l /opt/teradata/tara
total 12
drwxr-xr-x 4 root root 4096 Mar 9 10:47 gui
drwxr-xr-x 4 root root 4096 Feb 21 13:01 nbubar
drwxr-xr-x 3 root root 4096 Feb 23 07:15 server
# ls -ld /etc/opt/teradata/tara
drwxr-xr-x 3 root root 4096 Mar
1 10:49 /etc/opt/teradata/tara
# ls -l /var/opt/teradata/tara/server
total 42796
drwx------ 2 taraserver root
4096
drwx------ 2 taraserver root
12288
drwx------ 2 taraserver root
4096
drwx------ 2 taraserver root
4096
Mar
Mar
Mar
Mar
5
5
9
5
14:20
14:20
10:46
14:20
config
jir
logs
sr
To install the Teradata TARA GUI
On each 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:
rpm -ih taragui-15.00.00.00-1.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 NetBackup Access Module
On the Linux server where you want the NetBackup Access Module to run:
1
Install the Teradata Tools and Utilities packages for Teradata ICU, Teradata GSS, PIOM,
CLIV2, and ARC with the rpm utility.
2
Install the NetBackup Access Module package with the rpm utility. For example:
3
•
rpm -ih nbubar-15.00.00.00-1.i386.rpm
•
rpm -ih nbubar-15.00.00.00-1.x86_64.rpm
Run the post-installation script by typing one of the following:
•
/opt/teradata/tara/nbubar/bin/nbubar_postinstall.sh
•
cd /opt/teradata/tara/nbubar/bin
./nbubar_postinstall.sh
38
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
The post-installation script, nbubar_postinstall.sh, is usually located in /opt/teradata/tara/
nbubar/bin. The script designates the local server as a BAR server and sets up the required
TARA client elements.
4
Press Enter to accept the default client name to use in the TCS connection to the TARA
server, or enter another name. The default is the node name. If you enter another name, it
must be an alias for an IP address in an /etc/hosts file that can connect to the TARA server.
Verify the taraserver process is active in its designated BAR server, then:
1
Press Enter.
2
At the prompt, enter the machine name where the taraserver process is running. The
default is localhost, which can be selected by pressing Enter. There is only one TARA
Server process in a TARA configuration. So, every NetBackup access module client should
point to it.
3
At the prompt, type s for the SSH or t for the TCS communication service. The service
must match the service used by the TARA server.
Note: The taraserver process communicates with its TARA clients using SSH or TCS.
Ensure that all the NBUBAR TARA client installations are configured to use the same
communication method as the TARA server.
TCS is the preferred communication service.
After Installation
To verify that the NetBackup Access Module service is running, type:
/etc/init.d/tdtaraclient status
The status should be “RUNNING”.
After installing all TARA packages, use the Teradata TARA GUI to configure at least one
Teradata system.
Note: A dependency clause is included in the Teradata TARA GUI's rpm file to check for the
existence of the teradata-jre5 package version 1.5.0 or greater. If that package is not installed,
the installation of teradata-jre5 package fails due to a dependency error. To correct this error,
install the missing package with the rpm utility before retrying the installation.
Installation of Teradata TARA Components on Windows
Install Teradata TARA components in this sequence:
1
TARA server
2
TARA NetBackup Access Module and Teradata TARA GUI, in any order (installation
instructions are given for the TARA NetBackup Access Module first)
Teradata Extension for NetBackup Administrator Guide, Release 15.00
39
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
To install the TARA server
40
1
Go to Windows\TARA Server\setup.exe on the Teradata Extension for NetBackup CD.
2
Double-click setup.exe. This will install the copy of the TARA server that is on the Teradata
CD.
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.13.10.00, or taraserver.13.10.00 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.
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.
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
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 [Optional] If this an upgrade from TARA 1.01, a message indicates that the path for
repositories have been updated and the files relocated. Click OK.
13 After installation of the TARA server is complete, a post-install script starts and a
command line window appears. At the prompt, type n to install NetBackup, then press
Enter.
A choice of communication services is displayed.
14 Type t for Teradata Client Services (TCS) or s for OpenSSH, then press Enter.
•
If t is selected, postinstall scripts are completed. Press a key to continue.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
41
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
•
If s is selected, the command-line interface prompts for the name of the TARA service
owner.
Enter the name, or accept the default, which is taraserver. Press Enter.
15 Create and enter a Windows local user account password for the Teradata TARA server at
the command-line prompt, then press Enter. The password must follow system security
rules.
16 Enter a name for the security key file, or accept id_rsa by pressing Enter. Private and
public security key files are created, and Teradata TARA server files are created under
C:\Program Files\Teradata\TARA.
17 Enter a TARA Administrator password. The password must have at least:
•
Eight characters
•
One numeric character
•
One upper-case alphabetic character
•
One lower-case alphabetic character
Passwords cannot:
•
Have three identical characters
•
Be the reverse of the logon name
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”.
The Tara server installation completes.
18 Press any key to continue, as prompted.
To verify that the TARA server service is running
42
1
Click Windows Start>Run.
2
Enter services.msc.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
3
Click OK.
A Services window appears with a list of services in alphabetical order.
4
Scroll down the list of service names until you find TaraServer. It should have a status of
Started.
To install the TARA NetBackup Access Module
Before installing the TARA NetBackup Access Module on any BAR server, ensure that the
TARA server is installed and started on one of the BAR servers. Check that the TARA server
service is “STARTED” in the services list.
1
From the Teradata Extension for NetBackup CD, double-click
Windows\NBUBAR\setup.exe. The NBUBAR InstallShield Wizard dialog box appears.
2
Click Next. A dialog box for the license agreement appears.
3
To accept the agreement and install the TARA NetBackup Access Module, 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. If navigating to a different directory, add nbubar at
the end of the directory path.
Click OK.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
43
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
Click Next. The Start Copying Files dialog box appears.
4
Click Next if you are satisfied with the settings, or have made necessary changes. The Setup
Status dialog box displays installation status, then displays that installation is complete.
5
Click Finish. A command-line interface opens. 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.
The script automatically appends the name baruser to the path.
If no path is entered, the default path, C:\Documents and Settings\, is created.
6
44
Press Enter. The baruser home directory is created, and a choice of communication
services is displayed.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Teradata TARA Installation
7
Type t for TCS or s for OpenSSH. Press Enter.
The communication service for the NetBackup Access Module must match the
communication service chosen for the TARA server.
8
At the prompt for the name of the TARA server host, enter the name of the BAR server
where the TARA server is running.
The default is localhost.
9
Press Enter to accept the default client name to use in the TCS connection to the TARA
server, or enter another name. The default is the node name. If you enter another name, it
must be an alias for an IP address in an /etc/hosts file that can connect to the TARA server.
10 Press Enter to complete the postinstall script. A connection is made to the TARA server
host.
11 Press any key (with the exception of Enter) to continue. The TARA NetBackup Access
Module has been successfully installed.
To verify that the NetBackup Access Module service is running
1
Click Windows Start>Run.
2
Type services.msc.
3
Click OK. A Services window displays a list of services in alphabetical order.
4
Scroll down the list of services names until you find TaraClient. It should have a status of
Started.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
45
Chapter 2: Teradata TARA Installation and Uninstallation
Installed Components
To install the Teradata TARA GUI
1
From the Teradata Extension for NetBackup CD, double-click Windows\TARA
GUI\setup.exe.
Note: If this is an upgrade, the prior version of the TARA GUI 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.
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.
7
[Optional] To create a shortcut icon on the desktop, select that option.
8
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 (xinetd).
2
Click Enable.
3
Tab to Status for All Services and press Enter.
4
Highlight and press Activate All Services.
5
Click Finish, then OK.
The xinetd process is not necessary for Teradata TARA, however, it is vital for NetBackup
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\TARA for Windows
The install path is referenced by install_path.
46
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Installed Components
There are three TARA-related install packages:
•
TARA server install package
•
Teradata TARA GUI install package
•
NetBackup Access Module install package
TARA Server Package
The Windows install package and Linux taraserver_postinstall.sh script take the actions
described in Table 8 upon installation of the TARA server package.
Table 8: Actions Taken when TARA Server Package Installed
Action
Details
Creates a new login account.
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 NetBackup Access
Module, 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 NetBackup Access Module,
therefore change the default taraserver account for the TARA server.
If SSH is specified, creates SSH security keys
to allow the TARA server to communicate
with the BAR server (the node where the
backup/restore job runs).
A pair of Private/Public security key files are created in <home dir>/.ssh (for
example, /home/taraserver/.ssh). The user specifies the name of the security
key files. The defaults are id_rsa and id_rsa.pub.
If SSH is specified, replaces the tdbackex file
that NetBackup provides with the Teradata
version of that file.
The NetBackup version is renamed and saved as tdbackex_nbu. The tdbackex
and tdbackex_nbu files reside in /usr/openv/netbackup/bin.
Sets up the TARA server to run as a service on
the TARA server host.
Unavailable
Creates the TARA server install_path
directory, /opt/teradata/tara/server.
Under this directory, the taraserver_postinstall.sh script creates the bin, jir, sr,
logs, and config subdirectories, which are described in Table 9.
Table 9: Subdirectories of taraserver_postinstall.sh
Subdirectory Name
Description of Subdirectory
/bin
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
47
Chapter 2: Teradata TARA Installation and Uninstallation
Installed Components
Table 9: Subdirectories of taraserver_postinstall.sh (continued)
Subdirectory Name
Description of Subdirectory
/etc
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 the defaults file (see “Configure the
Log File” on page 75).
/jir
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.
/sr
This is the backup/restore script repository for the TARA server. Edit these scripts with the Edit
feature of the Teradata TARA GUI.
/logs
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.
/config
Used as a taraserver work directory for launching jobs and internal queries.
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 Table 10.
Table 10: Files in bin Subdirectory
File
Details
Teradata TARA GUI executable
file
This file is called taragui.jar.
TARALaunch
This utility launches a NetBackup backup or restore job from the Script Repository on a
specified TARA server.
TARAJobQuery
This utility displays information that is stored a Job Information file. The Job
Information file to be accessed is stored in the Job Information Repository on a specified
TARA server.
TARAMigrator
This utility migrates images created under the legacy Teradata Extension for NetBackup
to a Teradata TARA Job Information file. This allows Teradata TARA to restore data from
a NetBackup image.
TARAScriptConv
This utility converts a TDE backup or restore job from its native format to the format
that the TARA server uses. The converted script can then be stored in the Script
Repository on a specified TARA server.
48
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Installed Components
Table 10: Files in bin Subdirectory (continued)
File
Details
Script file
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.
For Linux, execute taragui by entering:
export DISPLAY=<your_IP_address or host_alias>
/opt/teradata/tara/gui/bin/taragui &
OR
cd /opt/teradata/tara/gui/bin
./taragui &
For Windows, double-click on taragui.jar
The command-line utilities are useful for field personnel who might not have access to the
Teradata TARA GUI.
Run the command-line utilities by typing:
/opt/teradata/tara/gui/bin/<utility name> <parameters>
OR
cd /opt/teradata/tara/gui/bin
./<utility name> <parameters>
NetBackup Access Module Package
The Windows install package and the Linux nbubar_postinstall.sh script take these actions
upon installation of the NetBackup Access Module 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 NetBackup Access Module, 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 NetBackup Access Module, therefore change the default taraserver account for the
TARA server.
•
Acquires the public SSH security key from a specified TARA server to allow that TARA
server to communicate with the BAR Server where the NetBackup Access Module package
was installed. The public SSH security key is stored in the authorized_keys file on the
NBUBAR host. The authorized_keys file is located in /home/baruser/.ssh.
•
Copies the runarcnb.bat and nbuquery.bat files to the baruser's home directory: /home/
baruser.
•
Sets up a path and symbolic link to allow access to the NetBackup Access Module's library
file, libnbubar.so, which resides in /opt/teradata/tara/nbubar/lib.
•
Creates the NetBackup Access Module install_path directory, /opt/teradata/tara/nbubar.
Under this directory, the nbubar_postinstall.sh script creates the bin and lib subdirectories:
Teradata Extension for NetBackup Administrator Guide, Release 15.00
49
Chapter 2: Teradata TARA Installation and Uninstallation
Uninstallation on Windows
Subdirectory
Name
Description of Subdirectory
/bin
Contains the executable files for those programs that are needed to support the
NetBackup Access Module.
/lib
Contains the NetBackup Access Module library file, libnbubar.so, which is used
in conjunction with ARCMAIN during a NetBackup backup or restore job.
Uninstallation on Windows
During installation, Teradata TARA creates folders and registry entries under Program
Files\Teradata\TARA, then copies required files under the folders.
When uninstalling Teradata TARA components, it is important to 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. Table 11 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.
To access the registry, do this: Start>Run>Regedit. Click OK.
Table 11: Folders and Registry Entries
Folder
Created
During
Installation
gui
Registry Entry Created During Installation
Manual Deletion During Uninstallation
HKEY_LOCAL_MACHINE\SOFTWARE\Terad
ata\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.
nbubar
HKEY_LOCAL_MACHINE\SOFTWARE\
Teradata\Nbubar
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.
50
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 2: Teradata TARA Installation and Uninstallation
Uninstallation on Linux
Table 11: Folders and Registry Entries (continued)
Folder
Created
During
Installation
server
Registry Entry Created During Installation
Manual Deletion During Uninstallation
HKEY_LOCAL_MACHINE\SOFTWARE\Terad
ata\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.
Other registry entries that require manual deletion are:
•
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2\jir
•
HKEY_LOCAL_MACHINE\System\ControlSet001\Services\TaraServer
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 nbubar
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
•
/etc/opt/teradata/tara
•
jir
•
logs
Teradata Extension for NetBackup Administrator Guide, Release 15.00
51
Chapter 2: Teradata TARA Installation and Uninstallation
Uninstallation on Linux
52
•
sr
•
the defaults file in /etc/opt/teradata/tara
•
/home/baruser
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 3
Teradata TARA Configuration
Configuring Teradata Extension for NetBackup requires using the NetBackup Administration
Console and the Teradata TARA GUI. Although the database agent is installed on the
NetBackup client, some configuration procedures are performed using the NetBackup
Administration Console on the Windows or Linux server. Use the Teradata TARA GUI to
configure the TARA environment.
The information in this chapter applies to Windows and Linux platforms. Before attempting
configuration, complete the installation procedure described in Chapter 2: “Teradata TARA
Installation and Uninstallation”.
The following topics describe using the NetBackup Administration Console, and the Teradata
TARA GUI, for configuration:
•
Start the NetBackup Administration Console
•
Configure the Media Manager
•
Set Maximum Jobs per Client
•
Configure a NetBackup Policy
•
Test Configuration Settings
•
Multiplexing
•
Create Restore Userids
•
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.
Start the NetBackup Administration Console
To start the Windows or Linux server version of the NetBackup Administration Console, follow
the instructions below.
To launch the Windows NetBackup Administration Console
1
Log on to the server as administrator.
2
Click Start>Programs>VERITAS NetBackup>NetBackup Administration Console.
The NetBackup Administration Console window opens.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
53
Chapter 3: Teradata TARA Configuration
Configure the Media Manager
To launch the Linux NetBackup Administration Console
1
Log on to the NetBackup master server or NetBackup Remote Administration Console.
2
Type /usr/openv/netbackup/bin/jnbSA. The NetBackup Remote Administration
Console opens.
Configure the Media Manager
Use the NetBackup Administration Console for this procedure.
An administrator can use the Media and Device Management section of the NetBackup
Administration Console for a single view of all NetBackup domain components. The Media
Manager is also available to configure tapes or other storage units for a Teradata Extension for
NetBackup configuration. Refer to the Media Manager for NetBackup System Administrator’s
Guide for more information.
The number of volumes required depends on the devices used, the size of the Teradata
Databases that are being backed up, and the size and frequency of the backups.
In a NetBackup Enterprise domain where the master server is not on one of the Teradata BAR
servers, the Backup Administrator, upon request from the Teradata Administrator, will
configure the media and devices. In a NetBackup configuration where the master server is also
on one of the BAR servers, the Teradata administrator will configure the master/media server.
The remaining sections in this chapter have two purposes in that they provide:
•
The Teradata Administrator the necessary detail of what additions and changes to request
from the Backup Administrator
•
The steps that are needed to configure the master/media server
Set Maximum Jobs per Client
Use the NetBackup Administration Console for this procedure.
The Maximum jobs per client attribute value is calculated with this formula:
Max Jobs per Client = Number of Streams * Number of Policies
Where:
•
Number of Streams is the number of backup streams between the database server and
NetBackup. Each separate stream starts a new backup job on the client.
•
Number of Policies is the number of policies that can back up this client at the same time.
This number can be greater than one. For example, a client might be in two policies in
order to back up two different databases. These backup windows might overlap.
Use the NetBackup Administration Console or a Remote Administration Console host to set the
Maximum jobs per client attribute.
54
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
To set the maximum jobs per client attribute
1
In the left pane of the NetBackup Administration Console, expand Host Properties. Click
Master Server.
2
In the right pane, double-click on the server icon.
The Master Server Properties dialog box appears.
3
Click the Global NetBackup Attributes tab.
The default value is 1 for Maximum jobs per client.
4
Change the Maximum jobs per client value to a value equal to the maximum number of
backup allowed per client.
Tip
To avoid any problems, enter a rule of 99 for the Maximum jobs per client global attribute.
Configure a NetBackup Policy
Use the NetBackup Administration Console for this procedure.
A NetBackup policy defines the backup criteria for a specific group of one or more clients and
is necessary whether the job is launched automatically using the scheduler, or is launched
manually using the Teradata TARA GUI, the NetBackup Database Extension GUI, or
tdbackex.
These criteria include:
•
storage unit and media to use
•
backup schedules
•
script files to be executed on the clients
•
clients to be backed up
To use Teradata Extension for NetBackup, define at least one NCR-Teradata or Teradata policy
with the appropriate schedules. A configuration can have a single policy that includes all
clients or there can be many policies, some of which include only one client.
Note: Beginning with NetBackup 7.0, the NCR-Teradata policy type name changes to
Teradata.
Most requirements for Teradata policies are the same as for file system backups. In addition to
the attributes described here, there are other attributes for a policy to consider. Refer to the
NetBackup System Administrator’s Guide for detailed configuration instructions and
information on all the attributes available.
Add Policies
Use this procedure when configuring a policy from a Windows or Linux server, or from a
NetBackup Remote Administration Console host.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
55
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
To add a policy
1
Log on to the server as administrator.
2
Start the NetBackup Administration Console.
3
If the site has more than one master server, choose the server on which to add the policy.
4
In the left pane, right-click Policies and click New Policy.
The Add a New Policy dialog box appears.
5
a
In the Policy name box, type a unique name for the new policy.
b
Choose whether to use the wizard for configuring the policy. The wizard simplifies the
setup process by automatically choosing default values that are good for most
configurations. If necessary, change the defaults later by editing the policy. Manually
add entries to the Scripts list after completing the wizard.
•
To use the wizard, select the Use Backup Policy Configuration Wizard dialog box and
click OK. Create the policy by following the prompts. When prompted, select the
NCR-Teradata policy type if you are using a version of NetBackup prior to 7.0.
Select the Teradata policy type if you are using NetBackup 7.0 or later.
•
If more control over the settings than the wizard provides is required, do not select
the Use Backup Policy Configuration Wizard dialog box. Instead, go to step 5.
Click OK.
A dialog box appears in which you can specify the general attributes for the policy.
6
From the Policy Type dialog box, select the NCR-Teradata policy type if you are using a
version of NetBackup prior to 7.0. Select the Teradata policy type if you are using
NetBackup 7.0 or later.
7
Complete the entries on the Attributes tab as explained in “Description of Attributes”.
8
Add other policy information:
9
•
To add schedules, see “Add Schedules” on page 57
•
To add scripts, see “Specify the Scripts List” on page 60
•
To add clients, see “Add Clients to a Policy” on page 62
Click OK. The new policy will be created.
Description of Attributes
With a few exceptions, NetBackup manages a database backup like a file system backup. Policy
attributes that are different for Teradata backups are explained in Table 12.
56
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
Table 12: Description of Policy Attributes
Attribute
Description
Policy type
The policy type attribute determines the type of clients that can
be in the policy and, in some cases, the types of backups that
can be performed on those clients.
To use Teradata Extension for NetBackup, there must be at least
one defined NCR-Teradata or Teradata policy.
Keyword phrase
The keyword phrase attribute is ignored in Teradata Extension
for NetBackup.
Other policy attributes vary with specific backup strategy and system configuration. Consult
the NetBackup System Administrator’s Guide for detailed explanations of policy attributes.
Add Schedules
Each policy has its own set of schedules. These schedules control initiation of automatic
backups and specify when user operations can be initiated.
A Teradata backup requires at least two schedule types: an Application Backup schedule and
an Automatic Backup schedule. It is possible to create additional schedules. Table 13 describes
Application Backups and Automatic Backups.
Table 13: Description of Backup Types for Teradata
Backup Type
Description
Application Backup
An Application Backup schedule enables user-controlled NetBackup
operations performed on the client. At least one Application Backup
schedule type must be configured for each NCR-Teradata or Teradata policy.
The Default-Application-Backup schedule is automatically configured as an
Application Backup schedule.
Automatic Backup
An Automatic Backup schedule specifies the dates and times when
NetBackup will automatically start backups by running the scripts in the
order that they appear in the file list. If there is more than one client in the
NCR-Teradata or Teradata policy, the scripts are run on each client.
See “Configure an Application Backup Schedule” on page 57 and “Configure an Automatic
Backup Schedule” on page 58 for procedures to add and configure the required schedule
types.
Configure an Application Backup Schedule
An Application Backup schedule is one of the two types of schedules required for a Teradata
backup. Refer to “Configure an Automatic Backup Schedule” on page 58 for information on
the other type of required schedule.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
57
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
To configure an Application Backup schedule
1
Double-click on the schedule named Default-Application-Backup.
All Teradata Database operations are performed through Teradata Extension for
NetBackup using an Application Backup schedule. This includes those backups started
automatically.
Configure an Application Backup schedule for each NCR-Teradata or Teradata policy,
otherwise you cannot run a backup. To help satisfy this requirement, an Application
Backup schedule named Default-Application-Backup is automatically created when a new
NCR-Teradata or Teradata policy is configured.
2
Specify the other properties for the schedule as explained in “Specify Schedule Properties”
on page 59.
The backup window for an Application Backup schedule must encompass the time period
during which all NetBackup jobs, scheduled and unscheduled, will occur. This is necessary
because the Application Backup schedule starts processes that are required for all Teradata
Extension for NetBackup backups, including those started automatically.
For example, assume that:
•
Users run NetBackup operations during business hours, 0800 to 1300
•
Configured automatic backups start between 1800 and 2200
The Application Backup schedule must have a start time of 0800 and a duration of 14
hours.
Table 14 describes and gives examples of settings for Application Backup schedules.
Table 14: Examples of Settings for an Application Backup Schedule
Type of Backup
Schedule Settings
Description
Settings
Application Backup
Retention
The length of time backup images
are stored
2 weeks
Backup Window
The time during which a NetBackup
operation can be performed
Sunday through Saturday
00:00:01 - 23:59:59
Tip
Set the time period for the Application Backup schedule for 24 hours per day, seven days per
week. This ensures that Teradata Extension for NetBackup operations are never locked out
due to the Application Backup schedule.
Configure an Automatic Backup Schedule
An Automatic Backup schedule is one of the two types of schedules required for a Teradata
backup. Refer to “Configure an Application Backup Schedule” on page 57 for information on
the other type of required schedule.
58
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
To configure an Automatic Backup schedule
1
In the left pane, right-click on the name of the policy and click New Schedule.
The Add New Schedule dialog box appears. The title bar shows the name of the policy to
which you are adding the schedules.
2
Specify a unique name for the schedule.
3
Click Type of Backup.
For information on the types of backups available for this policy, see Table 13 on page 57.
Refer to Table 15 for recommended settings for an Automatic Backup schedule.
Table 15: Examples of Settings for an Automatic Backup Schedule
Type of Backup
Schedule Settings
Description
Settings
Automatic Backup
Retention
The length of time to store
the record of a backup
2 weeks
Frequency
How often a backup must
be performed
every week
Backup Window
The time during which a
NetBackup operation can
be performed
Sunday. 18:00:00 - 22:00:00
4
Specify the other properties for the schedule as explained in “Specify Schedule Properties”.
Specify Schedule Properties
The properties for the Application Backup and Automatic Backup schedules are described in
Table 16. Be aware when you are specifying schedule properties that some properties have a
different meaning for database backups than for regular file system backups.
Table 16: Description of Schedule Properties
Property
Description
Type of backup
The type of backup property specifies the type of backup that this schedule
controls.
The selection list shows only the backup types that apply to the policy you are
configuring.
For more information see Table 13 on page 57.
Frequency
The frequency property specifies the period of time that will elapse until the next
backup or archive operation can begin on this schedule. For example, if the
frequency is seven days and a successful backup occurs on Wednesday, the next full
backup will not occur until the following Wednesday. Normally, incremental
backups will have a shorter frequency than full backups.
This setting is used only for scheduled backups, and not for user-directed backups.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
59
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
Table 16: Description of Schedule Properties (continued)
Property
Description
Calendar
The calendar property allows scheduling of backup operations based on specific
dates, recurring week days, or recurring days of the month.
This setting is used only for scheduled backups, and not for user-directed backups.
Retention
Frequency based scheduling
The retention period for an Application Backup Policy schedule refers to the length
of time that NetBackup keeps backup images.
The retention period for an Automatic Backup schedule controls how long
NetBackup keeps records of when scheduled backups have occurred.
The NetBackup scheduler compares the latest record to the frequency to determine
whether a backup is due. This means that if you set the retention period to expire
the record too early, the scheduled backup frequency will be unpredictable.
However, if you set the retention period to be longer than necessary, the
NetBackup catalog will accumulate unnecessary records. Therefore, set a retention
period that is longer than the frequency setting for the schedule.
For example, if the frequency setting is set to one week, set the retention period to
be more than one week.
Calendar based scheduling
The retention period for an Application Backup Policy schedule refers to the length
of time that NetBackup keeps backup images.
The retention period for an Automatic Backup schedule controls how long
NetBackup keeps records of when scheduled backups have occurred. However, this
setting is not significant for calendar based scheduling
Multiple copies
If you are licensed for the Inline Tape Copy feature and want to specify multiple
copies for your NCR-Teradata or Teradata policy, configure Multiple copies on the
Application Backup schedule.
Other schedule properties vary with specific backup strategy and system configuration.
Consult the NetBackup System Administrator’s Guide for detailed explanations of the schedule
properties.
Specify the Scripts List
Use the NetBackup Administration Console for this procedure.
The Scripts list in a database policy has a different meaning than the File list has for other
policies. In a Standard policy, files and directories to be backed up are listed. However, when a
database policy is configured, scripts are listed.
Add scripts only when setting up a policy for automatic scheduling. All scripts listed in the
Files list are executed for the Automatic Backup schedules as specified under the Schedules
tab.
All scripts specified in the Files list are executed during manual or automatic backups.
NetBackup starts backups by running the scripts in the order in which they appear in the Files
list.
60
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure a NetBackup Policy
To add scripts to the Scripts List
1
In the left pane of the NetBackup Administration Console, right-click on the policy name
and click New Backup Selection.
Add Script - Policy sample appears. The title bar shows the name of the policy to which the
scripts are being added.
For Teradata TARA, the script names are the TARA backup job names. (To create TARA
backup jobs, see “Archive a Database Object” on page 79.) The jobs reside on the TARA
server in the Script Repository.
2
Type in a simple name for the script. The script name must not have any spaces or any of
the following characters:
<
~
*
?
\
>
"
,
.
/
Note: Scripts that are created or modified manually are not checked to see if the name
contains spaces or the characters listed above.
3
Click Add.
4
Enter the name of the job script that was created using the Teradata TARA GUI, Build ARC
script option under Backup Selections (see Backup Selections tab of the Add New Policy
dialog box). Do not attempt to specify path overrides. The job script is extracted only from
the TARA server script repository.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
61
Chapter 3: Teradata TARA Configuration
Test Configuration Settings
Add Clients to a Policy
Use the NetBackup Administration Console for this procedure.
The client list is the list of clients on which scripts are executed during an automatic backup. A
NetBackup client must be in at least one policy, but can be in more than one.
To add clients to a policy
1
In the left pane of the NetBackup Administration Console, right-click on the policy name
and click New Client.
The Add New Client dialog box appears. The title bar shows the name of the policy to
which the clients are being added.
2
In the Client name box, enter the name of the Teradata Extension for NetBackup host that
performs the operations that the batch file and ARCMAIN script specify.
For Teradata TARA, the client name is always the name of the TARA server.
3
Choose the hardware and operating system type.
4
Click Add.
5
Do one of the following:
•
To add another client, repeat step 2 through step 4.
•
If this is the last client, click Close to close the dialog box.
Test Configuration Settings
Use the NetBackup Administration Console for this procedure.
After you have configured the master server for Teradata Extension for NetBackup, test the
configuration settings. For a description of status codes, refer to the Symantec NetBackup
Troubleshooting Guide for UNIX, Windows, and Linux.
Use the next procedure to test a policy configuration from a Windows or Linux server or from
the Remote Administration Console. The instructions are for Windows; however, Linux
procedures are similar.
To test the configuration settings on a Windows server
62
1
Log on to the server as administrator.
2
Start the NetBackup Administration Console.
3
In the left pane, click Policies. The policy list appears in the right pane.
4
Click the policy name to test.
5
Click Actions>Manual Backup. The Manual Backup dialog box appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Multiplexing
The Schedules pane contains the name of a schedule (or schedules) configured for the
policy you are going to test. The Clients pane contains the name of the client(s) listed in
the policy to be tested.
6
Follow the instructions on the dialog box.
7
Click Activity Monitor on the NetBackup Administration Console.
If the manual backup exits without a successful status, refer to the Chapter 8: “Teradata
TARA Troubleshooting”.
Multiplexing
Do not enable the NetBackup Storage Unit Tape Drive Multiplexing option for storage units
that are associated with Teradata policies.
Configure Client Overrides
When a TARA client must restore a dataset image that was created on a different TARA client,
it is important that Teradata Extension for NetBackup is configured to allow each Teradata
client access to the other Teradata clients’ datasets. There are two methods to make the client
override. They are normally done during installation. When this is completed, TARA clients
can access the images of other TARA clients.
Method #1
This method mainly applies to configurations where the NetBackup master is servicing only
TARA clients.
•
For Windows, create a directory and name it altnames in the
<Install_Path>\NetBackup\db directory.
•
For Linux, create a directory and name it altnames in the /usr/openv/netbackup/db
directory.
•
Create an empty file or directory called No.Restrictions
Method #2
This method allows each TARA client access to the dataset images of the other TARA clients,
but does not affect any other client access permissions.
•
For Windows, create a directory and name it altnames in the
<Install_Path>\NetBackup\db directory.
•
For Linux, create a directory and name it altnames in the /usr/openv/netbackup/db
directory.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
63
Chapter 3: Teradata TARA Configuration
Create Restore Userids
•
Create a file for each client that you are providing access permissions. The name of the file
is the client name. In each client file, add the names of each client that can access this
client's images. Each line of the file will contain one client name.
Create Restore Userids
Use the NetBackup Administration Console for this procedure.
Teradata Database requires exclusive use of userids to run a restore operation. Multi-stream
restores that use multiple Teradata logons require exclusive use of multiple userids. Teradata
Database logon accounts used for database and table restore processes must be established
prior to launching a NetBackup Teradata restore job.
Ensure that these userids have the restore privilege for any databases that they need to restore.
The following Teradata manuals are helpful in defining access rights (that is, restore
privileges) and other Teradata-specific terminology: Teradata Archive/Recovery Utility
Reference and Introduction to Teradata. This documentation is available from
www.info.teradata.com.
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 65)
2
Clients system (refer to “To configure the client systems” on page 66)
3
Client Groups (refer to “To configure the client groups” on page 68)
4
NetBackup information (refer to “To configure NetBackup information” on page 70)
After filling in the Netbackup Master Server, Metadata Query Client, and Policy Group
boxes, click Refresh to populate the Client Policies and Available Policies columns.
Note: Do not attempt to click Apply until you have completed these four steps. Applying these
changes before defining and refreshing the NetBackup information causes an error message
regarding 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.
64
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
To configure the Teradata Database system
1
Click Teradata Tiered Archive/Restore Architecture>Settings>Server Configuration. The
TARA Server Configuration dialog box appears with the Teradata tab selected by default.
2
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.
3
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.
4
In Teradata TDPID, type the Teradata Database machine name. Usually, the display name
and the Teradata TDPID name are the same.
5
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.
6
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. For more
details, refer to Teradata Archive/Recovery Utility Reference.
7
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
Teradata Extension for NetBackup Administrator Guide, Release 15.00
65
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
drives that are configured. For example, if there are four BAR servers, each having two tape
drives, enter eight streams.
8
In Default Session Count, the default for the selected database is set in the Teradata tab of
the TARA Server Configuration dialog box (see “TARA Server Configuration Dialog Box:
Teradata Tab” on page 206). 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.
9
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 64 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
1
66
Select the Clients tab of the TARA Server Configuration dialog box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
2
Do one of the following:
•
Select a current client system from the Client System list. Do not select prior system
names associated with active backup images or problems will result when you
synchronize images.
•
Click New to indicate information for a new client system.
3
[Optional] To remove a client system from the configuration, select the client system from
the Client System list, then click Remove.
4
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.
5
Enter the system name of the client node in Client Machine Name.
6
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 a NetBackup Media Manager. The maximum number of
streams cannot be greater than the total number of media devices defined for the
NetBackup Teradata domain.
7
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 64 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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
67
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
To configure the client groups
1
Select the Client Groups tab of the TARA Server Configuration dialog box.
2
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.
3
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.
4
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.
5
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.
6
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.
68
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
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.
7
Select the NetBackup tab of the TARA Server Configuration dialog box, then go to “To
configure NetBackup information”.
Step 4 - 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 64. If this is
not a new installation of Teradata TARA, there is no required order of configuration.
To configure ARC options
1
Select the ARC Options tab in the TARA Server Configuration dialog box.
2
[Optional] Select Use Catalog to specify positioning data, so that when an object is
restored, NetBackup can locate it without searching the entire tape.
3
[Optional] Clear the Use Checksum Verification box, which is checked by default. The
checksum verification feature verifies that the data being archived or restored is valid.
However, the overhead of error checking slows the archive or restore process.
4
[Optional] Select a character set other than ASCII in the Default Character Set list.
ASCII is the default.
Refer to the Teradata Archive/Recovery Utility Reference for details on valid ARCMAIN
command-line options.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
69
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
5
[Optional] In the Extra ARC Options box, enter any ARCMAIN command-line options
that are not part of the GUI ARC build flow. In the example, VB3 appears in the box as the
default (VB3 is a debug parameter that ARCMAIN uses to enable a level of tracing).
Step 5 - Configure NetBackup Information
After a new installation of Teradata TARA, the fourth step is configuring the NetBackup
information. Refer to “Configure the TARA Server” on page 64 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 NetBackup information
1
Select the NetBackup tab of the TARA Server Configuration dialog box.
2
The NetBackup Master Server box currently displays the name of the machine that has
NetBackup server software installed. It is possible to change this name.
3
The display name of the client node that is currently configured to receive NetBackup
information appears in the Metadata Query Client list. It is possible to select another
configured client machine.
Note: A Metadata Query Client is the BAR server that Teradata TARA uses to launch
NetBackup queries pertaining to policies, backup clients, and backup image information.
It can be any TARA BAR server that has NetBackup installed and resides in the
NetBackup-defined domain.
70
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
4
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 Policies.
Click Default to set the client group displayed in the Client Group drop-down list as the
default.
5
The Client Policies column lists the policies that have been added to a policy group.
To remove a policy from the group, highlight the policy and click Remove. The policy
name is transferred to the Available Policies column.
To add a policy to the group, highlight a policy in the Available Policies column. Click Add.
To move a policy up in the order in which it is used for a backup or restore job, highlight
the policy in the Client Policies column. Click Move Up. If there are more policies than
streams, the policy that appears first will be used for the backup or restore job.
To move a policy down in the order in which it is used for a backup or restore job,
highlight the policy in the Client Policies column. Click Move Down.
6
Select the ARC Options tab of the TARA Server Configuration dialog box, then go to “To
configure ARC options”.
Step 6 - TARA Server Port
By selecting the TARA Server Port tab, the port number can be changed. (The default port
number is 54323.)
To change 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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
71
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
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.
5
Enter the new Tara Server Port Number. Click OK.
6
Close all the existing TARA User Interface (UI) windows.
7
Restart the TARAServer and the TARAClient services.
8
Double-click
9
Logon to the TARA Server.
or click Start>All Programs>Teradata Client>TARA GUI.
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 54323.
Step 7 - Password Options
Use the TARA Logon Setup tab to create passwords for the administrator and user.
72
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
To set passwords
The user’s limited read-only privileges include viewing job details and the help files. The
administrator has full privileges. Supported with TARA 13.01 and later, passwords can be
created for one administrator and one user.
Passwords must have at least:
•
Eight characters
•
One numeric character
•
One upper-case character
•
One lower-case character
Passwords cannot:
•
Have three identical characters
•
Be the reverse of the administrator logon name
1
Enter passwords for the User Name one at a time.
2
After each password is entered, click Apply.
3
After all desired passwords are entered and applied, click OK.
Note: Only two User Names are allowed. They are Administrator and User. (For example, User
can’t be changed to User1.) The Administrator has full privileges. The User has the read-only
privilege.
The TARA logon credentials are completely separate from the operating system's logon
credentials.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
73
Chapter 3: Teradata TARA Configuration
Configure the TARA Server
Step 8 - Configure Logging
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 64. If this is not a new
installation of Teradata TARA, there is no required order of configuration.
To configure logging
Notice:
74
1
[Optional] Check Enable Audit Log to track TARA Server configuration changes. See
“TARA Server Audit Log” on page 218 for more information.
2
[Optional] Clear the Override Global Log Level box to change the log level. The Global Log
level is pre-set to 32, which is the minimum, or normal, log level. The maximum level is
63. Increasing the Global Log level adds verbosity to the log for each TARA server
component.
3
[Optional] Change other logging levels in the dialog box. Logging levels of the individual
components of the TARA server are pre-set and cannot be changed unless the Override
Global Log Level check box is selected.
Do not customize log settings unless Teradata Global Support recommends it.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 3: Teradata TARA Configuration
Configure the TARA Server GUI
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.
2
The localhost name is the default and appears in TARA Server 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 54323 and appears when the GUI is first
run.
4
Click Apply to apply changes.
Increasing the Java Heap Size
Increasing the Java heap size is necessary if the TARA GUI monitors a job whose ARC output
causes the GUI to exceed the default heap size of the Java Virtual Machine (JVM). Exceeding
the default size can cause the GUI to 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.
Configure the Log File
The default size of the Linux TARA server's logfile is 2GB. When this limit is reached, the
TARA server saves the existing log as logfile.prev, then creates a new logfile before writing more
log entries. Do not set the value greater than 2GB. Doing so can cause the TARA server to
become unresponsive.
Adjust the logfile maximum length to a value less than 2GB by adding an entry within the
[Defaults] stanza of the:
•
/etc/opt/teradata/tara/defaults file (Linux)
•
<install_path>\teradata/tara\server\config\defaults file (Windows)
Teradata Extension for NetBackup Administrator Guide, Release 15.00
75
Chapter 3: Teradata TARA Configuration
Configure the Log File
Example
Specify the file size in bytes:
filesize=numofbytes
For example, to set the log file size to exactly 500MB (500 * 1024), type:
filesize=524288000
76
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 4
Backup, Restore, and Migrate Operations
After completing installation and configuration, start Teradata backup and restore operations
through the Teradata TARA GUI. The Teradata TARA GUI also provides the ability to migrate
images created under the legacy Teradata Extension for NetBackup to a Teradata TARA Job
Information file. This allows Teradata TARA to restore data from a NetBackup image.
Chapter topics include:
•
Start the Teradata TARA GUI
•
Archive a Database Object
•
Select Individual Objects to Archive or Restore
•
Restore a Database Object
•
Restore Latest Backup Job
•
Manually Restore a Multistream Archive Using Fewer Streams
•
Restore a Multistream Archive Using Fewer Streams
•
Manually Restore a Multistream Archive Using Fewer Streams
•
Restore the DBC Database Backup Job
•
Valid Keywords
•
Validate Edited Job Scripts
•
Exclude Tables in Job Script
•
Synchronize TARA JobFiles with NetBackup Catalog Images
•
Extensions for Job Files
•
View Job History
•
Abort Jobs
•
Delete Failed Jobs in Job History
•
Search for Strings in Job Logs
•
Migrate an Image
•
Migrate an Existing Dictionary Backup Job
•
Verify a Migrated Object
•
Delete Temporary Files in baruser Directory
Teradata Extension for NetBackup Administrator Guide, Release 15.00
77
Chapter 4: Backup, Restore, and Migrate Operations
Start the Teradata TARA GUI
Start 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:
a
On Linux, type one of the following:
/opt/teradata/tara/gui/bin/taragui &
OR
cd /opt/teradata/tara/gui/bin
./taragui &
b
On Windows, do one of the following:
•
Double-click
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.
4
Enter the previously configured password.
The Teradata Tiered Archive/Restore Architecture dialog box appears.
78
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Displaying Help
•
There are problems displaying numbered lists when viewing help with Internet Explorer
V8.0. To remedy this problem, enable the browser setting to be compatible with Internet
Explorer V7.0.
•
When using a Linux operating system, the icon to expand a database tree is displayed as
.
•
When using a Windows operating system, the icon to expand a database tree is displayed
as
.
Archive a Database Object
You must log on to Teradata Database before you can select objects to archive or use Auto
Generate to automatically archive databases.
•
“To log on to Teradata Database” on page 80
•
“To archive a database object” on page 80
•
“To use Auto Generate to archive databases” on page 85
Teradata Extension for NetBackup Administrator Guide, Release 15.00
79
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
To log on to Teradata Database
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.
To archive a database object
80
1
In the left and right panes of the ARCHIVE object selection dialog box are database objects.
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.
2
Click on a level in the left pane. The database and tables appear in the right pane. The
following screen capture shows a database with a hierarchical view.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
3
[Optional] To specify Partitioned Primary Index (PPI) options for a table:
a
Right-click on a table in the right pane.
b
Click Options. A dialog box with a PPI options tab opens.
c
Click on one of the radio buttons:
•
Full table, which is the default, archives the entire table
•
Selected Partitions archives the specified partitions
All Partitions option is not valid for archive operations
Other PPI Options is not valid for archive operations.
4
From the ARCHIVE object selection File menu, click Build ARC script or
5
Select database objects, then confirm the selection by clicking OK in the Selection dialog
box. The Script Options dialog box appears.
6
Select options shown in the following table.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
.
81
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Option
Description
Job Name
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
The entry in this box reflects the TDPID with which you logged on. It is not
possible to change the TDPID.
User Name
The user name with which you logged on appears. To create another job for
the specified database, type a new user name.
Password
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.
Single stream or
Multi stream
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.
Default Group
The list defaults to all clients, which are assigned to streams in a round-robin
manner. For example, if there are six streams and four clients, the stream
assignment is:
• Client1 is assigned to Stream1
• Client2 is assigned to Stream2
• Client3 is assigned to Stream3
• Client4 is assigned to Stream4
• Client1 is assigned to Stream5
• Client2 is assigned to Stream6
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 or restore job.
82
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Option
Description
Assign Clients
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
This option is no longer valid. The Crypto Key Management System (KMS)
replaces Protegrity encryption.
QueryBanding
[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;
See Teradata Archive/Recovery Utility Reference for more information on
query banding.
Online Backup
[Optional]
1 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.
2 In the drop-down list, select Default or NoSync.
With the NoSync option, no read or access lock is placed on the database
and the tables are not synchronized. The tables do not have a shared
consistency point. Instead, each table has its own consistency point for
restore jobs. The primary purpose of NoSync is to minimize the effect of
transactions writing to the database.
See Teradata Archive/Recovery Utility Reference for more information on
online archive.
Sessions (per
stream)
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.
Extra Options
[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.
Backup
Application
The default is NetBackup.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
83
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Option
Description
Full Backup or
Dictionary Only
[Optional] Select Dictionary Only from the drop-down list to archive only
the dictionary, or allow the Full Backup selection to archive the dictionary
and data.
If you choose Dictionary Only, specify only one stream per job.
Use Catalog
[Optional] Select Use Catalog to specify positioning data, so that when an
object is restored, NetBackup can locate it without searching the entire tape.
Verify
Checksum
[Optional] Verify Checksum verifies that the data being archived is valid. The
checkbox is selected by default. However, the overhead of error checking
slows the archive process. To improve performance, clear the checkbox.
Note: Job scripts created prior to clearing the Verify Checksum box have the
verify checksum feature enabled by default.
Force online
logging off
[Optional] To stop online logging:
1 Check the Online Backup box.
2 Check the Force online logging off box.
Normally, Teradata ARC allows online logging to continue even when a job
fails or is aborted. Log files can become so large that subsequent attempts to
archive the same database result in job failure.
Turning online logging off avoids the problem of log files becoming too large
if a job fails or is aborted.
An ONLINE LOGOFF job is created and runs immediately after the parent
job completes, except when the TARA server aborts the parent job because
no connection could be made to stream 1 within 10 minutes. The ONLINE
LOGOFF job is also aborted for connection failure after 10 minutes.
Note: The ONLINE LOGOFF job can be aborted from the GUI, regardless
of its state.
Character set
The default is UTF-8. Select another character set if appropriate.
Policies
Click to display the Policy Selection dialog box. In the dialog box, select a
specific policy for each stream from Manual Policy Selection. All defined
policies are listed in Manual Policy Selection, not only the policies assigned to
the default policy group.
Other Buttons
7
Save
Click Save to accept the current script.
Launch
Click Launch to launch the job.
Preview
[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.
Close
Click Close to close the Script Options dialog box.
Click Save, then Launch.
The Teradata Tiered Archive/Restore Architecture dialog box displays the launched job and job
streams. Conditions for each stream appear in the State column.
84
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
•
ARCHIVE (B) - Build phase (only for restore operations)
•
ARCHIVE (D) - Dictionary (for archive and restore operations)
•
ARCHIVE (T) - Table Data (for archive and restore operations)
To use Auto Generate to archive databases
The Auto Generate feature automatically generates the scripts required for archiving only the
DBC database or all databases except the DBC database.
1
From the ARCHIVE object selection dialog box, click File>Auto Generate.
The Auto Generate dialog box appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
85
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
2
Select one of the following:
•
Archive DBC database only
•
Archive all databases except DBC database
An ARC script is automatically generated for the selected archive job.
3
[Optional] Edit the ARC script.
4
Click OK.
The Auto Generate dialog box closes and the Script Options dialog box appears.
5
Enter a job name in Job name.
6
[Optional] Enter or change other options in the Script Options dialog box.
7
Click Save.
8
Click Launch.
Job status can be tracked in the State column of the Teradata Tiered Archive/Restore
Architecture dialog box.
To view logs and job details
After a TARA archive or restore job completes, click one of the following tabs to view
information for each stream:
86
•
TARA Logs contains the ARC display lines for the stream
•
NetBackup Logs contains the NetBackup event lines for the stream
•
NetBackup Job Details contains NetBackup information for the stream
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Figure 2: Job Stream
Note: Job status displays in the Teradata Tiered Archive/Restore Architecture dialog box for ten
minutes after the job terminates. Then the job is automatically removed and can be seen in the
Job Viewer.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
87
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
1
Click on the stream to view information under the TARA Logs tab.
Figure 3: TARA Logs
2
88
Click on the NetBackup Logs tab for event log information for the resource assignment
and its management during the NetBackup job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Figure 4: NetBackup Logs
3
Click on the NetBackup Job Details tab to view the NetBackup job attributes associated
with the stream.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
89
Chapter 4: Backup, Restore, and Migrate Operations
Archive a Database Object
Figure 5: NetBackup Job Details
Table 17: NetBackup Job Details
Name
Job Details
Job
The NetBackup job number
ID
This is the image identifier that NetBackup calls the backupid. This can be used with the
bpmedialist utility.
Policy
The NetBackup policy that specifies the job attributes
First Image/Last Image
The names of the first and last segments of the stream’s image. The segments are in sequential
order from F0000 to F9999.
Status
The Netbackup job’s final status code.
Status Description
The interpretation of the status.
Media ID
Will contain the bar codes of the tapes used in the stream’s backup
90
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Select Individual Objects to Archive or Restore
Dictionary Only Archive
To create a Dictionary Only archive job
1
In the Script Options dialog box, select Dictionary Only from the Full Backup and
Dictionary Only drop-down list.
2
Ensure that SingleStream is selected.
Automatic Scheduling by NetBackup
Create a NetBackup policy for any job that will be scheduled automatically by NetBackup.
Refer to “Configure a NetBackup Policy” on page 55.
Select Individual Objects to Archive or Restore
Beginning with Teradata Database 13.00, selecting an individual view, macro, procedure, or
other Teradata object to archive or restore is valid. Prior to Teradata TARA 13.00, archiving
and restoring was limited to databases and tables.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
91
Chapter 4: Backup, Restore, and Migrate Operations
Select Individual Objects to Archive or Restore
The prerequisites for this feature are:
•
TARA 13.00
•
Teradata ARC 13.00
•
Teradata Database 13.00
In the next screen example, the BASIC macro in the bar_ac database is the only object selected
for archive.
Table 18 lists the icons that represent the objects.
Table 18: Object Icons
Icon
Object
Database
Function
Index
92
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Select Individual Objects to Archive or Restore
Table 18: Object Icons (continued)
Icon
Object
Join Index
Journal
Macro
Procedure
SQL-H
Table
Trigger
User Installed File
View
Teradata Extension for NetBackup Administrator Guide, Release 15.00
93
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
Restore 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.
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 the icon
to the left of the dataset name to expand the tree further.
94
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.
3
Double-click on the icon to the left of the object name to expand the tree and show the
specific tables to be restored. The following screen capture shows a database with a
hierarchical view.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
4
[Optional] Right-click on the database icon or table in the right pane to specify copy and
Partitioned Primary Index (PPI) options. A dialog box with COPY options and PPI options
tabs appears.
a
b
[Optional] Specify COPY options as described in the following table.
Option
Description
Rename Object
Gives the object in the archive a different name than the target
object.
Disable fallback on
table (NO FALLBACK)
Copies fallback tables into non-fallback tables. If the archived table is
already non-fallback, this option has no effect.
Disable journaling on
table (NO JOURNAL)
Copies all tables with journaling disabled, whether journaled in the
archive or not.
Replace table creator
value (REPLACE
CREATOR)
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.
Specify different journal
table
Specifies that a copied database has journaling for the specified
database and journal table.
APPLY TO list
Identifies the tables in the target system where the change images
apply.
[Optional] To specify PPI options:
i
Click the PPI options tab.
ii
Click one of the following radio buttons.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
95
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
•
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.
5
In the RESTORE object selection dialog box, click File>Build ARC script.
After the database objects are selected, the Selection dialog box appears.
When you click OK, the Script Options dialog box appears.
Note: If you are restoring a job that backed up only the DBC database or all of the DBC
database, the Restore DBC dialog box appears instead of the Script Options dialog box.
6
In the RESTORE object selection dialog box, select options as described in the following
table.
Option
Description
Job Name
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.
Always restore latest
[Optional] Check the Always restore latest box to automatically restore
the last image that was backed up successfully.
Note: If you are restoring an image created with a version of Teradata
Extension for NetBackup prior to 14.0, update the job IDs before
restoring the image. Update Latest Job Ids box in RESTORE object
selection>Edit>Update Latest Job Ids
96
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
Option
Description
Description
TDPID
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.
User Name
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.
Password
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.
SingleStream or
MultiStream
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.
You can specify fewer streams when restoring a job than were specified
when the job was archived. See “Restore a Multistream Archive Using
Fewer Streams” on page 109.
Default Group
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.
Assign Clients
Each stream defaults to All clients. Click Assign Clients to assign a
specific client to each stream.
Note: Assign a client system that uses a current name or the restore job
will fail.
Configure
RestoreScript
Objects are restored instead of copied.
The RestoreScript radio button is automatically selected. To copy objects,
click CopyScript.
Full or Dictionary
Only
[Optional] Select Dictionary Only from the drop-down list to restore only
the dictionary, or allow the Full Backup selection to restore the dictionary
and data.
The drop-down list is enabled only when the RestoreScript or CopyScript
radio button has been selected.
CopyScript
To copy, instead of restore an object, click CopyScript. The RestoreScript
radio button is cleared.
Analyze
When this option is selected, all the records are validated to ensure the
correct order and type of records are on the tape. The entire backup
image is analyzed, regardless of the databases that are selected for
the analyze job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
97
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
Option
Description
QueryBanding
[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;
QB Options
[Optional] Click QB Options to open the QueryBanding Options dialog
box. Selected options are added to the job script.
[Optional] Check the TVS Temperature box to enable a list with the
following selections:
• Hot
Specifies that the job is hot data, which is frequently accessed and
changed.
• Warm
Specifies that the job is warm data, which is more frequently accessed
and changed than cold data.
• Cold
Specifies that the job is cold data, which is infrequently accessed and
rarely changed.
• Auto
The temperature setting is based on the target system temperature
settings.
[Optional] Check the Block Compression box to enable a list with the
following selections:
• Yes
Block level compression is enabled. This setting overrides the setting
information saved with the archive job.
• No
Block level compression is disabled. This setting overrides the setting
information saved with the archive job.
• Auto
The block level compression setting is based on the target system
block level compression settings.
98
Sessions (per
stream)
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.
Extra Options
[Optional] Enter any ARCMAIN command line options that are not part
of the GUI ARC build flow. IOTRACE=5 is the default.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
Option
Description
Use Catalog
[Optional] Select Use Catalog to specify positioning data so that when an
object is restored, NetBackup can locate it without searching the entire
tape.
Verify CheckSum
[Optional] Verify Checksum verifies that the data being restored is valid.
The checkbox is selected by default. However, the overhead of error
checking slows the restore process. To improve performance, clear the
checkbox.
Note: Job scripts created prior to clearing the Verify Checksum box have
the verify checksum feature enabled by default.
Skip Build Steps
[Optional] Select this check box to skip the build steps, which NetBackup
considers idle time. If you skip the build steps now, manually run the
build step outside of NetBackup after all data is restored.
CharacterSet
The default is ASCII. Select another character set if appropriate.
Extra Buttons
Save
Click Save to accept the script options that have been selected.
Launch
Click Launch to launch the job. The job appears in the Teradata Tiered
Archive/Restore Architecture dialog box.
Preview
[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.
Close
Click Close, but do not click Save, to close the dialog box without saving
any changes.
7
In the Script Options dialog box, click Save.
8
Click Launch.
Restore job status appears in the Teradata Tiered Archive/Restore Architecture dialog box.
Overriding the Existing NetBackup CLIENT_READ_TIMEOUT Value
The CLIENT_READ_TIMEOUT option in NetBackup monitors the idle time between the
backup or restore application and the media server software. If the value of the option is
exceeded (no data transfer between the client and media server), the job is automatically
aborted. For a restore job, the value must account for the time it will take the client's arcmain
to complete the build step of each table.
To override the current value in the Script Options screen, include nbutime=<Value> in the
Extra Options field, where value is the number of seconds that the
CLIENT_READ_TIMEOUT option will allow no activity before aborting the job.
The rules for entering this option are:
•
There can not be spaces in the option. For example, nbutime = 30000 will fail.
•
The value must be between 300 and 32767. All other values will fail.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
99
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
After the job completes, the original CLIENT_READ_TIMEOUT value is automatically
restored.
Dictionary Only Restore
A job can be created for a dictionary-only restore job.
In the Script Options dialog box, select Dictionary Only from the Full and Dictionary Only
drop-down list.
Analyze Using Script Options Dialog Box
Selecting the Analyze option in the Script Options dialog box validates all records, which
ensures the correct order and type of records are on the tape. The entire backup image is
analyzed, regardless of the databases that are selected for the analyze job.
For information about the ANALYZE command, see the Teradata Archive/Recovery Utility
Reference.
Note: The Script Options dialog box does not appear if you are restoring a job that backed up
only the DBC database or all of the DBC database. Instead, the Restore DBC dialog box
appears.
100
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
Analyze Using Restore DBC Dialog Box
To run an analyze job when restoring DBC database
Use the Restore DBC dialog box to analyze a job that restores only the DBC database or all of
the DBC database.
1
Select the DBC database job from the RESTORE object selection dialog box.
2
Click RESTORE object selection>File>Build ARC script.
3
In the Restore DBC dialog box, click Skip Step 1.
4
Click Done in Step 2.
5
Click Generate in Step 3.
CopyScript
Supported with TARA 13.01 and later, there are three CopyScript options:
•
Check/Uncheck Selections
•
Rename and Copy into Same Database
•
Copy into New Database
Teradata Extension for NetBackup Administrator Guide, Release 15.00
101
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
To access CopyScript options
1
From the Teradata Tiered Archive/Restore Architecture screen, select Task>Restore.
2
The Restore object selection dialog box appears.
3
From the left pane, select a database to display database objects in the right pane.
4
From the right pane, select two or more consecutive database objects:
5
102
a
Left-click on the first database object you want to select.
b
Press Shift and left-click on the last database object in the series of database objects
you want to select. In the next screen, BLOBT01, CLOBT01, COMBOLOBT01, and
Count_Chars are selected.
c
[Optional] To add another object to your list of objects, select the object by pressing
CTRL and left-click. In the next screen, customer is added to the list of selected objects.
In the right pane, right-click. CopyScript options appear.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
6
Go to one of the following sections for instructions on CopyScript options:
•
To check or clear the selection of database objects
•
To rename and copy database objects into the same database
•
To copy into a new database
Teradata Extension for NetBackup Administrator Guide, Release 15.00
103
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
To check or clear the selection of database objects
1
104
From CopyScript options, select Check/Uncheck Selection to toggle the checkmarks of
highlighted database objects on or off.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
To rename and copy database objects into the same database
1
From CopyScript options, select Rename and Copy into Same Database.
The Rename and Copy into Same Database dialog box appears.
2
Enter a new name for each database object. Click OK.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
105
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
106
3
From the Restore object selection screen, select File>Build Arc Script. The Selection dialog
box appears.
4
Click OK to confirm the database object selections. The Script Options screen appears.
5
Enter the job name in Job Name.
6
Click Preview. The Script Editor screen appears displaying the renamed database objects.
7
Save the job by clicking Save when the Save Script dialog box appears. Leave the script
type as not available.
8
Click Launch to launch the job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Database Object
To copy into a new database
1
From CopyScript options, select Copy into New Database.
The Copy Into New Database dialog box appears.
2
Enter the new database name. Click OK.
3
From the Restore object selection screen, select File>Build Arc Script.
4
The Selection dialog box appears. Click OK to confirm the database object selections.
5
The Script Options screen appears.
6
Enter the job name in the Job Name field.
7
Click Preview. The Script Editor screen appears displaying the database objects that will be
copied into the new database.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
107
Chapter 4: Backup, Restore, and Migrate Operations
Restore Latest Backup Job
8
Save the job by clicking Save when the Save Script dialog box appears. Leave the script
type as not available.
9
Launch the job.
Restore Latest Backup Job
To restore latest backup job
You can automatically restore the last image that was backed up successfully. Depending on
the version of Teradata Extension for NetBackup that created the image, you must update the
job ID before restoring the image. If you are restoring an image created with:
•
A version of Teradata Extension for NetBackup prior to 14.0, update the job ID
•
Teradata Extension for NetBackup 14.0, updating the job ID is optional
Note: Updating the job ID before restoring the last image is recommended.
1
[Optional for images created by version 14.0] In the RESTORE object selection dialog box:
a
Click Edit>Update Latest Job Ids.
All job IDs are updated in the latestjobs file on the server.
b
2
108
Click OK.
In the RESTORE object selection dialog box, select the databases or objects for the restore
job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore a Multistream Archive Using Fewer Streams
3
Click Build ARC script.
4
Click OK to confirm the selection.
5
In the Script Options dialog box, check the Always restore latest box.
6
Complete the other fields in the Script Options dialog box.
7
Click Save, then Launch to run the restore job.
Restore a Multistream Archive Using Fewer
Streams
To restore a multistream archive job using 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, the restore job must be divided into two or more jobs.
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
Enter a job name.
4
To reassign client streams, click Assign Clients. The Assign Clients dialog box opens.
5
Select a client group or node for each stream, then click OK.
6
In the Multi stream box of the Script Options dialog box, change the number of streams to
the number of streams that are available. For example, if a backup job was created using 16
streams but only 4 storage devices are available for the restore job, select 4 streams.
A dialog box requests validation of the client and stream assignments, and the stream
count.
7
Click OK if the client and stream assignments are correct. If you click Cancel, the original
stream count is restored.
A dialog box notifies you that multiple jobs must be created to complete the entire restore
job.
8
Click OK.
Job scripts are created for the streams that were specified and are displayed in the Teradata
Tiered Archive/Restore Architecture dialog box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
109
Chapter 4: Backup, Restore, and Migrate Operations
Manually Restore a Multistream Archive Using Fewer Streams
9
In the Teradata Tiered Archive/Restore Architecture dialog box, select the first job script. In
the example, 4 streams are specified for a restore job called new_test. The scripts that are
created for the job are:
•
new_test_1.res
•
new_test_2.res
•
new_test_3.res
•
new_test_4.res
Each job script contains 4 of the 16 streams specified in the backup job and must be run
sequentially. In the example, new_test_1.res would be run first.
10 Click Launch, then confirm job launch.
11 Select and launch the next job that was created for the multistream restore job. In the
example, new_test_2.res would be run.
12 Run the remainder of the job scripts sequentially.
13 [Optional] To display information job progress:
a
Double-click the job or stream in the Teradata Tiered Archive/Restore Architecture
dialog box.
A dialog box appears with the job name.
b
Select a stream to display its information in the bottom pane of the dialog box.
Manually Restore a Multistream Archive Using
Fewer Streams
To manually restore a multistream archive job using 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 BARAC_AC backup was created using four streams. Only two storage devices are
available, therefore the example restores streams 1 and 2 in the first job, and streams 3 and 4 in
the second job.
110
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.
A dialog box advises reassigning the original clients and their streams before selecting
fewer streams.
5
Click OK. A warning that you are attempting to restore from fewer streams than the
streams used for the original backup appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Manually Restore a Multistream Archive Using Fewer Streams
6
Click Cancel.
7
Click Cancel when asked if you want to revert to the original stream count.
In this example, two streams are specified instead of the four streams with which the job
was created.
8
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.
9
Click Save, then Launch.
To display information on the job’s progress, double-click the job or stream in Teradata
Tiered Archive/Restore Architecture. A dialog box appears: select a stream to display its
information in the bottom pane of the dialog box.
10 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 opens.
11 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.
In this example, the job restores the remaining two streams of the database BAR_AC
backup.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
111
Chapter 4: Backup, Restore, and Migrate Operations
Restore the DBC Database Backup Job
Note: In the example, the NO BUILD statement is not removed from the script, therefore a
separate arcmain build is required after job completion. If the NO BUILD statement is
removed from this script, arcmain automatically performs the build step.
12 Save the job with a name different than the original job name, then click Launch.
Restore the DBC Database Backup Job
If you created a job using Teradata TARA 14.0 or later in which only the DBC database or all of
the DBC database was backed up, restoring the job requires a Teradata Database system
initialization process that destroys all user and dictionary data and reinitializes the system.
To reinitialize the system
Before you restore all data from the DBC backup job, delete the DBC database.
112
1
Run sysinit to reinitialize the system. Refer to Utilities: Volume 1 (A-K), B035-1102.
2
[Optional] If necessary, reconfigure the system to the desired configuration.
3
Run the DBC Initialization Procedure (DIP) to initialize system views, macros, users, and
error message tables. Refer to Utilities: Volume 1 (A-K), B035-1102.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Restore the DBC Database Backup Job
To restore the DBC database backup job
After you have deleted the DBC database and reinitialized the system, restore the DBC backup
job.
1
From the Teradata Tiered Archive/Restore Architecture dialog box, click Task>Restore.
2
In the Restore object selection dialog box, select the job that backed up all or only the DBC
database.
3
Click File>Build ARC script. The Restore DBC dialog box opens.
4
Click Generate in step 1. The DBC database is deleted and restored.
5
[Optional] Check the Skip Step 1 box if you will not complete the remaining steps listed in
this dialog box at the current time. Checking the box will remind you that the first step has
been completed.
6
Validate that the DBC database has been restored by checking job status in the TARA GUI.
7
On a TPA node, run the post_dbc_restore script. When PUTTools is installed, the script is
located at /opt/teradata/PUTTools/td14.xx.xx.xx/IUMB_script.
8
Validate that the restore script completed successfully. A message indicates when the script
has completed.
9
In the Restore DBC dialog box, click Done.
10 Click Generate in step 3.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
113
Chapter 4: Backup, Restore, and Migrate Operations
Valid Keywords
11 After the data and journal tables are restored, run the post_data_restore script on the TPA
node at /opt/teradata/PUTTools/td14.xx.xx.xx/IUMB_script.
12 Click Close.
Valid Keywords
The following table describes valid keywords for backup and restore job scripts.
Table 19: Keywords for Job Scripts
Keyword
Required
for
Backup
Required
for
Restore
CATALOG
No
No
Rules
Description
The CATALOG keyword
must be used in the
backup job script that is
associated with a restore
job.
CATALOG specifies positioning data so that
when an object is restored, the object can be
located without searching the entire tape.
If the CATALOG keyword is used in a
backup job script, positioning information is
saved so that is can be used in the associated
restore job.
COMMANDLINE
Yes
Yes
ENDSCRIPT
Yes
Yes
JOB
Yes
Yes
The value is the name assigned to the TARA
job.
MULTISTREAM
Yes
Yes
MULTISTREAM specifies the number of
streams that will be launched for the job.
NBUPOLICY
Yes
No
NBUPOLICYGROUP
Yes
No
114
COMMANDLINE specifies the optional
arguments that are passed to each ARC
stream when the stream is launched.
ENDSCRIPT must be the
last keyword in the script.
There must be the same
number of NBUPOLICY
keywords as the
MULTISTREAM value,
unless
NBUPOLICYGROUP is
used instead of
NBUPOLICY.
ENDSCRIPT marks the end of the ARC
script section.
The value is the name of the policy defined
by the Backup Administrator.
The value is the Client Group name, which is
configured in TARA and contains
NetBackup policy names.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Valid Keywords
Table 19: Keywords for Job Scripts (continued)
Keyword
Required
for
Backup
Required
for
Restore
ONLINELOGOFF
No
N/A
Rules
Description
Users must not add the
_ONLINE_LOGOFF
suffix to backup job file
names because the suffix
is used by TARA. A
backup job file name that
has been specified with a
suffix by the user does
not appear in the
RESTORE object
selection dialog box.
When ONLINELOGOFF is used, two jobs
are launched. The first job is an active
backup job. Status of the second job is
pending until the first job completes, at
which point the second job sets online
logging off.
The name of the second job appends
_ONLINE_LOGOFF to the name of the first
job.
OTB
Yes
No
PASSWORD
No
No
PASSWORD is used with
the USERID keyword.
This value cannot be
manually generated.
PASSWORD is used by the ARC userid logon
and Teradata Database.
SCRIPT
Yes
Yes
SCRIPT must
immediately precede the
ARC script.
SCRIPT marks the end of the TARA script
section and the beginning of the ARC script
section.
SESSIONS
Yes
Yes
SESSIONS specifies the number of data
sessions per stream that ARC establishes
with Teradata Database for a backup or
restore job.
SOURCEUID
No
Yes
SOURCEUID identifies the backup job that
created the dataset used for the restore job.
SOURCEUID is the file name and internal
TARA job identifier.
STREAM
Yes
Yes
STREAMNAME
N/A
No
TDPID
Yes
Yes
USERID
No
No
The value of OTB is "NetBackup".
There must be the same
number of STREAM
keywords as the
MULTISTREAM value.
STREAM is one of the following:
If used, there must be the
same number of
STREAMNAME
keywords as the
MULTISTREAM value.
In a restore job, STREAMNAME overrides
the image name that is stored in the backup
jobfile (SourceUID).
• Client name of the stream
• Client group (preceded by an @ sign)
The TDP identifier of the Teradata Database
to which Teradata ARC connects to perform
a backup or restore.
If used, there must be a
PASSWORD keyword.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
USERID is the Teradata user database logon
account that Teradata ARC uses.
115
Chapter 4: Backup, Restore, and Migrate Operations
Validate Edited Job Scripts
Validate Edited Job Scripts
You should validate any edited job script. Job script errors can result in the TARA server
failing.
Keywords
The following keyword lines are required in a job script:
•
COMMANDLINE
•
ENDSCRIPT
•
JOB
•
MULTISTREAM
•
NBUPOLICY (backup job only)
•
NBUPOLICYGROUP (backup job only)
•
OTB (backup job only)
•
SCRIPT
•
SESSIONS
•
STREAM
•
TDPID
Ensure all keywords are spelled correctly.
No Spaces
With the exception of the COMMANDLINE line, there must be no spaces at the end of a line
of code.
Permitted Characters
Ensure the values for the following lines contain only alphanumeric, underscore, and hyphen
characters:
•
JOB
•
NBUPOLICY
•
NBUPOLICYGROUP
•
STREAM
•
STREAMNAME
There should be no embedded spaces or special characters except underscore and hyphen.
116
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Exclude Tables in Job Script
Stream Values
Ensure the number of:
•
STREAM lines matches the MULTISTREAM value
•
STREAMNAME lines (if present) matches the MULTISTREAM value
•
NBUPOLICY lines matches the MULTISTREAM value
Exclude Tables in Job Script
If you back up the DBC database but exclude tables in the backup job script, only the
dictionary information of the excluded tables is backed up. Data is not backed up.
If you do not exclude tables when you restore the database, the excluded tables are empty
when restored. You must explicitly exclude the tables in the restore job script to avoid
overwriting the existing table.
Synchronize TARA JobFiles with NetBackup
Catalog Images
In most cases, the Netbackup Catalog images that are created for each stream in a TARA
backup job will eventually be automatically deleted according to the Policy's retention period
definition. When this occurs, the TARA backup file that is stored in the TARA server Job
Information Repository (JIR) is out of date.
Modified Job Files
You cannot synchronize job files that have been modified to use DIAGNOSTIC ARCHIVE or
FILE=_DUMMY. Instead, remove the job files using the TARAJobRM force (-f) option.
To synchronize job files
Notice:
Before synchronizing job files, verify that the client system has been correctly configured with
a current client system. A mismatch between the prior system name of an active system and
current system name will accidentally delete the JIR file of the backup job. For example, if the
prior system, nbmedia01, was configured as the client system instead of the current system,
nbmedia01.teradata.com, nbmedia01.teradata.com will not be found and the JIR file will be
deleted.
In the next example, the TARA jobname, BackRestoreTest1a, has four backup jobs. All four
jobs no longer have valid NetBackup catalog images and should be removed.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
117
Chapter 4: Backup, Restore, and Migrate Operations
Synchronize TARA JobFiles with NetBackup Catalog Images
1
Right-click on the TARA Job Name and select the Synchronize option. A warning displays.
The Synchronize option searches the NetBackup Catalog for the image name in the range
from the year the image was created to the current date.
118
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Synchronize TARA JobFiles with NetBackup Catalog Images
If OK is selected, TARA queries the NetBackup image catalog. The TARA backup JobFile is
deleted if all streams associated with that job run are no longer in the NetBackup image
catalog.
In this example, all four BackRestoreTest1a job runs do not have any images in the
NetBackup catalog. As a result, all four BackRestoreTest1a TARA job runs are deleted.
Individual TARA job runs can be synchronized also.
2
[Optional] Right-click on a specific job run you wish to delete if there is no NetBackup
catalog image. The Delete option appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
119
Chapter 4: Backup, Restore, and Migrate Operations
Synchronize TARA JobFiles with NetBackup Catalog Images
A warning displays asking for confirmation before attempting to delete the TARA job run.
If there are no images associated with any of the streams of the job, the TARA job run is
deleted. If there are no more job runs for that specific TARA job name, the TARA job name
is no longer displayed.
120
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Extensions for Job Files
Extensions for Job Files
Supported with TARA 13.01 and later, 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.
To rename a job
1
From the Teradata Tiered Archive/Restore Architecture screen, go to Options and select
Rename.
The Rename Script dialog box appears.
2
Enter the new name in Rename Script File.
3
[Optional] Select one of the following file extensions in Script Type:
•
.arc (archive)
•
.res (restore)
•
not available
Select not available when there is no file extension.
4
Click Save.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
121
Chapter 4: Backup, Restore, and Migrate Operations
View Job History
View 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.
To export job data in HTML format
122
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Abort Jobs
Abort Jobs
Abort a job by clicking Abort in the Teradata Tiered Archive/Restore Architecture dialog box.
Note: A job will not abort if:
•
A diagnostic ARC job is in progress
•
A lock on Teradata Database has not been released yet
•
The job is waiting on XBSA, for example, for a tape mount
Delete Failed Jobs in Job History
To delete failed jobs
To clean up the Job History view and search for jobs more easily, delete failed jobs.
1
Click Task>Job Viewer.
2
Select one or more failed jobs or jobs with unknown status, which is indicated by ?.
3
Right-click to display the shortcut menu.
4
Click Delete or Delete All.
A warning appears.
5
Click OK.
Search for Strings in Job Logs
To search for strings
You can search for a specific string in a job log instead of logging onto the node and searching
for the .out file in /home/baruser. For example, use the search function to determine if specific
tables or databases were backed up or if there were any errors or warnings during the job.
1
Click Task>Job Viewer.
2
In Job History, double-click a job.
A view with stream and object information for the specified job appears.
3
Click on a stream.
Job log information appears in the bottom half of the view.
4
Position your cursor anywhere in the job log output and do one of the following:
•
Right-click and select Search.
•
Press Ctrl+F.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
123
Chapter 4: Backup, Restore, and Migrate Operations
Migrate an Image
The Search dialog box appears.
5
Enter the search string in Enter text.
6
Click OK.
Migrate an Image
To use Teradata TARA to restore one or more backup images that were created by the legacy
Teradata Extension for NetBackup product, those backup images must first be migrated to the
TARA product. The backup images that are stored in the legacy image repository must be
recognized by the TARA product for a seamless migration to TARA. To do this, the image
names must reside in TARA’s job information repository (JIR). The migration process consists
of creating a TARA job record for each backup image that is selected.
Although new TARA backups integrate dictionaries and table data, the migrated backup jobs
will remain separated. Therefore, ensure that for any cluster jobs, both the dictionary job and
the table data are migrated.
124
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Migrate an Image
To migrate a backup image
1
Click Teradata Tiered Archive/Restore Architecture>Task>Migrate. The Migration Interface
dialog box appears.
2
Do one of the following:
•
Click All to display all Teradata images that are available in the legacy Teradata
Extension for NetBackup image repository.
•
Click Query to specify NetBackup backup images for migration. The Netbackup Object
Name and Date options become available. Do one or both of the following:
•
Type the NetBackup object name that was given to the image when it was first
created in Netbackup Object Name. The default is all Teradata images.
•
Specify the start and end dates that the images were created by selecting the day,
month, and year in the calendars. (It is possible to search using only one criterion,
for example, a start date of June 2007.)
The default for the start date is the earliest Teradata image found. The default for
the end date is the latest Teradata image found.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
125
Chapter 4: Backup, Restore, and Migrate Operations
Migrate an Existing Dictionary Backup Job
3
Click Select. The Migration Object Selection dialog box displays the images found in the
search.
4
Select the images to be migrated.
5
Click File>Migrate or
. The status of the migration is shown. A TARA job record is
created for each image upon successful migration.
Refer to “To verify that an object was migrated” on page 128 to see the objects that were
migrated.
Migrate an Existing Dictionary Backup Job
To migrate an existing dictionary backup job
Cluster backups from the legacy Teradata Extension for NetBackup consist of two separate
NetBackup jobs: the dictionary backup job and the cluster data backup job. It is necessary to
separately migrate the images for both jobs using the TARA migration process. In addition,
the migrated dictionary job must be manually edited prior to using it to perform a restore.
126
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Migrate an Existing Dictionary Backup Job
1
Click Teradata Tiered Archive/Restore Architecture>Task>Restore. The RESTORE object
selection dialog box appears.
(In this example, a cluster backup of the DK_TEST database was originally created with
the legacy Teradata Extension for NetBackup. Two images were migrated separately: one
for the dictionary (dk_dct) and one for the cluster data (dk_data).)
2
Select the dictionary dataset, then click File>Build ARC script. The Script Options dialog
box appears.
3
Ensure that the job is single-stream when filling out the text boxes.
4
Click Save, then Preview. The Script Editor dialog box appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
127
Chapter 4: Backup, Restore, and Migrate Operations
Verify a Migrated Object
5
Highlight DATA in the RESTORE DATA TABLES line of text. Change DATA to
DICTIONARY.
6
Click Save. The Save Script dialog box appears.
7
Accept the script name shown or type a new name, then click Save. The Script Editor
dialog box appears.
8
Click Launch.
Verify a Migrated Object
To verify that an object was migrated
128
1
To verify that the object was migrated, click Teradata Tiered Archive/Restore
Architecture>Task>Job Viewer. The Job History dialog box appears.
2
Double-click the object that was migrated. A dialog box with the object name appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Verify a Migrated Object
3
Click the stream. The date of the original backup is shown.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
129
Chapter 4: Backup, Restore, and Migrate Operations
Verify a Migrated Object
4
130
Click the Objects tab to display the objects that were migrated. Expand the tree in the left
pane and select a specific object to view. Tables that are included in the object are shown in
the right pane.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 4: Backup, Restore, and Migrate Operations
Delete Temporary Files in baruser Directory
Delete Temporary Files in baruser Directory
In Linux, the baruser cron job that monitors the TARA client process automatically cleans up
temporary files from /home/baruser on the 28th of each month at 6:00 pm. All temporary files
prior to the current month are deleted. Temporary files are created by the TARA client when a
job, query, or migration is run. The file format is ????????????????_*, for example,
4f4660b600000001_1.out.
To clean up /home/baruser manually, change the first variable in the /home/baruser/tcsmon.bat
script from CLEANUP=1 to CLEANUP=0.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
131
Chapter 4: Backup, Restore, and Migrate Operations
Delete Temporary Files in baruser Directory
132
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 5
Retrieval of Teradata NetBackup Image
Names Using bplist
This chapter describes using the bplist command to retrieve Teradata Extension for
NetBackup restore images. See the NetBackup System Administrator’s Guide for general
information about bplist and the NetBackup Commands User Guide for more information on
other parameters to include in the command to refine the search.
The bplist command retrieves Teradata Extension for NetBackup restore images. See the
NetBackup System Administrator’s Guide for general information about bplist and the
NetBackup Commands User Guide for more information on other parameters to include in the
command to refine the search.
Extract all Teradata Extension for NetBackup
Backups
To extract all of the Teradata Extension for NetBackup backups from a specific server for a
specific client, execute the following command.
install_path/NetBackup/bin/bplist [-C client] -t 26 [-S server] -R /
where client is the host machine on which Teradata Extension for NetBackup resides and
server is the host machine of the NetBackup server. Be sure to include the / at the end of the
command or an error message will result.
The next example shows how to obtain the list of Teradata backups that occurred between all
clients and the NetBackup master server. The command in the example does not show the -S
parameter because the backup occurred on the NetBackup master server.
[root@bsrv3 1137000000]# bplist -C bsrv3 -t 26 -R /
/single_large_43d125ba00000030_DSTREAM0001/F0000
/defaults_43d125ba0000002e_DSTREAM0001/F0000
/no_default_43d125ba0000002d_DSTREAM0001/F0000
/no_policy_43d125ba0000002b_DSTREAM0001/F0000
/extra_option_archive_43d125ba0000002a_DSTREAM0001/F0000
/utf8_43d125ba00000024_DSTREAM0001/F0000
/checksum_on_43d125ba00000023_DSTREAM0001/F0000
/no_checksum_43d125ba00000022_DSTREAM0001/F0000
/bs_test_43d125ba0000001c_DSTREAM0001/F0000
/syrah_test2_43d125ba0000001a_DSTREAM0001/F0000
/01-30-06_single-test_43d125ba00000017_DSTREAM0001/F0000
/davce_43d125ba00000016_DSTREAM0001/F0000
/swl_big_43d125ba0000000f_DSTREAM0001/F0000
Teradata Extension for NetBackup Administrator Guide, Release 15.00
133
Chapter 5: Retrieval of Teradata NetBackup Image Names Using bplist
Extract all Teradata Extension for NetBackup Backups
/swltest_43d125ba0000000e_DSTREAM0001/F0000
/swltest_43d125ba0000000d_DSTREAM0001/F0000
/cy_basic_single_43d125ba0000000c_DSTREAM0001/F0000
/swltest_43d125ba0000000b_DSTREAM0001/F0000
/swltest_43d125ba00000008_DSTREAM0001/F0000
/mm_tst1_43d125ba00000007_DSTREAM0001/F0000
/nonroottest_43d125ba00000004_DSTREAM0001/F0000
/BackupTest_43d125ba00000001_DSTREAM0001/F0000
/jyjm_43d11f6a00000001_DSTREAM0001/F0000
/nbuuiaefbghiu_43d110ab00000004_DSTREAM0001/F0000
/nbuuiaefbghiu_43d110ab00000003_DSTREAM0001/F0000
/nbuuiaefbghiu_43d110ab00000002_DSTREAM0001/F0000
/OTBPtrTest2_43d10c0b00000004_DSTREAM0001/F0000
/OTBPtrTest2_43d10c0b00000003_DSTREAM0001/F0000
/OTBPtrTest_43d10c0b00000002_DSTREAM0001/F0000
/AnotherBackupTest_43d10ad300000001_DSTREAM0001/F0000
/NBUTester_43d0504e00000002_DSTREAM0001/F0000
/ARCHIVE2/F0000
134
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 6
Teradata TARA Command-Line Utilities
This chapter contains information on Teradata TARA stand-alone command-line utilities:
•
TARAJobRM provides the DBA the ability to delete scripts from the script repository, or
job files from the job information repository.
•
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
•
TARAMigrator migrates images created under the legacy Teradata Extension for
NetBackup to a Teradata TARA Job Information file. This allows Teradata TARA to restore
data from a NetBackup image.
•
taraping tests TARA server health.
•
TARAScriptConv allows the conversion of ARC script files from an existing Backup
Application Software format to the TARA format
•
TARASetCfg allows the explicit request of a TARA server to reset its configuration
parameters by re-reading the defaults configuration file
Note: Job scripts created prior to TARA 13.01 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].
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>
Teradata Extension for NetBackup Administrator Guide, Release 15.00
135
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobRM
-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
tarajobrm -u [ <username> ] -p [ <password> ]
OR
-e [ <path to encoded file> ]
-S [ <script_name> | -f <input_filename> ]
[ -s <TARAServer_name> ] [ -v 0|1|2|3 ]
[-P <Port>]
Example
tarajobrm -J [ <jobfile_name> | -f <input_filename> ]
[ -s <TARAServer_name> ] [ -v 0|1|2|3 ]
[-F]
Table 20: Parameters for TARAJobRM
Parameter
Description
Required
-u <User Name>
Specifies the User Name that the utility uses to connect to the TARA Server. Yes
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.
Yes
Example
TARAJobRM -u administrator -p xjmT94Rs
-P <port>
Specifies the port number that the TARA server is running on. The default
port is 54323. If the TARA Server port is changed to a different number,
this option has to be specified with the correct TARA Server port number.
No
Example
TaraJobRM -u administrator -p xflu7H3g -j
MyBackupJob -P 55555
The default is 54323.
136
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobRM
Table 20: Parameters for TARAJobRM (continued)
Parameter
Description
Required
-e <path to encoded
password file>
Specifies the path to the file that contains the encoded password to the User
Name.
Yes
Example
TARAJobRM -u administrator -e C:\Teradata\tara.pwd
Note: The file containing the encoded password is created during the postinstall 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 <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:
This parameter, or
the -J
<jobfile_name>
parameter, is
required.
• 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.
No
-J <jobfile_name>
Specifies a job name, or the name of a file that has a list of jobfile names to
delete.
This parameter, or
the -S
<script_name>
parameter, is
required.
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.
-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.
No
-v
Specifies the verbosity of the utility after parameter validation. The range is
0 to 3.
No
The default is 1.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
137
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobRM
Table 20: Parameters for TARAJobRM (continued)
Parameter
Description
Required
-F
For a TARA JobFile only. Forces removal of the JobFile even if there is a
valid image in the NetBackup image catalog.
No
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)
Notice:
Verify that X is the correct number of jobs or scripts. After the jobs or scripts are deleted, they
cannot be recovered.
Table 21 lists TARAJobRM return codes.
Table 21: TARAJobRM Return Codes
Return Code
Description
Return codes 101 - 111 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.
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 700-753 designate parameter validation errors.
138
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Table 21: TARAJobRM Return Codes (continued)
Return Code
Description
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 3.
749
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.
753
Invalid level specified for -v (0, 1, 2 or 3).
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 NetBackup Administrator Guide, Release 15.00
139
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.
TARAJobQuery parameter indicators are case sensitive, therefore use the correct case when
specifying 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
-j
-s
-P
-S
-O
-f
-l
-L
-N
-v
-O -f -l -L -N -P -v]
<jobid> - (required)
<TARA servername> - (optional)
<port>
- (optional)
<stream options> - (optional)
<object options> - (optional)
<output file name> - (optional)
<output ARC logs> - (optional)
<output NetBackup logs> - (optional)
<output NetBackup job data> - (optional)
<verbose level: 1|2|3> - (optional)
Table 22 describes TARAJobQuery parameters, and indicates if the parameter is required.
Table 22: Parameters for TARAJobQuery
Parameter
Description
Required
-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.
Yes
Example
TARAJobQuery -u administrator
-p
Specifies the password for the user name the utility uses to connect to the TARA Server.
Yes
Example
TARAJobQuery -u administrator -p xjmT94Rs
140
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Table 22: Parameters for TARAJobQuery (continued)
Parameter
Description
Required
-e <path to encoded
password file>
Specifies the path to the file that contains the encoded password to the User Name.
Yes
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 run TARAJobQuery
using the Query option (see the -j parameter).
Yes
There is no value specified with this parameter.
Example
-L
Note: If you specify -L, you cannot use the -j <jobid> parameter.
-j <jobid>
This is the Query option. This parameter enables the display of the job information
stored in a single Job Information file.
Yes
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 43c2ac5800000001
Note: If you specify -j <jobid>, you cannot use the -L parameter.
-N
Displays the NetBackup job information associated with each stream. The fields
displayed are the TARA stream number, NetBackup Job Number, NetBackup BackupID,
NetBackup policy name, the first image name, and the last image name.
No
To obtain the NetBackup job information, you must specify the TARA job name using
the -j parameter.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
141
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Table 22: Parameters for TARAJobQuery (continued)
Parameter
Description
Required
-L
When -L is specified after the -j query option, it displays each TARA stream's NetBackup
job log information.
No
To obtain the NetBackup job information, you must specify the TARA job name using
the -j parameter.
When you specify this option, the NetBackup job information is automatically displayed,
and the -f option is required.
-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,
153.64.14.142).
No
Example
-s localhost
Example
-s 153.64.14.142
This parameter is valid with the List option and the Query option.
The default is localhost.
-P <port number>
Specifies the port number that the TARA server is running on. The default port is 54323.
If the TARA Server port is changed to a different number, this option has to be specified
with the correct TARA Server port number.
No
Example
TaraJobQuery -u administrator -p xflu7k3M -j MyBackupJob -P
55555
The default is 54323.
-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:
No
• 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.
The default is cest.
142
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Table 22: Parameters for TARAJobQuery (continued)
Parameter
Description
Required
-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:
No
• 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
(Table 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.
The default is sty.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
143
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Table 22: Parameters for TARAJobQuery (continued)
Parameter
Description
Required
-f <output file name>
This parameter specifies the name to be used in creating files for the output that is
generated by TARAJobQuery.
No
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.
144
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Table 22: Parameters for TARAJobQuery (continued)
Parameter
Description
Required
-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.
No
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.
If this parameter is not specified, the ARC output that the TARA job generates will not be
stored in a user-specified 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.
No
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.
If this parameter is not specified, debug information will not display.
Code Samples
tarajobquery -u administrator -p xdmjk4Rs -L
tarajobquery -u administrator -p xdmjk4Rs -L -s localhost
tarajobquery -u administrator -p xdmjk4Rs -L -s 153.64.14.142 -f "my name"
tarajobquery -u administrator -p xdmjk4Rs -L -s remotehostname -f myname -l -v 3
tarajobquery -u administrator -p xdmjk4Rs -j 4302081100000001
tarajobquery -u administrator -p xdmjk4Rs -j 4302081100000001 -s 153.64.14.142
tarajobquery -u administrator -p xdmjk4Rs -j 4302081100000001 -s remotehostname -S cest O sty
Teradata Extension for NetBackup Administrator Guide, Release 15.00
145
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
tarajobquery -u administrator -p xdmjk4Rs -j 4302081100000001 -s 153.64.14.142 -S cest O sty -f "my name" -l
tarajobquery -u administrator -p xdmjk4Rs -j 4302081100000001 -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 '127.0.0.1'.
File Name/Job ID
Job Name
4302081100000001
43c2ac5800000001
43c2ac5800000002
43d526d500000001
43d526d500000002
Date
bkjob3-dbc_all
bkjob6-rec-ptrs
bkjob2_DB-level_2streams
bkjob6-rec-ptrs
bkjob4_table_level
2005-04-16
2006-01-09
2006-01-09
2006-01-23
2006-01-23
Stream Cnt
17:14:31
10:33:21
10:34:42
10:57:51
11:02:09
1
1
2
0
0
List of summary Job information completed.
Sample Query Option Output - Traditional View
This output is generated by entering:
tarajobquery -j 4302081100000001 -O oy
Job "bkjob3-dbc_all" - 2005-04-16 17:14:31
(ID 4302081100000001)
Operation: ARCHIVE
TDPID: JKW2K
Streams: 1
Stream
-----1
Client
Size
Time Exitcode
-------------------- ------------------- --------- -------Jkw2k
680,532,117
:00:00
0
Object
-------------------------------ARCBARPPI_CATDB1
T1_PPI
T2_PPI
t3_ppi
ARCBARPPI_CATDB2
T1_PPI
T2_PPI
146
Type
--------Database
Table
Table
Table
Database
Table
Table
Owner
-----------------------------ARCBARPPI_CATU
ARCBARPPI_CATU
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
t3_ppi
ARCBARPPI_CATU
Dbase
ARCUSER
ARPTEST
INDEXTABLE
LOBTABLE
PPITABLE
BARP_FAOCPU
BARP_FAOD
BARP_PPI_SIBT006
BARP_PPI_SIBT008
BARP_FAOU
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
COPY29CHARDBNAMEWWWXXXXXYYYYY
twentyninechartbnamexxxxyyyyy
COPY30CHARDBNAMEWWWXXXXXYYYYYZ
thirtychartbnamewwwxxxxxyyyyyz
COPYSMALLDBNAME
smalltbname
CRASHDUMPS
DBC
AccessRights
AccLogRuleTbl
Accounts
CollationTbl
Dbase
Hosts
LogonRuleTbl
Next
OldPasswords
Owners
Parents
Profiles
RCConfiguration
RCEvent
RCMedia
RepGroup
RoleGrants
Roles
SysSecDefaults
Translation
UDTCast
UDTInfo
UDTTransform
Table
Database
Table
Database
Database
Table
Table
Table
Database
Database
Table
Table
Database
Table
Table
Table
Table
Table
Table
Table
Table
Table
Database
Table
Database
Table
Database
Table
Database
Table
Database
Database
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
DBC
DBC
ARCUSER
DBC
BARP_FAOU
DBC
DBC
dbnametest
dbnametest
dbnametest
DBC
DBC
Teradata Extension for NetBackup Administrator Guide, Release 15.00
147
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
DBNAMETEST
DRXXX13
T1
SMALLDBNAME
smalltbname
SYSADMIN
FastLog
HelpSyntax
SYSLIB
SYSTEMFE
CleanupQCF
CreateQCF
opt_cost_table
Opt_DBSCtl_Table
opt_ras_table
Temp_ReconfigSpace
SYSUDTLIB
TPMP_POINT_T_04dc_C
tpmp_point_t_FromSql
tpmp_point_t_Ordering
UDTINT_04de_C
SYS_CALENDAR
CALDATES
TDPUSER
THIRTYCHARDBNAMEWWWXXXXXYYYYYZ
thirtychartbnamewwwxxxxxyyyyyz
TWENTYNINECHARDBNAMEXXXXYYYYY
twentyninechartbnamexxxxyyyyy
Database
Database
Table
Database
Table
Database
Table
Table
Database
Database
Table
Table
Table
Table
Table
Table
Database
DBC
DBC
Database
Table
Database
Database
Table
Database
Table
DBC
dbnametest
DBC
DBC
DBC
DBC
DBC
dbnametest
dbnametest
Sample Query Option Output - Hierarchical View
This output is generated by entering:
tarajobquery -j 4302081100000001 -O hoy
Job "bkjob3-dbc_all" - 2005-04-16 17:14:31
(ID 4302081100000001)
Operation: ARCHIVE
TDPID: JKW2K
Streams: 1
Stream
-----1
Client
Size
Time Exitcode
-------------------- ------------------- --------- -------Jkw2k
680,532,117
:00:00
0
Object
---------------------------------------------DBC
ARCBARPPI_CATU
ARCBARPPI_CATDB1
T1_PPI
T2_PPI
t3_ppi
ARCBARPPI_CATDB2
T1_PPI
T2_PPI
148
Type
--------Database
Database
Database
Table
Table
Table
Database
Table
Table
Owner
-----------------------------DBC
DBC
ARCBARPPI_CATU
ARCBARPPI_CATU
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
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_Table
opt_ras_table
Temp_ReconfigSpace
SYSUDTLIB
TPMP_POINT_T_04dc_C
tpmp_point_t_FromSql
tpmp_point_t_Ordering
UDTINT_04de_C
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Table
Table
Database
Database
Table
Table
Table
Database
Database
Database
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Database
Table
Database
Database
Database
Table
Database
Table
Database
Table
Database
Table
Database
Table
Database
Table
Database
Table
Database
Table
Table
Database
Database
Table
Table
Table
Table
Table
Table
Database
DBC
ARCUSER
DBC
DBC
BARP_FAOU
DBC
DBC
DBC
dbnametest
dbnametest
dbnametest
dbnametest
dbnametest
dbnametest
DBC
DBC
DBC
DBC
DBC
149
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
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
Table
Database
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
DBC
DBC
Sample Query Option Output with NetBackup Job Information
This output is generated by entering:
tarajobquery -N
The output is for the job specified by the -j parameter.
# /home/marcm/tarajobquery -P 54323 -u Administrator -p abc123de -j 4b62153600000022 -N
Port number: 54323
Job information for Job ID '4b62153600000022' using a Traditional view
Job "Test-dr138200-isis" - 2010-02-01 18:46:34
(ID 4b62153600000022)
Operation: ARCHIVE
TDPID: isis
Streams: 4
Stream
-----1
2
3
4
NetBackup Stream Information
Stream Job#
Status: Description
------ ------ ----------------------------------------------------------------1
1289 0: the requested operation was successfully completed
150
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAJobQuery
Backup ID
Policy
------------------------------ -----------------------------bsrv15_1265068244
TD_disk_bsrv15
First Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0001/F0000
Last Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0001/F0000
Stream Job#
Status: Description
------ ------ ----------------------------------------------------------------2
1288 :
Backup ID
Policy
------------------------------ -----------------------------barlnx2_1265068243
TD_disk2
First Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0002/F0000
Last Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0002/F0000
Stream Job#
Status: Description
------ ------ ----------------------------------------------------------------3
1290 0: the requested operation was successfully completed
Backup ID
Policy
------------------------------ -----------------------------bsrv15_1265068245
TD_disk2_bsrv15
First Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0003/F0000
Last Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0003/F0000
Stream Job#
Status: Description
------ ------ ----------------------------------------------------------------4
1287 :
Backup ID
Policy
------------------------------ -----------------------------barlnx2_1265068242
TD_disk4
First Image
-----------------------------------------------------------/Test-dr138200-isis_4b62153600000022_DSTREAM0004/F0000
Last Image
------------------------------------------------------------
Teradata Extension for NetBackup Administrator Guide, Release 15.00
151
Chapter 6: Teradata TARA Command-Line Utilities
TARALaunch
/Test-dr138200-isis_4b62153600000022_DSTREAM0004/F0000
Object
-------------------------------TARADB1
t1
t2
t3
TARALaunch
TARALaunch is a stand-alone, command-line utility that allows you to run a TARA script
without having to use the Teradata TARA GUI. You can also use TARALaunch as a commandline utility to send an abort request to the TARA server for an active TARA job. The launch
option and the abort option are two separate uses of the utility and cannot be used in the same
instance.
Guidelines and Parameters for Launching Scripts
The script that TARALaunch runs 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.
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: 0|1|2|3> - (optional)
-w <seconds-to-wait> - (optional)
If a seconds value is not specified, the job will wait indefinitely until the TARA job completes.
If a value is specified, this job will wait until the TARA job completes or the specified number
of seconds has elapsed.
Parameters for Aborting Jobs
TARALaunch -u -p -a [-b -s -v]
-a <jobid>
- (required)
-b
- (optional)
-u <username> - (required)
-p <password> - (required)
OR
-e <path to encoded password file> - (required)
-s <TARA servername>
- (optional)
-v <verbose level: 0|1|2|3> - (optional)
152
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARALaunch
TARALaunch Parameters
Table 23 describes TARALaunch parameters, and indicates if the parameter is required.
TARALaunch parameter indicators are case sensitive, therefore use the correct case when
specifying parameters. Each parameter can only be specified once in the command-line.
Table 23: Parameters for TARALaunch
Parameter
Description
Required
-a <jobid>
Specifies the 16-character TARA job identification name.
Yes (abort
option only)
For this parameter, use the job ID that is generated when TARALaunch has
launched a job or TARAJobQuery is used with the -L option.
-b
Specifies batch mode, which suppresses interactive messages.
No (optional for
abort option
only)
-j <jobname>
Specifies the 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.
Yes (job launch
option only)
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.
Yes
Example
TARALaunch -u administrator
Teradata Extension for NetBackup Administrator Guide, Release 15.00
153
Chapter 6: Teradata TARA Command-Line Utilities
TARALaunch
Table 23: Parameters for TARALaunch (continued)
Parameter
Description
Required
-p <password>
Specifies the password for the user name the utility uses to connect to the TARA
server.
Yes
Example
TARALaunch -u administrator -p xjmT94Rs
-e <path to encoded
password file>
Specifies the path to the file that contains the encoded password to the User
Name.
Yes
Example
TARALaunch -u administrator -e C:\Teradata\tara.pwd
Note: The file containing the encoded password is created during the postinstall 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 54323. If the TARA Server port is changed to a different number, this option
has to be specified with the correct TARA Server port number.
No
Example
TaraLaunch -u administrator -p xflu74Rs -j
MyBackupJob -P 55555
The default is 54323.
-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, 153.64.14.142).
No
The launched job will be run on the specified TARA server host.
Example
-s taraserver1
Example
-s localhost
Example
-s 153.64.14.142
The default is localhost.
154
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARALaunch
Table 23: Parameters for TARALaunch (continued)
Parameter
Description
Required
-v <verbose level:
0 |1|2|3>
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.
No
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 Table 24 on page 156 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.
The default is level 1.
-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. Table 24 documents all return codes.
No (optional for
launch option
only)
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.
TARALaunch exits after the TARA job is launched by the TARA server.
TARALaunch Return Codes
Table 24 lists TARALaunch return codes.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
155
Chapter 6: Teradata TARA Command-Line Utilities
TARALaunch
Table 24: TARALaunch Return Codes
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.
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 120 - 129 indicate that the TARA job was successfully launched with the Wait-forCompletion option, but TARALaunch could not continue monitoring the TARA job.
126
156
The seconds-to-wait time expired during the wait-for-job-completion monitoring.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARALaunch
Table 24: TARALaunch Return Codes (continued)
Code Number Description
127
Network error terminated the TARALaunch connection to the TARA server during
the wait-for-job-completion monitoring.
Return codes 200 - 209 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 fqn6t4Rs -j MyBackupJob -s localhost -v 3
taralaunch -u administrator -p fqn6t4Rs -j "My Backup Job" -s
153.64.14.142
taralaunch -u administrator -p fqn6t4Rs -j MyBackupJob
taralaunch -u administrator -p fqn6t4Rs -a 515c9deb0000001a
Output
Unless the verbosity is increased, TARALaunch displays only 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 4b033b4800000002 returned in launch
Job 'Inventory_weekly.arc' was successfully launched on TARA Server
'127.0.0.1'
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
157
Chapter 6: Teradata TARA Command-Line Utilities
TARAMigrator
TARAMigrator
The Teradata TARA GUI migration feature migrates images created under the legacy Teradata
Extension for NetBackup to a Teradata TARA Job Information file. This allows Teradata TARA
to restore data from a NetBackup image.
In addition to the Teradata TARA GUI, there is a command-line method that accomplishes
the same goal. This method consists of using the NetBackup utility, bplist, and the
TARAMigrator command-line utility.
Use the NetBackup utility, bplist, to create a file of image records that will be supplied to the
TARAMigrator utility. In the following syntax, parameters enclosed in brackets are optional:
bplist -t 26 [-k <policy_name>] [-s <start_date>] [-e <end_date>] -R /*.0000.B
bplist is piped into the find (Windows) or grep (Linux) command. The output is redirected to
a file. For example:
Windows
bplist -t 26 -k TD_pol1 -s 02/28/2007 -e 03/01/2007 -R /*.0000.B | find "0001of"
>Migrate.out
Linux
bplist -t 26 -k TD_pol1 -s 02/28/2007 -e 03/01/2007 -R /*.0000.B | grep 0001of
Migrate.out
>
The file will contain lines such as the following:
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B:\
barbera.NCR_TD.usr.syrah.barac.dat.0001of0002onbarbera.20070327053741.0002.0000.0000.B:\
barbera.NCR_TD.usr.syrah.syscal.dat.0001of0001onbarbera.20070327052222.0000.0000.0000.B:
\
Edit the file, removing the :\ (colon backslash) from the end of each line:
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B
barbera.NCR_TD.usr.syrah.barac.dat.0001of0002onbarbera.20070327053741.0002.0000.0000.B
barbera.NCR_TD.usr.syrah.syscal.dat.0001of0001onbarbera.20070327052222.0000.0000.0000.B
After the file is edited, it is ready for the TARAMigrator utility:
TARAMigrator -u -p -i [-v -P] | -f [-v -P]
-u <username to logon to TARA server> - (required)
-p <password to logon to TARA server> - (required)
OR
-e <path to encoded password file> - (required)
-i <image name>
- (required)
-f <image file name>
- (required)
-v <verbose level: 0|1|2|3>
- (optional)
-P <port>
- (optional)
Table 25 describes TARAMigrator parameters, and indicates if the parameter is required.
158
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAMigrator
Table 25: Parameters for TARAMigrator
Parameter
Description
Required
-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.
Yes
Example
TARAMigrator -u administrator
-p <password>
Specifies the password for the user name the utility uses to connect to the TARA Server
Yes
Example
TARAMigrator -u administrator -p xjmT94Rs
-e <path to encoded
password file>
Specifies the path to the file that contains the encoded password to the User Name.
Yes
Example
TARAMigrator -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. If the TARA Server port is
changed to a different number, this option has to be specified with the correct TARA
Server port number.
No
Example
TaraMigrator -u administrator -p xflu78nS -j MyBackupJob -P
55555
The default is 54323.
-i <image name>
This parameter is used if there is only one image that needs to be migrated (as opposed
to a file of image names).
Yes
Specify the -i or the -f option. Do not specify both options in the same command-line.
-f <file_name>
This parameter is the file that was created by bplist and edited as described previously.
Yes
Specify the -i or the -f option. Do not specify both options in the same command-line.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
159
Chapter 6: Teradata TARA Command-Line Utilities
TARAMigrator
Table 25: Parameters for TARAMigrator (continued)
Parameter
Description
Required
-v <verbose level:
0|1|2|3>
This parameter 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.
No
Level 0 suppresses most debug information, with the exception of some parameter
validation errors.
Level 1 is the default level if the -v option is not specified. A message is output that
indicates the success or failure of the migration operation, including a status line that
indicates how many images were migrated and how many failed. If any errors are
encountered during the migration, these will be displayed also, with associated error
messages.
Level 2 provides a low level of debug information collected during the migration process
and is typically only useful for utility developers when gathering information about a
reported problem.
Level 3 provides a higher level of debug information collected during the migration
process and 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 a lower level of debug information.
Example
-v 0
Specifying 0 results in no debug information.
If this parameter is not specified, level 1 is used.
The verbose level provides diagnostic levels of trace output. Level 0 is useful in scripts where
the possible output display of TARAMigrator might not be desired.
Sample Lines of Code
taramigrator -u administrator -p xjmT94Rs -i
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B
taramigrator -u administrator -p xjmT94Rs -v 3 -i
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B
taramigrator -f C:\MyDir\My_Image_File.txt
taramigrator -f C:\MyDir\My_Image_File.txt -v 0
160
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
taraping
Output
TARAMigrator produces messages that the migration operation was a success or failure,
including a status line indicating how many images were successfully migrated and how many
images failed.
Verify that a Job Information File was Created
To verify that a Job Information file was created for each image given to the TARAMigrator:
1
Start the Teradata TARA GUI (refer to “Start the Teradata TARA GUI” on page 78).
2
Click Teradata Tiered Archive/Restore Architecture>Task>Restore. The RESTORE object
selection dialog box appears. In the left pane of the dialog box, the name of each Job
Information File created by TARAMigrator should appear.
3
Click on the job (Job Information File) to view the job information and the list of objects
contained in that Job Information File.
The name for each Job Information file that TARAMigrator creates is taken from the
UserName value in the NetBackup image name. The UserName value is the fifth value in the
NetBackup image name, where each value is delimited by a period (.). In the next example,
UserName is barac:
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B
taraping
The taraping command line utility tests TARA server health by testing TARA server
connectibility interactively or in a script. Testing is performed externally from the TARA
clients.
The taraping parameter indicators are case sensitive, therefore use the correct case when
specifying parameters. Also, specify each parameter only once in the command-line.:
/opt/teradata/tara/nbubar/taraping [-s -p -v]
-s <TARA servername>
- (optional)
-p <port>
- (optional)
-v <verbose level: 1|2|3> - (optional)
Table 26 describes taraping parameters.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
161
Chapter 6: Teradata TARA Command-Line Utilities
taraping
Table 26: Taraping Parameters
Parameter
Description
Required
-s <TARA servername>
Specifies the TARA server host. The TARA servername value can be a
host name (for example, taraserver1 or localhost) or an IP
address of a host (for example, 153.64.14.142).
No
Example
-s localhost
Example
-s 153.64.14.142
TARA server name defaults are:
• localhost
• 127.0.0.1
-p <port>
Specifies the port number that the TARA server is running on. If the
TARA server port is changed to a different number, this option has to be
specified with the correct TARA Server port number.
No
The default is 54323.
-v <verbose level: 1|2|3>
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.
No
The verbose level default is 1, which generates no display unless the test
fails.
Table 27 describes taraping return codes.
Table 27: Taraping Return Codes
Return Code
Description
0
Successful
255 (-1)
Failed
Sample Lines of Code
# /opt/teradata/tara/nbubar/bin/taraping
Unable to connect to TARA server '127.0.0.1'.
# echo $?
255
#
# /opt/teradata/tara/nbubar/bin/taraping -p 55555
162
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
# echo $?
0
#
# /opt/teradata/tara/nbubar/bin/taraping -s bsrv20 -p 55555 -v 2
Connecting to the socket on TARA Server 'bsrv20'
Send to TARA Server.
Close connection.
Close returned 0.
Test successful.
# echo $?
0
#
TARAScriptConv
The TARAScriptConv utility allows the conversion of NetBackup ARC script files from an
existing Backup Application Software format to the TARA format. (Currently, only the
conversion of NetBackup ARC script files is supported.) TARAScriptConv is a stand-alone,
command-line utility. Only one ARC script file can be converted at a time.
After the ARC script file(s) has been converted by TARAScriptConv, it can be stored as a
stand-alone local script file or as a script file in a Script Repository (SR directory) on a TARA
server host. See the output target parameter (-r) for information on how to do this.
TARAScriptConv parameter indicators are case sensitive, therefore use the correct case when
specifying parameters. Each parameter can only be specified once in the command-line.
TARAScriptConv -t -i -r -U -W [-s -f -o -u -p -P -v]
-t <Backup Application Software script type: NB> - (required)
-i <input file name> - (required)
-r <output target: R|F|B> - (required)
-U <username to logon to TARA server> - (required)
-W <password to logon to TARA server> - (required)
OR
-E <path to encoded password file> (required)
-s <TARA servername> - (optional)
-P <port>
- (optional)
-f <script file name> - (optional)
-o <output name> - (optional)
-u <user id> - (optional)
-p <password> - (optional)
-v <verbose level: 1|2|3> - (optional)
Note: If the .bch file that is being converted has more data streams listed than were specified
by n in the DATASTREAMS field, only the number of streams that were designated by n will
be included in the converted script.
Table 28 describes TARAScriptConv parameters, and indicates if the parameter is required.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
163
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv
Parameter
Description
-t <Backup Application
Specifies the type of Backup Application Software script to
Software script type: NB> convert.
Required
Yes
Note: Currently, TARAScriptConv only supports the
conversion of NetBackup ARC scripts. The Backup
Application Software script type value is NB.
The Backup Application Software script type value is case
sensitive.
Example
-t NB
-i <input file name>
Yes
Specifies the name of the primary ARC script file to be
converted. All Backup Application Software vendors must
have a primary ARC script file. For NetBackup, the input file
name value is the name of the NetBackup batch file and
must have a .bch extension. A fully qualified input file name
value can be specified.
Example
-i mybackup.bch"
Example
-i "/mydir/My Documents/mybackup.bch"
Example
-i "/usr/mybackup.bch"
If a fully-qualified input file name is specified, the file must
exist in the specified location. If a fully-qualified input file
name is not specified, the file must exist in the current
directory.
If the input file name contains embedded spaces or special
characters, enclose the entire name in double quotes.
Example
-i "my backup.bch"
Example
-i "C:\My Documents\mybackup.bch"
164
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv (continued)
Parameter
Description
-r <output target: R|F|B> Specifies the target for the converted ARC script file. The
output target values, which are case-sensitive, are:
Required
Yes
R - repository
F - local file
B - repository and local file
Specify only one of these values at a time.
If R is specified, the converted ARC script file is stored in
the Script Repository on the specified TARA server host
with the specified name (see the -s and -o parameters).
If F is specified, the converted ARC script file is stored as a
local file on the host on which you are executing
TARAScriptConv (see -o parameter for name and location
information).
If B is specified, the converted ARC script file is stored in
the specified Script Repository and as a local file on the
executing host.
Example
-r R
Example
-r F
Example
-r B
Local file names can be fully qualified. Repository file
names cannot be qualified.
-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.
Yes
Example
TARAScriptConv -U administrator
-W <password>
Specifies the password for the user name the utility uses to
connect to the TARA Server.
Yes
Example
TARAScriptConv -U adminstrator -W xjmT9
Teradata Extension for NetBackup Administrator Guide, Release 15.00
165
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv (continued)
Parameter
Description
Required
-E <path to encoded
password file>
Specifies the path to the file that contains the encoded
password to the User Name.
Yes
Example
TARAScriptConv -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 where the converted ARC
script file will be stored if the -r R or the -r B parameter was
specified. If -r F is specified, this parameter is ignored.
No
The TARA servername value can be a host name (for
example, taraserver1 or localhost) or an IP
address of a host (for example, 153.64.14.142).
Example
-s localhost
Example
-s 153.64.14.142
The default is localhost.
-P <port>
Specifies the port number that the TARA server is running
on. The default port is 54323. If the TARA Server port is
changed to a different number, this option has to be
specified with the correct TARA Server port number.
No
Example
TaraScriptConv -U administrator -p
xflu74Rs -j MyBackupJob -P 55555
The default is 54323.
166
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv (continued)
Parameter
Description
Required
-f <script file name>
Specifies the name of a secondary ARC script file to be
converted. Not all Backup Application Software vendors
will have a secondary ARC script file. For NetBackup, the
script file name value is the name of the ARCMAIN script
file and must have an .scr extension. A fully qualified script
file name value can be specified.
Yes, for
NetBackup.
The script name must not have any spaces or any of the
following characters:
No, for
other
Backup
Application
Software
products.
<
>
~
"
*
,
?
.
\
/
Note: Scripts that are created or modified manually are not
checked to see if the name contains spaces or the characters
listed above.
Example
-f mybackup.scr
Example
-f "/mydir/My Documents/mybackup.scr"
Example
-f "/usr/mybackup.scr"
If a fully-qualified script file name is specified, the file must
exist in the specified location. If a fully-qualified script file
name is not specified, the file must exist in the current
directory.
If the script file name contains embedded spaces or special
characters other than those listed above, enclose the entire
name in double quotes.
Example
"my backup.scr"
Example
"/mydir/My Documents/mybackup.scr"
Teradata Extension for NetBackup Administrator Guide, Release 15.00
167
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv (continued)
Parameter
Description
Required
-o <output name>
Assigns the name to the converted ARC script file. The
output name value is used for the Repository file and the
Local file. A fully qualified output name value can be
specified.
No
Example
-o mybackup
Example
-o "/mydir/My Documents/mybackup"
Example
-o "/usr/mybackup"
Local file names can be fully qualified. Repository file
names cannot be qualified.
If a fully qualified output name value is specified, that name
will be used for any Local file that is created.
Repository files cannot be qualified, therefore any fully
qualified output name value must be modified before it can
be applied to the Repository file. Any path qualifier(s) will
be stripped from the name and only the file name portion
of the fully qualified output name value will be used.
Example
If the output name value is specified as:
-o “mydir/My Documents/mybackup”
then the Local file name will be:
mydir/My Documents/mybackup
and the Repository file name will be:
mybackup
If the output name value is specified as:
-o mybackup
then the Local file name will be:
mybackup
and the Repository file name will be:
mybackup
If this parameter is not specified, the name of the converted
ARC script file will be the input file name value minus the
.bch extension.
168
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv (continued)
Parameter
Description
Required
Example
If the input file name value is specified as:
-i /mydir/My Documents/mybackup.bch
then the Local file name will be:
/mydir/My Documents/mybackup
and the Repository file name will be:
mybackup
If a fully-qualified file name is specified, the Local script file
will be created in the specified location. The Repository file
will be created in the Script Repository on the specified
TARA server host.
If a fully-qualified file name is not specified, the Local script
file will be created in the current directory. The Repository
file will be created in the Script Repository on the specified
TARA server host.
The script name must not have any spaces or any of the
following characters:
<
>
"
~
*
,
?
.
\
/
Note: Scripts that are created or modified manually are not
checked to see if the name contains spaces or the characters
listed above.
If the output name value contains embedded spaces or
special characters other than those listed above, enclose the
entire name in double quotes.
Example
-o "my backup"
Example
-o "/mydir/My Documents/mybackup"
Teradata Extension for NetBackup Administrator Guide, Release 15.00
169
Chapter 6: Teradata TARA Command-Line Utilities
TARAScriptConv
Table 28: Parameters for TARAScriptConv (continued)
Parameter
Description
Required
-u <user id>
Specifies the User ID in the TARA script. This user ID, plus
the password value, is required to log on to the host that the
ARC script runs against. For example, if the ARC script
performs an archive of host A, then the user id value must
be the User ID needed to log on to host A.
No
Example
-u user1
If a user ID is not specified, TARA uses a default User ID in
the ARC script.
-p <password>
Specifies the password in the TARA script. This password,
plus the user id value, is required to log on to the host that
the ARC script runs against. For example, if the ARC script
performs an archive of host A, then the password value must
be the password needed to log on to host A.
No
Example
-p password1
If a password is not specified, TARA uses a default password
in the ARC script.
-v <verbose level: 1|2|3>
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.
No
Example
-v 3
Specifying 3 results in the highest level of debug
information.
If this parameter is not specified, debug information does
not display.
Sample Lines of Code
tarascriptconv -U administrator -W xjmT9 -t NB -i mybackup.bch -r R -s localhost -f
mybackup.scr -o mybackup -u userid1 -p pass123w -v 3
tarascriptconv -U administrator -W xjmT9 -t NB -i "/mydir/My Documents/mybackup.bch" -r F
-s 153.64.14.142 -f
"/mydir/My Documents/mybackup.scr"
tarascriptconv -U administrator -W xjmT9 -t NB -i "/mydir/My Documents/mybackup.bch" -r B
-s MyBackupHost -f
"/mydir/My Documents/mybackup.scr" -o "/mydir/My Documents/MarchBackup"
170
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARASetCfg
tarascriptconv -U administrator -W xjmT9 -t NB -i mybackup.bch -r R -f mybackup.scr
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.
TARASetCfg parameter indicators are case-sensitive, therefore use the correct case when
specifying 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)
Table 29 describes TARASetCfg parameters, and indicates if the parameter is required.
Table 29: Parameters for TARASetCfg
Parameter
Description
Required
-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.
Yes
Example
TARASetCfg -u administrator
-p <password>
Specifies the password for the user name the utility uses to
connect to the TARA Server.
Yes
Example
TARASetCfg -u administrator -p xjmT94Rs
Teradata Extension for NetBackup Administrator Guide, Release 15.00
171
Chapter 6: Teradata TARA Command-Line Utilities
TARASetCfg
Table 29: Parameters for TARASetCfg (continued)
Parameter
Description
Required
-e <path to encoded
password file>
Specifies the path to the file that contains the encoded
password to the User Name.
Yes
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.
No
The TARA servername value can be a host name (for
example, taraserver1 or localhost) or an IP
address of a host (for example, 153.64.14.142).
Example
-s taraserver1
Example
-s localhost
Example
-s 153.64.14.142
The default is localhost.
-P <port>
Specifies the port number that the TARA server is running
on. The default port is 54323. If the TARA Server port is
changed to a different number, this option has to be
specified with the correct TARA Server port number.
No
Example
TaraSetCfg -u administrator -p xflu74Rs
-j MyBackupJob -P 55555
The default is 54323.
172
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 6: Teradata TARA Command-Line Utilities
TARASetCfg
Table 29: Parameters for TARASetCfg (continued)
Parameter
Description
Required
-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
provide more extensive debug information. This
information is typically only useful for utility developers
when gathering information about a reported problem.
No
Example
-v 3 results in the highest level of debug information
The parameters can be specified in any order.
If this parameter is not specified, debug information will
not appear.
Sample Lines of Code
tarasetcfg -u administrator -p xjmT94Rs
tarasetcfg -u administrator -p xjmT94Rs -s localhost
tarasetcfg -u administrator -p xjmT94Rs -s 153.64.14.142
tarasetcfg -u administrator -p xjmT94Rs -v 1
tarasetcfg -u administrator -p xjmT94Rs -s localhost -v 2
tarasetcfg -u administrator -p xjmT94Rs -s 153.64.14.142 -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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
173
Chapter 6: Teradata TARA Command-Line Utilities
TARASetCfg
174
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 7
Reference for Teradata TARA GUI
This section provides reference information for the Teradata TARA GUI for Linux and
Windows platforms. Refer to “Teradata Tiered Archive/Restore Architecture Dialog Box” on
page 176 for information on the GUI’s main dialog box. Other dialog boxes are listed
separately.
To start the Teradata TARA GUI
1
To start the Teradata TARA GUI:
a
On Linux, type one of the following:
/opt/teradata/tara/gui/bin/taragui &
OR
cd /opt/teradata/tara/gui/bin
./taragui &
b
On Windows, do one of the following:
•
Double-click
if you installed the TARA GUI icon on your desktop.
•
Click Start>All Programs>Teradata Client>TARA GUI.
The Logon to TARA Server dialog box appears.
2
Enter the previously configured password.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
175
Chapter 7: Reference for Teradata TARA GUI
Teradata Tiered Archive/Restore Architecture Dialog Box
Teradata Tiered Archive/Restore Architecture
Dialog Box
The Teradata Tiered Archive/Restore Architecture dialog box has:
•
a menu bar, which contains the Task and Settings menus (see Figure 6 on page 177 and
Figure 7 on page 177)
•
a toolbar, which has buttons for shortcuts to commands in the Task and Settings menus
•
the job list, plus Abort, Launch, Refresh, and Options buttons at the bottom of the dialog
box
See the table below for descriptions of the Teradata Tiered Archive/Restore Architecture menu
commands and buttons.
176
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Teradata Tiered Archive/Restore Architecture Dialog Box
Figure 6: Task Menu
Figure 7: Settings Menu
Table 30: Teradata Tiered Archive/Restore Architecture Dialog Box
Menu
Command
Button
Description
Information
Archive databases and tables.
“ARCHIVE Object
Selection Dialog
Box” on page 180
Task
Archive
Opens the Log on to Teradata DBS dialog box. After you
have logged on, opens the ARCHIVE object selection dialog
box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
177
Chapter 7: Reference for Teradata TARA GUI
Teradata Tiered Archive/Restore Architecture Dialog Box
Table 30: Teradata Tiered Archive/Restore Architecture Dialog Box (continued)
Menu
Command
Button
Restore
Description
Information
Restore databases and tables.
“RESTORE Object
Selection Dialog
Box” on page 193
Opens the RESTORE object selection dialog box.
Migrate
“Migration
Convert backup images that were created by the legacy
Teradata Extension for NetBackup to a Teradata TARA Job Interface Dialog
Box” on page 186
Information file.
Opens the Migration Interface dialog box.
Job Viewer
View the jobs that have run, and export data to html table
format.
“Job History Dialog
Box” on page 184
Opens the Job History dialog box, which displays the:
• date and time of the job (in yyyy-mm-dd and hh:mm:ss
format)
• job name
• size of the job (in bytes)
• length of time the job took to run in hours, minutes,
and seconds (in hh:mm:ss format)
• job rate (in MB/sec)
Exit
None
Exit the Teradata TARA GUI.
None
Server
Configuration
Configure TARA server, clients, and NetBackup clients.
“TARA Server
Configuration
Dialog Box” on
page 205
Graphical User
Interface
Configuration
Change the connection between the Teradata TARA GUI
and the TARA server.
Settings
Opens the TARA Server Configuration dialog box.
Opens the Graphic User Interface Configuration dialog
box.
“Graphic User
Interface
Configuration
Dialog Box” on
page 183
Help
178
About
None
Displays version of TARA.
None
Help Contents
None
Displays online help.
None
Troubleshoot
None
Displays the utility that provides problem and remedy
details for any ARC or Access Module errors for TARA
jobs.
See Chapter 8.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Teradata Tiered Archive/Restore Architecture Dialog Box
Table 30: Teradata Tiered Archive/Restore Architecture Dialog Box (continued)
Menu
Command
Button
Description
Information
Abort job in progress.
None
Buttons at bottom of dialog box
None
None
Abort
Note: A job will not abort if:
• A diagnostic ARC job is in progress
• A lock on Teradata Database has not been released yet
• The job is waiting on XBSA, for example, for a tape
mount
None
None
Job list
Select any job that has been run on the TARA server.
None
None
None
Launch
Launch the job that has been selected in the job list.
None
The launched job temporarily appears in the Job/Stream
column of the Teradata Tiered Archive/Restore
Architecture dialog box.
None
None
Refresh
Refresh the information.
None
None
None
Options
Provide options to:
“Script Editor
Dialog Box” on
page 195 for
information on
editing the job
script
• Edit the job script
• Delete the job
• Rename the script file
“Rename Script
Dialog Box” on
page 192 for
information on
renaming the script
file
Note: To launch the online Help on Linux, TARA extracts the name of the browser executable
specified in help_info_file, located in the tara/gui/bin directory. If TARA fails to launch the
online Help, ensure that the correct name of the browser executable is specified in
help_info_file and the full path is provided to the browser executable.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
179
Chapter 7: Reference for Teradata TARA GUI
ARCHIVE Object Selection Dialog Box
ARCHIVE Object Selection Dialog Box
1
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Task>Archive.
2
Allow defaults in the Log on to Teradata DBS dialog box or enter other information.
3
Click Connect.
The ARCHIVE object selection dialog box appears.
Select jobs for archival. Options for this dialog box are described in Table 31.
Table 31: ARCHIVE Object Selection Dialog Box
Menu
Command
Button or Pane
Description
File
Build ARC
script
Build ARC script.
Auto
Generate
Automatically generate job scripts to archive databases.
Exit
180
Opens the Script Options dialog box, which allows parameter
specification for the ARC script.
Closes the ARCHIVE object selection dialog box and opens the Auto
Generate dialog box.
None
Close the ARCHIVE object selection dialog box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Assign Clients Dialog Box
Table 31: ARCHIVE Object Selection Dialog Box (continued)
Menu
Command
Button or Pane
Description
Edit
Unselect
All
Clear the database objects selected for archival.
View
Refresh
None
Refresh the view of the databases displayed in the ARCHIVE object
selection dialog box.
Opens the Log on to Teradata DBS dialog box again. After logging on,
the ARCHIVE object selection dialog box appears again.
Panes in Dialog Box
None
None
Left pane
The left pane of the ARCHIVE object selection dialog box contains an
expandable list of database objects that are available for archival.
To expand, click the icon by the database name. To archive a database
object, check the box next to the database object.
None
None
Right pane
The right pane of the ARCHIVE object selection dialog box contains:
• Name column - lists the names of the database objects. The
database objects that have been selected for archival appear with a
check in the checkbox.
• Size (Bytes) column - lists the size, in bytes, of the database object.
• Tables column - specifies how many tables the database object
contains.
• Others column - lists views and macros.
Assign Clients Dialog Box
Teradata Extension for NetBackup Administrator Guide, Release 15.00
181
Chapter 7: Reference for Teradata TARA GUI
Auto Generate Dialog Box
To access this dialog box, click Assign Clients in the Script Options dialog box for archive jobs.
Use this dialog box to assign a specific client (or a specific client group) to each stream. Dialog
box options are described in Table 32.
Table 32: Assign Clients Dialog Box
Option
Description
Stream
The Stream column shows the available streams in the job.
Client Group/Node
Client Group/Node lists the clients or client groups that can be assigned to
a stream.
Auto Generate Dialog Box
1
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Task>Archive.
2
Allow defaults in the Log on to Teradata DBS dialog box or enter other information.
3
Click Connect.
4
From the ARCHIVE object selection dialog box, click Auto Generate.
Use this dialog box to automatically archive only the DBC database or all databases except the
DBC database.
182
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Graphic User Interface Configuration Dialog Box
Table 33: Auto Generate Dialog Box
Option
Description
Archive DBC database only
A script is automatically generated to archive only the DBC database.
Archive all databases except
DBC database
A script is automatically generated to archive all databases except the
DBC database.
Graphic User Interface Configuration Dialog
Box
To access this dialog box, click Teradata Tiered Archive/Restore
Architecture>Settings>Graphical User Interface Configuration.
Use this dialog box to configure the TARA server on which the Teradata TARA GUI is
installed. Dialog box options are described in Table 34.
Table 34: Graphic User Interface Configuration Dialog Box
Option
Description
TARA Server
The localhost name is the default and appears when the GUI first runs.
Type another TARA server name if the server on which the Teradata TARA
GUI is installed changes.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
183
Chapter 7: Reference for Teradata TARA GUI
Job History Dialog Box
Table 34: Graphic User Interface Configuration Dialog Box (continued)
Option
Description
TARA Server Port
Number
The TARA server port number is the TCP port on which the TARA server
listens for GUI and ARC connections. The default is 54323 and appears
when the GUI first runs.
Type another port number if necessary.
Job History Dialog Box
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Task>Job Viewer.
Use this dialog box to view information on jobs that have run. Dialog box options are
described in Table 35.
Table 35: Job History Dialog Box
Menu
Command
Column
Description
Export list
to html
None
Save the job information in html table format.
File
184
The Save dialog box opens. Save the html file in any
location.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Log on to Teradata DBS Dialog Box
Table 35: Job History Dialog Box (continued)
Menu
Command
Column
Description
Close
None
Close the Job History dialog box.
Refresh
None
Refresh the information.
None
None
Date
Indicates the date and time the job ran.
None
None
Job Name
Indicates the job name.
None
None
Size (Bytes)
Indicates the size, in bytes, of the job.
None
None
Job Time
Indicates how long the job took to run.
None
None
Rate (MB/sec)
Indicates, in MB per second, the rate at which the job
ran.
View
Columns
Log on to Teradata DBS Dialog Box
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Task>Archive.
Use this dialog box to log on to Teradata Database. Dialog box options are described in
Table 36.
Table 36: Log on to Teradata DBS Dialog Box
Option
Description
TPDPID
To log on to a Teradata Database, select it from the TDPID list.
UserID
Type a user account name for the Teradata Database in the UserID box.
Password
Type the password for the user account in the Password box.
Connect
Click Connect to connect to the Teradata Database.
Cancel
Click Cancel to exit the dialog box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
185
Chapter 7: Reference for Teradata TARA GUI
Migration Interface Dialog Box
Migration Interface Dialog Box
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Task>Migrate.
Use this dialog box to convert backup images that were created by the legacy Teradata
Extension for NetBackup to a Teradata TARA Job Information file. Dialog box options are
described in Table 37.
Table 37: Migration Interface Dialog Box
Option
Description
All
Display all Teradata images available in the NetBackup image repository.
Query
Select specific images to view, based on an image-creation date range or the
NetBackup object name that the user gave the image when it was first
created.
Click Query, then enter one or both of the following:
• NetBackup object name
Type the name that the user gave the image when it was first created.
The default is all Teradata images.
• Date range that the images were created
Select the start and stop dates that the images were created.
The default for the start date is the earliest Teradata image found. The
default for the end date is the latest Teradata image found.
Select
186
Click Select to view the images that were selected with the query options.
The Migration Object Selection dialog box opens.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Migration Object Selection Dialog Box
Migration Object Selection Dialog Box
To access this dialog box, click Select in the Migration Interface dialog box.
Use this dialog box to select objects to migrate. Dialog box options are described in Table 38.
Table 38: Migration Object Selection Dialog Box
Menu
Command
Button
Description
File
Migrate
Click Migrate to migrate the selected images. A TARA Job Information file is
generated for the selected images. A completion message appears after the records
are created.
Exit
None
Click Exit to exit the dialog box without making changes.
Select All
None
Click Select All to select all objects for migration.
Unselect All
None
Click Unselect All to clear all selected objects.
Edit
Teradata Extension for NetBackup Administrator Guide, Release 15.00
187
Chapter 7: Reference for Teradata TARA GUI
Options Dialog Box for Archive Operations
Options Dialog Box for Archive Operations
To access this dialog box, right-click a database or table object in the ARCHIVE object selection
dialog box.
Use this dialog box to archive partitions. Dialog box options are described in Table 39.
Table 39: Options Dialog Box for Archive Operations
Option
Description
Full table
Archive the entire table.
This is the default.
188
All Partitions
This option is not valid for archive operations.
Selected Partitions
Archive the partitions that is specified in the Selected Partitions box.
LOG WHERE
This option is not valid for archive operations.
Error table name
This option is not valid for archive operations.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Options Dialog Box for Restore Operations - Copy Options Tab
Options Dialog Box for Restore Operations Copy Options Tab
To access this dialog box, right-click a database or table object in the RESTORE object
selection dialog box.
Use this dialog box to specify copy options during restore operations. Dialog box options are
described in Table 40.
Table 40: Options Dialog Box for Restore Operations - Copy Options
Option
Description
Rename Object
Give the object in the archive a different name than the target object.
Disable fallback on table
(NO FALLBACK)
Copy fallback tables into non-fallback tables.
Disable journaling on
table (NO JOURNAL)
Copy all tables with journaling disabled, whether journaled in the
archive or not.
Replace table creator
value (REPLACE
CREATOR)
Replace 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).
Specify different journal
table
Specify that a copied database has journaling for the specified database
and journal table.
APPLY TO list
Identify the tables in the target system where the change images apply.
If the archived table is already non-fallback, this option has no effect.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
189
Chapter 7: Reference for Teradata TARA GUI
Options Dialog Box for Restore Operations - PPI Options Tab
Options Dialog Box for Restore Operations PPI Options Tab
1
To access this dialog box, right-click a database or table object in the RESTORE object
selection dialog box.
2
Select the PPI options tab.
Use this dialog box to specify partitions to be restored. Dialog box options are described in
Table 41.
Table 41: Options Dialog Box for Restore Operations - PPI Options
Option
Description
Full table
Restore the entire table.
This is the default.
190
All Partitions
Restore all partitions.
Selected Partitions
Restore the partitions that are specified in the Selected Partitions box.
LOG WHERE
Specify rows to be logged to an error table for manual insertion and
deletion.
Error table name
Specify a table name other than the default name that is shown.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Policy Selection Dialog Box
Policy Selection Dialog Box
To access this dialog box, click Policies in the Script Options dialog box when you are building
an archive script.
Use this dialog box to assign a policy group or policy to the archive job. Dialog box options are
described in Table 42.
Table 42: Policy Selection Dialog Box
Option
Description
Use Policy Group
Use Policy Group is automatically selected and the policy group that is set
as the default in the NetBackup tab of the TARA Server Configuration dialog
box appears.
It is possible to select another policy group from the list.
Manual Policy
Selection
Select a specific policy for each stream from Manual Policy Selection. All
defined policies are listed in Manual Policy Selection, not only the policies
assigned to the default policy group.
Stream
The number of streams specified for the job are shown in the Stream
column.
Click Manual Policy Selection, then select the stream to which you want to
assign a specific policy.
Policy
After you click Manual Policy Selection, the Policy column displays the
policies that are available.
Select a policy from the list to assign to a specific policy.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
191
Chapter 7: Reference for Teradata TARA GUI
Rename Script Dialog Box
Rename Script Dialog Box
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Options>Rename.
Use this dialog box to rename a script file. Dialog box options are described in Table 43.
Table 43: Rename Script Dialog Box
192
Option
Description
Rename Script
File
In the Rename Script File box, type the new script file name.
Save
Click Save to save the new script file name.
Cancel
Click Cancel to close the Rename Script dialog box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
RESTORE Object Selection Dialog Box
RESTORE Object Selection Dialog Box
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Task>Restore.
Use this dialog box to select the jobs that you want to restore. Dialog box options are described
in Table 44.
Table 44: RESTORE Object Selection Dialog Box
Menu
Command
Button or Pane
Description
File
Build ARC script
Build ARC script.
To restore a job, select it, then click Build ARC script.
Exit
None
To exit the RESTORE object selection window, click Exit.
Edit
Unselect All
Select the checkbox next to Unselect All, or press the button, to
clear the jobs that were selected to be restored.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
193
Chapter 7: Reference for Teradata TARA GUI
Save Script Dialog Box
Table 44: RESTORE Object Selection Dialog Box (continued)
Menu
Command
Button or Pane
Update Latest Job
Ids
Description
Select to update job IDs for all job scripts before selecting Always
restore latest box in Script Options dialog box.
Note: It is best practice to update job IDs before restoring any
backup job.
View
Refresh
None
Refresh the view of the RESTORE object selection dialog box.
None
Left pane
The left pane of the RESTORE object selection dialog box
contains an expandable list of database objects that are available
for restoration.
Panes in dialog box
None
To expand, click the icon by the database name. To restore a
database object, check the box next to the database object.
None
None
Right pane
The right pane of the RESTORE object selection dialog box
contains:
• Dataset - lists the names of the database objects. The database
objects that have been selected for archival appear with a check
in the checkbox.
• Size (Bytes) column - lists the size, in bytes, of the database
object.
• Streams - the number of streams assigned to the job.
Save Script Dialog Box
To access this dialog box, click Save from the Script Editor dialog box.
194
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Script Editor Dialog Box
Use this dialog box to enter a new name for the job script. Dialog box options are described in
Table 45.
Table 45: Save Script Dialog Box
Option
Description
Script File Name
[Optional] Type a new script name in Script File Name.
Save
Click Save to accept the current script name or the new name in Script File
Name.
Cancel
Click Cancel to close the Save Script dialog box without making changes to
the script name.
Script Editor Dialog Box
To access this dialog box, click Preview in the Scripts Options dialog box.
Use this dialog box to edit a job script. Dialog box options are described in Table 46.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
195
Chapter 7: Reference for Teradata TARA GUI
Script Editor Dialog Box
Table 46: Script Editor Dialog Box
Menu
Command
Button
Description
Save
None
Click Save to save the job script.
Launch
None
Click Launch to launch the job.
Close
None
Click Close to close the Script Editor dialog box.
Cut
None
Highlight text to delete, then click Cut.
Copy
None
Highlight text to copy, then click Copy.
Paste
None
Insert the cursor at the point to paste copied text, then click
Paste.
None
None
Save
Click Save to save the job script.
None
None
Launch
Click Launch to launch the job.
None
None
Close
Click Close to close the Script Editor dialog box.
File
Edit
Additional
Buttons
196
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Archive Operations
Script Options Dialog Box for Archive
Operations
To access this dialog box, click File>Build ARC script from the ARCHIVE object selection dialog
box.
Use this dialog box to specify parameters when building an ARC script. Dialog box options are
described in Table 47.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
197
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Archive Operations
Table 47: Script Options Dialog Box for Archive Operations
Option
Description
Job Name
Entries in Job Name are case-sensitive. A job name must not contain any
spaces, or these characters:
<
>
~
"
*
,
?
.
\
/
Description
TDPID
The entry in this box reflects the TDPID with which you logged on. It is not
possible to change the TDPID.
User Name
The user name with which you logged on appears. To create another job for the
specified database, type a new user name.
Password
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.
Single stream or
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.
Multi stream
Default Group
The list defaults to all clients, which are assigned to streams in a round-robin
manner. For example, if there are six streams and four clients, the stream
assignment is:
• Client1 is assigned to Stream1
• Client2 is assigned to Stream2
• Client3 is assigned to Stream3
• Client4 is assigned to Stream4
• Client1 is assigned to Stream5
• Client2 is assigned to Stream6
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 or restore job.
Assign Clients
Each stream is defaulted to All clients. Click Assign Clients to assign a specific
client (or a specific client group) to each stream.
Configure
198
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Archive Operations
Table 47: Script Options Dialog Box for Archive Operations (continued)
Option
Description
Protegrity
Encryption
This option is no longer valid. The Crypto Key Management System (KMS)
replaces Protegrity encryption.
QueryBanding
[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;
See Teradata Archive/Recovery Utility Reference for more information on query
banding.
Online Backup
[Optional]
1 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.
2 In the drop-down list that is enabled, select Default or NoSync.
With the NoSync option, no read or access lock is placed on the database
and the tables are not synchronized. The tables do not have a shared
consistency point. Instead, each table has its own consistency point for
restore jobs. The primary purpose of NoSync is to minimize the effect of
transactions writing to the database.
See Teradata Archive/Recovery Utility Reference for more information on online
archive.
Sessions (per
stream)
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.
Extra Options
[Optional] Enter any ARCMAIN command line options that are not part of the
GUI ARC build flow.
Backup
Application
The default is NetBackup.
Full Backup or
[Optional] Select Dictionary Only from the drop-down list to archive only the
dictionary, or allow the Full Backup selection to archive the dictionary and data.
Dictionary Only
If you choose Dictionary Only, specify only one stream per job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
199
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Archive Operations
Table 47: Script Options Dialog Box for Archive Operations (continued)
Option
Description
Use Catalog
[Optional] Select Use Catalog to specify positioning data, so that when an
object is restored, NetBackup can locate it without searching the entire tape.
Verify Checksum
[Optional] Verify Checksum verifies that what it is archiving or restoring is
valid data. The checkbox is selected by default.
Force online
logging off
[Optional] To stop online logging:
1 Check the Online Backup box.
2 Check the Force online logging off box.
Normally, Teradata ARC allows online logging to continue even when a job fails
or is aborted. Log files can become so large that subsequent attempts to archive
the same database result in job failure.
Turning online logging off avoids the problem of log files becoming too large if
a job fails or is aborted.
An ONLINE LOGOFF job is created and runs immediately after the parent job
completes, except when the TARA server aborts the parent job because no
connection could be made to stream 1 within 10 minutes. The ONLINE
LOGOFF job is also aborted for connection failure after 10 minutes.
Note: The ONLINE LOGOFF job can be aborted from the GUI, regardless of
its state.
Character set
The default is UTF-8. Select another character set if appropriate.
Policies
Click to display the Policy Selection dialog box. Select a policy group or an
individual policy from the drop-down lists to use for this job.
Other Buttons
200
Save
Click Save to accept the current script.
Launch
Click Launch to launch the job.
Preview
[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.
Close
Click Close to close the Script Options dialog box.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Restore Operations
Script Options Dialog Box for Restore
Operations
To access this dialog box, click RESTORE object selection>File>Build ARC script.
Use this dialog box to specify parameters when building an ARC script. Dialog box options are
described in Table 48.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
201
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Restore Operations
Table 48: Script Options Dialog Box for Restore Operation
Option
Description
Job Name
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.
Always restore latest
[Optional] Check the Always restore latest box to automatically restore the
last image that was backed up successfully.
Description
TDPID
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.
User Name
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.
Password
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.
SingleStream or
MultiStream
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.
202
Default Group
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.
Assign Clients
Each stream defaults to All clients. Click Assign Clients to assign a specific
client to each stream.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Restore Operations
Table 48: Script Options Dialog Box for Restore Operation (continued)
Option
Description
Configure
RestoreScript
Objects are restored instead of copied.
The RestoreScript radio button is automatically selected. To copy objects,
click CopyScript.
Full or Dictionary
Only
[Optional] Select Dictionary Only from the drop-down list to restore only
the dictionary, or allow the Full Backup selection to restore the dictionary
and data.
The drop-down list is enabled only when the RestoreScript or CopyScript
radio button has been selected.
CopyScript
To copy, instead of restore an object, click CopyScript. The RestoreScript
radio button is cleared.
Analyze
When this option is selected, all the records are validated to ensure the
correct order and type of records are on the tape. The entire backup image is
analyzed, regardless of the databases that are selected for the analyze job.
QueryBanding
[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;
Teradata Extension for NetBackup Administrator Guide, Release 15.00
203
Chapter 7: Reference for Teradata TARA GUI
Script Options Dialog Box for Restore Operations
Table 48: Script Options Dialog Box for Restore Operation (continued)
Option
Description
QB Options
[Optional] Click QB Options to open the QueryBanding Options dialog box.
Selected options are added to the job script.
[Optional] Check the TVS Temperature box to enable a list with the
following selections:
• Hot
Specifies that the job is hot data, which is frequently accessed and
changed.
• Warm
Specifies that the job is warm data, which is more frequently accessed
and changed than cold data.
• Cold
Specifies that the job is cold data, which is infrequently accessed and
rarely changed.
• Auto
The temperature setting is based on the target system temperature
settings.
[Optional] Check the Block Compression box to enable a list with the
following selections:
• Yes
Block level compression is enabled. This setting overrides the setting
information saved with the archive job.
• No
Block level compression is disabled. This setting overrides the setting
information saved with the archive job.
• Auto
The block level compression setting is based on the target system block
level compression settings.
204
Sessions (per stream)
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.
Extra Options
[Optional] Enter any ARCMAIN command line options that are not part of
the GUI ARC build flow.
Use Catalog
[Optional] Select Use Catalog to specify positioning data so that when an
object is restored, NetBackup can locate it without searching the entire tape.
Verify CheckSum
[Optional] Select this check box to verify that what it is archiving or
restoring is valid data.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
Table 48: Script Options Dialog Box for Restore Operation (continued)
Option
Description
Skip Build Steps
[Optional] Select this check box to skip the build steps, which NetBackup
considers idle time. If you skip the build steps now, manually run the build
step outside of NetBackup after all data is restored.
CharacterSet
The default is ASCII. Select another character set if appropriate.
Extra Buttons
Save
Click Save to accept the script options that have been selected.
Launch
Click Launch to launch the job. The job appears in the Teradata Tiered
Archive/Restore Architecture dialog box.
Preview
[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.
Close
Click Close, but do not click Save, to close the dialog box without saving any
changes.
TARA Server Configuration Dialog Box
To access this dialog box, click Teradata Tiered Archive/Restore Architecture>Settings>Server
Configuration.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
205
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
Use this dialog box to configure TARA servers. Dialog box tabs are:
•
“TARA Server Configuration Dialog Box: Teradata Tab” on page 206
•
“TARA Server Configuration Dialog Box: Clients Tab” on page 207
•
“TARA Server Configuration Dialog Box: Client Groups Tab” on page 208
•
“TARA Server Configuration Dialog Box: ARC Options Tab” on page 210
•
“TARA Server Configuration Dialog Box: NetBackup Tab” on page 211
•
“TARA Server Configuration Dialog Box: TARA Server Port Tab” on page 212
•
“TARA Server Configuration Dialog Box: TARA Logon Setup Tab” on page 213
•
“TARA Server Configuration Dialog Box: Logging Tab” on page 213
The buttons at the bottom of the dialog box are the same on each tab.
Table 49: Buttons for TARA Server Configuration Dialog Box
Option
Description
OK
Click OK to save changes. The TARA Server Configuration dialog box closes.
Cancel
Click Cancel to close the TARA Server Configuration dialog box.
Apply
Click Apply to save changes and keep the dialog box open.
TARA Server Configuration Dialog Box: Teradata Tab
The Teradata tab is the first tab of the TARA Server Configuration dialog box.
Table 50: TARA Server Configuration Dialog Box: Teradata Tab
Option
Description
Teradata System
This list contains the display names (not the TDPID names) of the Teradata
Database systems that have been configured for this TARA server.
Display Name
This is the name that to be displayed for this TDPID within the Teradata
TARA GUI environment. Usually, the display name and the Teradata TDPID
name will be the same.
Teradata TDPID
Specifies the Teradata Database machine name. You can change this to
specify another Teradata Database machine name.
Browse User/Password
The Browse user and password is the Teradata logon information that the
TARA server uses to query the Teradata Database. The user name and
password must be a valid account within the target Teradata Database.
ARC User/Password
Specifies the ARC user name. You must have backup and restore privileges
for the ARC user name that you specify.
Type the password for the ARC user.
Default Stream Count
206
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
Table 50: TARA Server Configuration Dialog Box: Teradata Tab (continued)
Option
Description
Default Session Count
The default is four sessions per stream. 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 because some of the sessions remain idle. Refer to
Teradata Archive/Recovery Utility Reference for more detail.
New
Click New to allow entry of information for new Teradata machine.
Remove
Click Remove to remove Teradata machine from the configuration. A dialog
box asks for confirmation.
TARA Server Configuration Dialog Box: Clients Tab
Table 51: TARA Server Configuration Dialog Box: Clients Tab
Option
Description
Client System
This list contains an alphabetical list of client system names in which ARC
backups occur.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
207
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
Table 51: TARA Server Configuration Dialog Box: Clients Tab (continued)
Option
Description
Display Name
The display name is the client name that you want to appear for this client
within the Teradata TARA GUI environment. It is not necessary for the
display name to match the system name.
To change the display name, click New. The Display Name box now displays
New Client Machine. Type the new display name in the Display Name
box.
Client Machine Name
This is the system name of the client node. Any name must be a valid system
name.
Max Streams Per Job
This specifies the maximum streams per job.
New
Click New to allow entry of information for new client machine.
Remove
Click Remove to remove client machine from the configuration. A dialog
box asks for confirmation.
TARA Server Configuration Dialog Box: Client Groups Tab
Table 52: TARA Server Configuration Dialog Box: Client Groups Tab
208
Option
Description
Client Group
This alphabetical list specifies the name of a client group, a logical group of
ARC main clients.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
Table 52: TARA Server Configuration Dialog Box: Client Groups Tab (continued)
Option
Description
New
Click New to allow entry of information for new client group.
Remove
Click Remove to remove client group from the configuration. A dialog box
asks for confirmation.
Display Name
The display name is the client group name that you want to appear for this
client group within the Teradata TARA GUI environment. It is not
necessary for the display name to match the system name.
To change the display name, click New. The Display Name box now displays
New Group. Type the new display name in the Display Name box.
Selected Clients
This column lists 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.
Available Clients
This column lists the clients available for addition to a client group.
To add a client, highlight it, then click Add. The client name appears in the
Selected Clients column.
Add
Click Add to add a client to the group.
Remove
Click Remove to remove a client from the group.
Move Up
Highlight the client in the Selected Clients column, then click Move Up to
move a client up in the order in which it is used for backup. If there are
more clients than streams, the client that appears first will be used for
backup.
Move Down
Highlight the client in the Selected Clients column, then click Move Down to
move a client down in the order in which it is used for backup. If there are
more clients than streams, the client that appears first will be used for
backup.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
209
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
TARA Server Configuration Dialog Box: ARC Options Tab
Table 53: TARA Server Configuration Dialog Box: ARC Options Tab
210
Option
Description
Use Catalog
Select the checkbox to specify positioning data, so that when an object is
restored, NetBackup can locate it without searching the entire tape.
Use Checksum
Verification
Select the checkbox to verify that what it is archiving or restoring is valid
data.
Default Character Set
The default in the list is UTF-8. Select another character set if appropriate.
Extra ARC Options
Enter any ARCMAIN command-line options that are not part of the GUI
ARC build flow. Refer to Teradata Archive/Recovery Utility Reference for
details on valid ARCMAIN command-line options.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
TARA Server Configuration Dialog Box: NetBackup Tab
Table 54: TARA Server Configuration Dialog Box: NetBackup Tab
Option
Description
NetBackup Master
Server
This is the name of the machine that has NetBackup server software
installed.
Metadata Query Client The display name of the client node that is currently configured to receive
NetBackup information is shown in the Metadata Query Client list. To select
another configured client machine, select the name from the list.
Client Group
The list displays the current selected client group that was configured using
the Client Groups tab. Or, select another client group from the list and click
Refresh to refresh the list of available clients under Client Policies.
Default
Default is automatically selected. To remove the client group listed in the
Client Group list as the default, click Default.
Refresh
Refreshes the information that appears in the dialog box.
Client Policies
This column lists the policies that have been added to a policy group.
To remove a policy from the group, highlight the policy, then click Remove.
The policy name is transferred to the Available Policies column.
Available Policies
This column displays, in alphabetical order, all NetBackup-configured
policies.
To add a policy, highlight the policy, then click Add. The policy name
appears in the Client Policies column.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
211
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
Table 54: TARA Server Configuration Dialog Box: NetBackup Tab (continued)
Option
Description
Add
Click Add to add a policy to the policy group.
Remove
Click Remove to remove a policy from the policy group.
Move Up
Highlight the policy in the Client Policies column, then click Move Up to
move a policy up in the order in which it is used for a backup or restore job.
If there are more policies than streams, the policy that appears first will be
used for the backup or restore job.
Move Down
Highlight the policy in the Client Policies column, then click Move Down to
move a policy down in the order in which it is used for a backup or restore
job. If there are more policies than streams, the policy that appears first will
be used for the backup or restore job.
TARA Server Configuration Dialog Box: TARA Server Port Tab
Table 55: TARA Server Configuration Dialog Box: TARA Server Port Tab
212
Option
Description
Enter the new TARA
Server Port Number
In the field provided, enter the new TARA Server Port Number.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
TARA Server Configuration Dialog Box: TARA Logon Setup Tab
Table 56: TARA Server Configuration Dialog Box: TARA Logon Setup Tab
Option
Description
Select User Name
Select either Administrator or User.
Enter Password
Enter the password.
TARA Server Configuration Dialog Box: Logging Tab
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 64. If this is not a new
installation of Teradata TARA, there is no required order of configuration.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
213
Chapter 7: Reference for Teradata TARA GUI
TARA Server Configuration Dialog Box
To configure logging
Notice:
214
1
[Optional] Check Enable Audit Log to track TARA Server configuration changes. See
“TARA Server Audit Log” on page 218 for more information.
2
[Optional] Clear the Override Global Log Level box to change the log level. The Global Log
level is pre-set to 32, which is the minimum, or normal, log level. The maximum level is
63. Increasing the Global Log level adds verbosity to the log for each TARA server
component.
3
[Optional] Change other logging levels in the dialog box. Logging levels of the individual
components of the TARA server are pre-set and cannot be changed unless the Override
Global Log Level check box is selected.
Do not customize log settings unless Teradata Global Support recommends it.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
CHAPTER 8
Teradata TARA Troubleshooting
This chapter covers the following troubleshooting topics:
•
Troubleshoot Utility
•
TARA Support Bundle
•
TARA Server Audit Log
•
Teradata and NetBackup Debug Logs
•
Other NetBackup Logs
•
TARA Server Repositories Backup
•
Client and Server System Health
•
Backup Jobs with the Same Name
•
TARA Server Stop and Restart
•
Command Line for Obtaining Information
•
States for Archive Jobs
•
Job Stream Failure
•
Failure 8205 Error Message
•
Unresponsive TARA Server
•
Recovery to a Different TARA Server
Troubleshoot Utility
The troubleshoot utility provides problem and remedy details for any ARC or Access Module
errors for TARA jobs.
To troubleshoot a problem
1
From the Teradata Tiered Archive/Restore Architecture screen, select Help>Troubleshoot.
The Troubleshoot screen appears.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
215
Chapter 8: Teradata TARA Troubleshooting
Creating a Diagnostic Bundle for Support
2
Enter the Error Code.
3
Click Search. The description, problem, and remedy are displayed.
Note: The error code can be an ARC or TARA Access Module (BAM) error. For example,
it can be ARC0001 or BAM0001.
Creating a Diagnostic Bundle for Support
For situations such as job failure, job hanging, or other issues that require an incident report,
Teradata includes command-line, interactive scripts to collect necessary job and system
information. The resulting diagnostic bundle is sent to Teradata Customer Support so they
can provide optimum analysis and resolution. Customer support is available around-theclock, seven days a week through the Global Technical Support Center (GSC). To learn more,
go to http://www.tays.teradata.com.
1
Locate the script at /opt/teradata/tara/support/bin.
2
Run supportbundle.sh to create a diagnostic bundle on the TARA server.
Result: After the script collects the data, a bundle named tarasupportbundle_$DATE.zip is
created in /var/opt/teradata/SupportBundle and submitted to Teradata Customer Support.
3
216
[Optional] Contact Teradata Customer Support to let them know the diagnostic bundle is
ready for review.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
TARA Support Bundle
TARA Support Bundle
The TARA Support Bundle gathers log files and server information for Teradata Global
Support Center (GSC) troubleshooting purposes. The TARA Support Bundle script produces
a .zip output file, which Teradata GSC personnel manually runs. Alternately, GSC instructs the
customer to run the script, then forward the .zip output file to the GSC. The script gathers
local information that is specific to each server. If there are multiple Teradata Managed Servers
for BAR in the environment, GSC can request a .zip file from each server.
Script, Log, and .zip File Names and Location
Table 57: Script, Log, and .zip File Names and Location
File Type
Location
Description
Executable script
/opt/teradata/tara/support/bin/supportbundle.sh
Script that GSC runs to gather log files and server
information.
Log file
/opt/teradata/tara/support/bin/logfile
Log file that results when the executable script is run.
Support bundle
.zip file
/var/opt/teradata/tara/
supportbundle_MM_DD_YYYY.zip
Support bundle .zip file that results when the
executable script is run.
An example of the file name is
supportbundle_04_02_2013.zip
Support Bundle Information
The following table lists TARA Support Bundle information, including log files, software
package version numbers, and hardware information.
Table 58: Support Bundle Information
Destination
Source
/var/opt/teradata/tara/supportbundle/config
/var/opt/teradata/tara/server/config
/var/opt/teradata/tara/supportbundle/baruser
/home/baruser
Contains the last 7 days of all files, including modified .out files.
/var/opt/teradata/tara/supportbundle/coredump
Core dump files from /var/opt/teradata/core-name
Only taraserver core dump files are included.
/var/opt/teradata/tara/supportbundle/jir
/var/opt/teradata/tara/server/jir
Contains files modified within the last 7 days.
/var/opt/teradata/tara/supportbundle/sr
/var/opt/teradata/tara/server/sr
/var/opt/teradata/tara/supportbundle/logs
• /etc/opt/teradata/tara/defaults
• /var/log/messages output file
• /var/opt/teradata/tara/server/logs/logfile output file
Teradata Extension for NetBackup Administrator Guide, Release 15.00
217
Chapter 8: Teradata TARA Troubleshooting
TARA Server Audit Log
Table 58: Support Bundle Information (continued)
Destination
Source
/var/opt/teradata/tara/supportbundle/os
• ifconfig output file
The ifconfig file is the output file for server IP addresses.
•
•
•
•
•
/var/opt/teradata/tara/supportbundle/versions
netstat 54323 port status output file
lspci output file
QLogic port status and HBA information output file
isscsi output file
/etc/hosts file output
• /opt/teradata/tara/gui/bin/config (TARA version installed)
• /usr/openv/netbackup/bin/version (NetBackup version
installed)
• /etc/SuSE-release (SLES version installed)
• TTU installed packages and versions of:
• bteq
• cliv2
• piom
• sqlpp
• tdicu
• teradata_arc
• TeraGSS
TARA Server Audit Log
The TARA Server audit log tracks the following TARA Server configuration changes:
•
Job file deletion
•
Job script creation
•
Job script deletion
•
TARA job launch
The following information is recorded for the tracked events:
•
Date and time of the event
•
Details of the event
•
IP address of the workstation initiating the event
The audit log is located at /var/opt/teradata/tara/server/logs/auditlog.
To enable the audit log, check the audit log box in the Logging tab of the Teradata Tiered
Archive/Restore Architecture>Settings>Server Configuration dialog box.
218
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
TARA Server and TARA Client Log Files
TARA Server and TARA Client Log Files
The TARA server log file location and name is /var/opt/teradata/tara/server/logs/logfile for
Linux and <INSTALL_PATH>\Teradata\TARA\server\logs\logfile for Windows.
Each TARA client has its own log file. The name of the file is TaraDLogFile_<server>.txt and
the location is the BAR user home directory of each TARA client.
When the TARA server is restarted, the existing logfile is renamed to logfile.prev before
opening a new logfile. When a TARA client is restarted, the existing logfile is renamed
TaraDLogFile_<server>.txt before opening a new TaraDLogFile_<server>.txt .
Teradata and NetBackup Debug Logs
The NetBackup Administration Console and Backup, Archive, and Restore interface offer a
comprehensive set of debug logs for troubleshooting problems that occur on the NetBackup
server. See the NetBackup Troubleshooting Guide at http://seer.entsupport.symantec.com/docs/
290230.htm for more information on NetBackup debug logs.
For detailed troubleshooting information, create the folders or directories listed in Table 59 on
each BAR server.
Table 59: Log Folders and Directories
Operating
System
Folder or Directory
Format for Log Name Special Instructions
Windows • install_path\NetBackup\logs\bphdb\
• install_path\NetBackup\logs\dbclient\
MMDDYY.log
Allow public access to the folders.
Linux
log.MMDDYY
None
• cd /usr/openv/netbackup/logs
• mkdir -m 777 bphdb
• mkdir -m 777 dbclient
Note: Unless specified by Teradata Global Support, trace logging above level 32 is not
necessary.
Other NetBackup Logs
In addition to debug logs, NetBackup provides a set of logs that are useful in isolating
problems. One such log is All Logs Entries on the master server. See the NetBackup System
Administrator’s Guide at http://seer.entsupport.symantec.com/docs/ for a description of this
and other logs.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
219
Chapter 8: Teradata TARA Troubleshooting
TARA Server Repositories Backup
TARA Server Repositories Backup
Backing up TARA server repositories reduces downtime in recovery of the TARA server if the
server fails. Use NetBackup to back up the following TARA server repositories to a BAR server:
•
/home/baruser
•
/home/teradata
•
/var/opt/teradata/tara/server - versions prior to TARA 14.0
•
/etc/opt/teradata/tara/ - TARA 14.0 and later versions
Client and Server System Health
A heartbeat is sent between the TARA server and TARA clients to monitor the system health of
each component, then system health information is logged in the server and client logs.
Client Heartbeat
The TARA server records receipt of the client heartbeat in /var/opt/teradata/tara/server/logs/
logfile when the ARC Server log level is set to 62 or greater.
The first line in the following example is always displayed in the log. When the log level is set
to 48 or greater, the second line is recorded and is contiguous to the first line.
2012/02/13 07:58:58.313 (19400:-2072160928) <32> main: Received request from
host=[153.64.106.109] port=[52543]
2012/02/13 07:58:58.313 (19400:1076898112) <02> RunRecvThread:Connection request valid
type = 4001
The TARA client sends a heartbeat to the TARA server once a minute. The time interval
cannot be changed.
Server Heartbeat
Heartbeats are not logged in the TARA client log file unless the TARA server does not respond
to the client heartbeat. If the TARA server does not respond:
1
The TARA client logs the following two lines in /home/baruser/TaraDLogFile.txt, regardless
of the log-level setting.
2012/02/14 07:14:50.716 (18250:733088512) <32>
from taraserver
2012/02/14 07:14:55.716 (18250:733088512) <32>
lost, TCS must restart
TaraService: Error -2, receiving command
TaraService: Connection to taraserver
2
The TARA client terminates.
3
The TARA client is restarted automatically:
•
For Linux, the automatic restart occurs within five minutes.
•
For Windows, the automatic restart occurs in one minute.
Note: The taraping command-line utility can also be used to monitor TARA server health
220
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Backup Jobs with the Same Name
Backup Jobs with the Same Name
Do not run two backup jobs with the same name at the same time. Job results can be
unpredictable.
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 on Linux
1
Type:
/etc/init.d/tdtaraserver stop
Wait 60 seconds. If you attempt to start the tdtaraserver script immediately after stopping
the service, the operation might fail.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
221
Chapter 8: Teradata TARA Troubleshooting
Command Line for Obtaining Information
2
Type:
/etc/init.d/tdtaraserver start
To restart the TARA server on Windows
1
Right-click the My Computer icon on the desktop and select Manage.
2
Select Services from the Services and Applications heading.
3
Select the TaraServer name in the list.
4
Select the Restart the service option to the left.
Command Line for Obtaining 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 -u administrator -p <password> -L
The output is similar to the following:
File Name/Job ID
469d370300000001
469d42ff00000001
469d42ff00000002
Job Name
frank
frank
frank
Date
2007-07-17 14:47:47
2007-07-17 15:33:36
2007-07-17 15:49:06
Stream Cnt
1
1
1
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 Table 60:
Table 60: 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 NetBackup.
222
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Job Stream Failure
Table 60: States for Archive Jobs (continued)
State
Step in Job Launch
Description
Archive
4
After the media is made available by NetBackup, 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 Failure
Symptom
The job stream fails: in the TARA GUI, the job stream is shown trying to connect for some
time before it fails (see Table 60 on page 222 for job states). 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. Go to “Step 4: Examine
Directory Permissions” on page 225.
•
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”.
Step 2: Examine the Script that Launches Teradata ARC
The script that launches Teradata ARC is called runarcnb.bat and is located in /home/baruser.
The baruser account must be the owner of this file or Teradata ARC will not launch.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
223
Chapter 8: Teradata TARA Troubleshooting
Job Stream Failure
To examine the script
1
Verify that the runarcnb.bat file has the proper permissions and owners assigned to it:
-rwxr-xr-x
2
1 baruser root 2274 Jul 17 15:26 runarcnb.bat
Determine if runarcnb.bat can properly locate the ARCMAIN binary.
The runarcnb.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/runarcnb.bat script and replace the INSTALLPATH
variable with a hard-coded path to ARCMAIN: /opt/teradata/arc/bin/.
If the script is valid and has the proper permissions, go to “Step 3: Test SSH Connectivity.”
Step 3: Test SSH Connectivity
In the SUSE Linux environment, Teradata TARA relies on SSH (Secure Shell) communication.
The test of that communication process involves the taraserver account and its
communication through SSH to the baruser account of a specified media server. Therefore,
permissions for /opt/teradata/tara are significant. If this directory does not have execute
permissions, Teradata ARC cannot access the IOMODULE file that is located at /opt/teradata/
tara/nbubar/lib/libnbubar.so.
To test SSH connectivity
1
Set the permissions for the /opt/teradata/tara directory to drwxr-xr-x. If the permissions
are incorrect, the Teradata TARA GUI does not show any Teradata ARC output because
the Teradata ARC stream has not connected to the ARC server. The job remains in the
Connecting phase, then finally fails.
The error shown in the Teradata ARC output file in /home/baruser is:
"Failure ARC0805:Access Module returned error code 3: Requested Access
Module not found"
2
The test then executes the pwd command. If a password is requested, SSH authentication
is not configured properly. A successful test executes the pwd command without
requesting authentication.
In the following example, the name of the TARA server (BAR media server) is lussdgscbar00:
lussdgsc-bar00:~ # su - taraserver
224
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Job Stream Failure
taraserver@lussdgsc-bar00:~> ssh -o StrictHostKeyChecking=no
baruser@lussdgsc-bar00 pwd
A successful test returns the password results, that is, authentication is not requested. The
results in the example are successful: /home/baruser is returned.
3
The nbubar postscript is responsible for setting the proper SSH permissions on the
taraserver and baruser accounts. When installing Teradata TARA, running a postscript
after installing each package (such as nbubar and taraserver) is required. It is possible this
script was not run or did not complete properly.
Table 61 gives information on the postscripts for nbubar and taraserver.
Table 61: Information on nbubar and taraserver Postscripts
Teradata
TARA
Component Postscript Name and Location
nbubar
Description
/opt/teradata/tara/nbubar/bin/nbubar_postinstall.sh
on each media server
This postscript creates the proper SSH
authentication between the TARA server and the
media server. The postscript also creates, or
recreates, runarcnb.bat and nbuquery.bat.
IMPORTANT: Before running this script, ensure
that you have backed up runarcnb.bat if there have
been any edits or changes. Otherwise, the script will
be replaced.
taraserver
/opt/teradata/tara/server/bin/taraserver_postinstall.sh
on the TARA server
This postscript defines the name of the TARA
server.
If SSH is functioning properly, go to “Step 4: Examine Directory Permissions.”
Step 4: Examine Directory Permissions
•
A common output error from Teradata ARC in this situation is:
Failure ARC0805: Access Module not found
•
Other directories that should be investigated are:
•
/home/baruser/.ssh (each media server)
The following is an example of a valid /home/baruser/.ssh/authorized_keys path/
filename, with .ssh included in the path:
barlnx1:/home
drwxr-xr-x 3
barlnx1:/home
drwxr-xr-x 2
barlnx1:/home
-rw-r--r-- 1
•
# ls -ld baruser
baruser root 16032 Apr 26 07:20 baruser
# ls -ld baruser/.ssh
baruser root 80 Oct 6 2006 .ssh
# ls -l baruser/.ssh/authorized_keys
baruser root 892 Apr 26 07:29 authorized_keys
/home/taraserver/.ssh (only TARA server)
Teradata Extension for NetBackup Administrator Guide, Release 15.00
225
Chapter 8: Teradata TARA Troubleshooting
Failure 8205 Error Message
The following is an example of a valid /home/tara/.ssh/ path/filename:
lussdgsc-bar00:/home # ls -ld
drwxr-xr-x 3 taraserver root
lussdgsc-bar00:/home # ls -ld
drwxr-xr-x 2 taraserver root
taraserver
4096 Jul 17 10:00 taraserver
taraserver/.ssh
4096 Jul 19 12:31 taraserver/.ssh
Step 5: Verify that Encryption Specifications Match
Client-Side Encryption for NetBackup 6.5.2 and Later
Use client-side encryption (encryption that takes place on the client machine) only with
NetBackup 6.5.2 and later. With earlier versions of NetBackup, a backup job fails if client
properties are set to “Encryption required” but the policy is created without encryption
enabled. In this situation, NetBackup terminates the job and issues a status code of 6 in the
status column of the job's entry in Activity Monitor - NetBackup Administration Console.
To see the specific reason the job failed (because status code 6 can occur in other situations)
view the dbclient log in:
•
Windows
<Install_Path>\Veritas\NetBackup\logs\dbclient
•
Linux
/usr/openv/netbackup/logs
The log will contain the line “Encryption not requested by server, but required by client” if the
scenario described above was the reason for the job failure.
Earlier Versions of NetBackup
Do not use client-side encryption with versions of NetBackup earlier than 6.5.2. To verify that
client-side encryption is not used:
•
Set the Client Properties, Encryption option to “Not Allowed”.
In the NetBackup Administration Console, click
Host Properties>Client>client_name>Properties>Encryption.
•
Verify that the policy does not have the Encryption option specified.
Failure 8205 Error Message
*** Failure 8205:LSN not found in the HUT controls segment.
The Failure 8205 message appears in the master stream (stream 1) ARC log because one or
more child streams incurred a Teradata Database control error that aborted the ARC sessions.
The ARC process of the master stream is notified by Teradata Database before the child stream
can notify the master stream through the TARA server.
When this error occurs on stream 1, view the child streams to find the actual cause of the
problem. For those child streams that did not incur the error, "Job aborted due to
226
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Unresponsive TARA Server
error on stream x" appears in their ARC logs. Go to stream x ARC log to view the cause
of the error.
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 -u administrator -p <password> -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 75.
Another area to investigate is looking at the core files. See “Step 1: Add ulimit”.
Step 1: Add ulimit
If the TARA server is unresponsive, add ulimit -c 131072 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 131072
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
total 1690
drwx------ 2 taraserver root
176 Aug 28 11:24
drwxr-xr-x 7 root
root
168 Aug 9 15:13
-rw------- 1 taraserver users 13176832 Aug 28 11:01
-rwxr-xr-x 1 taraserver root
901 Aug 13 14:57
-rwxr-xr-x 1 root
root
430 Aug 10 15:16
-l
.
..
core.8849
defaults
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.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
227
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different 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.
Recovery to a Different TARA Server
To migrate a TARA archive from one NetBackup master server to another requires importing
the image to NetBackup’s media database. TARA must recognize the images and generate a
restore script from the archived objects.
Import Images to NetBackup
The first step in recovery to a different TARA server is importing images to NetBackup, which
consists of the following procedures:
•
(Prerequisite) Remove Media from NBU Database
•
Add Tape Archives to New NetBackup Master Server
•
Import Phase I
•
Import Phase II
Remove Media from NBU Database
Verify that the volume (barcode) is not already part of the media database on the new
NetBackup server. If the volume is part of the media database, remove the media:
228
1
In the NetBackup Administration Console, select Media. In the media list, select the media
ID to remove.
2
Right-click on the media ID and select Eject Volumes from Robot.
3
Click Eject.
4
Click No at the “Remove ejected media from the media access port. Do you wish to
continue with the eject?” prompt.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
5
Click No.
6
Run bpexpdate to remove the save sets. For example:
bpexpdate –m BR5001 –d 0
7
Delete the volumes from the media list.
Add Tape Archives to New NetBackup Master Server
Run Inventory Robot to add the tape archives to the new NetBackup Master Server:
1
In the NetBackup Administration Console, right-click Devices.
2
Select Update volume configuration.
3
Verify that the empty media port prior to update option is selected if the tape is in the access
port. (The access port is also called a cap door, entry port, or exit port.)
Import Phase I
Use the NetBackup Administration Console for this procedure.
1
Select Catalog.
2
Click Actions>Initiate import.
Note: Do not select the drop-down list of Verify, Duplicate, and Import.
3
Select the correct media server and set Image type as Tape.
4
Specify the Media ID, for example BR5001. Assign all tapes written to a stream to the same
media server.
5
From the Activity Monitor, verify initiation status.
Import Phase II
Use the NetBackup Administration Console for this procedure.
1
Select Catalog.
2
Under the Actions drop-down list, select Import.
3
Set the media ID to the imported tape and the correct date range.
4
Click on Search Now. Backups from the original NBU Master server are listed.
5
Highlight the backup you want, right-click and select Import.
6
From the Activity Monitor, verify import status.
Data from the archive on each tape is read. The NetBackup image files are placed in the
db\images directory and available for use.
7
Run bplist to verify that the images were imported:
bplist –t 26 –C <client> -R /
Run an Analyze Job
Running an Analyze job enables the TARA application to recognize the backup job. A restore
job is created and the archived objects are listed in the restore window of the new TARA server.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
229
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
To run an Analyze job
1
Record the IOPARM and the ARCHIVE FILEDEF information from the original backup.
For example:
IOPARM = SERVER=barlnx1 POLICY=TD_pol1 CLIENT=barlnx1
DK_gcperf_syscal_archive_478fdb1500000004_DSTREAM0001
2
Using the TARA GUI, create a generic backup job.
3
In the job script:
a
Specify the number of job streams. The example sets MULTISTREAM to 1.
b
Create a STREAM line for each stream of the original backup. Indicate the server on
which the stream will run. In the following example, the stream runs on bsrv3.
c
Using the stream image name from the stream ARC log, create a STREAMNAME line
following the STREAM line.
If there are multiple streams, specify all STREAMNAME lines after the STREAM lines. For
example:
STREAM 1
STREAM 2
STREAM 3
STREAMNAME 1
STREAMNAME 2
STREAMNAME 3
d
Change the script type from Archive to Analyze.
e
Replace the archive script with ANALYZE ALL, VALIDATE, DISPLAY LONG.
JOB DK_analyze_to_create_restore_2
SESSIONS 12
MULTISTREAM 1
STREAM bsrv3
STREAMNAME DK_gcperf_syscal_archive_478fdb1500000004_DSTREAM0001
COMMANDLINE CSNAME=ASCII CHECKSUM=2
TDPID gcperf
USERID dbc
OTB NetBackup
NBUPOLICY TD_b3_pol1
SCRIPT Analyze
LOGON $LOGON;
ANALYZE ALL, VALIDATE, DISPLAY LONG,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT
4
In /home/baruser/runarcnb.bat, verify that the server is the new NetBackup master and the
client is the original NetBackup client (media server) that created the image. Edit if
necessary.
Comments at the top of the following runarcnb.bat file examples specify SERVER as the
current NetBackup Master and CLIENT as the original client.
230
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
Windows
@echo off
Setlocal
rem For analyze only- overriding client. Comment out for normal use
set ARCENVX=IOPARM='SERVER=bsrv3 CLIENT=barlnx1'
Linux
#!/bin/bash
# For analyze only- overriding client. Comment out for normal use
export ARCENVX=IOPARM='SERVER=bsrv3 CLIENT=barlnx1'
# For a restore job, disable the MEDIA_MOUNT_TIMEOUT and
#
MULTI_HOST_TIMEOUT until arcmain completes
ADMINDIR="/usr/openv/netbackup/bin/admincmd"
BPCONF="${ADMINDIR}/bpconfig"
BPREREAD="${ADMINDIR}/bprdreq"
Alternative Method for Moving Image and Media
The following procedure is an alternative for moving the image and media to a destination
media server. This process might be easier than using the script and ARCENVX variable when
many streams are involved.
1
Identify all the backups to be moved in TARA and NetBackup.
2
Identify all media associated with each backup or stream.
3
Decide which destination media servers will be used for the restore operation and where
each stream should run if the job is a multistream job.
4
Find all of the TARA jir files for the backups by looking at the file timestamps and
comparing them with the backup times.
5
Use robocopy (Windows) or rsync (Linux) to copy the jir files to the new TARA server.
Note: The file timestamps must not change when copying the files. If the new TARA server
does not reflect the backup times correctly, the ability of the new TARA server to perform
restores is affected.
6
If a different NetBackup master is used for the restore, import the media using the media
server you intend to use for that stream in your analyze job. Select that media server when
you import from the NetBackup Administration Console. If your backup has more than
one stream, select the media server for each of the import operations. If the import
operation defaults to ANY media server, you cannot map each stream's (imported) image
to the appropriate STREAM and STREAMNAME combination.
7
Use bpmedia -movedb to move the images to the desired destination media servers. Run a
command for each media involved:
bpmedia -movedb -m <media_barcode> -newserver <dest_media-svr> oldserver <orig_media-svr> -v
8
Launch the TARA GUI and browse for backups available to restore. Build and edit the job
script as appropriate.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
231
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
TARA Restore and Copy Procedure
After the Analyze job completes, the image appears in the restore window of the new TARA
server. The image uses the Analyze job name.
To restore:
1
Create the restore script. For example:
JOB DK_Copy_syscal_mm_barrm
SESSIONS 8
MULTISTREAM 1
STREAM bsrv3
COMMANDLINE CSNAME=ASCII CHECKSUM=2
TDPID gcperf
USERID dbc
SOURCEUID 47d994c600000001
SCRIPT Restore
LOGON $LOGON;
COPY DATA TABLES
(mm_barrm.CALDATES) (FROM (SYS_CALENDAR.CALDATES)),
RELEASE LOCK,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT
2
After the restore or copy job completes, comment out the addition to the runarcnb.bat file.
Otherwise, the IOPARM specified in the script might override your archives.
Multi-Stream Archives and Restores
There are other considerations when dealing with multi-stream archives and restores.
•
Place each STREAMNAME line after all listed STREAMs.
•
Verify that the assigned clients and policies are correct for each stream.
•
Specify the correct SERVER for each stream in runarcnb.bat. This value will be the same on
each media server running the restore or copy. However, the CLIENT must specify the
correct client where the backup image was launched. Problems might arise when running
multiple streams on the same media server that came from different clients. This will
require modification to runarcnb.bat, depending on which stream was launched from the
alternate client.
[Optional] Run each analyze and restore stream separately from the multi-stream archive.
However, do not restore each stream with the build command until the last stream is restored.
Mark the Skip Build Steps setting in the TARA script options, then run a separate BUILD
statement after each stream has been completed.
Two NetBackup Media Servers to One NetBackup Master/Media Server
In the following example, the source domain has one NetBackup master on bsrv3 and two
NetBackup media servers on bsrv3 and bsrv4. The destination domain has one NetBackup
master on barlnx1 and one media server on barlnx1. Although the destination domain is
smaller than the source domain, the destination domain has the same number of tape drives
and therefore can handle the same number of streams as the source domain.
232
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
To launch two streams
The following procedure launches two streams, each from a different media server, to a single
media server in parallel.
1
Create the backup.
2
Use NetBackup to import images from all tapes used in the archive.
3
Modify runarcnb.bat to specify the two streams:
Runarcnb.bat Linux Example
This example specifies the correct client for the stream used in the archive.
# For analyze only- overriding client. Comment out for normal use.
# We may have 2 streams that originate from two different
# TARA clients.
grep DSTREAM0001 $1.dflt >/dev/null 2>&1
if [ "$?" = "0"]; then
export ARCENVX="IOPARM='SERVER=barlnx1 CLIENT=bsrv3'"
else
export ARCENVX="IOPARM='SERVER=barlnx1 CLIENT=bsrv4'"
fi
4
Create and run an Analyze script with multi-stream capabilities. For more details, see
“Run an Analyze Job” on page 229. For example:
JOB DK_anlz_bsrv3_2str
SESSIONS 1
MULTISTREAM 2
STREAM barlnx1
STREAM barlnx1
STREAMNAME
DK_Archive_gcperf_syscal_multistream_47e16ef40000000c_DSTREAM0001
STREAMNAME
DK_Archive_gcperf_syscal_multistream_47e16ef40000000c_DSTREAM0002
COMMANDLINE CSNAME=ASCII CHECKSUM=2 VB3
TDPID gcperf
USERID dbc
OTB NetBackup
NBUPOLICY TD_pol1
NBUPOLICY TD_pol2
SCRIPT Analyze
LOGON $LOGON;
ANALYZE ALL, VALIDATE, DISPLAY LONG,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT
5
Run the restore or copy script. For example:
JOB DK_copy_syscal_2str
SESSIONS 4
MULTISTREAM 2
STREAM barlnx1
STREAM barlnx1
COMMANDLINE CSNAME=ASCII CHECKSUM=2
TDPID gcperf
USERID dbc
Teradata Extension for NetBackup Administrator Guide, Release 15.00
233
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
SOURCEUID 47e04fea00000017
SCRIPT Restore
LOGON $LOGON;
COPY DATA TABLES
(mm_barrm.CALDATES) (FROM (SYS_CALENDAR.CALDATES)),
RELEASE LOCK,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT
Do not modify runarcnb.bat.
Restore Streams Serially
The following example restores serially from two NetBackup media servers to one NetBackup
master/media server.
1
Create the backup.
2
Use NetBackup to import images from all tapes used in the archive.
3
Edit runarcnb.bat to point to the correct client for each stream.
Windows Example
For a stream archived on bsrv3:
export ARCENVX="IOPARM='SERVER=barlnx1 CLIENT=bsrv3'"
For a stream archived on bsrv4:
export ARCENVX="IOPARM='SERVER=barlnx1 CLIENT=bsrv4'"
4
Create a restore job for each single stream, checking the Skip Build Steps option in the
TARA GUI Script Editor. If Skip Build Steps is not checked from the first stream, the
restore job will include a BUILD statement at the end.
5
After each stream has completed, run a BUILD statement to build the objects in the
restore job.
Multi-Stream Archive from One NetBackup Master/Media Server to Two
NetBackup Media Servers
In the following example, barlnx1 is the source server. The destination master server is bsrv3
and the destination media server is bsrv4.
1
Create the backup.
2
Use NetBackup to import images from all tapes used in the archive.
3
Modify the runarcnb.bat file on both media servers to specify the streams coming from the
media server. For example:
# For analyze only- overriding client. Comment out for normal use
export ARCENVX="IOPARM='SERVER=bsrv3 CLIENT= barlnx1'"
4
Run an Analyze script. For example:
JOB DK_anlz_barlnx1_2str
SESSIONS 1
MULTISTREAM 2
STREAM bsrv3
STREAM bsrv4
STREAMNAME
DK_Archive_gcperf_syscal_multistream_47e04fea00000001_DSTREAM0001
234
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
STREAMNAME
DK_Archive_gcperf_syscal_multistream_47e04fea00000001_DSTREAM0002
COMMANDLINE CSNAME=ASCII CHECKSUM=2 VB3
TDPID gcperf
USERID dbc
OTB NetBackup
NBUPOLICY TD_b3_pol1
NBUPOLICY TD_b4_pol2
SCRIPT Analyze
LOGON $LOGON;
ANALYZE ALL, VALIDATE, DISPLAY LONG,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT
5
Create and run the restore script. For example:
JOB DK_Copy_multistream
SESSIONS 8
MULTISTREAM 2
STREAM bsrv3
STREAM bsrv4
COMMANDLINE CSNAME=ASCII CHECKSUM=2 VB3
TDPID gcperf
USERID dbc
SOURCEUID 47e16ef400000014
SCRIPT Restore
LOGON $LOGON;
COPY DATA TABLES
(mm_barrm.CALDATES) (FROM (SYS_CALENDAR.CALDATES)),
RELEASE LOCK,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT
Troubleshooting Errors After the Import Procedures
Symptom: Received ARC0805 and BAM1007 Errors
02/28/2008 09:26:57
ARCHIVE MAPPED TO
DK3_gcperf_archive_syscal_barlnx1_478fdb1500000006_DSTREAM0
001.
02/28/2008 09:26:58 *** Failure ARC0805:Access Module returned error
code 34:
Error BAM1007: No backup file(s) found with
NameSpace=Teradata,
Path=DK3_gcperf_archive_syscal_barlnx1_478fdb1500000006_DST
REAM0001, Segment=F????, Generation=0.
02/28/2008 09:26:58 LOGGED OFF
2 SESSIONS
02/28/2008 09:26:58 ARCMAIN TERMINATED WITH SEVERITY 12
Solution
1
To verify that the images were imported from the tape that contains the archive job, type:
bplist –t 26 –C <client> -R /
2
Make sure the addition to runarcnb.bat has the correct addition to the script.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
235
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
Symptom: Save Set did not Appear in Restore List
After running the Analyze job successfully, the save set did not appear in the restore list.
Solution
Verify that the script says SCRIPT Analyze, not SCRIPT Archive.
Symptom: Received ARC0805 and BAM1300 Errors
03/17/2008 07:29:58
code 34:
*** Failure ARC0805:Access Module returned error
Error BAM1300: 135:Server Status:
client is not
validated
03/17/2008 07:29:58
03/17/2008 07:29:58
to perform the requested operation .
LOGGED OFF
2 SESSIONS
ARCMAIN TERMINATED WITH SEVERITY 12
Solution
There could be a problem with clients not being allowed to perform redirected restores. Here
is an example of the problem reflected in the dbclient log:
11:01:27.898 [3873] <4> VxBSAInit: VERITAS NetBackup XBSA Interface - 5.0GA 2006101718
11:01:27.904 [3873] <2> logconnections: BPRD CONNECT FROM 153.64.106.124.36350 TO
153.64.106.124.13720
11:01:27.910 [3873] <4> NBUBAR:OpenSession: SessionActive set to true
11:01:28.640 [3873] <4> VxBSABeginTxn: INF - entering VxBSABeginTxn.
11:01:28.640 [3873] <4> VxBSAQueryObject: INF - entering QueryObject.
11:01:28.640 [3873] <4> dbc_GetServerClientConfig: ServerName: <barlnx1>, ClientName:
<barlnx1>
11:01:28.640 [3873] <8> VxBSAQueryObject: WARNING - NBBSA_CLIENT_HOST name= <bsrv3>
differs from NBU config name= <barlnx1>
11:01:28.646 [3873] <2> logconnections: BPRD CONNECT FROM 153.64.106.124.36354 TO
153.64.106.124.13720
11:01:28.652 [3873] <2> get_string: read 0 of 15 bytes from socket
11:01:28.652 [3873] <2> get_string: (8) network read() error: Connection reset by peer
(104)
11:01:28.652 [3873] <16> dbc_get_string: Read of file list info failed
11:01:28.652 [3873] <16> VxBSAQueryObject: ERR - dbc_get_string() failed 23
11:01:28.652 [3873] <16> NBUBAR:QueryObject: BSAQueryObject error 23, Server Status:
socket read failed
11:01:28.706 [3873] <4> VxBSAEndTxn: INF - entering VxBSAEndTxn.
11:01:28.706 [3873] <4> VxBSAEndTxn: INF - Transaction being ABORTED.
11:01:28.706 [3873] <4> VxBSATerminate: INF - entering VxBSATerminate.
Here is an example of the problem reflected in the bprd log:
11:01:28.651 [3875] <2> get_type_of_client_free_browse: db_getCLIENT_by_hostname()
failed: no entity was found (227)
11:01:28.652 [3875] <2> db_valid_client: no alternate names to check in /usr/openv/
netbackup/db/altnames - No such file or directory (2)
11:01:28.652 [3875] <2> db_valid_client: client_name=bsrv3
peername=barlnx1.PioneersTD.Teradata.com
11:01:28.652 [3875] <2> db_valid_client: barlnx1.PioneersTD.Teradata.com is not a valid
client
11:01:28.652 [3875] <2> process_request: client bsrv3 peername
barlnx1.PioneersTD.Teradata.com is invalid for list request
To resolve the issue with the altnames, create a /netbackup/db/altnames/No.Restrictions file.
236
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
Symptom: Received ARC0805 and BAM1300 Errors
03/18/2008
03/18/2008
03/18/2008
03/18/2008
03/18/2008
10:53:04
10:53:04
10:53:04
10:53:04
10:53:04
03/18/2008 10:53:04
03/18/2008 10:53:04
03/18/2008 10:53:04
STATEMENT COMPLETED
ANALYZE ALL, VALIDATE, DISPLAY LONG,
FILE=ARCHIVE;
ARCHIVE MAPPED TO
DK_Archive_single_gcperf_SysCal_47d9b47f00000003_DSTREAM000
1.
*** Failure ARC0805:Access Module returned error code 34:
Error BAM1300: 23:Server Status: socket read failed .
LOGGED OFF
2 SESSIONS
ARCMAIN TERMINATED WITH SEVERITY 12
Solution
Check the bprd log file from the master server for:
•
HOSTS_NOT_FOUND entries
•
Invalid server
Create an altnames directory and the No.Restrictions file. This allows the Analyze job to bypass
this error.
Symptom: A Stream from the Restore Job Hangs on Tape Mounts
Here is an example of NetBackup Activity Monitor output when this error occurs:
3/20/2008 3:18:17 PM - media BR5002 required
3/20/2008 3:18:20 PM - restoring image barlnx1_1205947236
3/20/2008 3:18:25 PM - requesting resource BR5002
3/20/2008 3:18:25 PM - awaiting resource BR5002
Reason: Drives are in use., Media Server: bsrv3,
Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
3/20/2008 3:18:35 PM - connected
Solution
The issue is related to the NetBackup scheduler attempting to use a drive that is already in use.
As a workaround, see the next section on deadlock situations.
Symptom: Deadlock Situation
During a multi-stream restore, the child stream running on one of the non-master media
servers might default to using another drive. In the following example, media server bsrv4
should have mounted tape BR5002 and used drive b4-lto3-d1. However, the NBU scheduler
used drive b3-lto3-d1 and media server bsrv3, which was busy with a tape already mounted
from another stream. This resulted in a deadlock situation.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
237
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
3/21/2008 7:28:34 AM - 1 images required
3/21/2008 7:28:34 AM - media BR5002 required
3/21/2008 7:28:37 AM - restoring image barlnx1_1205947236
3/21/2008 7:28:42 AM - requesting resource BR5002
3/21/2008 7:28:43 AM - awaiting resource BR5002
Reason: Drives are in use., Media Server: bsrv3,
Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
3/21/2008 7:28:52 AM - connected
Workaround
Modify the tape and drive type
1
In NetBackup Administration Console>Media and Device Management>Devices>Drives,
double-click the drive and change the drive type.
2
Select Media. In the media list, select the media ID to remove.
3
Right-click on the media ID and select Eject Volumes from Robot.
4
Click Eject.
5
Click No at the “Remove ejected media from the media access port. Do you wish to
continue with the eject?” prompt.
6
Click No.
7
Run bpexpdate to remove the save sets. For example:
ìbpexpdate –m BR5001 –d 0
8
Delete the volumes from the media list.
9
Right-click Devices.
10 Select Update volume configuration.
11 Verify that the empty media port prior to update option is selected if the tape is in the access
port. (The access port is also called a cap door, entry port, or exit port.)
12 Under Advanced Options, change the media type from DEFAULT to match the drive type.
Reimport the backup images to the server:
1
Click NetBackup Administration Console>Catalog.
2
Click Actions>Initiate import.
3
Select the media server and set Image type as Tape.
4
Specify the Media ID, for example BR5001.
5
From the Activity Monitor, verify initiation status.
This procedure places the Netbackup images into:
netbackup\db\images\<server name>\<timestamp>\tmp
238
6
Click NetBackup Administration Console>Catalog>Action. Select Import from the list.
7
Set the media ID to the imported tape and the correct date range.
8
Click Search Now.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
Backups from the other master server are listed.
9
Highlight the backup you want, right-click and select Import.
10 Use the Activity Monitor to verify import status.
Note: Netbackup image files are placed in db\images and available for use.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
239
Chapter 8: Teradata TARA Troubleshooting
Recovery to a Different TARA Server
240
Teradata Extension for NetBackup Administrator Guide, Release 15.00
APPENDIX A
Error Messages
This appendix contains TARA error messages.
TARA Error Messages
BAM0011
Access module called by <program_name> when expecting arcmain
Explanation:
The Access Module is being called by some other program than ARCMAIN.
For whom:
End User/Field Engineer
Notes:
The access module can only be used for Teradata Backup and restore.
Remedy:
Correct software configuration issue and re-run job. Refer to your release
letter documentation or contact Global Support to determine the compatible
software versions to use for your environment.
BAM0018
Expected Data Connector Version <xx> but actually got <yy>
Explanation:
The Data Connector software version is incompatible with the Access Module
software.
For whom:
End User/Field Engineer
Notes:
The Data Connector software corresponds to the libpm.dll component on
Windows and libpm.so component on a UNIX system. You might be loading
the wrong shared component because of a path installation issue.
Remedy:
Correct software configuration issue and re-run job. Refer to your release
letter documentation or contact Global Support to determine the compatible
software versions to use for your environment.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
241
Appendix A: Error Messages
TARA Error Messages
BAM0020
Syntax error <IOParm_string>
Explanation:
The IOPARM string or some command contains a syntax error.
For whom:
End User
Notes:
This error message can result from a number of causes all related to the userentered command syntax. Refer to the relevant access module documentation
for proper syntax diagrams.
Remedy:
Correct the indicated problem and resubmit job.
BAM0024
Unsupported function code <xx>
Explanation:
The access module is incompatible with the calling program.
For whom:
End User/Field Engineer
Notes:
The access module can only be used for Teradata Backup and restore. This
error suggests that you are using a version of ARCMAIN software that is not
compatible with the access module software level.
Remedy:
Correct software configuration issue and rerun job. Refer to your release letter
documentation or contact Global Support to determine the compatible
software versions to use for your environment.
BAM0033
NBUBAR Access Module currently does not support the <xx> file attribute
Explanation:
The access module is incompatible with the calling program.
For whom:
End User/Field Engineer
Notes:
The access module can only be used for Teradata Backup and restore. This
error suggests that you are using a version of ARCMAIN software that is not
compatible with the access-module software level.
Remedy:
Correct software configuration issue and rerun job. Refer to your release letter
documentation or contact Global Support to determine the compatible
software versions to use for your environment.
BAM0013
Invalid open mode <xx> requested
242
Explanation:
The access module was requested to open a file in an invalid mode.
For whom:
Field Engineer
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Appendix A: Error Messages
TARA Error Messages
Notes:
This might be indicative of a software version incompatibility between the
access module and the Data Connector component but more likely it is
related to some type of software corruption.
Remedy:
Contact Global Support to determine the root cause of this issue.
BAM1000
Internal error <error_code>
Explanation:
An internal software error was detected.
For whom:
Field Engineer
Notes:
This error code can be given for a large number of reasons and indicates a
severe unexpected condition. Supporting text describing the exact nature of
the error should be printed out.
Remedy:
Contact a field engineer or Global Support.
BAM1001
Internal error <error_code>
Explanation:
An internal software error was detected.
For whom:
Field Engineer
Notes:
This error code is more severe than the one above because it would only
happen if the core error reporting routines are corrupted. Other error
conditions may be hidden behind this one.
Remedy:
Contact a field engineer or Global Support.
BAM1003
Access Module currently does not support restarts in WRITE mode
Explanation:
The access module currently does not support restart processing when the
backup file is opened in WRITE mode.
For whom:
End User
Notes:
All data written to the storage manager up to this point should now be rolled
back and deleted.
Remedy:
At the current time, there is nothing the user can do other than resubmit the
job from the beginning of the current ARCMAIN step. If the user prefers to
**NOT** resubmit the job at this time, they will probably want to issue a
RELEASE LOCK statement on the Teradata server to remove any database
locks set.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
243
Appendix A: Error Messages
TARA Error Messages
BAM1004
IOPARM SegSize field must be integer between 1 and <max_size>
Explanation:
User specified an illegal value for target file segment size in IOPARM
SEGSIZE field.
For whom:
End User
Notes:
The access module stores the Teradata backup in a series of file segments
approximately two gigabytes in size. The SEGSIZE field on the IOPARM
parameter to ARCMAIN defines an alternative number of gigabytes to use.
Negative numbers, decimals, or fractional numbers are not allowed.
Remedy:
Correct the IOPARM SEGSIZE field and resubmit job.
BAM1005
Access module cannot open more than one file at the same time
Explanation:
User specified more FILE= clauses on the ARCMAIN backup statement than
are currently supported by the access module.
For whom:
End User
Notes:
None.
Remedy:
Correct the ARCMAIN statement and resubmit job.
BAM1006
Access Module detected multiple backups for NameSpace=<TDname>,
Path=<image_basename>, Segment=<segment_no>
244
Explanation:
The storage manager qualified multiple backups for the indicated Namespace,
Pathname, and Segmentname pattern. This is an error because both backup
and restore need to work with only one high-level name per ARCMAIN
statement.
For whom:
End User
Notes:
The most likely reason for this error is that the Namespace or Pathname fields
contain a wild-card character that qualifies multiple backup files from the
storage manager catalog. You can test this by using the native API query tool
to see which backup file names come back. Make sure you are logged on as the
same userid to the storage server. It is OK for the low-level segment name to
have wildcard characters because the access module reserves those names for
its own purposes. Users need only worry about the Namespace and
Pathname.
Remedy:
Correct the indicated name to remove wildcard characters and resubmit the
job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Appendix A: Error Messages
TARA Error Messages
BAM1007
No backup file(s) found with NameSpace=<TDname>, Path=<image_basename>,
Segment=<segment_no>, Generation=0
Explanation:
No backup file corresponding to the indicated Namespace, Pathname,
Segment name pattern, and Backup File Generation number was found.
For whom:
End User
Notes:
The Namespace field is either entered as an IOPARM field or defaults to
"Teradata".
The Pathname is set by one of the following methods:
• DataSetName field on the IOPARM string
• "External name" of the FILEDEF parameter
• Value assigned on the "FILE=" clause of the ARCMAIN restore statement
The Segment name is only controlled by the Access Module, but it 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, -2, etc., count backwards from the current
"active" backup (gen=0).
Remedy:
Correct the indicated name and resubmit the restore job.
BAM1008
Duplicate storage objects found with NameSpace=<TDname>, Path=<image_basename>,
Segment=<segment_no>, Generation=0
Explanation:
The access module found two different storage objects with the same name/
backup generation but with different object identifiers.
For whom:
End User/Field Engineer
Notes:
The access module 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. Finding two objects with the same name/
generation could mean one of the following:
• Someone made a copy of an existing ARCMAIN backup or corrupted the
Object Info field to have two backups with the same "generation" number.
• The storage catalog is corrupted or the access module has a bug.
Remedy:
Verify the heritage of the pertinent storage objects and if necessary, delete
"bad" objects. You want to ensure that no backups are creating new objects as
you update the metadata. If all else fails, contact your Field Engineer or
Global Support to help you with this situation.
BAM1009
Access Module currently does not support repositioning when writing to backup files
Teradata Extension for NetBackup Administrator Guide, Release 15.00
245
Appendix A: Error Messages
TARA Error Messages
Explanation:
The access module currently does not support restart processing when the
backup file is opened in WRITE mode. This is because it is not possible to
reposition to the exact point of failure inside the storage manager.
For whom:
End User
Notes:
All data written to the storage manager up to this point should be rolled back
and deleted as a result of this error.
Remedy:
At the current time, there is nothing the user can do other than to resubmit
the job from the beginning of the current ARCMAIN step. If the user prefers
to **NOT** resubmit the job at this time, they will probably want to issue a
RELEASE LOCK statement on the Teradata server to remove any database
locks set.
BAM1011
SetPos file segment number <segment_no> not found in retrieved list of backup segments
Explanation:
A request was made to re-position the file within the backup set. The access
module could not find the desired file segment number. Either the position
information is corrupted or there is a mis-match between the backup set
being requested and the position information.
For whom:
Field Engineer
Notes:
None.
Remedy:
Contact a field engineer or Global Support.
BAM1012
NBUBAR <function_name> error <error_no>: <description>
246
Explanation:
The access module detected an unexpected error when invoking a function of
the vendor storage manager product. The vendor product, API function that
was called, error code, and error message text should indicate the nature of
the error.
For whom:
End User
Notes:
The clarity of the error message and it's ultimate cause may or may not be
easy to determine. The access module SHOULD be coded properly to the
particular vendor's API but in some instances one has to understand BOTH
how the storage manager works and how ARCMAIN and the access module
are designed.
Remedy:
Refer to support documentation of the indicated storage manager and correct
the job or configuration settings. If you need to execute the access module
with a particular option that is not explicitly recognized on the IOPARM of
the ARCMAIN job, you will need to configure the storage manager runtime
environment to have this as a default configuration option. f, for whatever
reason, you choose NOT to run this job again, do not forget to release any
database locks and perform any necessary cleanup on the Teradata server.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Appendix A: Error Messages
TARA Error Messages
BAM1014
Invalid Segment name for NameSpace=<TDname>, Pathname=<image_basename>,
Segment=<segment_no>, CopyId=<xx>. Skipping.
Explanation:
When querying the vendor's storage catalog metadata, the access module
picked up a storage object that qualified on the name pattern but which does
not follow the proper naming convention. This is not a fatal error message but
the relevant object is skipped from processing.
For whom:
End User/Field Engineer
Notes:
The convention used by the access module is to store the segment sequence
number as part of the file segment name. For example, F0014 would
correspond to the 15th file segment of a single ARCMAIN backup file (file
segment numbering starts at zero). The precise cause of this error is that the
access module is unable to parse the segment name properly.
Remedy:
If the segment name is getting picked up because the NameSpace and
PathName you are using is too close to the name chosen for some other
storage process, then just pick a different name. If the skipped object really
was created by a Teradata backup operation then this error suggests a software
bug. Report the situation to your local Field Engineer or Global Support.
BAM1015
Unable to open diagnostic file <filename> because <reason>. Logging disabled.
Explanation:
Diagnostic logging was requested but the access module was unable to open
the indicated file. This is a non-fatal error but no diagnostic logging will be
captured.
For whom:
End User/Field Engineer
Notes:
The access module opens the indicated file in write-append mode. Therefore,
you will want to periodically delete or purge this file if you expect to run the
same job over and over again. Also, two different jobs logging to the same file
at the same time will interfere with each other.
Remedy:
Correct the indicated problem and resubmit the job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
247
Appendix A: Error Messages
TARA Error Messages
BAM1016
IOPARM BufSize field must be integer between <xx> and <yy>.
Explanation:
User specified an illegal value for BUFSIZE field of the IOPARM initialization
string.
For whom:
End User
Notes:
This field indicates the memory buffer size in kilobytes for I/O data transfers
to storage. The entered value must be an integer in the indicated range but the
effective upper bound may be different depending upon available memory
and storage vendor. Increasing the buffer size may not always result in
improved performance.
Remedy:
Correct the IOPARM BUFSIZE field and resubmit job.
BAM1017
Unable to open DEFAULT file <filename> because <reason>.
Explanation:
The access module was unable to open the command line DEFAULT file. The
cause of the file open error is indicated.
For whom:
End User/Backup Storage Administrator
Notes:
The DEFAULT file is specified via the BARAM_DEFAULT.
Remedy:
Specify a valid path to a DEFAULT file that is accessible to your userid and
then resubmit.
BAM1018
Access module is aborting the backup transaction.
248
Explanation:
The access module was called to close the backup file in an error condition.
The write transaction will be aborted and all storage objects created by this
job will be rolled back.
For whom:
End User/Backup Storage Administrator
Notes:
This is an informational message to the user and not the root cause error
condition. ARCMAIN should indicate the cause of the error or that the
backup process has been interrupted. If it is unclear why the backup was
aborted, refer the output listing to the Global Support Center.
Remedy:
Correct the root cause of the error and resubmit the job.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Appendix A: Error Messages
TARA Error Messages
BAM1019
Access module is aborting due to insufficient memory
Explanation:
While allocating resources the access module has run out of memory.
For whom:
End User/Backup Storage Administrator
Notes:
There are a number of conditions that can cause insufficient memory. There
could be a lack of memory or swap space.
Remedy:
Correct the root cause of the error and resubmit the job.
BAM1300
<NetBackup_error_number>: <Error_description>
Explanation:
An unrecoverable error was returned to NBUBAR by the NetBackup client
interface.
For whom:
End User/Backup Storage Administrator
Notes:
The error may have occurred in the NetBackup master or in the media server.
If this is the case, troubleshooting means examining the NetBackup logs. In
this case, if the cause is not obvious from the error description and you are
unfamiliar with using the NetBackup logs, contact the Teradata
GlobalSupport center.
Remedy:
Start with the dbclient log and backtrace the error to the NetBackup process
where the error originated. Most errors will need the assistance of the
Teradata Global Support center. The following is a list of the error numbers,
their origin and a brief description what they mean:
## Origin
Description
-- ---------- -------------------------03 NBU Server ABORT NBU Server ERROR
04 NBU Server AUTHENTICATION FAILURE
05 XBSA
INVALID CALL SEQUENCE
06 XBSA
INVALID HANDLE
13 NBU Server FEATURE NOT LICENSED
11 XBSA
INVALID VOTE
17 NBU Server NO MATCH
21 XBSA
Teradata Extension for NetBackup Administrator Guide, Release 15.00
INVALID PARAMETER
249
Appendix A: Error Messages
TARA Error Messages
26 NBU Server OBJECT NOT FOUND
32 XBSA
TRANSACTION ABORTED
52 XBSA
INVALID DATABLOCK
75 NBU Server VERSION NOT SUPPORTED
77 NBU Server ACCESS FAILURE
250
78 XBSA
BUFFER TOO SMALL
79 XBSA
INVALID COPYID
80 XBSA
INVALID ENVIRONMENT
81 XBSA
INVALID OBJECTDESCRIPTOR
83 XBSA
INVALID QUERYDESCRIPTOR
85 XBSA
NULL ARGUMENT
Teradata Extension for NetBackup Administrator Guide, Release 15.00
APPENDIX B
Methods to Obtain NetVault Capabilities
in NetBackup
This is directed toward customers who are transitioning from NetVault to NetBackup.
NetVault Features
The following is a list and description of selected NetVault features that can be achieved by the
use of scripting with NetBackup options and utilities. However, it is recommended that you
reassess your previous NetVault backup strategy to determine if it is more efficient to adjust to
the NetBackup options instead of trying to emulate a few NetVault capabilities.
For more information about the NetBackup features and options used, please refer to the
Symantec NetBackup™ Administrator's Guide, volumes 1 and 2. For more information about
the NetBackup utilities used, please refer to the Symantec NetBackup™ Commands Reference
Guide.
Table 62: NetVault Features
NetVault Feature
NetBackup Counterpart
Comments
Discard after X Full Backups
None
Create scripts that use the Retention,
Keyword features and the bpexpdate
command
Ensure backup is the first on the media
Volume pool and bpmedia command
usage
Create scripts or manage pool via
NetBackup Console
Protect media from further writes after
backup
bpmedia command usage
Create scripts or manage media via
NetBackup Console
Discard after “X” Full Backups
NetBackup retention is set up on a time or date basis, meaning that you specify a number of
days, a period of time, or exact days that the dataset image is active. The dataset images have
no awareness of how many copies are in retention.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
251
Appendix B: Methods to Obtain NetVault Capabilities in NetBackup
NetVault Features
While it is strongly recommended that your backup strategy be designed or revised to use the
calendar or time-interval retention provided by NetBackup, it is possible to implement a
generation-based retention schema using scripts that perform the following:
•
Set all retentions on desired generation-capable images to Infinite. This will allow any time
span to be possible between generations. Set the retention to Infinite within the
NetBackup policies used for the TARA streams.
•
Use the Keyword feature in the policies to group the images together for a complete
generation. An incrementing value can be used such as "G1…G2…G3" and so on. The
higher the number, the more recent the generation.
•
Implement scripting to manage images by the Keyword. The script will list images by using
the bpimage command and build a condensed generation list using the Keyword value.
For example, the desired generation number is 4 and after today's successful backup, the
current generation list is G5, G6, G7, G8, and G9. The images with the Keyword value of
G5 are then expired by the bpexpdate command in your script.
Ensure Backup is First on the Media
NetBackup uses an image-stacking methodology in order to save tapes. There is no explicit
option to request a backup to be the first one on that tape, but it can be accomplished in this
way. Tape pooling allows backups to be isolated into a unique tape pool by any number of
criteria. By defining a transient tape pool that contains only new or recently-erased tapes, the
duplication/vaulting copies will be the first image on those tapes.
Protect Media from Further Writes after Backup
This feature is normally used separately from Ensure backup is first on the media. However, if
these two procedures are used together, the result is a tape that contains only the one image.
Use the SUSPEND feature in NetBackup media management. Suspending a tape will not allow
any further images to be placed on that tape. The SUSPEND feature is available in the Media
section of the NetBackup Console and also as an option of the bpmedia utility.
252
Teradata Extension for NetBackup Administrator Guide, Release 15.00
APPENDIX C
TVI Events
The Linux TARA server logs syslog events in /var/log/messages. Server Management generates
alerts that can be viewed in SMWeb Alert Viewer.
The Teradata Vital Infrastructure (TVI) escalates some alerts to Teradata, creating
INCIDENTS with Teradata Services. In the TARA domain, TVI escalates the alert with
messageID 12. Other alerts for the TARA domain are not escalated by TVI.
Note: TVI logging is not supported on the Windows TARA server.
TVI logging is enabled by default.
TVI Messages
TVI messages for the Teradata Extension for NetBackup are listed below by message ID
number. Message 12 is automatically reported to Teradata.
12
TARA-SignalHandler
Explanation:
The TARA server crashed due to an access violation, causing the TARA server
service to stop. If there is an existing job running, the job will fail. No TARA
jobs can be run until the service is started.
Severity:
Critical
Probable
Cause:
Recent activity in TARA or the launched job caused the TARA server to crash.
Remedy:
Contact the Global Support Center. Provide the stack that is stored as a text
file in the TARA server's logs directory and the TARA server logfile in the
TARA server's logs directory.
Teradata Extension for NetBackup Administrator Guide, Release 15.00
253
Appendix C: TVI Events
21
21
TARA-ServerService-Down
Explanation:
TARA server service was stopped. No TARA jobs can be run.
Severity:
Critical
Probable
Cause:
The TARA service can be stopped manually or during a shut down or reboot.
The TARA server service should start automatically on reboot. If the TARA
server crashed or hit a segmentation fault, the TARA server service will go
down. This is generally accompanied by a TARA-SignalHandler alert.
Remedy:
Check to see why the TARA server service went down. In the event of a
segmentation fault, the stack is stored as a text file in the TARA server's logs
directory.
22
TARA-ServerService-Up
Explanation:
The TARA server service was started. You can run TARA jobs.
Severity:
Information only
Probable
Cause:
The TARA server service was started.
Remedy:
N/A
23
TARA-Config-Change
254
Explanation:
A user has updated the TARA server configuration. The updated information
should be reflected in the defaults file.
Severity:
Information only
Probable
Cause:
The user updated the configuration.
Remedy:
N/A
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Appendix C: TVI Events
24
24
TARA-Job-Warning
Explanation:
The TARA job completed with a warning return status from ARCMAIN. This
might require the TARA user's attention.
Severity:
Warning
Probable
Cause:
ARCMAIN completed the job but had problems that were not severe enough
for the job to fail completely.
Remedy:
Refer to TARA logs for details. For more details, set the VB3 ARCMAIN
parameter.
25
TARA-Job-Fail
Explanation:
The TARA job failed to complete. There might be a direct ARC error or other
ARC dependant software errors, including DBS, CLI, TARA access module, or
third-party application errors.
Severity:
Critical
Probable
Cause:
ARCMAIN encountered a severe problem and failed to complete the job.
Remedy:
Refer to TARA logs for details. For more details, set the VB3 ARCMAIN
parameter.
26
TARA-Job-Abort
Explanation:
The TARA job was aborted. The job did not complete.
Severity:
Information only
Probable
Cause:
The user might have aborted the TARA job.
Remedy:
N/A
Teradata Extension for NetBackup Administrator Guide, Release 15.00
255
Appendix C: TVI Events
27
27
TARA-JIRSync
Explanation:
A request from the TARA GUI or the command line utility was sent to the
TARA server to synchronize the TARA repository with the NetBackup catalog.
Severity:
Information only
Probable
Cause:
The user ran a Synchronize on a dataset from the Restore Object Selection or
used a TARA command line utility.
Remedy:
N/A
28
TARA-JIRDelete
256
Explanation:
A request from the TARA GUI or the command line utility was sent to the
TARAserver to delete a specific job information file in the TARA repository.
Severity:
Information only
Probable
Cause:
The user ran a Delete on a specific job information file from the Restore
Object Selection or used a TARA command line utility.
Remedy:
N/A
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Index
Symbols
.out files 223
A
Activity Monitor 63
administrator
responsibilities 24
system 3
Application Backup schedule 58
configuring 58
ARC output files 223
archive
job states 222
NetBackup definition 21
Teradata definition 21
ARCHIVE object selection dialog box 80, 177, 180
Assign Clients dialog box 181
attributes 56
audit log 218
Auto Generate feature 85
automatic backup 24, 27
B
backup 26
automatic 27
criteria 23, 55
schedules 55
baruser account 224
block compression
selecting 98, 204
bplist command 133
C
capabilities of Teradata Extension for NetBackup 3, 26
character set 84, 99, 200, 205
client defined 22
client heartbeat 220
command line utility
TARAJobQuery 139
TARAMigrator 158
TARAScriptConv 163
TARASetCfg 171
communication methods 33
configuration changes
TARA server audit log 218
Teradata Extension for NetBackup Administrator Guide, Release 15.00
configure
ARC options 69
client
groups 68
systems 66
Teradata Database system 65
using NetBackup Administration Console 53
core files 227
creating schedules 57
D
debug logs overview 219
delete job 179
dialog box
ARCHIVE object selection 80, 177, 180
Assign Clients 182
Job History 184
Log on to Teradata DBS 177, 185, 188, 191
Migration Interface 186, 187
Options 189, 190
Policy Selection 191
Rename Script 192
RESTORE object selection 94, 125, 161, 192, 193
Save Script 194
Script Editor 195
Script Options
for archive operations 81, 197
for restore operations 201
dictionary data 127
directory permissions 225
documentation 21
E
edit script file 179
error messages 241
export job data in HTML format 122
F
failure 8205 message 226
G
Graphic User Interface Configuration dialog box 75
GUI, Teradata TARA 78
257
Index
H
O
HTML format, exporting job data in 122
online archive 83, 199
online logging
stop 84, 200
overview
NetBackup 21
Symantec Teradata Extension for NetBackup 3
Teradata Extension for NetBackup 26
I
installation 29
J
job
delete 179
history 122
performance 69, 84, 99
Job History dialog box 178, 184
job IDs 108
K
keywords 114
L
launch times, using the command line to obtain 222
log level 220
Log on to Teradata DBS dialog box 177, 185
logfile 227
logs 219
M
manual backup 62
master server
defined 23
domain defined 23
maximum jobs per client 54
Media Manager 21
configuration 54
media server, defined 23
migrate dictionary data 127
Migration Interface dialog box 125, 186
Migration Object Selection dialog box 126, 187
N
nbubar postscript 225
NetBackup
Administration Console
configuring with 53
set maximum jobs per client 54
client software 21
master server 21, 26
policy 23, 55
server software 21
terminology 22
NoSync option 83, 199
258
P
permissions
directory 225
for Windows environment 31
policies
adding 55
adding clients to 62
attributes 57
configuring 55, 200
defined 23
positioning data 69, 84, 99, 200, 204
product version numbers 4
Q
query banding 83, 98, 199, 203
query banding options 98, 204
R
Remote Administration Console
defined 23
host 54
Rename Script dialog box 192
rename script file 179
report all log entries 219
restore
database object 94
latest backup image 96, 202
multi-stream 64
operations 26
userids 64
RESTORE object selection dialog box 94, 125, 161, 193
retention period 60
runarcnb.bat file 223
running backup jobs
with the same name 221
S
Save Script dialog box 194
schedules
adding 57
application backup 57
automatic backup 27
Teradata Extension for NetBackup Administrator Guide, Release 15.00
Index
types of 57
Script Editor dialog box 195
Script Options dialog box
for archive operations 195, 197
for restore operations 201
scripts
editing 84, 99, 200, 205
names, using the command line to obtain 222
Secure Shell (SSH) communication 224
server, NetBackup
All Logs Entries report 219
remote operations 27
sessions per stream 98, 204
special characters, do not use 27
starting the TARA server 221
state conditions
build phase 85
dictionary 85
table data 85
stopping the TARA server 221
system health 220
T
troubleshooting
Teradata TARA 215
using debug logs 219
TVS temperature 98, 204
U
updating job IDs 108
user name 82, 97, 198, 202
V
verify checksum 84, 99, 200, 204
verify job script 116
version numbers 4
view job history 122
W
Windows server 62
X
xinetd process 46
TARA
server 179
server audit log 218
server log, change verbosity 227
TARA Server Configuration dialog box
ARC Options tab 69, 210
Client Groups tab 68, 208
Clients tab 66, 207
Logging tab 213
NetBackup tab 70, 211
Teradata tab 65, 206
TARA server response to client heartbeat 220
TARAJobQuery command line utility 139
TARALaunch command line utility 152
TARAMigrator command line utility 158
taraping command line utility 161
TARAScriptConv command line utility 163
taraserver account 224
TDE troubleshooting 241
TDPID 82, 97, 198, 202
Teradata Extension for NetBackup configuration 53
Teradata TARA GUI 175
Teradata Tiered Archive/Restore Architecture 78
graphical user interface configuration command 178
Job Viewer 178
restore command 178
server configuration command 178
settings menu commands 178
testing configuration settings for Teradata Extension for
NetBackup 62
Teradata Extension for NetBackup Administrator Guide, Release 15.00
259
Index
260
Teradata Extension for NetBackup Administrator Guide, Release 15.00