123userdocs.s3-website-eu-west-1.amazonaws.com123userdocs.s3-website-eu-west-1.amazonaws.com/d/80/fc... ·...

TERADATA BAR SOLUTIONS GUIDE

January 12, 2007

Teradata Research and Development

THIS DOCUMENT AND INFORMATION HEREIN ARE THE PROPERTY OFNCR CORPORATION

AND ALL UNAUTHORIZED USE AND REPRODUCTION ARE PROHIBITED

Copyright © 2007 by NCR Corporation, Dayton, Ohio U.S.A.All Rights Reserved. Printed in U.S.A.

NCR ConfidentialUnpublished Property of NCR Corporation

2: Hardware BAR Solutions Guide

NCR ConfidentialThis document, which includes the information contained herein,: (i) is the exclusive property of NCR Corporation; (ii) constitutes NCR confidential information; (iii) may not be disclosed by you to third parties; (iv) may only be used by you for the exclusive purpose of facilitating your internal NCR-authorized use of the NCR product(s) described in this document to the extent that you have separately acquired a written license from NCR for such product(s); and (v) is provided to you solely on an "as-is" basis. In no case will you cause this document or its contents to be disseminated to any third party, reproduced or copied by any means (in whole or in part) without NCR's prior written consent. Any copy of this document, or portion thereof, must include this notice, and all other restrictive legends appearing in this document. Note that any product, process or technology described in this document may be the subject of other intellectual property rights reserved by NCR and are not licensed hereunder. No license rights will be implied. Use, duplication or disclosure by the United States government is subject to the restrictions set forth in DFARS 252.227-7013 (c) (1) (ii) and FAR 52.227-19. Other brand and product names used herein are for identification purposes only and may be trademarks of their respective companies.The product described in this book is a licensed product of Teradata, a division of NCR Corporation.NCR, Teradata and BYNET are registered trademarks of NCR Corporation.EMC is a registered trademark of EMC Corporation.Ethernet is a trademark of Xerox Corporation.Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.IBM and Tivoli are registered trademarks of International Business Machines Corporation.Intel is a registered trademark of Intel Corporation.Linux is a registered trademark of Linus Torvalds.Active Directory, Microsoft, Windows, Windows Server, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.SUSE is a trademark of SUSE LINUX Products GmbH, a Novell business.QLogic is a registered trademark of QLogic Corporation.Sun is a registered trademark of Sun Microsystems, Inc. in the U.S. or other countries.UNIX is a registered trademark of The Open Group in the US and other countries.NetVault is a trademark and BakBone is a registered trademark of BakBone Software, Inc.NetBackup and VERITAS are trademarks of VERITAS Software Corporation.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 NONINFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL NCR CORPORATION (NCR) 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 NCR intends to announce such features, functions, products, or services in your country. Please consult your local NCR 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. NCR 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 e-mail: [email protected] comments or materials (collectively referred to as “Feedback”) sent to NCR will be deemed non-confidential. NCR 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, NCR 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-2006 by NCR Corporation. All Rights Reserved.

Preface REVISION HISTORY

Revision/Version Author(s) Principal

Contributors Date Comments

Reviewers of Current RevisionRevision Reviewer Name Function(s) Represented by ReviewerA01 Cyrus Afkhampour BAR SME

Jeremy Davis BAR SMEAnita Jones BAR SMESteve Kahle BAR SMEJerry Kong BAR SMEMarc Mundt BAR SMEDexter Oliver BAR SMEJefferson Uy BAR SME

Other Interested People Revision

Name Function(s) Represented

A01 Engineering group BAR SMEsDon Klarner Technical Sales ConsultantJosh Mereminsky Technical Sales ConsultantSimon Martinelli Technical Sales ConsultantEddie Tan Technical Sales ConsultantYsbrand Bergman Operational Service ConsultantRandy Bell Operational Service ConsultantDavid Hardy Customer ServicesDavid VandenBrink Customer ServicesWilliam Brennan Customer ServicesCraig McPhie Customer ServicesArt Spickerman Customer ServicesChris McClure BAR and Data Migration Service Offer

ManagerJames Crouse Solution Account ManagerRex Miller Senior Product ManagerReier Torgerson Product Management Manager

Approver Dennis Glover

May 17, 2023 NCR Confidential iDocument No. 541-0006487

SUPPORT INFORMATIONOperational Services, BAR Pre-Sales

Operational Services provides BAR pre-sales support for Teradata BAR architectures and configurations and BAR post-sales support for BAR implementation.

Contact Phone NumberDirector Mark Newton 1-858-485-3260Project Manager Fred Denham 1-858-485-3652Post-Sales Randall Bell 1-512-853-9492Region Contact Phone Number

AmericasDon Klarner 1-858-794-1621Josh Mereminsky 1-858-314-2957

EMEAYsbrand Bergman 31-228-52-47-15

Simon Martinelli +612-9935-3615

Asia/Pacific/AustraliaEddie Tan (65) 6240-6261Dean Frost +64-9-3566742

Global Sales Support (GSS)GSS provides Teradata sales support and validations for all configurations.Primary Support Contact Global Sales Support – Online Assistance CenterLocation San Diego, CAE-mail address GSS, Teradata Help [email protected] number 1-858-485-3888Fax number 1-858-485-4015

Global Support Center (GSC)The Large Systems Global Support Center provides customer support for all Teradata and Teradata BAR solutions.Support Organization Large Systems Global Support CenterLocation San Diego, CAE-mail address GSC. [email protected] number 1-800-322-1012 or 1-858-485-3700Fax number 1-858-485-3666 or 1-858-485-3400

May 17, 2023 NCR Confidential iiDocument No. 541-0006487

mailto:GSC.%[email protected]

mailto:GSS,%20Teradata%20Help%[email protected]

BAR Solutions Guide 2: Hardware

Table of ContentsPreface.......................................................................................................................................................... i

Revision History........................................................................................................................................ iSupport Information.................................................................................................................................. ii

Operational Services, BAR Pre-Sales................................................................................................... iiGlobal Sales Support (GSS)................................................................................................................. iiGlobal Support Center (GSC)............................................................................................................... ii

List of Figures.......................................................................................................................................... viList of Tables.......................................................................................................................................... viiIntroduction to the BAR Solutions Guide................................................................................................viii

Background........................................................................................................................................ viiiPurpose.............................................................................................................................................. viiiAudience............................................................................................................................................ viiiWhat You Can Expect from this Guide...............................................................................................viii

Related Documents................................................................................................................................. xiInternal Sites....................................................................................................................................... xiiExternal Sites...................................................................................................................................... xvPartner Sites...................................................................................................................................... xvii

1: Concepts................................................................................................................................................ 19

Introduction to Backup, Archive and Restore.........................................................................................19Overview............................................................................................................................................. 19Teradata BAR History......................................................................................................................... 20

Legacy Direct-Attached BAR Architecture..............................................................................................20How it Works...................................................................................................................................... 20Advantages......................................................................................................................................... 21Disadvantages.................................................................................................................................... 22

LAN-Based BAR Architecture................................................................................................................22How it Works...................................................................................................................................... 22Advantages......................................................................................................................................... 23Disadvantages.................................................................................................................................... 24Why the Change was Made to LAN-Based Architecture....................................................................24

Tapes and Disks: The Two-Tiered Strategy...........................................................................................26How it Works...................................................................................................................................... 26Advantages......................................................................................................................................... 28Disadvantages.................................................................................................................................... 29

Teradata Integration............................................................................................................................... 29How it Works...................................................................................................................................... 29Advantages......................................................................................................................................... 30Disadvantages.................................................................................................................................... 31

Software Concepts Overview................................................................................................................. 32BAR Hardware Concepts Overview.......................................................................................................33

Options Overview............................................................................................................................... 33

2: Hardware............................................................................................................................................... 35

The Teradata 9203 BAR Server.............................................................................................................35BAR Server Function..........................................................................................................................35BAR Server Connectivity....................................................................................................................37BAR Server Description......................................................................................................................39BAR Server Components................................................................................................................... 40

Adapters................................................................................................................................................. 42

January 12, 2007 NCR Confidential iiiDocument No. 541-0006487


Fibre-channel HBAs............................................................................................................................ 42Network Adapters............................................................................................................................... 44

Switches................................................................................................................................................. 44LAN Switch: Teradata 6535 Gigabit Switch (Copper Ethernet)..........................................................45SAN Switches: Teradata 6533 and 6534 SAN Switches (Fibre-channel)...........................................47

Tape Libraries........................................................................................................................................ 49Choosing a Library.............................................................................................................................. 50Teradata 9200.................................................................................................................................... 51Teradata 9202.................................................................................................................................... 55Teradata 9201 (StorageTek ACSLS)..................................................................................................62

Tape Drives............................................................................................................................................ 64Sharing Tape Drives........................................................................................................................... 64Tape Drive Function........................................................................................................................... 65Tape Drive Connectivity...................................................................................................................... 66Description: Ultrium (LTO) Fibre-channel Drives................................................................................67Description: StorageTek Fibre-channel Drives...................................................................................69

Teradata 9204 Backup 2 Disk................................................................................................................739204 Function..................................................................................................................................... 739204 Connectivity............................................................................................................................... 749204 Description................................................................................................................................. 749204 Components.............................................................................................................................. 76Typical Teradata 9204 Configuration..................................................................................................78

Teradata 9205 Virtual Tape Library........................................................................................................799205 Function..................................................................................................................................... 799205 Connectivity............................................................................................................................... 799205 Description: CDL 710, 720, and 740..........................................................................................799205 Components.............................................................................................................................. 81Typical Teradata 9205 Configuration..................................................................................................83

3: Software................................................................................................................................................. 85

Teradata Tools and Utilities.................................................................................................................... 85ARC.................................................................................................................................................... 85Multi-ARC........................................................................................................................................... 87Teradata TARA................................................................................................................................... 88Access Modules................................................................................................................................. 88

NetVault (BakBone)................................................................................................................................ 89NetVault Overview.............................................................................................................................. 89NetVault Components.........................................................................................................................93

NetBackup (Symantec, formerly Veritas).............................................................................................101NetBackup Overview........................................................................................................................ 101NetBackup Components................................................................................................................... 104

Tivoli Storage Manager (IBM)..............................................................................................................107Tivoli Storage Manager Overview.....................................................................................................108Tivoli Components............................................................................................................................ 110

4: Performance Variables........................................................................................................................ 115

Teradata............................................................................................................................................... 115TD Platform...................................................................................................................................... 115Backup Strategy Impacts on Performance.......................................................................................118TD Database Factors........................................................................................................................120Teradata Database Performance Variables......................................................................................123(TBA)Data Rate to/From Teradata....................................................................................................124

Networks.............................................................................................................................................. 124(TBA)Network................................................................................................................................... 124LAN Tuning....................................................................................................................................... 124

iv NCR Confidential January 12, 2007Document No. 541-0006487


CLI tunables..................................................................................................................................... 127Network Encryption........................................................................................................................... 127Gateway Selection through COP Entries..........................................................................................127COP Configuration............................................................................................................................ 128(TBA)Parallel LAN Guidelines..........................................................................................................128

BAR Server.......................................................................................................................................... 128(TBA)Bar server processing speed...................................................................................................128(TBA)Data Rate through server(s)....................................................................................................128(TBA)Distribution of Data Streams across Nodes and Servers........................................................129(TBA)Number of data streams..........................................................................................................129Operating System Dependencies (Tunables)...................................................................................129

Software/OTB/Utilities.......................................................................................................................... 132Checkpointing: Advantages and Disadvantages..............................................................................132Performance Tunables..................................................................................................................... 134Cluster Counts.................................................................................................................................. 139Number of session attributes in setting up ARC jobs........................................................................139Software Encryption.......................................................................................................................... 139

SAN / Devices...................................................................................................................................... 141(TBA)SAN tunables zoning...............................................................................................................141(TBA)Compressibility of the data......................................................................................................141(TBA)I/O........................................................................................................................................... 141(TBA)Datablock size......................................................................................................................... 141(TBA)Number of buffers....................................................................................................................141(TBA)Encryption Devices..................................................................................................................141(TBA)Number of devices and load leveling.......................................................................................141(TBA)Type of devices.......................................................................................................................141(TBA)Tape and Disk......................................................................................................................... 141(TBA)Disk to tape copies.................................................................................................................. 142

Appendix.................................................................................................................................................. 143

Frequently asked Questions.................................................................................................................143Backups............................................................................................................................................ 143Support and Compatibility.................................................................................................................148NetBackup........................................................................................................................................ 149NPARC............................................................................................................................................. 153Tape Drives...................................................................................................................................... 153

TD Services.......................................................................................................................................... 154BAR and Business Continuity..............................................................................................................154

Glossary................................................................................................................................................... 157

Index........................................................................................................................................................ 189

January 12, 2007 NCR Confidential vDocument No. 541-0006487


LIST OF FIGURESFigure 1: Example of a direct-attached BAR architecture with NetVault....................21Figure 2: The legacy layout for the direct-attached architecture................................21Figure 3: Example of a LAN-based BAR architecture with Backup 2 Disk..................23Figure 4: Another example of a LAN-based BAR architecture with backup-to-disk....23Figure 5: The two-tiered backup strategy....................................................................27Figure 6: Example of a two-tiered backup-to-disk configuration.................................28Figure 7: LAN-based BAR components.........................................................................33Figure 8: Direct-attached BAR components.................................................................34Figure 9: BAR Server Types.........................................................................................37Figure 10: Typical Backup to Tape Architecture..........................................................39Figure 11: HBA and NIC fibre-channel connectivity....................................................43Figure 12: 9200 Fibre-channel Connectivity - LAN-based Architecture......................52Figure 13: 9200 Fibre-channel Connectivity - Direct Connect Architecture................52Figure 14: 9202 Fibre-channel Connectivity - Indirect...............................................56Figure 16: LAN-Based Homogeneous Library for Teradata.........................................57Figure 17: LAN-Based Heterogeneous Shared Library between Teradata and Open Systems.........................................................................................................................57Figure 18: Fibre-channel Connectivity.........................................................................58Figure 19: Direct-Attached Homogeneous Library for Teradata Error! Bookmark not defined.Figure 15: The Teradata 9202 Modular Library System..............................................59Figure 20: Shared Library Comparisons......................................................................65Figure 21: Library Controller Module..........................................................................77Figure 22: Disk Array Expansion Modules...................................................................78Figure 23: Typical Teradata 9204 Configuration.........................................................78Figure 24: Typical Teradata 9205 Configuration.........................................................83Figure 25: Access Module/Data Connector API Linkage..............................................89Figure 26: Storage Management System.....................................................................91Figure 27: The NetVault Enterprise.............................................................................91Figure 28: NetVault with a LAN-based Library............................................................93Figure 29: NetVault with a Direct-Attached Library....................................................93Figure 30: Dynamically Shared Devices - Tape Drive Configurations..........................96Figure 31: Dynamically Shared Devices - Disk Backup................................................97Figure 32: VaultShare Diagram for Teradata...............................................................99Figure 33: VaultShare Diagram for Open Systems....................................................100Figure 34: LAN-based Configuration..........................................................................104Figure 35: Teradata extension ordering examples for NetBackup............................106Figure 36: TSM Configuration....................................................................................110Figure 37: Tivoli Requirements Diagram...................................................................112Figure 38: Configuration Illustration for SMP and single-node MPP configurations.113Figure 39: Configuration Illustration for Dual Node MPP Configuration..................114

vi NCR Confidential January 12, 2007Document No. 541-0006487


Figure 40: Configuration Illustration for a Four-Node System with One Tape Drive per Node............................................................................................................................114

LIST OF TABLESTable 1: Advantages of LAN-Based BAR Solutions.......................................................23Table 2: Advantages with and disadvantages without Teradata Integration...............30Table 3: Operating system, storage, and software options..........................................32Table 4: 2950 BAR Server.............................................................................................40Table 5: 6535 Gigabit LAN Switch Feature Chart........................................................46Table 6: Fibre-channel Switch Matrix..........................................................................49Table 7: Library Comparison Matrix.............................................................................50Table 8: 9200 library-to-tape matrix.............................................................................54Table 9: 9202 Library-to-Tape Matrix...........................................................................60Table 10: Library to Tape Matrix..................................................................................66Table 11: LTO2/LTO3 Tape Drive Common Features...................................................67Table 12: LTO2/LTO3 Tape Drive Differing Features...................................................67Table 13: LTO2/LTO3 Tape Media Common Features.................................................69Table 14: LTO2/LTO3 Tape Media Differing Features.................................................69Table 15: Fibre-channel Tape Drive Comparison Chart...............................................70Table 16: Fibre-channel Tape Media Comparison Chart..............................................72Table 17: 9204 Features...............................................................................................75Table 18: RAID-5 Factoring..........................................................................................76Table 19: CDL Library Comparison Chart....................................................................80Table 20: CDL library components...............................................................................81Table 21: NetVault with Direct-attached Architecture.................................................89Table 22: NetVault with LAN-based Architecture........................................................90Table 23: NetBackup with LAN-Based Configuration................................................101Table 24: NetBackup Operating System Support.......................................................103Table 25: TSM (LAN-Based Architecture Only)..........................................................108Table 26: Basic Teradata BAR Server Configuration.................................................132Table 27: Relative Speeds and Maximum Capacities of Tape Drives.........................142Table 28: Backup Solution Matrix – Small Tables......................................................147Table 29: Backup Solution Matrix – Medium Tables..................................................147Table 30: Backup Solution Matrix – Large Tables......................................................148Table 31: Customer Requirements for NetBackup Migration....................................151

January 12, 2007 NCR Confidential viiDocument No. 541-0006487


INTRODUCTION TO THE BAR SOLUTIONS GUIDEBackground

The Teradata BAR solutions have evolved from standard tape backup to include LAN-based media servers, both disk and tape BAR devices, and the concept of OTB (Open Teradata Backup) software. These ongoing support and technology changes have resulted in more options for arranging these products than ever before. At the same time, customer needs for appropriate BAR solutions have been increasing. Teradata senior management took steps to address the confusion that can come from such growth, driving a shared vision of the BAR solution. The BAR Solutions Guide is part of that directive.

PurposeWhile the individual components of Teradata BAR solutions are well documented, the need was recognized for documentation of the overall BAR solution (both hardware and software) in a form that ties all of the components together and explains how the various options relate to each other. The purpose of the BAR Solutions Guide is to do that in such a way as to allow Technical Sales Consultants, Operational Services, and Customer Services to assess a customer’s BAR needs and recommend the appropriate BAR solution from Teradata’s offerings.

AudienceThe BAR Solutions Guide is for the use of Teradata BAR professionals only: Technical Sales Consultants, Operational Services, and Customer Services. Use of the information presented in this guide by persons other than trained and experienced Teradata BAR professionals may result in less than optimal or incomplete solutions. If you are not a Teradata BAR specialist and believe you need to use any of the information in this guide, always use the support information listed in this guide (in front of the table of contents) to contact someone to be certain that you are using the information correctly.

What You Can Expect from this GuideSince the details of the individual BAR components are already documented, the BAR Solutions Guide is developed by BAR Engineering from a product solution perspective to provide an

viii NCR Confidential January 12, 2007Document No. 541-0006487


overall, high-level look at Teradata BAR solutions. It should serve as a starting point for information in a changing, growing BAR environment.Note that this guide does not cover the information provided in The Teradata BAR Solution with 9203-3000/3001 BAR Server Hardware Installation and Service Guide, B035-5176-017A, or The Teradata BAR Solution with 9203-3000/3001 BAR Server Hardware Product and Site Preparation Guide, B035-5175-017A.

Chapter by ChapterPreface Support Information: Who to contact when customer needs

exceed the scope of this Guide Related Documents: Links to Teradata BAR-related

documents Vendor (third-party) sitesChapter One: Concepts Why we changed from the way things used to be How the legacy direct-attached and the LAN-based

architectures compare to each other Disk vs. tape Teradata integrationChapter Two: Hardware How all the parts fit together into the whole solution How each part functions in the Teradata BAR environment What each of the parts connect toChapter Three: OTB Software Advantages and Disadvantages of each OTB product How each OT product fits into the BAR architecturesChapter Four: Performance Variables Information about the many things that can affect the BAR

system performance and what can be done to optimize themAppendix Some FAQs collected to date, and additional Teradata

services that relate to BARGlossary The Teradata BAR-specific meaning for BAR-related terms

January 12, 2007 NCR Confidential ixDocument No. 541-0006487


Index We’ll make our best educated guesses at how you might try

to find things and put them in the index for you

Icons Used in the DocumentDefinitions – Simple, high-level, and introductory

Notes – Additional useful information

See – Includes handy links to referenced sites

Alerts – Information that may need special attention

Go There – These icons contain links to referenced locations within this document. They are placed there for your convenience when you are using the document on your computer screen. Ctrl/Click on the icon to go there. Reminder: Since there is no way to link you back to where were, you should note your location in the document before using a hyperlink.

Tips for Using This Document in MS Word

Navigation

There are two things you can do to make it easier to navigate through this document if you have it in Microsoft Word and are viewing it on your computer screen.

Document MapTurn on the Document Map. Go to View and click on “Document Map.” This is a toggle switch. This view takes up some space on your screen, but the document is set up so that what you see in that adjustable space on the left side of the screen is a 5-level outline of the document. You’ll see the familiar and signs that let you open and close the outline levels.

Hide White Space

x NCR Confidential January 12, 2007Document No. 541-0006487


It’s easier to read through a section of text on the screen without having to scroll through those headers and footers that are needed for the printed document. To hide them, hover your pointer over the space between the pages until you see this

symbol , then click on it. To show them again, place your pointer on the line that is now there instead of the header, footer, and space between the pages (the arrows will look like this now ) and click again.

Caveats for Document Appearance in Word

A number of things can change the appearance of a Word document from one computer to another. There is no way to control this, so there may be some minor difference in the appearance of the document on your computer from the way it was prepared. Here’s a quote from what you might call a Word power user who knows what he’s talking about: “Keeping objects in precise locations in an “editable” Word document is an ongoing challenge - especially if handled by multiple users who may or may not understand the principles behind the scenes. If all users don't have the same printer, driver, video, and fonts it will be impossible to control the appearance and text flow.”

Printing Tips

Should you wish to print the document, be aware that there are two things that can change the page breaks and reduce the accuracy of your table of contents. One is the differences between computers mentioned above, and the other is paper size. This document is formatted for 8 ½ X 11, so use that paper size to print if at all possible. All kinds of things in the document formatting will suffer if you print in A4.

A Note about the Links in this GuideInternet and intranet links are provided in this document in the belief that the information will be useful to our readers. It is understood that things will change, requiring an ongoing maintenance task. The links were verified from inside the firewall at the San Diego Teradata office as of January 1, 2007. Note that when not signed in to the employee portal, links to OCIs, for example, may only open the Employee Portal first page. There are no means for this writer to verify the differences that may exist in accessibility among readers.

January 12, 2007 NCR Confidential xiDocument No. 541-0006487


RELATED DOCUMENTSTo ensure that optimum benefits are received from the OTB software, there is Teradata documentation that should be read before, during, or after any OTB installation. You need to be familiar with all of this; your particular needs will determine what you must read, use, and stay current with. Here is a list of what they are and where you can find them. You may also need to read documentation from our vendors, so links to our partner sites are also included for your convenience.

Internal SitesInternal sites can only be accessed by Teradata and other staff from inside the Teradata firewall.

Teradata Service Documentation Library, BAR Solutions The Teradata Service Documentation Library has a BAR (backup/archive/restore) Solutions section at http://infocentral.daytonoh.ncr.com/tsd-library/iBarSolutions.cfmThere is an effort underway to get all BAR product documentation located here, including the hardware and third-party documentation that you need. Sections that are still under construction are waiting for permission from the vendors to post their manuals.

BAR Installation and Service Guide

The Teradata BAR Solution with 9203-3000/3001 BAR Server Hardware Installation and Service Guide, B035-5176-017A, is available at the Service Documentation Library site provided above.

SEE: For the BAR Site Prep Guide, see this section under “External Sites.”

Open Teradata Backup Release DefinitionBefore beginning any OTB installation, you need to read the latest Open Teradata Backup Release Definition, along with the supporting technical publications. The Release Definition is located in the Service Documentation Library, but this will take you straight to it: http://infocentral.daytonoh.ncr.com/tsd-library/iDownload.cfm?itemid=061770009This document covers all three OTB products and is downloadable in PDF format.

xii NCR Confidential January 12, 2007Document No. 541-0006487

http://infocentral.daytonoh.ncr.com/tsd-library/iDownload.cfm?itemid=061770009


http://infocentral.daytonoh.ncr.com/tsd-library/iBarSolutions.cfm


The Employee PortalSome important BAR documentation is now accessible through the Employee Portal at:

https://www.ncr4me.ncr.com

Ordering and Configuration Information

If you need detailed ordering and configurationError! Bookmark not defined. information, consult the BAR OCI (Ordering and Configuration Information). The formal way to access them is through the Employee Portal. In the top right corner of the page, drop down the “Choose a Site” list and select the Knowledge Repository. Type “OCI” into the search bar next to it and click on Search. You can then use the search tool on the next page.

CSNet and SalesNet

From the Employee Portal main page, access CSNet and SalesNet from “Intranet Sites” as shown below.

January 12, 2007 NCR Confidential xiiiDocument No. 541-0006487

https://www.ncr4me.ncr.com/


CSNet

CSNet is the Teradata Customer Services Sales Intranet. You can go directly there at: http://www.csnet.ncr.com/level0.asp From its start page, click on the BAR documents.

Or go directly to the CSNet BAR documents page at http://www.csnet.ncr.com/level3.asp?ResultType=4&NavBotLyr=50&SortFlag=1

ORhttp://www.csnet.ncr.com/level3.asp?ResultType=1&ResFlag=1&rbSearchType=Quick&strAND_OR=And&SortFlag=1&search=BAR&strAND=And

The BAR documents page includes the following:BAR Implementation ProcessOr go directly there at: http://www.csnet.ncr.com/level4download.asp?navIDVar=&DocSpec=1319&DocType=3BAR Delivery Process GuideOr go directly there at:http://www.csnet.ncr.com/level4download.asp?navIDVar=&DocSpec=1318&DocType=3Pre-Implementation Checklist (PIC)Or go directly there at:http://www.csnet.ncr.com/ShareDoc/CS/Sales/BAR%20COE/BARCOE-PreImpCheck.xls

SalesNet

The page headed Teradata Customer Services Sales Intranet can be reached at:

xiv NCR Confidential January 12, 2007Document No. 541-0006487

http://www.csnet.ncr.com/ShareDoc/CS/Sales/BAR%20COE/BARCOE-PreImpCheck.xls

http://www.csnet.ncr.com/ShareDoc/CS/Sales/BAR%20COE/BARCOE-PreImpCheck.xls

http://www.csnet.ncr.com/level4download.asp?navIDVar=&DocSpec=1318&DocType=3




http://www.csnet.ncr.com/level3.asp?ResultType=1&ResFlag=1&rbSearchType=Quick&strAND_OR=And&SortFlag=1&search=BAR&strAND=And



http://www.csnet.ncr.com/level3.asp?ResultType=4&NavBotLyr=50&SortFlag=1

http://www.csnet.ncr.com/level3.asp?ResultType=4&NavBotLyr=50&SortFlag=1

http://www.csnet.ncr.com/level0.asp


https://myc.gateway.ncr.com/Site00EC/level3.asp?ResultType=1&ResFlag=1&rbSearchType=Quick&strAND_OR=And&SortFlag=1&search=BAR&strAND=AndNote that the only way that this writer could gain access to this site was to paste the URL into the browser from the Employee Portal home page (after signing in if offsite, of course). This was true both offsite as well as onsite from the San Diego office. Also note that, in this writer’s test, this is not the same page that appears when clicking on “Teradata SalesNet” from the Employee Portal start page. The page heading that appears in that case is simply “Teradata Intranet.” It is not the same page.

CSDeliveryNetThe Teradata Customer Services Delivery Intranet is where the support plans for all the products are kept. Find it at: http://www.csdeliverynet.ncr.com/

GSC Support Knowledge Base (Tech Alerts and Knowledge Articles)

Just what you need to know to resolve an OTB issue may have been recently posted as a Tech Alert or Knowledge Article, so you will want to know where they are. Find them on the GSC site at:http://san101ln.sandiegoca.ncr.com:8080/domino.htm

RepositoriesTeradata Realization-Information Repositories are located at:

January 12, 2007 NCR Confidential xvDocument No. 541-0006487

http://san101ln.sandiegoca.ncr.com:8080/domino.htm

http://www.csdeliverynet.ncr.com/

https://myc2.gateway.ncr.com/exchweb/bin/redir.asp?URL=https://myc.gateway.ncr.com/Site00EC/level3.asp?ResultType=1%26ResFlag=1%26rbSearchType=Quick%26strAND_OR=And%26SortFlag=1%26search=BAR%26strAND=And




http://www.sandiegoca.ncr.com/socal/realization/repositories.cfm

External SitesExternal sites can be accessed by employees and customers alike.

NCR Information Products Publishing Repository

BAR Site Prep Guide

The Teradata BAR Solution with 9203-3000/3001 BAR Server Hardware Product and Site Preparation Guide, B035-5175-017A, is downloadable from the Information Products Publishing repository, www.info.ncr.com. Use the General Search function to locate documents with a Publication Product ID containing "5175".

SEE: For the BAR Installation and Service Guide, see this section under “Internal Sites.”

NCR Information Products

NCR Information Products is an external site that is home to a number of on-line publications in downloadable, PDF format.The current release definitions for OTB software have been posted on the Services Documentation Library BAR Solutions site listed previously, but the previous release definitions remain here along with those for TTU (Teradata Tools and Utilities), OTB, and TDBMS (Teradata Database Management System).The search page is at:http://www.info.ncr.com/Gen-Srch/eOnLine-Srch.cfm . Type your OTB product name in the “Title or Keyword” block. Click the “Date” radio button on the “Sort By” bar to make it

easier to find the latest publications.

xvi NCR Confidential January 12, 2007Document No. 541-0006487

http://www.info.ncr.com/Gen-Srch/eOnLine-Srch.cfm

http://www.sandiegoca.ncr.com/socal/realization/repositories.cfm


January 12, 2007 NCR Confidential xviiDocument No. 541-0006487


Partner Sites

HardwareSun/StorageTek: SAN switches, backup to disk, tape libraries, drives, and cartridgeshttps://www.sun.com/storagetek/

Dell Servers, Storage, and Networkinghttp://www.dell.com/content/products/category.aspx/enterprise ? c=us&cs=555&l=en&s=biz

Qlogic Fibre-channel Adaptershttp://qlogic.com

IntelPro adapters http://www.intel.com/support/network/adapter/index.htm#PRO1000

Brocade Silkworm SAN switch (through Sun/StorageTek)http://www.brocade.com/products/silkworm.jsp

McData SAN Switch (through Sun/StorageTek)http://www.mcdata.com/products/index.html

EMC Clariion Disk Libraryhttp://www.emc.com/products/systems/disk_library/index.jsp

HP Ultrium tape drives (through Sun/StorageTek)http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?&lang=en&cc=us&prodTypeId=12169&prodSeriesId=42915&lang=en&cc=us

SoftwareBakBone NetVault http://www.bakbone.com/Home.aspx?id=1868

Symantec (Veritas) NetBackuphttp://www.symantec.com/enterprise/products/overview.jsp?pcid=1018&pvid=2_1

IBM Tivoli Storage Managerhttp://www-306.ibm.com/software/tivoli/products/storage-mgr/

xviii NCR Confidential January 12, 2007Document No. 541-0006487

http://www-306.ibm.com/software/tivoli/products/storage-mgr/

http://www.symantec.com/enterprise/products/overview.jsp?pcid=1018&pvid=2_1

http://www.symantec.com/enterprise/products/overview.jsp?pcid=1018&pvid=2_1

http://www.bakbone.com/Home.aspx?id=1868

http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?&lang=en&cc=us&prodTypeId=12169&prodSeriesId=42915&lang=en&cc=us



http://www.emc.com/products/systems/disk_library/index.jsp

http://www.mcdata.com/products/index.html

http://www.brocade.com/products/silkworm.jsp

http://www.intel.com/support/network/adapter/index.htm#PRO1000

http://qlogic.com/

http://www.dell.com/content/products/category.aspx/enterprise?c=us&cs=555&l=en&s=biz

http://www.dell.com/content/products/category.aspx/enterprise?c=us&cs=555&l=en&s=biz

https://www.sun.com/storagetek/


January 12, 2007 NCR Confidential xixDocument No. 541-0006487

1: CONCEPTS

INTRODUCTION TO BACKUP, ARCHIVE, AND RESTORE

Teradata BAR (Backup/archive/restore) is an end-to-end storage management solution that protects the enterprise data and its ability to do business.

Overview

Because Teradata provides our customers with vast opportunities to manage, analyze, utilize, and make strategic decisions with large amounts of data, the Teradata Database has become the key investment that our customers make in their quest for a competitive edge in their respective markets.The Teradata Database has been designed with exceptional reliability and redundancy. Unexpected conditions, however, can put a customer's most crucial asset, its data, at risk. Although disasters can strike, the need to restore data most often comes from user-related failures: either operator error or the introduction of corrupted data. Recognizing the need to protect and also archive data, Teradata has developed world-class backup/archive/restore (BAR) solutions that have been optimized for operation with the Teradata nodes and database. Also recognizing that customers use the Teradata Database in different enterprise operating environments, we have provided multiple BAR solutions to best match each customer's environment. Teradata BAR solutions using OTB software can be viewed as two possible architectures. The most recent (and now advocated) solution is LAN-based, where Teradata nodes are connected to BAR servers using gigabit Ethernet LAN connections. The BAR servers initiate and run the backup/archive/restore. The traditional solution is the direct-attached architecture where tape libraries and drives are connected directly to the Teradata nodes, which initiate and run the backup/archive/restore.Although Teradata has moved away from the direct-attached architecture, we will continue to support the investment of our customers using NetVault with direct-attached architecture.

January 12, 2007 NCR Confidential 20Document No. 541-0006487


Teradata BAR HistoryIn its earliest days, Teradata backup and restore shared a mainframe along with the Teradata Database, using ARC and sending the data over the mainframe channels to the tape storage devices.Although this is not the best approach for performance or cost-effectiveness, some of this early backup architecture is still around. It is not the purpose of this guide to discuss mainframe architecture, however. It is mentioned here simply to provide the historical background and will not be mentioned again.The traditional model for backup, archive, and restore became a direct connection from each Teradata node to the tape library. Today, the LAN-based BAR architecture offers so many advantages that it has become the advocated Teradata BAR solution.

LEGACY DIRECT-ATTACHED BAR ARCHITECTUREThe direct-attached solution has been the traditional approach for Teradata systems. In this architecture, the tape drives and library are directly attached to the Teradata system and the Teradata nodes initiate and run the backup/restore.

The newer LAN-based architecture is the advocated solution for all Teradata Systems, whether MP-RAS UNIX, Windows, or Linux. The only time that the legacy direct-attached architecture is an option is if the customer has MP-RAS nodes and is using NetVault. Teradata will continue to support the investment of our customers using NetVault with direct-attached architecture.

How it WorksIn the legacy direct-attached architecture, one of the Teradata nodes has a tape library connection and each node has a tape drive, the ARC utility, and the NetVault client module. The data travels over a direct SCSI* or fibre connection rather than over a network. The recommended strategy for the NetVault Server module is to have it run on a separate server, but it can also run on a Teradata node.Figure 1 is the new advocated layout for the direct-attached architecture. This new architecture moves the management functions of the NetVault Server off of the Teradata node and improves the performance of the backup.



*SCSI is a legacy technology; the Teradata 5400 uses fibre connection as shown in Figure 1.

FIGURE 1: EXAMPLE OF DIRECT-ATTACHED BAR ARCHITECTURE WITH NETVAULT

Figure 2: The Legacy Layout for the Direct-Attached Architecture

AdvantagesThe advantage of the direct-attached architecture, for some configurations, is the lower initial cost because the network of BAR servers and interconnections are not needed. Another advantage of the direct-attached architecture is that it provides legacy investment protection for existing Teradata customers with MP-RAS operating systems that are using NetVault. There is also a perceived advantage of fewer complications in the management of that additional hardware. Some customers may initially view it that way until they learn more about the LAN-based architecture and find it not to be a real concern. The direct-attached architecture is best suited for single systems that do not need shared BAR resources and have

22 NCR Confidential January 12, 2007Document No. 541-0006487


adequate windows of time to do backups when the system is quiet or not doing other workloads.

Disadvantages With the BAR hardware and software directly on Teradata nodes, the disadvantage is the contention with Teradata resources that results in a less than optimal parallel environment. BAR exceptions and maintenance windows can also cause Teradata downtime.The direct-attached architecture also provides less flexibility for customers to re-utilize their existing hardware components or to utilize hardware that is not Teradata-certified.The direct-attached architecture is least suited for multiple system environments that can take advantage of shared BAR resources, have mixed workload environments, and little or no windows of quiet system time.

LAN-BASED BAR ARCHITECTUREThe LAN-based architecture moves the BAR activity off of the Teradata nodes to a dedicated system that manages Teradata backups by linking the Teradata nodes and backup data storage devices.

The LAN-based architecture is the advocated solution for all Teradata systems (MP-RAS UNIX, Windows, and Linux). It is required for all configurations with backup to disk (both 9204 and 9205), for all Teradata Systems running Windows or Linux, and for all configurations using shared BAR devices.

How it WorksLAN-based BAR is built around a private LAN system that is used to move data between the Teradata nodes and the BAR servers. The OTB software initiates and runs the backup/restore from the BAR servers, which are also connected to the tape drives and storage devices. This frees up duty cycles for the Teradata nodes.Transmission control protocol (TCP) overhead is essentially the same for both architectures, but direct-attached TCP sessions are configured for the BYNET and rob CPU time from Teradata processes.



Figure 3: Example of LAN-Based BAR Architecture with Backup 2 Disk

Figure 4: Another Example of LAN-Based BAR Architecture with Backup to Disk

AdvantagesThere are a number of reasons to move the BAR activity to a dedicated server, and LAN-based solutions are now the first recommendation in new customer BAR installations. We offer and strive to sell all components for a LAN-based BAR solution. Some of the strongest reasons are shown in Table 1.



Table 1: Advantages of LAN-Based BAR SolutionsAdvantages of LAN-Based BAR Solutions

Improves fit into standard enterprise architectures

The LAN-based Teradata BAR solutions allow Teradata to offer and provide a complete end-to-end solution: certified, sold, and supported by Teradata.

Reduces planned downtime

Having BAR processes on the BAR server provides the ability to upgrade or modify the BAR architecture without physical changes to the Teradata system, reducing planned downtime.

Avoids operating system restrictions

The LAN-based architecture provides broader OTB, platform, and feature support. This allows Teradata BAR to fit into a wider range of enterprise architectures.

Increases Teradata availability

Moving the BAR hardware and software off the Teradata nodes reduces or eliminates the impact of BAR events on Teradata operations.

Lowers costsMoving the BAR application workload from the Teradata nodes to low-cost server platforms reduces total cost of ownership.

Better supports emerging technologies

LAN-based BAR also has the advantage of supporting emerging capabilities (for example, backup to disk and encryption) that will not be available on legacy BAR solutions.

Better supports customer growth

Improved flexibility: LAN-based solutions detach devices from the direct-attached mode, attaches them in a switched mode, and allows them to be shared resources.Improved scalability: LAN-based solutions detach devices from the direct-attached mode, attaches them in a switched mode, and allows for incremental growth at a component level.

DisadvantagesThe only disadvantage of the LAN-based architecture is the additional initial cost for BAR servers and network interconnections. A dedicated Gigabit Ethernet Card is required for each node that handles the transmission of data to the BAR Server via the Gigabit Switches.There is also a perceived disadvantage in the minds of some customers that there are more complications in the management of that additional hardware. Some customers may initially view it that way until they learn more about the LAN-based architecture.



Why the Change was made to LAN-Based ArchitectureThe change to the LAN-based architecture at Teradata spans at least three years of careful planning. Here is some of the background and rationale:

OTB SoftwareThe concept of Open Teradata Backup exists to give Teradata customers the broadest possible choice of industry-leading backup, archive, and restore software offers such as BakBone NetVault, Symantec NetBackup, and IBM Tivoli Storage Manager. The LAN-based architecture was seen as the correct path to pursue in order to support this objective because it provides the greatest flexibility and adaptability in customer environments. OTB software is capable of fitting into new Teradata

customer enterprises going forward. The approach for LAN-based BAR is standardized across all

current OTB software offers.

BakBone NetVault (NV): The Advocated Solution

The LAN-based architecture is available for use with BakBone NetVault.

Teradata will continue to support the investment of our customers using NetVault with direct-attached architecture.

Symantec (previously Veritas) NetBackup (NBU)

With the evolution of the relationship with NetBackup it became clear that a new solution was needed for Teradata to fit into NetBackup standard Media Server Architecture and to enable continued support and growth of our current NetBackup customers.

IBM Tivoli Storage Manager

We developed a Windows-based TSM (Tivoli Storage Manager) BAR client and TSM was introduced as a LAN-based BAR solution in January 2004.

TSM is a client-server architecture and the TD-TSM BAR client was developed as a Windows-based TSM client and was introduced as a LAN-based BAR solution in January 2004.



Future GrowthThe continued growth of the LAN-based BAR solution will come from several areas of interest within our customer base and new prospects: All BAR SANs (Storage Area Networks) are implemented and

supported via the LAN-based architecture. This means that BAR SANs will not be supported when attached directly to MP-RAS nodes.

The backup-to-disk offers are certified and supported only from the LAN-based architecture.

All Teradata SUSE Linux systems are supported via the LAN-based architecture.

TAPES AND DISKS: THE TWO-TIERED STRATEGYModular-tape-library-systems are an integral component of the Teradata BAR environment, providing a protected repository for the customer’s data. Connected either to a BAR server in LAN-based architecture or directly to the Teradata nodes, Teradata tape libraries provide high performance backups, archives, and restores. Backup-to-disk storage systems are disk-based data management solutions that include controllers, disk arrays, and integrated software that manages and controls the disk system. Backup-to-disk technology is gaining popularity due to its greater reliability, and in some cases, higher performance. However, tape remains the most cost-effective technology for long term archiving and for sending data to offsite locations.In the LAN-based architecture, Teradata advocates a complementary approach using both technologies: a two-tier backup strategy using both disk and tape.

How it Works

ConceptWhen a backup is initialized, data flows from Teradata through the BAR server to the disk array. The Teradata 9204 or Teradata 9205 backup to disk arrays provide the initial “landing zone” for backing up Teradata where one to two copies or generations are stored for short-term storage (measured in hours or days).The BAR servers and tape management software then initialize the secondary copying from disk to tape. Multiple copies are



prepared, stored, and managed in the tape library for intermediate-term storage (measured in weeks or months). For off-site media storage, also called vaulting, tape media can be ejected from the tape library and moved to off-site storage for safe keeping (measured in months to years). Special software is available to manage the accountability of tape media being moved off-site.This copy operation does not require input from Teradata, leaving Teradata fully operational and uninvolved.Backup-to-disk eliminates the problems associated with mechanical tape drive and tape media failure by using global hot spares and disk drives (SATA drives for the Teradata 9204 and low-cost fibre-channel disk drives for the Teradata 9205) in a RAID-5 configuration. If a disk fails, the controller activates a global hot spare and continues the backup, thereby ensuring protection against failure. This built-in redundancy and reliability reduce the overall operational down time.

The array has a limited amount of storage space, however. Under normal circumstances the array can only maintain a few

generations of backup. For extended storage, the data must be migrated to tape.For a restore, data is pulled either from the disk array or from the tape library, depending on which media is available. This means that data that was originally written to disk and then copied to tape can be restored directly from tape. With NetBackup, a tape copy can be made concurrently with backup to disk.Figure 5 shows the various possibilities for backup and restore in a backup-to-disk-to-tape configuration.


Backup to disk does not

replace backup to tape.


Figure 5: The two-tiered backup strategy



Figure 6 shows the two-tiered strategy in the LAN-based architecture using the Teradata 9202 SL8500. Figure 6: Example of a Two-Tiered Backup To Disk Configuration

Advantages

ReliabilityThe advantage of backing up to disk in the Teradata environment is not faster performance, but reliability. Including disk in the backup strategy minimizes the risk of potential hardware failures. The greatest problem that can occur in tape backup is tape drive or media failure. When the media fails (such as the tape breaking or jamming) the backup has to be restarted, lengthening the downtime of the system. Disk backup is also not subject to media errors when reading back.Customers with shrinking backup windows and those who have situations where it is absolutely critical to have backups at a



certain time of the day have a more reliable solution with the two-tiered strategy.

Cost SavingsWhile a backup-to-disk solution has reliability advantages over tape, it is significantly more expensive to do deep archiving and off-site disaster recovery with disk. Tape achieves the cost advantage over disk as multiple copies of backups are retained, deep-archived, or sent off site. Additionally, many customers have regulatory requirements that require off-site media storage in secured vaults. The two-tiered strategy provides the customer with the best overall cost advantage.

DisadvantageAs with the LAN-based solution, there are the initial and ongoing maintenance costs of the required hardware. Similarly, there may be the perceived disadvantage in the minds of some customers about additional complications involved in managing and maintaining that additional hardware.

TERADATA INTEGRATIONAn integrated Teradata BAR solution is optimized for a Teradata parallel environment: all of its elements are certified, sold, and supported by Teradata.

How it Works

Teradata as the Single Source

Teradata should be the customer’s single source for their entire BAR solution: all hardware, software, service, and training needs. When the customer buys a Teradata solution, it is tested and certified. We know it works and how it works: there is a very low risk. See Table 2 to compare the benefits of a turnkey solution and the customer’s risks when not making that choice.

Customer ServiceThe best outcome in a customer service situation is to have an integrated solution. Without a completely Teradata-integrated system, the most advantageous situation is to have accurate records about where the non-Teradata-certified components are in the customer system so that we are not attempting to support components that we did not provide. GSC can only provide support up to the customer-provided component and then the



incident must be turned back over to the customer to take to the other vendor.Also be aware that when problems come up after the installation of a non-integrated system, customers may still turn to the GSC because of an existing support relationship. When the GSC attempts to assist the customer but 1) has only limited information about the customer’s entire setup, and 2) the problems turn out not to be Teradata issues, the support they can provide is severely limited.

AdvantagesTable 2: Advantages with and disadvantages without Teradata Integration

Advantages of Teradata Integration

Disadvantages without Teradata Integration

Overall Issues There is very low risk. Customers get one-stop

shopping and support. Customers get realistic

performance and capacity planning.

Customers benefit from Teradata scalability with system growth.

Customers get a full family of storage devices and BAR applications.

The more customers do on their own, the higher the risk that things will go wrong.

The customer has to coordinate planning and installation with multiple vendors.

Startup Issues Teradata engineering puts all

the disparate pieces together and runs extensive interoperability testing, optimizing the whole BAR solution for the Teradata parallel environment.

All components of each specific BAR solution are fully integrated, tested, and certified with Teradata.

Customers have the benefit of established Teradata Best Practices.

Install time is reduced when the customer does not have to do it themselves.

The Teradata parallel architecture – which is unique and valuable – presents some extreme challenges to industry-standard products. Neither the customer nor their consultants or vendors have the expertise to adequately do the integration.

Customer must configure the components themselves and take responsibility for integration, installation, setup, testing, and support.

It takes longer to install. The customer has to troubleshoot

problems between vendors. Even if the customer uses a

TERADATA-specified manufacturer and part number, what the vendor ships can be different enough that



Advantages of Teradata Integration

Disadvantages without Teradata Integration

something does not work. The customer will have a unique

configuration that does not benefit from Teradata experience or best practices.

Support Issues Integrated solutions are fully

supported by Teradata Customer Services.

The customer is likely to get ineffective help from the individual software or hardware vendors of non-integrated components since they have no knowledge of the entire solution.

Teradata cannot support solutions it has not configured, but can only troubleshoot to the point of the last Teradata-installed component. At that point, the incident has to be turned back over to the customer to identify the next vendor.

Customers who do not accept the integrated solution must sign a non-compliance form (in the statement of work), releasing Teradata from responsibility.

Teradata charges a foreign-attach fee to implement customer-provided components because of the risks involved.

Disadvantages

While there are no disadvantages for employing Teradata integration, the perceived risks in the minds of some of our customers may be as follows: Not being able to comply with corporate standards

For example, the customer’s organization may have chosen to use equipment from vendor “X” for certain applications and by selecting Teradata they would deviate from this standard. Deviating from the standard might slow down the whole sales cycle.

The learning curve for new equipment from a vendor that the customer is not familiar with

Purchasing all of their equipment from Teradata might jeopardize the existing relationship with other vendorsThis is not always true. In some cases, the partner relationship with the vendor may be such that the vendor



salesperson and the Teradata salesperson are both compensated. Contact the local vendor account representative.

SOFTWARE-CONCEPTS OVERVIEWBAR Backup and Recovery Software schedules and sets up the backup and restore, and manages drive availability.

SEE ALSO: Chapter Three, BAR Software

Table 3 shows the different operating systems, storage media, and software that can be used with each of the two BAR architectures.Table 3: Operating System, Storage, and Software Options

Architecture

Teradata Database Operating Systems

BAR Server

OS

Storage Media

Data Backup and Recovery Software

NetVaultTightly

Integrated

NetBackupLoosely

Integrated

TSMNon-

Integrated

LAN-Based BAR

Windows2000/2003

MP-RAS (UNIX)

SUSE Linux

Windows

Tape

Disk

SUSE Linux

Tape Expecte

d by 2007

Disk Expecte

d by 2007

Direct-Attached

BAR

MP-RAS (UNIX)

N/A Tape NO NO

N/A Disk NO NO NO


BAR HARDWARE CONCEPTS OVERVIEWThe LAN-based BAR environment includes not only data-storage devices, but a variety of other devices to connect peripheral units, perform processing, route traffic, optimize the data path, and increase bandwidth.

SEE: Chapter Two, BAR Hardware

Options Overview

Figure 7 and Figure 8 show the difference between the components required for the LAN-based and direct-attached architectures.Figure 7: LAN-Based BAR Components

11/17/2006 NCR Confidential 35Document No. 541-0006487


Figure 8: Direct-Attached BAR Components


2: HARDWARETHE TERADATA 9203 BAR SERVER

A server is a computer or a part of a computer system that processes requests and provides information to other computers or other parts of the system.

SEE ALSO: 9203 BAR Server/6535 Gigabit Switch OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM022524&BV_SessionID=@@@@0975951390.1161899350@@@@&BV_EngineID=cccfaddjekhfddecfngcfgldhkgdgfk.09203 BAR Server (2950)/6535 Gigabit Switch OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681043&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0

SEE ALSO: instructions for accessing the OCIs through the Employee Portal.

BAR Server Function

Architectures

Legacy Direct-Attached

In the legacy direct-attached architecture, a BAR server can host the NetVault Server (management) software and TTU software to provide better functionality and resource usage. The Teradata nodes are used as client servers to host and run the client software.

LAN-Based

BAR servers and LAN gigabit Ethernet switches are the foundation of the LAN-based architecture. The BAR servers can be used as management server or as data servers. In a typical BAR LAN-based environment, a BAR controller infrastructure is created with switches and servers placed in the BAR controller rack. The management functions are placed on one server and the data movement functions are placed on the


https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681043&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0



https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM022524&BV_SessionID=@@@@0975951390.1161899350@@@@&BV_EngineID=cccfaddjekhfddecfngcfgldhkgdgfk.0



other servers. Management and data movement functions must be on separate servers, since performance suffers if both of those functions are combined on the same BAR server.The two BAR server roles are shown in the “BAR Management and Data Server Functions” section of this chapter.

BAR Management and Data Server Functions

BAR Management Server

The BAR management server runs the OTB tape management software that controls the BAR devices (drives, robotics, storage media, etc.) and provides the command and control for the backup and restore. It starts jobs on the data servers.The BAR management server is sometimes referred to as the BAR master server.

BAR Data Server

The other BAR servers, known as BAR data servers, run the OTB client software components and the TDE (Teradata Extension) agents for the OTB software. The data servers are the workhorses for moving data. Data servers take the role of clients, processing all of the requests for BAR functions sent to them by the management server and doing the actual movement of data during backup and restore operations.Once the management server has started a job, the ARC utility then initiates on the data servers to retrieve data from the Teradata nodes or to send data back to the Teradata nodes.The BAR data server is sometimes referred to as the BAR media server.



Figure 9: BAR Server Types

BAR Server Connectivity

Teradata System Nodes to Bar Server(s)The NCR 6535 Gigabit LAN switch optimizes the data path to and from the Teradata system.The Teradata 6535 Gigabit Ethernet LAN switch optimizes the data paths to and from each Teradata node. Since Teradata is a parallel architecture, the more nodes there are with connections to the Gigabit Ethernet switches, the more available bandwidth there is to move data from the nodes. Each Teradata node should have one dedicated NIC (Network Interface Card) with two ports. The recommendation is to have two connections from each Teradata node to the Gigabit Ethernet switches for optimal throughput.

Each BAR Server Each BAR server has two dedicated fibre-channel HBAs (host

bus adapters) with two ports on each adapter. Each BAR server has one NIC adapter with two ports. These must be installed in each BAR server to ensure proper data flow during backup and restore operations. If they are not installed, the system will not work. If they are not properly integrated, the system performance will be degraded.



SEE ALSO: There are more details about these adapters in “Adapters” section of this chapter.

NOTE: Gigabit Ethernet LAN should be a privately mapped network or subnet and support jumbo packets (9000 MTU – maximum transfer units). Gigabit Ethernet switches should support maximum aggregate throughput for all ports. NICs should support maximum transmit/receive descriptors up to at least 2048.

The BAR Management (Master) server The BAR management (master) server is connected to all of

the BAR servers via a separate public-LAN (not shown in Figure 10) through the OTB management and client software components passing control information.

The management (master) server is also connected through the BAR data LAN to the Teradata nodes for browser purposes when creating backup jobs and for administering the LAN switch(es). The master is typically not involved in data transfer to tape.

The management (master) server is also connected to the storage libraries for passing control information.

BAR Data (Client) Servers The data (client) servers communicate with the management

(master) server through the OTB client software, passing control information.

The data (client) servers communicate with Teradata using TDE agent software to pass database requests to the Teradata nodes, and to send and receive data streams to and from the Teradata nodes.

The servers are also communicating to the Teradata nodes over TCP using CLI (call level interface)-type messages.

SEE ALSO: The Teradata BAR Solution with 9203-3000/3001 BAR Server Hardware Installation and Service Guide, B035-5176-017A, is available at the Service Documentation Library at: http://infocentral.daytonoh.ncr.com/tsd-library/iBarSolutions.cfm





Storage ConnectivityStorage connectivity may include either of the following options: The Teradata 6533 SAN switch (required for the Teradata

9205) A single fibre-channel HBA port on the server connected

directly to a fibre-channel port on the device

Tape Backup and Storage ConnectivityBackup and storage may be connected to automated tape libraries. Teradata 9200: Fibre-channel, from the BAR management

server) Teradata 9202: From the BAR management server across

TCP through the Automated Cartridge System Library Software (ACSLS)

The BAR server may also connect to: Tape drives Tape library robotic control (implemented by an additional

connection from a BAR server to the library or through a connection to a separate application master server)

Tape backup and storage (used alone or together with a disk backup system).

Disk Backup ConnectivityMost disk backup systems are used together with tape storage systems. Disk storage is only available for LAN-based architectures and includes both B2D (backup-to-disk) and virtual options: Teradata 9204 (B2D) Teradata 9205 (Virtual)Figure 10 illustrates the possible connection paths within the BAR system.



Figure 10: Typical Backup to Tape Architecture

BAR Server DescriptionThe Teradata BAR Server is built by Dell and customized for the LAN-based architecture. Only one model is available and it is sold fully preconfigured and optimized to support the Teradata BAR LAN-based architecture. The customer has the choice of

two operating systems; a Windows 2003 server or a SUSE Linux enterprise server.

The Teradata 9203 BAR server (Dell PowerEdge 2950), with Intel® Xeon® processors and a balance of internal expandability and rack density, gives our customers both the high performance and drive capacity they need for their growing applications. It is recommended for any Teradata system.Table 4: 2950 BAR Server

Features Dell PowerEdge 2950Form Factor 2U rack heightProcessor Two 3.0-GHz Intel® Xeon™ Core Duo with 4-MB of cacheFront side Bus 1333 MHzMemory 2-GB DDR-2 400 MHz SDRAMDisk Drive Two 73-GB 10K RPM SAS drives, with RAID-1Ethernet Intel® Pro1000PT dual port Gigabit – copper adapter

Embedded two Gigabit ports on motherboardFibre-channel Two QLogic 2462 dual port 4-Gigabit fibre-channel adaptersCD-ROM 48X IDE CD-ROMFloppy Drive 1.4- MB floppy drivePower Redundant power supply with Y-CORDOperating System Windows: Windows Server 2003 R2 Standard Edition

Linux: SUSE Linux Enterprise ServerRoHS Compliant



BAR Server Components

Standard BAR Server ComponentsThe BAR server rack and the following components are delivered with each BAR server: Two fibre-channel HBAs One Gigabit Ethernet HBA Two disk drives



BAR Server Rack The BAR server rack (A Dell 4210 PowerEdge 42U Cabinet) is an industry-standard 42U rack that can hold up to 13 BAR servers, 3 Gigabit switches, 2 SAN switches, 1 1U rack console, a 0U KVM (keyboard/video/mouse) switch, and 8 0U port expansion modules.

Features

Easy accessibility and excellent hardware security features

Integrated cable management Easy hardware installation featuresRack Console Rack console allows the system

administrator’s control station to mount directly into the rack without sacrificing the rack space needed for servers and other peripherals

15-inch LCD flat-panel monitor with height adjustment, keyboard and trackball, twin PS/2 connectors, and SVGA video output in a 1U package

Required when there are more than two BAR servers

Requires a KVM switch Monitor and keyboard/mouse kit available for configurations

with only 1 or 2 BAR Servers; KVM switch with rack console also available for these configurations

PDUThe power cords for the power distribution unit are region specific. All run at 16 AMPs and 208V. Americas/Asia NEMA L6-20 power cord Europe/Asia IEC 309-16 power cord.Rail Mounting Kit Easy-to-install tool-less

mounting rails and cable management arms



Servers and peripherals slide out of the rack without having to remove hardware or disconnect cables.

One rail kit is required for each BAR server.Console SwitchForm factor: 0U in a Dell RackRack console: 1 per KVM switchPort expansion

Up to 8 port expansion

Modules: modules; supports a total of 64 BAR ServersSystem ports: 8 CAT-5 slotsPower: Voltage: 100-240V AC, freq. 50-60HzVideo: 1600x1200, VGA, SVGA, XGA

ADAPTERSAdapters are devices that allow one system to connect to and work with another. An adapter can be a simple circuit that converts one set of signals to another, but the term also refers to devices that perform extensive processing such as network interface adapters (NICs) and fibre-channel host adapters.

Fibre-Channel HBAs

Fibre-Channel HBA FunctionIn the Teradata BAR environment, the HBAs transport SCSI (small computer system interface) traffic from the BAR server to the disk arrays. An HBA interfaces with fibre-channel-connected peripheral devices (including BAR tape drives, tape libraries, and disk units) and the BAR server. The HBA sends and receives the server SCSI protocol transactions, which initiate and drive device operations via fibre-channel frames which are sent to and from the device through optical fibre cables.

Fibre-Channel HBA ConnectivityThe BAR servers connect to the tape libraries and/or backup to disk Library, via fibre-channel, either directly or through a fibre-channel switch. Each BAR server has two fibre-channel host bus adapters.



Figure 11: HBA and NIC Fibre-channel Connectivity

SEE: Network Adapter Connectivity in this chapter.

FIBRE-CHANNEL HBA DESCRIPTIONThe fibre-channel adapter used for Teradata BAR solutions is the QLogic 2462. Dual-port fibre-channel adapter 266 MHz 4 Gigabit PCIe Multi-mode optic LC connectors 64-bit Single-integrated fibre-channel Auto-negotiation of fibre-channel

speed bit rate (1 Gbps or 2 Gbps) Automatic topology detection Concurrent support for SCSI and IP protocols Simultaneous initiator and target mode support Easy detection of activities through an LED panel 300,000 IOPS delivers high I/O (input/output) transfer rates

for storage applications. Intelligent interleaved DMA (iiDMA) Out-of-order frame reassembly (OfOFR) Multi-ID and N_Port virtualization ready - allows physical

ports to be part of multiple logical networks Universal boot support



Overlapping protection domains for continuous protection of internal data paths

T10 cyclic redundancy check (CRC) ensures end-to-end data integrity across SANs

Three LEDs per port display real-time status and link activity information

SEE ALSO: download the datasheet at http://download.qlogic.com/datasheet/41115/Datasheet%20-%20QLA2462%20%5BG%5D.pdf

Network AdaptersEvery BAR Server includes an Intel Pro1000 PT Gigabit Ethernet adapter.

Network Adapter FunctionThe Network Interface Card (NIC) is the physical card that plugs into a computer to allow it to have access to a network or to have the network be able to access it.

Network Adapter ConnectivityNetwork adapters connect the Teradata node to the gigabit switch, and the gigabit switch to the BAR server.

SEE: FIGURE 11: HBA AND NIC FIBRE-CHANNEL CONNECTIVITY

NETWORK ADAPTER DESCRIPTIONThe Network Interface Card (NICs) in use for Teradata BAR solutions is the Intel Pro 1000. It has four Gigabit Ethernet copper server connections in a single PCI Express slot.

SEE ALSO: download the product brief at http://www.intel.com/network/connectivity/products/prodbrf/pro1000_pt_desktop_adapter.pdf

SWITCHESA switch is a network device that cross-connects stations or LAN segments. LAN switches are able to route traffic. Network switches are increasingly replacing shared media hubs in order to increase bandwidth.


http://www.intel.com/network/connectivity/products/prodbrf/pro1000_pt_desktop_adapter.pdf

http://www.intel.com/network/connectivity/products/prodbrf/pro1000_pt_desktop_adapter.pdf

http://download.qlogic.com/datasheet/41115/Datasheet%20-%20QLA2462%20%5BG%5D.pdf

http://download.qlogic.com/datasheet/41115/Datasheet%20-%20QLA2462%20%5BG%5D.pdf


LAN Switch: Teradata 6535 Gigabit Switch (Copper Ethernet)

SEE ALSO: 6535 OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM022524&BV_SessionID=@@@@0975951390.1161899350@@@@&BV_EngineID=cccfaddjekhfddecfngcfgldhkgdgfk.0

SEE ALSO: Instructions for accessing OCIs through the Employee Portal






LAN Switch FunctionIn the LAN-based architecture, the Teradata 6535 Gigabit switches provide the connectivity and data paths between the Teradata nodes and the BAR servers. The Teradata 6535 gigabit switch plays an important role by optimizing the data flow between the Teradata nodes and the BAR servers.

LAN Switch ConnectivityFigure 12: LAN Switch Connectivity

The Teradata node is connected to the BAR server via two private Gigabit Ethernet LAN connections.

LAN Switch DescriptionThis high-performance gigabit Ethernet switch (Dell™

PowerConnect™ 5324) is customized for the BAR LAN-based architecture. It features robust security capabilities and easy remote Management. It is a Managed Switch in that it supports a console interface for configuration, and it also supports http connections (once the IP address and IP mask have been set).Table 5: 6535 Gigabit LAN Switch Feature Chart

Features Teradata BAR Gigabit Switch

Total Switch Capacity 48 GbpsMaximum Forwarding Rate 35.6 MppsBuilt-in Gigabit Ethernet Ports

24 Copper Gigabit Ethernet ports (10/100/1000Base T)

Fibre-Capable Gigabit Ethernet Ports

4

Edge Authentication via 802.1x

Supports single and multiple host access

802.1Q VLAN Up to 247 VLANs802.1p Priority YesManagement Access Profiles YesGVRP YesQuality of Service Yes, L2/L3-aware



Features Teradata BAR Gigabit Switch

Priority Queues 4Link Aggregation Yes, LACP and manual (IEEE

802.3ad)Multicast Support IGMP SnoopingSpanning Tree Support Spanning Tree and Rapid Spanning

Tree w/FastLinkRemote Management YesAuthentication Support RADIUS and TACACS+MAC-based Port Security YesManagement Traffic Encryption

SSLv3 and SSHv2

Dual Firmware Image Support

Yes

Configuration File Management

File upload and download

SNMP Support SNMPv2cRemote Logging SyslogIndustry-standard CLI YesCable and Transceiver Diagnostics

Virtual Cable Tester and Optical Transceiver Analysis

Form Factor 1U, Rackmountable

SEE ALSO: download the product data sheet at http://www.dell.com/downloads/global/products/pwcnt/en/pwcnt_5324_specs.pdf

RoHS Alert: o The 6535-0002-8090 Teradata BAR Gigabit Switch is

RoHS compliant.o The older version of the Gigabit Switch, 6535-0001-

8090, is not RoHS compliant and has been discontinued.

SAN Switches: Teradata 6533 and 6534 SAN Switches (Fibre-channel)

SEE ALSO: Teradata 6533/6534 Fibre-channel SAN Switcheshttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM003372&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0



https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM003372&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0



http://www.dell.com/downloads/global/products/pwcnt/en/pwcnt_5324_specs.pdf


SAN Switch FunctionIn a LAN-based BAR configuration, the Teradata 6533 and 6534 switches are storage area networking (SAN) products for data storage backup and recovery applications in a shared storage environment. We also use them to connect storage devices to BAR servers. SAN Switches are required for all 9205 CDL installations.

NOTE: SAN switches are not advocated in the Teradata BAR direct-connect architecture Although it is technically possible to do that, we don’t do it because of potential Teradata node interference issues. If you reset on one node, it will cause a loop initialization protocol (LIP).

SAN Switch Connectivity Figure 13: SAN Switch Connectivity

SAN switches are required for all 9205 CDLs (Clariion Disk Libraries). Due to limited slots on the 9205 CDL, SAN Switches are needed to provide connectivity between the BAR Servers and the CDL.

SAN Switch DescriptionTeradata 6533 and 6534 are industry-standard, RoHS-compliant, fibre-channel SAN switches that provide basic SAN functionality. They support both the FC-AL (fibre-channel arbitrated loop) and “fabric” operation of the SAN as well as the use of “zoning” where necessary or desired to partition the SAN. They are certified for use with the following systems:The 6533 and the 6534 fibre-channel switch are sourced from Sun StorageTek and manufactured by Brocade and McData. 9200 SL500 Modular Tape Library 9202 SL8500 Modular Tape Library system 9205 Clariion Disk Library Legacy Teradata fibre-channel tape libraries



Table 6: Fibre-channel Switch MatrixTeradata 6533 (Brocade Silkworm

4100)Teradata 6534 (McData Sphereon

4500)HARDWARE

16-port Fibre-channel Switch 24-port Fibre-channel Switch (1U) (RoHS compliant)

Includes an 8-port upgrade. Two can be added for a total port count of 32.

Standard (RoHS compliant) Rail Kit. You need one per Switch (6534-2001-8090).

4Gb Long Wave SFP Fibre-channel supports connections up to 6.2 miles (10 km). (You need one per port.)

Optional McData (RoHS compliant) Management Cabinet has space for up to 32U of components.

OPTIONAL SOFTWAREFabric Watch Software (SAN traffic monitoring, management software)

Sphereon 4500, ISL Trunking Software (Logically groups multiple ISLs into a single link)

Extended Fabric Software (SAN distance extension software)

Sphereon 4500, Element Manager Software (used in conjunction with EFC Manager Server and only required when ordering the EFC management server and Sphereon 4500 switches. You’ll need one copy per switch)

ISL (inter switch link) Trunking Software (SAN optimization software)Remote Switch Software (Remote access software)Advanced Performance Monitor Software (Expanded monitoring software)Secure Operating System Software (Customizable security software for SANs.)

SEE ALSO: product data sheet sTeradata 6533 http://www.brocade.com/san/pdf/datasheets/SW4100_DS_05lr.pdf

Teradata 6534 http://www.storagetek.com/upload/documents/495.pdf


http://www.storagetek.com/upload/documents/495.pdf

http://www.brocade.com/san/pdf/datasheets/SW4100_DS_05lr.pdf


TAPE LIBRARIESIn data storage, a tape library is a collection of magnetic tape cartridges and tape drives. An automated tape library is a hardware device that contains multiple tape drives for reading and writing data, access ports for entering and removing tapes, and a robotic device for mounting, dismounting, and moving the tape cartridges between slots without human intervention.

SEE ALSO: Teradata 9200 SL500 Modular Library Systemhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681261&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0Teradata 9202 SL8500 Modular Library Systemhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681246&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0


Choosing a LibraryTeradata offers a range of tape libraries for the backing up and archiving of data. They are designed to handle the needs of data warehouses from small SMP systems (50 to 400GB) to very large MPP systems (with tens of terabytes of data).There are two options to consider for tape storage: the 9200 (SL500) and 9202 (SL8500). Both of these tape libraries are designed to provide high performance when backing up, archiving, or restoring data. Each library has been designed to scale for future growth, and they both use advanced robotics to support a mixture of environments. For the best initial library system footprint, it is important to consider both the future growth of the customer’s Teradata system as well as their enterprise needs. Any need above ten tape drives and the 9202 should be considered.The Teradata 9200 and 9202 modular tape library systems are integral components of the Teradata BAR environment, providing a protected repository for the customer’s data. Teradata tape libraries may also be incorporated into a comprehensive backup to disk solution.


https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681246&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0







Table 7: Library Comparison Matrix9200 9202

Nodes 1 to 18 1 to 64Drives 1 - 18 1 - 64Cartridge Slots Up to 410 (Tape Centric) Up to 10000Maximum CapacityUltrium 2 (LTO2) 82 TB 2,000 TBUltrium 3 (LTO3) 164 TB 4,000 TB9840C N/A 400 TB9940B N/A 2,000 TB

Teradata 9200SEE ALSO: Teradata 9200 OCI at: https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681261&BV_SessionID=@@@@0238055004.1167950043@@@@&BV_EngineID=cccgaddjkgjeikecfngcfgldhkgdgfl.0

9200 FunctionThe Teradata 9200 SL500 Modular Library System is an integral component of the Teradata environment that provides the backup, archive, and restoration services for the Teradata system.

9200 Connectivity The 9200 can be connected either directly to the Teradata nodes or, in the LAN-based architecture, to a BAR server. In the direct-attached architecture, a dedicated fibre-channel host bus adapter is required in the node. In the LAN-based architecture, a dedicated Gigabit adapter is required in the node.

9200 Connectivity, LAN-Based Architecture

In a LAN-based system, management of backup and restores are handled by the BAR servers for Teradata with a gigabit switch providing the interconnectivity between the two.


https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681261&BV_SessionID=@@@@0238055004.1167950043@@@@&BV_EngineID=cccgaddjkgjeikecfngcfgldhkgdgfl.0




Figure 14: 9200 Fibre-channel Connectivity, LAN-Based Architecture

9200 Connectivity, Direct-Attached Architecture

In the legacy direct-attached approach, the tape drives and library are directly attached to the Teradata system and the Teradata nodes initiate and run the backup/restore. Figure 15: 9200 Fibre-channel Connectivity, Direct-Connect Architecture



9200 DescriptionThe Teradata 9200 (SL500) modular library system from StorageTek is our entry-level library. It fits into an industry-standard 19-inch rack, or in a rack specifically designed for the 9200.Customers that need more than ten tape drives should consider the 9202 (SL8500).

Scales from 30 to 410 LTO cartridge slots Stores up to 164 terabytes in a standard 19-inch, 40U cabinet Heterogeneous attached and mixed media support Hot-swappable drives Ethernet and serial ports for diagnostics and reporting Redundant, hot-swappable power supplies with redundant fans Modular designed allows for complete library system or installation into customer’s racks.

SEE ALSO: product data sheethttp://www.storagetek.com/upload/documents/TC0003I_SL500tape_DS.pdf

Teradata 9200 Components

Modules

The 9200 is designed around three modules which are the basis for building the Library. Each module is 8U and a total of five (5) modules can be installed in a rack. There are three types of modules: Base, Drive Expansion, and Cartridge Expansion.

Base Module Required module Two (2) drive bays 30 or 50 cartridge slots 5-slot cartridge access port Robotics


http://www.storagetek.com/upload/documents/TC0003I_SL500tape_DS.pdf


Manages the complete library system

Drive Expansion Module Four (4) drive bays 50 or 90 cartridge slots 10-slot cartridge access port Most popular module for Teradata configurations Teradata-aligned due to drive-to-node relationships

Cartridge Expansion Module Additional 130 cartridge slots No cartridge access port Generally will not be used in a Teradata configuration

Teradata 9200 Tape Drives

The following table shows the drive options that are available for the Teradata 9200. Table 8: 9200 library-to-tape matrix

Drive TypeMaximum Drives per

Library

Total Storage

Slots

Tape Capacity

Library Capacity

Transfer Rate per drive/node

Ultrium 2 18 410 200 GB 82 TB *30 MB/sec (108 GB/hr)

Ultrium 3 18 410 400 GB 164 TB *80 MB/sec (288 GB/hr)

*These rates are the specified rates. Actual rates may vary significantly, based on the backup environment.

SEE ALSO: For more information about tape drives, see the Tape Drive section of this chapter.



Power

The base module and the drive expansion modules require power to operate the robotics, tape drives and other components. There are two methodologies available for connecting the modules to power: use of the internal power distribution units in the frame, or connecting each module directly to the data center’s power grid. (A cartridge expansion module is designed to only provide storage space for tape cartridges and therefore does not require power.) The basic rules for power are: When the 9200 SL500 is configured with the 9200 SL500

frame, internal power distribution units are required. When the 9200 SL500 is packaged and configured as a

deskside unit, region-specific external power is required. When the 9200 SL500 is to be installed in a customer-

provided rack, region-specific external power is required.

9200 Library ConfigurationsWhen configuring a 9200, you need to determine the quantity of tape drives. The minimum number of tape drives is 1 and the maximum number of drives is 18. Tape drives may be directly or indirectly connected to the nodes.

NOTE: For MPP nodes, the minimum ends up being 2 because we always use the bundled version of the base modules. Technically, a minimum of one is needed.

Teradata 9202SEE ALSO: The Teradata 9200 SL500 Modular Library System OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681261&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0

9202 FunctionThe Teradata 9202 (StorageTek SL 8500) modular library system is an integral component of the Teradata environment that provides the backup, archive, and restoration services for the Teradata system. It is designed to handle data warehouse storage from SMP systems to very large MPP systems with tens






of terabytes of data, multiple Teradata systems, and data center backup consolidation.

9202 Connectivity The 9202 can be connected either directly to the Teradata nodes or, in the LAN-based architecture, to a BAR server. In a direct-attached configuration, a dedicated fibre-channel host bus adapter is required in the node. In the LAN-based architecture, a dedicated Gigabit adapter is required in the node. The Teradata 9202 requires the Teradata 9201 Automated Cartridge System Library Software.

ACSLS

The ACSLS is the interface between the tape management software and the 9202, controlling and managing the robotics and library system.Housed on a separate server, the ACSLS software allows multiple systems (each with different tape management software, such as NetVault and NetBackup), to share the library.

SEE ALSO: For more information about ACSLS, see the ACSLS section of this chapter.

Figure 16: 9202 Fibre-channel Connectivity - Indirect



9202 Connectivity, LAN-based Architecture

In a LAN-based system, management of backup and restores are handled by the BAR servers for Teradata with a gigabit switch providing the interconnectivity between the two. NICFigure 17: LAN-Based Homogeneous Library for Teradata

NOTE: As of this writing, we are limited to two connects per server, so if there are more switches the networks will be partitioned.



Figure 18: LAN-Based Heterogeneous Shared Library between Teradata and Open Systems

9202 Connectivity, Direct-Attached Architecture (MP-RAS UNIX Systems Only)

In the legacy direct-attached approach, the tape drives and library are directly attached to the Teradata system and the Teradata nodes initiate and run the backup/restore. Figure 19: Fibre-channel Connectivity



9202 Description The 9202 is a high-end, scalable, high performance modular library system for the Teradata environment. It provides the following additional values above the 9200: Mixed tape management application (i.e. NetVault and NetBackup connecting to the same library) via ACSLS Mixed tape technologies for different applications (e.g. Ultrium 2, Ultrium 3, 9840C, 9940B in the same library) Enterprise consolidation of multiple Teradata footprints and libraries Enterprise consolidation of Teradata and Enterprise Servers and Systems to a single library or set of libraries

SEE ALSO: product data sheethttp://www.storagetek.com/upload/documents/TC0018F_SL8500_DS.pdf

9202 COMPONENTSFigure 20 provides an overview of the Teradata 9202 modular library system and its components. The library is designed in a “U” configuration, with the tape drives located in the rear of the unit, the cartridge slots located in the middle, and the cartridge access ports located in the front. The robotics run on four (4) tracks with the option of having up to two (2) robots per track.


http://www.storagetek.com/upload/documents/TC0018F_SL8500_DS.pdf

http://www.storagetek.com/upload/documents/TC0018F_SL8500_DS.pdf


Figure 20: The Teradata 9202 Modular Library System

The Teradata 9202 modular library system is a scalable product designed around the concept of components (building blocks) to permit easy ordering and smooth expansions in the field. There is one model of the 9202 that forms the basic building block of the library. The components are described below.

Slots

The minimum number of cartridge slots is 1448. All Teradata 9202s are shipped with the minimum level unless greater capacity is configured.

Modules

Every library contains three basic frames: the Customer Interface Module, the Drive Module, and the Base Module. A fourth frame, the Expansion Module, is added when more than 1448 slots are desired, allowing the library to scale to 10000 slots.



Customer Interface Module:

Located at the front of the library, this module is the primary interface through which the customer can perform maintenance, monitor performance, change diagnostic and cleaning cartridges, or easily replace robotics should they fail.

Drive Module Houses the tape drives, drive power supplies, electronic control module, and power distribution.

Base Module Houses tape cartridge slots and pass through port

Expansion Module

Houses tape cartridge slots

Teradata 9202 Tape Drives

The following table shows the drive options that are available for the Teradata 9202. For more information about tape drives, see the Tape Drive section of this chapter.Table 9: 9202 Library-to-Tape Matrix

Drive Type

Maximum Drives

per Library

Total Storage

Slots

Tape Capacity

Library Capacity

Transfer Rate per drive/node

9840C64 10000 40 GB 400 TB *30 MB/sec (108 GB/hr)

9940B64 10000 200 GB 2000 TB *30 MB/sec (108 GB/hr)

Ultrium 264 10000 200 GB 2000 TB *35 MB/sec (126 GB/hr)

Ultrium 364 10000 400 GB 4000 TB *80 MB/sec (288 GB/hr)

*These rates are the specified rates. Actual rates may vary significantly, based on the backup environment.

SEE ALSO: For more information about tape drives, see the Tape Drive section of this chapter.

Robotics

To eliminate cabling, each library has four rails which supply power for the robots. Instructions to the robots are transmitted wirelessly. Two robot features are available for the library.

4 S-RobotsWith four robots, one is assigned to each rail and can access up to 16 tape drives plus all cartridges along the rail path. The



robots are independent of each other. Should one robot fail the other three can continue to operate, however the tape drives and cartridges assigned to the failed robot will not be accessible until the failed robot resumes operations or is replaced.

8 S-RobotsWith eight robots, two are assigned to each rail and share access to as many as 16 tape drives. The cartridges along the rail path are subdivided into two, with half assigned to robot 1 and the other half to robot 2. As with the 4 S-Robots, the 8 S Robots are independent of each other; however the robots sharing a rail are cognizant of the other and are managed for optimum performance.Unlike the 4 S-Robots, the 8 S-Robots provide redundancy to the Library since each rail has two robots. In the event of a robot failure, the active robot on the rail will push the failed robot to the service access area and take over management of the rail. Once the failed robot has been repaired and returned to service, normal shared operations on the rail will resume.

Power

The library has three power components: Primary, Robotic, and Connection. Each of these is available with full redundancy. The primary system provides power to the tape drives and library as a whole, the robotic system provides power for the robots, and the connection system is the physical connection to the data center’s power grid.

9202 Library ConfigurationsWhen configuring a 9202, the user needs to determine the type and quantity of tape drives. The minimum number of tape drives is 1 and the maximum number of drives is 64. Tape drives may be directly or indirectly connected to the nodes.

Teradata 9201 (StorageTek ACSLS)SEE ALSO: The ACSLS Server and ACSLS Software 7.1 OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA679458&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0






9201 FunctionAutomated Cartridge System Library Software (ACSLS) controls and manages the robotics of mid-to-large robotic tape systems. It enables the consolidation and centralization of BAR functions across multiple systems, each with different tape management software (such as NetVault or NetBackup), allowing them to share a single tape library system. ACSLS is required for the Teradata 9202 and is an optional connection for the 9200.

9201 ConnectivityFigure 21: 9201 Connectivity

The ACSLS server is directly connected to the robotic control card on the library.

9202 Description Remote connections to ACSLS server to manage the library RoHS compliant Directly connected to the robotic control card on the library Multiple libraries managed on single server High availability with two-server configuration Firewall Security allows ACSLS to be used behind a firewall

while the client software makes requests across the firewall from external locations

Restricts incoming connections for ACSLS communications to a single TCP port for all registered program numbers

Support for mixed media Required for all 9202 SL8500 configurations.

SEE ALSO: product data sheethttp://www.storagetek.com/upload/documents/GC0004B_ACSLS_ DS.pdf

9201 COMPONENTSSince ACSLS is housed on its own server, it has two components: software and hardware.


http://www.storagetek.com/upload/documents/GC0004B_ACSLS_DS.pdf

http://www.storagetek.com/upload/documents/GC0004B_ACSLS_DS.pdf


Software

The ACSLS server runs on the Sun Solaris operating system. To enable communication between Solaris and Windows whenever BAR servers running Windows are in the configuration, LibAttach software is required. LibAttach is not required for BAR Servers running SUSE Linux, or for direct-attached to MP-RAS UNIX Teradata nodes.The ACSLS software is included and preloaded on the ACSLS Server but the software must be licensed. Since a single ACSLS server can manage multiple libraries simultaneously, licensing is based on the total number of slots for all of the libraries being managed.

Hardware: ACSLS Server V240

The ACSLS Server V240 is sourced from Sun and based on a Sun Sunfire V240 Server. It has been designed to provide a platform for library management and supports both standard and high-availability requirements.

9201 Configuration

Sharing Drives with Different Tape Management Software

Sharing tape drives with open systems typically requires that both systems use the same tape management software. With ACSLS, a shared library may accommodate systems with differing tape management systems.By dedicating tape drives to specific applications and the 9201 ACSLS server, ACSLS enables multiple systems, each with its own Tape Management Software, to share a single 9202.

SEE: The 9201 OCI at: https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA679458&BV_SessionID=@@@@1093167239.1167951856@@@@&BV_EngineID=cccgaddjklkmlidcfngcfgldhkgdfgi.0

SEE ALSO: Figure 18 in the Teradata 9202 Library Configurations

TAPE DRIVES

A tape drive reads and writes computer data to magnetic tape for the purpose of backup, archive, and restore: it writes the data to tape, one tape at a time. The data on magnetic tapes can also be erased.


http://searchStorage.techtarget.com/sDefinition/0,,sid5_gci211633,00.html


https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA679458&BV_SessionID=@@@@1093167239.1167951856@@@@&BV_EngineID=cccgaddjklkmlidcfngcfgldhkgdfgi.0




SEE ALSO: Teradata 9200 SL500 Modular Library Systemhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681261&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0Teradata 9202 SL8500 Modular Library Systemhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA681246&BV_SessionID=@@@@0893235363.1160089228@@@@&BV_EngineID=ccccaddimhmiiikcfngcfgldhkgdgfl.0

SEE ALSO: Accessing OCIs through the Employee Portal

Sharing Tape DrivesAll Teradata tape libraries can be shared with another Teradata system. Typically, a shared Library has dedicated tape drives. For example, a library shared between a Teradata production system and a Teradata development system would have a tape drive dedicated to each system.A fibre-channel switch allows multiple Teradata systems to share tape drives, thereby providing better utilization of a customer’s tape resources. There is a very important distinction that must be made. All Teradata tape libraries can be shared between several systems by directly connecting the systems to tape drives in the library/silo; the difference is that the 6533 and 6534 fibre-channel switches permit the sharing of the drives themselves.Figure 22: Shared Library Comparisons









The diagram on the left shows two Teradata systems sharing a library but connected to a specific tape drive. The diagram on the right shows the library sharing the tape drives.

IMPORTANT NOTE: Unless the 9201 ACSLS server is added to the configuration, both systems must use the same tape management software.

Tape Drive FunctionTape drives store data sequentially: specific data is accessed by starting at the beginning and rolling through the tape until the desired data is reached.

Tape Drive Backup SpeedWhile industry literature describes much higher performance for backup to disk solutions, our Teradata testing has shown that in the Teradata environment the Ultrium 3 (LTO3) tape drive when configured with 5450 nodes achieves equivalent performance to a backup-to-disk solution. At first glance this does not seem logical, however the reason for the difference has to do with the technical differences in the way Teradata and typical applications interact with their primary disk.Teradata interacts with its primary disks via continuous I/O where data is continuously being written or read. Most applications are intermittent users of I/O, reading then stopping or writing then stopping. The flow of data during a backup also follows a similar pattern, with Teradata sending its data continuously from its disk arrays and typical applications going through a directory structure with many “start/stop” actions. Backup-to-disk solutions are able to quickly start and stop writing whereas there is a mechanical time delay for tape media: hence, disk is able to write faster. This does not hold true when a continuous stream of data is sent to tape, where tape is capable of equivalent and sometimes faster performance. The reason for this is that once the tape drive heads have physically come into contact with the media, the tape drive is able to continuously stream data onto the tape media.It is important to note that equivalent performance is achieved against the latest high speed LTO3 tape drives. Previous generations of tape drives, such as LTO2 or LTO1, show diminishing equivalences, meaning that statistical differences



begin to become relevant enough to show the expected faster performance of disk.Teradata offers the following Fibre-channel tape drives as outlined below. Table 10: Library to Tape Matrix

Library Drive Type

Maximum Drives per

Library

Total Storage

Slots

Tape Capacity

Library Capacity

Uncompressed

(Native)

Transfer Rate per

drive/nodeUncompresse

d(Native)

9200Ultrium 2 18 410 200 GB 82 TB *30 MB/sec

(108 GB/hr)

Ultrium 3 18 410 400 GB 164 TB *80 MB/sec(288 GB/hr)

9202

9840C 64 10000 40 GB 400 TB*30 MB/sec(108 GB/hr)

9940B 64 10000 200 GB 2000 TB*30 MB/sec(108 GB/hr)

Ultrium 2 64 10000 200 GB 2000 TB*35 MB/sec(126 GB/hr)

Ultrium 3 64 10000 400 GB 4000 TB*80 MB/sec(288 GB/hr)

*These rates are the specified rates. Actual rates may vary significantly, based on the backup environment.Some of the major differences between these drives and their media are shown in the Table 12. Complete feature charts are in the following sections of this chapter.

Tape Drive ConnectivityThe tape drives are located in the tape libraries and use fibre-channel connectivity. In the LAN-based architecture, the tape drives connect to the BAR servers, while in the direct-connect architecture the tape drive connects to the Teradata nodes.



Description: Ultrium (LTO) Fibre-channel DrivesLTO2 LTO3

Table 11: LTO2/LTO3 Tape Drive Common FeaturesLTO Common Features

Built-in read-after-write verification for a high level of data integrityLong data life (15-30 years)Data rate matching (DRM)Intelligent LTO-DC dual-mode compression algorithmFailsafe leader capture mechanismLTO-cartridge memoryLibrary and tape tools software to verify successful installation and troubleshoot problemsSCAM (SCSI configured automatically)-1 compliant store up to 400 gigabytes of native data and move data at rates as high as 80 megabytes per second.2 Gigabit fibre-channel interface Enhanced data protection with ratings at more than 100,000 loads and unloads and one million tape passes before failure

Table 12: LTO2/LTO3 Tape Drive Differing Features



LTO Drive Differing FeaturesFeature LTO-2 LTO-3

Performance

Please note that these are vendor specifications, not Teradata laboratory numbers. Results at customer sites may be quite different.

Tape load and thread to ready

15-24 sec 18 sec

Average file access time (first file)

64-75 sec 72 sec

Maximum/average rewind time

98/49-104/5 sec

98/49 sec

Unload time 13-19 sec 19 secData transfer rate, native (uncompressed)

32-35 MB/sec 80 MB/sec

Data transfer rate, compressed (2 :1)

60-70 MB/sec 160 MB/sec

WORM media support

NO YES

Data rate matching Ultra160, 2 Gb FC

Ultra320, 2/4 Gb FC

Capacity Capacity, Native (uncompressed)

200 GB 400 GB

Head channels 8 16Bit Density 7.86 kbpi 10.2 kbpiNumber of Tracks 512 704Media Length 609 m 680 m

Availability: Mean time between failures (MTBF)

Power on 250,000 hr@100% duty cycle

250,000 hr@100% duty cycle

Head life 60,000 hr 60,000 hrUncorrected bit error rate

1x10-17 1x10-17

Undetected bit error rate

1x10-27 1x10-27

Media Compatibility

Read/write Ultrium 2Ultrium 1

Ultrium 3, Ultrium 2,Ultrium 1 (read only)

Emulation modes LTO Ultrium 2, Ultrium

LTO Ultrium 3

Supports new Write-Once Read-Many (WORM) HP Ultrium Data Cartridges.

No Yes



Media: LTO Tape Cartridges

The Ultrium cartridge is smaller than most existing single-reel tape cartridges.

NOTE: Teradata Tape Libraries use Ultrium drives manufactured by Hewlett Packard and supplied to us through Sun/StorageTek. Some Legacy Ultrium Tape Drives sold in the past by Teradata were manufactured by IBM and supplied to us through Sun/StorageTek. Tape media written by either tape drive manufacture’s tape drives are completely interchangeable.

Table 13: LTO2/LTO3 Tape Media Common FeaturesLTO Media Common Features

Storage space: 384 data tracks, divided into four regions (data bands). Each data band is bounded on top and bottom by a band of servo information. Each data band can contain up to 96 tracks. Data bands are filled one at a time.Shock resistant cartridge mechanism. High precision coating for optimum data integrity Read-While-Write (RWW) capability allows real-time verification of written data.Single-hub design allows for optimal packing of media. High capacity is further enhanced by the use of an LTO Technology data compression algorithm with two control modes to maximize compression efficiencyLTO-CM is a non-contacting passive RF interface embedded in the cartridge which allows remote reading of the contents of the built-in 4KB (32 Kbits) of non-volatile memory. Calibration information, manufacturers' data, and information about initialization may be retrieved without having to insert the tape cartridge into a drive.Dedicated Dual Servo: The servo bands are pre-written on the tape during the tape cartridge manufacture process. If one servo element becomes defective, or if a portion of the servo code on the tape becomes corrupt, the head will continue to track as a result of the second "redundant" servo system.Longitudinal position words encoded within the servo frames allow access to absolute locations down the length of the tape.Two levels of error correction can provide recovery from longitudinal media scratches.



LTO Media Common FeaturesUniversal cleaning cartridge maximizes performance of Ultrium LTO tape drive.

Table 14: LTO2/LTO3 Tape Media Differing FeaturesLTO Media Differing Features

Feature LTO-2 LTO-3

Capacity: Up to 200/400*GB of data (* with 2:1 compression)

Up to 400/900 *GB of data(* with 2:1 compression)

Data Transfer Rate:

30/60*MB per second (* with 2:1 compression)

80/160*MB per second (* with 2:1 compression)

SEE: product information at: http://www.ultriumlto.com/ltomedia.htm

Description: StorageTek Fibre-channel Drives The StorageTek Fibre-channel drives are fast, high duty cycle tape drives for enterprise applications.

T9840C T9940B

The T9840C is the logical choice for enterprise customers requiring extremely rapid data access, unmatched reliability and power at a significantly lower price point than disk-based solutions.

The T9940B stores greater amounts of historical data for critical business applications. Cost savings result from fewer drives being required, reduced SAN complexity, and simplified management.

Table 15: Fibre-channel Tape Drive Comparison Chart



Fibre-channel Drive FeaturesPerformance T9840C Drive T9940B Drive

Tape load and thread to ready 4 sec 18 sec (formatted)Average file access time (first file) 8 sec 41 sec

Average access time 12 sec 59 secMaximum/average rewind time 16/8 sec 90/45 secUnload time 4 sec 18 secData transfer rate, native (uncompressed) *30 MB/sec

Data transfer rate, (compressed) *70 MB/sec

Capacity T9840C Drive T9940B DriveNative (uncompressed) 40 GB 200 GB

Availability T9840C Drive T9940B Drive(MTBF) Mean time between failures

Tape path motion

216,000 hr @ 70% TPM duty cycle

196,000 hr @ 70% TPM duty cycle

Power on 290,000 hr @ 100% duty cycleTape load 240,000 hr @ 10 loads/day (100,000

loads)Head life 8.5 yr @ 70% TPM duty cycleUncorrected bit error rate 1x10-18Undetected bit error rate 1x10-33

Compatibility T9840C Drive T9940B DriveInterface (Fibre-channel) N & NL port, FC-

PLDA (hard and soft AL-PA capability), FC-AL-2 FCP-2, FC-TAPE

FC-PLDA (Hard and soft AL-PA capability), FC-AL-2 FCP-2, FC-TAPE

Emulation modes Native, 3490E, 3590

Native, T9940A, 3490E, 3590

Interface 2-Gb Fibre-channel, ESCON, ESCON for VSM, 2-Gb FICON for FICON and FICON Express channels

Read/write compatibility interface Proprietary format

Channel rate (Fibre-channel) 200 MB/sec (maximum instantaneous)*These rates are the specified rates. Actual rates may vary significantly, based on the backup environment.

SEE ALSO: product data sheethttp://www.sun.com/storagetek/docs/TC0024B_T9840C_DS.pdf


http://www.sun.com/storagetek/docs/TC0024B_T9840C_DS.pdf


MEDIA: STORAGETEK TAPE CARTRIDGES9840 9940

The StorageTek® 9840 tape cartridge was designed concurrently with the StorageTek T9840 tape drives to provide fast access to data and storage of up to 40 gigabytes of uncompressed data on a single cartridge.

The StorageTek® 9940 tape cartridge was designed with StorageTek T9940 tape drives to store up to 200 gigabytes of uncompressed data, or up to 400 gigabytes with 2:1 data compression, on a single cartridge.



Table 16: Fibre-channel Tape Media Comparison ChartFibre-channel Tape Media Comparison Chart

10 MB/sec Performance (Tape Speed)

T9840C Media T9940B Media

Read and write 2.0 m/sec (79 ips) - T9840A, 4.0 m/sec (158 ips) - T9840B, 3.4 m/sec (134 ips) - T9840C

2.0 m/sec (79 ips) T9940A, 2.4 m/sec (95 ips) T9940B

Search and rewind 11.0 m/sec (440 ips)Formulation Advanced meta l particle (AMP)Coercivity 1625+/-75Oersteds (130+/16.0 KA/m)Substrate Polyethylene naphthalate (PEN)Track-following servo Factory pre-recorded

Capacity T9840C Media T9940B Medianative (uncompressed)

20 GB (T9840 A/B), 40 GB (T9840C)

60 GB (T9940A), 200 GB (T9940B)

Availability T9840C Media T9940B Media

Long-length durability

6,500 write/read passes minimum (361 full file write/read passes minimum)

6,500 read/write passes minimum

Archival life 15–30 yearsShort-length durability 80,000 write/read passes minimum

Uncorrected bit error rate 1x10(-18)

Permanent errors 0Loads/unloads 10,000 minimum

Compatibility T9840C Media T9940B MediaSupported tape drives T9840A, T9840B, T9840C T9940A, T9940B

Number of tracks 288 (T9840A, T9840B, T9840C)

288 (T9940A), 576 (T9940B)

Form Factor Half inch, 3480/3490E Half inch, 3480/3490E



TERADATA 9204 BACKUP 2 DISKDisk-to-disk backup systems are reliable, but using standard disk alone creates other challenges, especially when longer term retention is required.

A disk-to-disk-to-tape solution is a two-tier backup strategy using both disk and tape technologies.

SEE ALSO: The Teradata 9204 Backup 2 Disk OCI https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM003488&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0SEE ALSO For an overview of backup to disk in the Teradata environment, see Chapter One, “Tapes and Disks: The Two-Tiered Strategy.”

SEE ALSO: Accessing OCIs through the Employee Portal

9204 FunctionThe 9204 is designed specifically to provide data protection and cost-effective online storage for archive and fixed content information. It is a disk-as-disk backup to disk solution, since it involves using disk drives behaving as disk drives (the disks are not pretending to be tape). A disk volume is assigned to each server. Each server then puts a filesystem on that volume.Data backups are then sent to that filesystem for storage.






9204 Connectivity Disk arrays are connected to one or more BAR servers via a disk controller hooked up to multiple host bus adapters (HBAs).

The 9204 connects to the BAR servers via HBA.

9204 DescriptionThe Teradata 9204 Backup 2 Disk (StorageTek FlexLine 680) solution is a next-generation, capacity-centric platform. A disk-based data management solution, it includes hardware consisting of controllers and disk arrays, as well as integrated software to manage and control the system.The Teradata 9204 Backup 2 Disk Library is a versatile, scalable, modular backup to disk system for Teradata. The product has been designed with modular components that allow flexible configurations. Two modules are available: the Library Controller Module and the Disk Array Expansion Module.

File system configuration Use with NetBackup storage units or NetVault virtual library Raw disk partition Failover capable Up to 58 TB Up to 600 MB/second Low-touch management Reliability



Highest efficient capacity availableTable 17: 9204 Features

Teradata 9204 B2D (StorageTek FlexLine 680)SpecificationsMaximum burst I/O rate:

200,000 IO/sec

Maximum sustained throughput:

772 MB/sec

Total cache size: 4 GBConnectivityHost interface 2 Gb/secHost connections 16 FC-AL direct attach or 4 FC-SW SAN

attachDrive interface 2 Gb/secDrive connections 4 Fibre-channelCapacityMaximum number of drives 232 drives, 116–500 GB blades

Compatible arrays FLC600Drive capacity SATA: 250 GB; blade: 500 GBMaximum number of FLC600 arrays 5

Drive connection SATADrive interface 200 MB/sec per connectionAvailability

Redundant componentsStorage controllers, Fibre-channel drive loops, cache memory, power supplies and cooling fans

Hot-swap components 500 GB blades, storage controllers, power supplies, cooling fans and battery backup

High-availability features

Automatic drive failure detection and rebuild using global hot spare drives, cache battery backup

RAID levels supported 1, 5, and 8CompatibilitySupported operating systems

Windows Server 2003, Solaris, AIX, SUSE Linux

ManagementStorage management software Web interface or CLI

Standard featuresOnline storage management, Storage class manager, Over subscription, Advanced fault management, Storage partitions (up to 255 hosts)

SEE ALSO: product datasheethttp://www.storagetek.com/upload/documents/DC0003E.pdf


http://www.storagetek.com/upload/documents/DC0003E.pdf


9204 COMPONENTS

Disk DrivesThe 9204 Backup 2 Disk uses 250GB 7200 RPM SATA disk drives. Two drives are grouped together into a carrier for a total of 500GB of raw disk space. The carriers in turn are installed into either the library controller module or the disk array expansion module. Disk drives are bundled and are not available for individual sale.

RAID–5The 9204 uses RAID-5 to provide data protection and redundancy. The RAID-5 factor for the 9204 is 0.80. To calculate the actual data space (ADS) available for data from Teradata, multiply the raw capacity by 0.80. The following chart outlines this calculation.Table 18: RAID-5 Factoring

Component Carriers Raw Space ADSLibrary Controller Module 16 8.0 TB 6.4 TBDisk Array Expansion Module – 10 TB 20 10.0 TB 8.0 TB

5TB Disk Array Upgrade Kit 10 5.0 TB 4.0 TB

It is important to remember, when determining the amount of space required to host data in a 9204, that the RAID-5 factor be applied. Otherwise, you risk not having enough capacity to host the data.

TERADATA ALERT: The 9204 Backup 2 Disk Library is not designed for use as primary storage. It may not be used in place of the Teradata Enterprise Storage or EMC Symmetrix Storage.

Backup 2 Disk Library Frame

The frame for the Backup 2 Disk Library has been designed to support up to ten (10) modules. The mixture of the module types is dependent on configuration implemented for the customer. The frame features heavy-duty construction to provide a stable and secure platform for the various Backup 2 Disk Library modules.The frame includes an external power cable, has four 60 AMP power strips, and can support up to 10 modules. There are two frames available: frame choice is dependent upon the region in which the customer’s data center is located.



Controller Module

The controller module is the primary building block of a 9204 Backup 2 Disk Library. It is sold as a bundle containing quad HBAs, 4GB cache and 16 500 GB disk carriers. A disk carrier consists of two 250GB 7200 RPM SATA disk drives.Figure 23: Library Controller Module

Quad Controllers 4 GB Cache May connect to a maximum of five

(5) expansion disk array modules Maximum raw capacity is 58 TB

The library controller module can connect to and manage a maximum of five (5) disk array expansion modules for a total of 58 TB of raw storage. RAID-5 is deployed to provide redundancy within the library.One library controller module can support up to four (4) BAR servers (8 data paths). This structure forms a “backup group.” A backup group is a library controller module and associated expansion disk array modules that are assigned to support four BAR servers and accompanied Teradata nodes. A backup group will always have a library controller module but may or may not have additional expansion disk array modules. How the backup group is designed is determined by the amount of Teradata customer data space contained in the associated cliques and the number of copies of that the customer desires to be retained on the Backup 2 Disk system.Rules: A library controller module can support up to four BAR

servers Library controller modules must be added for every four BAR

Servers. A quick rule of thumb: when there are more than four BAR Servers, divide the number of BAR Servers by 4 and round to the next whole number. The result is the number of library controller modules required.

Here is an example for a 20-Node System:20 Node system = 10 BAR Servers

10 ÷ 4 = 2.5 rounded to 3January 12, 2007 NCR Confidential 83

Document No. 541-0006487


Three Controller Modules would be required.

Disk Array Expansion Module

The Disk Array Expansion Module provides disk capacity for the 9204 Backup 2 Disk Library. It is designed to hold up to 20 500GB disk carriers and must be coupled with a library controller module. The Disk Array Expansion Module will be sold as two bundles, one half populated with disk carriers and a second fully populated with disk carriers.Figure 24: Disk Array Expansion Modules

A maximum of five (5) disk array expansion modules may be connected to one library controller module.



Typical Teradata 9204 ConfigurationFigure 25: Typical Teradata 9204 Configuration

TERADATA 9205 VIRTUAL TAPE LIBRARYVirtual Tape is still backup to disk, but the disk arrays are placed behind an internal server running an application that makes the disk array look like a tape library to the backup software application. When employing the two-tier strategy, it uses the backup software's tape-to-tape copy function to migrate data from virtual tape to physical tape.

SEE ALSO: The Teradata 9205 Virtual Tape Library OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM013052&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0

9205 Function The 9205 is a disk-based backup system that utilizes virtual tape technology to emulate tape libraries, tape drives, and tape media as a means of backing up Teradata.

9205 Connectivity

CDL Connectivity Front-end: Four 200 MB/s FC optical ports






Back-end (CDL server to CLARiiON disk array): Four 200 MB/s FC optical ports

The above numbers are per server. Double them for DL720 and DL740 models (except optional tape ports, which is two per server or four per system for the DL740).

NOTE: The tape ports may be configured, if desired, as front-end ports.

Back-End (Disk) Connectivity DL710 has four 200 MB/s fibre-channel arbitrated loops. The

DL720 and DL740 each have eight 200 MB/s fibre-channel arbitrated loops.

Multiple RAID groups are distributed across redundant loops to maximize bandwidth to disks.

9205 Description: CDL 710, 720, and 740The Teradata 9205 is sourced from EMC. Three of their CLARiiON® Disk Libraries are available from Teradata: the 710, the 720, and the 740.



Table 19: CDL Library Comparison Chart710 720 740

Failover Cold standby/Spare Dual channel/path

Linked Dual 720s

CLARiiON® CX700 Storage Arrays

Single Single Two in separate cabinets

Total Number of BAR Servers Supported

4 5 8

Maximum TB of User Space per Library

82.5 82.5 165

Number of Library Service Modules (a dedicated server that runs the tape emulation and virtualization engine)

Optional standby server

Two redundant active servers that run together

Two redundant active servers, each assigned to its own storage array

Standby server provides manual failover (inactive until needed and requires user intervention to activate)

Dual service modules can support up to 5 BAR Servers (10 Teradata Nodes). If one server fails, the other can manage the entire CDL until the failed server is repaired, although performance will be reduced when the CDL is running in failover mode.

Maximum Disk Array Enclosures (DAE)

15 per 9205-1005-8090 enclosure

Minimum DAEs One per enclosure is required to power up the arraysTeradata systems supported

SMP and MPP



710 720 740Number of CLARiiON® Disk Library Racks Required

Two 9 DAEs in one; 6 DAEs in the second The second rack is referred to as a “spillover” rack

as it houses only DAEs. A minimum of 1 DAE is required to power up the array.

SEE ALSO: product datasheethttp://www.emc.com/products/systems/clariion_disk/pdf/C1156_emc_disk_library_ds_ldv.pdf

9205 COMPONENTS

Table 20: CDL Library ComponentsComponent Comments 710 720 740

Required ComponentsDisk Library FC DAE

Required operating system infrastructure drives: one per library

Yes Yes Yes

Library Array Two per library No No YesActive Engine Failover Software

One per library No Yes Yes5M Cable Two per DAE required for a

second “spillover rack” Yes Yes YesFibre-channel LC-LC Cables

Two per BAR Server

Library Rack One per library: a second is required when the DAEs exceed 9. Industry standard 40U. All three libraries use the same rack.

Yes Yes Yes

DAE with Drives 500 GB, 7200 RPM low-cost fibre-channel disk drives Yes Yes Yes

Library Service Module (Windows 2003)

One per system; the modem connects to this server (for EMC support services). Customer must have a phone line for the modem.

Yes Yes Yes

BAR Servers You need one management server and at least one data server.

Yes Yes Yes

Fibre-channel Adapters

Two per BAR server. Yes Yes YesFibre-channel Switches

The 9205 has only four ports and requires dedicated FC switches between the BAR servers and the library to ensure enough connectivity. The number of switches required depends on the relationships between the number of ports on the switch, the number of BAR servers, and the number of 9205s.

Yes Yes Yes


http://www.emc.com/products/systems/clariion_disk/pdf/C1156_emc_disk_library_ds_ldv.pdf

http://www.emc.com/products/systems/clariion_disk/pdf/C1156_emc_disk_library_ds_ldv.pdf


Component Comments 710 720 740Required ComponentsOptional Components

Standby Server For manual failover (user must activate when needed) Yes No No

Spillover Rack For additional DAEs only Yes Yes YesRegionally Specific

Power Cord Required for the rack Yes Yes YesModem One per system Yes Yes Yes

You can place up to 6 DAEs in a single spillover rack. The 6 DAEs are connected to the array with two 5M cables per DAE.

Typical Teradata 9205 ConfigurationSEE ALSO: Section 3.0 (starting on page 18) of the 9205 OCI has details for designing various combinations of Teradata Nodes, BAR Servers, and 9205 Libraries. https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM013052&BV_SessionID=@@@@1320760082.1162595403@@@@&BV_EngineID=cccdaddjfgidgjhcfngcfgldhkgdgfk.0


https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM013052&BV_SessionID=@@@@1320760082.1162595403@@@@&BV_EngineID=cccdaddjfgidgjhcfngcfgldhkgdgfk.0




Figure 26: Typical Teradata 9205 Configuration


3: SOFTWARETERADATA TOOLS AND UTILITIES

SEE ALSO: Teradata Tools and Utilitieshttp://www.info.ncr.com 1. Select the General Search check box.2. In the Publication Product ID box, type the book number: B035-2029-096C

ARCTeradata ARC is the archive/recovery interface program to Teradata and is sold with the backup applications. No matter what BAR solution is used, ARC is always involved.

FunctionTeradata ARC creates files when you archive databases, individual data tables, selected partitions of primary partition index (PPI) tables, or permanent journal tables from the Teradata Database. You provide Teradata ARC with such files when you restore databases, individual data tables, partitions of tables, or permanent journal tables back to the Teradata Database. Teradata ARC writes and reads sequential files from a

Teradata client system to archive, restore, and recover, as well as copy Teradata Database table data.

With the ARC utility you can copy a table and restore it to another Teradata Database. It is scalable and parallel, and can run on a channel-attached client, network-attached client, or a Teradata node.

ARC interfaces to third-party products to support backup and restore capabilities in a network-attached or a direct-attached environment.

The Teradata ARC utility, through its associated script language, provides an interface between Teradata’s Open Teradata Backup (OTB) solutions and the Teradata Database.

Supported Platforms Channel-attached systems Linux RedHat, SUSE Linux


http://www.info.ncr.com/

Microsoft® Windows® 2000/XP/Server 2003 systems MP-RAS systems

ARC Terminology OverviewThe terms backup and dump are often used interchangeably with archive. Restore, which is a specific Teradata ARC keyword and the name of a Teradata ARC operation, is part of the recovery process. There is no Teradata ARC statement called “recover.” In addition to restore, recovery entails other operations, such as returning data tables to their state following their modification (called rolling forward), returning data tables to the state they were in before they were modified (called rolling back), and so on. For further explanation, see the “Archive/Recovery Control Language” chapter of the Teradata Archive/Recovery Release as outlined below.The difference between copy and restore is in the kind of operation being performed: A restore operation moves data from archived files back to

the same Teradata Database from which it was archived or to the same Teradata Database on a different system, so long as the database DBC is already restored.

A copy operation moves data from an archived file back to a Teradata Database, not necessarily to the same system, and creates a new table if one does not already exist on the target database. When you copy selected partitions, the table must exist and be a table that was previously copied as a full-table copy.

ARC and OTB SolutionsIn general, the purpose of Teradata’s OTB solutions is to automate Teradata ARC script generation, reducing the need for an in-depth knowledge of Teradata ARC functions. The OTB solutions also provide tape management, device management, job management, and device I/O.An in-depth knowledge of Teradata ARC will only be necessary if you need to analyze performance problems or develop Teradata ARC scripts that perform operations that are not supported by a particular OTB. Such in-depth knowledge may be needed by system administrators, database administrators, and other technical personnel responsible for maintaining a Teradata database. If you need that level of knowledge, see the



instructions to access the Teradata Archive/Recovery Release as given below.

SEE: Teradata Archive/Recovery Releasehttp://www.info.ncr.com 1. Select the General Search check box.2. In the Publication Product ID box, type the book number: B035-2412-096A

Multi-ARC

FunctionMulti-ARC is a mechanism for performing parallel backup/restore. Currently released for NetBackup on SUSE Linux Future releases to support NetVault on Windows and SUSE

Linux. Key Features (e.g. Multi-ARC) will be integrated into

NetVault Functional replacement for cluster backup Parallel ARC processes coordinate division of data

automatically No explicit cluster options; effectively a parallel all-AMP

backup Reduce some of the complexity of parallel archive/restore Remove cluster backup restrictions

Description

Ease-of-use benefits

One all-AMP script One backup/restore user

Functional benefits

DBC and journal archives can be done in parallel Support for all backup features Selected partition backup

Performance benefits

Better data distribution per stream (AMP-level) Parallel restore supported to changed configurationESCON (enterprise systems connection) Channel




Number of ESCON connections to TDP LPAR IBM rated at 17.2 MB/s Typical ESCON Backup Performance

One ESCON Link ~ 5 - 15 MB/so Dependent on Teradata database performance

variableso Dependent on number of ESCON director contentiono Dependent on tape drive ratingo Dependent on number of ARCMAIN jobs and available

MIPS (millions of instructions per second)CPU Utilization (TDP+ARCMAIN+CLI) per ARCMAIN job Available LPAR (logical partition) MIPS Archive 18-32 MIPS Restore 27-48 MIPSWorkload Mix ARC process competing with other mainframe tasks Database activity

Teradata TARATeradata TARA is a Teradata-developed software package for managing Teradata archive/restore operations. It works in conjunction with the Teradata ARC utility and the OTB application. Teradata TARA components include the TARA server, the TARA GUI, and the TARA OTB extension. In the future, it will be released with all OTB applications that are certified with Teradata: NetVault, NetBackup and Tivoli Storage Manager. Teradata TARA is currently available for NetBackup in SUSE Linux OS platforms. Future platforms to be supported are Windows and Red Hat. It is worth noting that the upcoming Teradata TARA implementation with NetVault will be different from NetBackup and TSM. Only the Teradata TARA server is applicable to NetVault.

SEE ALSO: User’s Guide information for Teradata TARA is included in the Veritas NetBackup Extension for Teradata Administrator Guide.http://www.info.ncr.com 1. Select the General Search check box.2. In the Publication Product ID box, type the book number: B035-2400-056A




Access ModulesAccess modules are dynamically attached software components of the Teradata client utility configuration that provide the input/output interface with different types of external data storage devices, OLE DB data sources, and message queuing software. Each access module is tailored to a specific type of external device, and can be dynamically linked to one or more Teradata client utilities by the Data Connector API, as shown in Figure 27.Figure 27: Access Module/Data Connector API Linkage

NETVAULT (BAKBONE)SEE ALSO: The NetVault OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM010903&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0SEE ALSO: Accessing OCIs through the Employee Portal

NetVault Overview

NetVault Advantages and DisadvantagesTable 21: NetVault with Direct-attached Architecture

NetVault with Direct-Attached ArchitectureBenefits Limitations Configuration

Highest integration with Teradata features, Fastpath

High predictable

Dedicated tape resources

Mixed workload contention

NetVault Server on Teradata node or (recommended) on a BAR server.






performance Ease of use Flexibility and

tuning for improved resource utilization

Integrated exception handling

Highly scalable Growth and

investment protection

Less flexibility to meet demands for enterprise infrastructure

No backup to disk

OS: APM MP-RAS/Windows

Teradata OS can be: o Windows

(2000/2003)o MP-RAS

(UNIX) Teradata nodes with

Fibre-channel host bus adapter (HBA)

Direct connect cable Tape library and

drives only

Table 22: NetVault with LAN-Based ArchitectureNetVault with LAN-Based Architecture

Benefits Limitations Configuration Highest integration

with Teradata features, Fastpath

High predictable performance

Ease of use Flexibility and

tuning for improved resource utilization

NetVault on BAR Servers

Integrated exception handling

Highly scalable Growth and

investment protection

Potential network contention

Higher initial investment for LAN and BAR servers

BAR server with Windows or Linux SUSE

Teradata nodes with Gbit adapters

Gigabit LAN switch StorageTek tape

drives and libraries Backup-to-disk

options Teradata OS can be:

o Windows (2002/2003),

o MP-RAS (UNIX)o Linux SUSE

NetVault DescriptionNetVault (BakBone) is the advocated OTB storage management backup and restore solution for Teradata. It is tightly integrated with Teradata, giving it a high level of ease-of-use. It is a flexible, scalable, modular storage management solution designed to backup and restore a Teradata Database of any size. NetVault is the only OTB offering that supports the direct-attached architecture. Although Teradata has moved away from the direct-attached architecture, we will continue to support the investment of our customers using NetVault with direct-attached architecture.



Figure 28shows the complete integration of storage management with Teradata. Figure 28: Storage Management System

Figure 29: The NetVault Enterprise

NetVault Main FeaturesNetVault can support a multitude of server platforms and applications within the customer’s data center in addition to



Teradata, allowing for the central management of all of our customer’s enterprise backup needs. Tightly integrated Teradata plug-in modules provide

seamless interface between Teradata and data storage devices.

Uses Teradata ARCMAIN to extract data from and restore data to your Teradata Database

Graphical user interface (GUI) to select the data objects you want to backup and/or restore

Central management console for centralized control over backup, archive, and restore operations

Create scripts, launch jobs, and track data specific to your Teradata Database

Media management, device management, and job management for operating system and Teradata backup and restore operations

Access Module interface for data stream transfer to and from the NetVault managed media

Fully automated backup through the media library management and job scheduling features

Operating Systems (Teradata Extension): UNIX MP-RAS, Microsoft Windows, and SUSE Linux

SEE ALSO: TABLE 3 in Chapter 1, Software Concepts Overview.

Optimized and certified for operation with Teradata products Command line support Automated Cartridge System Library Software (ACSLS)

support

NetVault Installation, Upgrade, and Key Setup InformationInstallation, upgrade, and key setup information is found in the PDF documents to be printed out directly from the installation CD that is delivered with the product.

SEE ALSO: NetVault documentation is also available for download from the BakBone site at http://www.bakbone.com/Support.aspx?id=386

NetVault ConfigurationsFigure 30 and Figure 31 represent the two architectures for Teradata BAR and the NetVault software. The key difference between the two is the location of the NetVault software: in the


http://www.bakbone.com/Support.aspx?id=386


LAN-based solution, it is located on the BAR servers, and in the direct-attached solution the software is located on the Teradata nodes.Figure 30: NetVault with a LAN-Based Library

Figure 31: NetVault with a Direct-Attached Library

NetVault LicensingLaying out the details of licensing is beyond the scope of this Guide. Licensing is affected by many factors. LAN-based and direct-attached architectures are licensed differently. The NetVault Server is sold in three different software packages depending upon the size of the system, the number of nodes, storage capacity, and many other factors. Specific licenses for clients and slots must be purchased in addition to the NetVault Server license. To determine the detailed licensing requirements for a specific system, consult the NetVault OCI.



NetVault Components NetVault is built around the concept of server (master) and client. It is important to note that this concept is different from the traditional hardware concept of server and client personal computers. In NetVault, the Server is the node or workstation where the main storage management software resides. The Server controls the backup activities for the entire system. The client is a node or nodes that are controlled by the Server.

NetVault ServerThe NetVault Server is the core software package that provides management for the data storage devices (including the logical control of robotics), and the software that enables disk-based backups is included. For Teradata, NetVault is certified for MP-RAS UNIX, Microsoft Windows 2003, and SUSE Linux. Several components have been designed into NetVault that are unique to Teradata. These components include: Copy utility for cluster archives Customization of ARC scripts User scriptable restores from auto-backups Multi-library support ARC command line support “Copy From:” support ACSLS tape library sharing Support for virtual tape data management solutions Restore from latest backup Retry failed clusters on another remaining client

NetVault ClientThe NetVault client is a node that is controlled by the NetVault Server. The client is responsible for managing the archive/backup/restore operations on the node in which it resides including the operating system, file system, and Teradata. Clients are either dependent or semi-dependent on instructions received from the NetVault Server. The amount of dependence is determined by the NetVault client package installed. There are basically two types of clients: heterogeneous and SmartClient™.



Heterogeneous Clients

The heterogeneous client is the basic, non-operating-system-specific client software that allows the NetVault Server to recognize the Teradata node, BAR server, or another client. It provides instructions for the operating system and file system backup in addition to Teradata and application backup support. Heterogeneous clients are not directly attached to a storage device and must send data to a designated SmartClient for transmittal to the storage device. It receives all instructions from the NetVault Server.

SmartClients

SmartClients are required whenever a server, node or client has a storage device attached to it either directly or through a switch (Tape SAN). SmartClients are operating-system-specific and install enhanced client software on the node.While SmartClients receive instructions from the NetVault Server, they are able to independently manage those instructions and the attached storage device.

NetVault Dynamically Shared DevicesA dynamically shared device (DSD) is a tape drive or virtual tape drive (disk), which is shared by multiple servers, clients, and nodes.

Tape Libraries

For tape libraries, a DSD is associated with a specific tape device which allows it to be shared by multiple servers, clients, and nodes. A DSD allows the SmartClient to recognize the shared tape drive and allows the NetVault Server to direct the flow of information to a tape drive through the switch (Tape SAN). Due to configuration issues discovered with direct connection and MP-RAS, the LAN-based architecture will be required when utilizing dynamically shared devices for tape libraries. Remember that DSD is required whenever the tape drive itself is shared. Figure 32 shows tape drive sharing in the LAN-based architecture.



Figure 32: Dynamically Shared Devices - Tape Drive Configurations

Disk Backup

For disk backup libraries, such as the Teradata 9204 Backup 2 Disk Library or the 9205 CLARiiON® Disk Library, the DSD software works with the storage management software to share a backup storage system.



Figure 33: Dynamically Shared Devices - Disk Backup

NetVault Teradata Application PLUG-IN ModulesTeradata application plug-in modules are required when connecting to a Teradata system. The modules permit NetVault and Teradata to communicate with each other. Through the Teradata plug-in, NetVault becomes a fully integrated component of Teradata.The following NetVault plug-in modules are available with the core release: Data Copy

Data Copy allows a user to generate copies of previously completed backups of data that was generated with any NetVault APM or Plug-in.

Duplicate



Duplicate allows the user to copy a backup from one piece of media to another, as well as to set various options pertaining to the type of duplication. Once a backup is duplicated, NetVault will treat the duplicate as another instance of the same data.

Virtual Devices Virtual devices allocate a portion of a Client system’s hard drive space and act as a specific device type, maintaining all of the properties of that device.

VerifyOnce a backup has completed, the data transfer will be checked and a job message will be created in the NetVault Job Log stating “backup job has verified successfully.”

The TTU backup/archive/restore architecture is required by the NetVault Teradata plug-in module to communicate with the Teradata DBMS. The Tape Storage Management Enabler CD included with the plug-in modules includes the following components: ARC CLIV2 (Call-Level Interface, version 2) Data connector API (PIOM (parallel I/O Module) SQLPP Teradata GSS Teradata ICUThe NetVault Teradata plug-in is operating-system-specific, so you must order the version of the plug-in that corresponds to the operating system of the underlying Teradata node or BAR server. Direct-attached: One Teradata plug-in module is required for every Teradata node that has a directly attached or shared attachment to a tape drive.LAN-based: One instance of the Teradata plug-in is required for each BAR server.

NetVault VaultShare All Teradata storage systems that use ACSLS require VaultShare software. VaultShare provides an interface between NetVault and the ACSLS server and software.VaultShare also enables the sharing of storage systems by interfacing with the ACSLS tape automation management utilities.



NOTE: these utilities are not included with VaultShare but are part of the ACSLS.

Sharing is defined as follows: Sharing storage systems among multiple Teradata systems

managed by NetVault Sharing storage systems among Teradata systems and open

systems managed by NetVault Sharing storage systems among NetVault-managed Teradata

systems and other storage management applicationsFigure 34: VaultShare Diagram for Teradata

Node 1 Node 2 Node 3 Node 4Node 1

NV ServerHCSCVSVS DL (4)TDE

Node 2

HCSCTDE

Node 3

HCSCTDE

Node 4

HCSCTDE

Gbit Switch

Legend:

NV = NetVaultVS = VaultShareVS DL = VaultShare ACSLS Drive LicenseHC = Heterogeneous ClientSC = SmartClientTDE = Teradata Database Extension

BAR ServerNV ServerHCSCVSVS DL (4)TDE (2)

BAR ServerHCSCTDE (2)

LAN-based ArchitectureDirect Connect

9202Modular Library System

AC

SLS


AC

SLS



Figure 35: VaultShare Diagram for Open Systems

Node 1 Node 2 OpenSystem

(HP-UX)

HCSC

OpenSystem(Windows)

HCSC

Node 1

NV ServerHCSCVSVS DL (4)TDE

Node 2

HCSCTDE

OpenSystem

(HP-UX)

HCSC

Gbit Switch

Legend:

NV = NetVaultVS = VaultShareVS DL = VaultShare ACSLS Drive LicenseHC = Heterogeneous ClientSC = SmartClientTDE = Teradata Database Extension

BAR ServerNV ServerHCSCVSVS DL (4)TDE (2)

BAR ServerHCSC

LAN-based ArchitectureDirect Connect


AC

SLS


AC

SLS

OpenSystem(Windows)

HCSC



NOTE: ACSLS may be used with the following Libraries:

Current Legacy

9202 SL8500 6465 Tape Library6466 Tape Library6476-Silo6477 Silo

NETBACKUP (SYMANTEC, FORMERLY VERITAS)SEE ALSO: The NetBackup OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM010901&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0SEE ALSO: Accessing OCIs through the Employee Portal

NetBackup Overview

Advantages and DisadvantagesTable 23: NetBackup with LAN-Based Architecture

NetBackup (LAN-Based Architecture Only)

Benefits Limitations Configuration

Leverages existing NetBackup infrastructure and resources

Flexibility and tuning for improved resource utilization

NetBackup on BAR Servers

Growth and investment protection

Extensive documentation library and command line features

Only loosely integrated with Teradata

Potential network contention

Higher initial investment

Reporting and feature information

Limited feature support for ARC (archive/recovery)

No Fastpath support for Teradata

BAR server only BAR Server OS:

Windows or SUSE Linux

Teradata nodes with Gigabit adapters

Gigabit LAN switch StorageTek tape


options Teradata OS can be: Windows

(2000/2003) MP-RAS (UNIX) SUSE Linux






DescriptionThe advocated storage management backup and restore solution for Teradata is NetVault by BakBone Software. Symantec’s NetBackup is an available option if the advocated solution will not work in the customer’s environment. Because it does not include as many custom enhancements for Teradata, it does not have the same ease-of-use as the NetVault software NetBackup provides media management, device management, and job management for Teradata backup and restore operations.

SEE ALSO: product datasheets and other vendor documentation can be found at http://www.symantec.com/enterprise/products/datasheets.jsp?pcid=1018&pvid=2_1

In all cases, Teradata Operational Services should be given an opportunity to position our advocated offer, BakBone NetVault.

SEE ALSO: Chapter 1: Concepts, Software Concepts Overview, for a table showing the benefits, limitations, and configurations for NetBackup LAN-based BAR.NETBACKUP NOTES: Integration of Bare Metal Restore (Purchased separately from

Symantec) Teradata Customer Services remains the single focus of

knowledge for these configurations (pre-sales, implementation and support)

Migration plan (described later in this chapter) for moving current customers from MP-RAS to the new LAN-based configuration.

NetBackup versions 5.0/5.1 and newer are not available with a direct-attached BAR configuration on Teradata nodes (MP-RAS UNIX, Windows, and SUSE Linux).

Main Features Data protection from datacenter to vaulting Highly scalable Windows and SUSE Linux platforms Automatic, unattended backups for client systems across a

network Media Manager manages tape and disk storage devices Multiple servers work together under control of master

server


http://www.symantec.com/enterprise/products/datasheets.jsp?pcid=1018&pvid=2_1

http://www.symantec.com/enterprise/products/datasheets.jsp?pcid=1018&pvid=2_1


Master server manages backup and restore operations Teradata TARA NetBackup extensionThe Teradata Extension uses the Teradata Tools and Utilities utility ARCMAIN to extract and restore data to/from the Teradata Database via an “Access Module” which provides data stream transfer to and from the NetBackup managed media. The extension provides: Teradata GUI data object selection Backup/restore script generation Job launch and data tracking capabilities specific to the

Teradata Database Fully automated backup through media library management

and job scheduling capabilities within NetBackupTable 24: NetBackup Operating System Support

Windows Components SUSE Linux ComponentsTTU for Windows 2003NetBackup for Windows 2003NetBackup Teradata extension for Windows 2003

TTU for SUSE LinuxNetBackup for SUSE LinuxServer for SUSE LinuxTeradata TARA GUITeradata TARA extension (NetBackup or BAR)

Installation, Upgrade, and Key Setup Information for NetBackupSEE: Installation, upgrade, and key setup information is found at http://www.info.ncr.com/Teradata/eTeradata-BrowseBy.cfm?page=Teradata%20Tools%20and%20Utilities, TTU 8.1, Veritas NetBackup Extension for Teradata Administrator Guide.

ConfigurationNetBackup is available for the LAN-based architecture only.


http://www.info.ncr.com/Teradata/eTeradata-BrowseBy.cfm?page=Teradata%20Tools%20and%20Utilities




Figure 36: LAN-based Architecture

LicensingLaying out the details of licensing is beyond the scope of this guide. To determine the licensing requirements for a specific system, consult the NetBackup OCI.There are at least two license keys that will be supplied in the NetBackup/Teradata Extension software package: The NetBackup core product license key and the license key that enables the Teradata option within NetBackup.

NetBackup ComponentsFor a Teradata system, NetBackup consists of three required components: the enterprise master/data (media) server, the Teradata extension, and the tape drive and/or virtual tape option.

NetBackup Enterprise Master/Media ServerThe NetBackup enterprise server provides the direction and the intelligence for the backup. There are two types of enterprise servers: master servers and data (media) servers.



The master server provides the intelligence for all data protection activities from scheduling to managing tape media and file catalogs. It is the management control server over all activities. Main backup server – manages all data protection operations Backs up and restores local and client data to attached

storage Manages attached (direct/SAN) storageThe data (media) server operates under the control of the master server and connects to the media storage device(s). Media servers distribute the data workload.In any NetBackup configuration, one enterprise server will be designated as the master server and all remaining servers will be designated as data (media) servers. This configuration requires the Teradata BAR data (media) servers to run on either Windows or the SUSE Linux operating system.The master server and media server are ordered using the same product ID. The configuration of the software on the server determines whether it is a master or media server. The version of the software used is determined by the operating system of the BAR server.

NOTE: The operating system version of the software must match the operating system of the BAR server.

NetBackup Extension for TeradataThe Teradata extension provides the communication link between NetBackup server and the Teradata database. We have updated the Teradata extension for NetBackup and it now includes a SUSE Linux version. This software is developed and supported by Teradata.

SEE ALSO: the section on Teradata TARA at the beginning of the chapter.

NETBACKUP TERADATA EXTENSION MODULESTeradata extension modules are required when connecting to a Teradata system. The Teradata extension modules permit NetBackup and Teradata to communicate with each other. Two distinct Teradata extension modules are currently available. The first, called NB TDE, runs on the Windows operating system. The second, Teradata TARA, is the newest and runs on the SUSE Linux operating system. In the future, Teradata TARA will



also be available for the Windows operating system and will replace NB TDE.The TTU backup/archive/restore architecture is required by the NetBackup Teradata extension module to communicate with the Teradata DBMS. The Tape Storage Management Enabler CD included with the extension modules includes the following components: ARC CLIV2 Data connector API (PIOM) ODBC Teradata GSS Teradata ICUThe NetBackup Teradata extension is operating-system-specific, so you must order the version of the extension that corresponds to the operating system of the underlying Teradata node or BAR server. Direct-Attached: One Teradata extension module is required for every Teradata node that has a directly attached or shared attachment to a tape drive.LAN-based: One instance of the Teradata extension is required for every Teradata node.Figure 37: Teradata Extension Ordering Examples for NetBackup



NetBackup Shared Storage Option NetBackup shared storage option (SSO) dynamically shares individual tape drives among multiple NetBackup enterprise servers.

NetBackup Virtual Tape OptionNetBackup virtual tape option enables support for virtual tape drives. It is required when NetBackup will be part of a backup system that includes the 9205 Clariion Disk Library. It is not required for the 9204 Backup 2 Disk storage system.

NetBackup Advanced Reporter or NetBackup Operations ManagerNetBackup Advanced Reporter or NetBackup Operations Manager provides the ability to provide consolidated summary reports of the NetBackup environment.

NetBackup VaultNetBackup Vault provides media management of the tracking and movement of individual media sets that are associated with specific NetBackup backup and restore jobs both onsite and offsite, and manages the offline archival storage of those media sets according to rules set by the user.

TIVOLI STORAGE MANAGER (IBM)SEE ALSO: The Tivoli OCIhttps://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=SA679634&BV_SessionID=@@@@1296984687.1160091017@@@@&BV_EngineID=ccceaddjddeglldcfngcfgldhkgdfgi.0SEE ALSO: Accessing OCIs through the Employee Portal






Tivoli Storage Manager Overview

Advantages and DisadvantagesTable 25: TSM (LAN-Based Architecture Only)

TSM (LAN-Based Architecture Only)Benefits Limitations Configuration

Leverages existing TSM infrastructure and resources

Flexibility and tuning for improved resource utilization

Teradata-developed access module to TSM

TSM on BAR Servers Growth and

Investment Protection

Not integrated with Teradata

No GUI High TSM initial

investment Complex to learn

and use Potential network

contention Limited feature

support for ARC

Only with existing TSM infrastructure

BAR server Teradata nodes with

Gigabit adapters Gigabit LAN switch StorageTek tape


options Teradata OS can be: Windows

(2002/2003), MP-RAS (UNIX) SUSE Linux

DescriptionThe advocated tape management backup and restore solution for Teradata is NetVault by BakBone Software. Tivoli Storage Manager (TSM) is a LAN-free (it uses a SAN switch to allow the BAR servers to write to the storage device) backup solution that enables Teradata to be connected to an existing TSM server environment. It is being released only for those customers who have an existing Tivoli infrastructure in their data center and require Teradata to “fit in” to this structure. In all cases, Teradata Operational Services should be given an opportunity to

position our advocated offer, BakBone NetVault. Under no circumstances should Tivoli Storage Manager for Teradata be

offered to a customer who does not already use Tivoli at the enterprise level.

SEE ALSO: product overview page at http://www-306.ibm.com/software/tivoli/products/storage- mgr/

Main Features Automatic data backup and restore functions Centralized storage management operations Highly scalable





Addresses regulatory compliance for data retention

Tivoli Teradata Extension Modules (TIVBAR)Teradata extension modules (TIVBAR) are required when connecting to a Teradata system. The Teradata extension modules permit TSM and Teradata to communicate with each other. The TTU backup/archive/restore architecture is required by the TSM Teradata extension module to communicate with the Teradata DBMS. The Tape Storage Management Enabler CD included with the extension modules includes the following components: TIVBAR ARC CLIV2 Data connector API (PIOM) Teradata GSS Teradata ICUThe TSM Teradata extension is released for Windows operating systems only.One instance of the Teradata extension is required for each BAR server.

Controlled Distribution GuidelinesTivoli Storage Manager is a controlled distribution product; the following guidelines must be adhered to when ordering Tivoli. Operational Services pre-sales involvement

This includes direct interaction with the prospect or customer to establish requirements and set correct expectations around performance and usability, along with acknowledgement that existing TSM environments for most customers will require expansion/upgrade to support the Teradata data rates and capacity.

BAR Services costs are required; therefore the quote to the customer needs to properly represent this cost.

Support and maintenance must be quoted and when implemented, must be properly recorded in the Customer Services D1 system.



Installation, Upgrade, and Key Setup Information for TSMInstallation, upgrade and key setup information is found in the PDF documents to be printed out directly from the installation CD (disk 3 of 3) that is delivered with the product.

ConfigurationFigure 38: TSM Configuration

LicensingLaying out the details of licensing is beyond the scope of this Guide. To determine the licensing requirements for a specific system, consult the latest OCI for the IBM Tivoli Storage Manager.

Maintenance RequirementsAll sales of Tivoli Storage Manager for Teradata will require the sale of a Teradata customer support maintenance agreement.

Tivoli Components

Teradata Extension for TivoliWe have written a Teradata Extension module (TIVBAR) that allows Teradata to interface its backup routines to TSM. It is important to note that there are several caveats to a TSM-based backup solution for Teradata. These caveats are:1. Teradata will impact the customer’s LAN performance. Since

Tivoli uses a customer’s LAN, a Teradata backup may degrade the performance of the LAN during the backup



period. Care should be taken when determining the time of day when a backup is scheduled. Also, it is recommended that Tivoli be setup as a separate or “sub” LAN to isolate the backup process, as much as possible, from business-critical LAN traffic. This does not apply to the LAN-free configuration, where the use of a SAN switch allows the BAR servers to communicate directly to the storage device.

2. Not all Teradata-integrated operations will be available.3. Customer will have to purchase gigabit switches and a

dedicated BAR server.4. Tivoli is under post-GCA controlled distribution. Approval by

Product Management and Operational Services is required.5. Teradata system and open system backups should not be

scheduled concurrently. Any interim open system backups should be suspended during the period when a Teradata backup occurs.

6. Teradata backups in the Tivoli environment must be initiated through command line scripts. This is labor-intensive, as there is no auto-generation of these scripts; the user must write each of them.

Teradata Access Module for TivoliThe Teradata Access Module for Tivoli for Windows gives you access to the IBM Tivoli Storage Manager environment and is supported by ARCMAIN as an interface for administering backup images. The access module manages the I/O interfaces from the Teradata ARCMAIN client utility to the IBM Tivoli Storage Manager. The same ARCMAIN executable code can communicate with a variety of access modules (while only one per job can be run). In addition to the Teradata Access Module for Tivoli, an administrative command-line tool called TDDSMC is provided. The TDDSMC tool reports on ARCMAIN backups stored in the IBM Tivoli Storage Manager (TSM) and performs maintenance activities, such as deleting backups that are no longer needed.

SEE: For more information on the Teradata Access module and the TDDSMC tool, refer to the Teradata Access Module for Tivoli Installation and User Guide in the Service Documentation Library, or go directly there at http://infocentral.daytonoh.ncr.com/tsd-library/iDownload.cfm?itemid=061350002





Tivoli BAR serverTivoli Storage Manager for Teradata requires a Windows server to be used as a BAR application server. The BAR application server will be the mechanism for transporting data from Teradata to the Tivoli-based tape libraries.

IMPORTANT NOTE: One BAR server will support up to four tape drives. A second BAR server is required when configuring two tape drives per node.

Tivoli System ConfigurationsThis section provides a step by step guide to building a Tivoli based backup solution for Teradata. The following diagram outlines the necessary components.Figure 39: Tivoli Requirements Diagram

Existing Components Required at Tivoli Customer Site

The Customer should be an existing Teradata customer who wishes to utilize their existing Tivoli infrastructure to back up Teradata. The customers should have the following components:1. Tivoli Storage Manager Server (version 5.2 or higher)2. SAN Switches



3. SAN data gateway routers (only required with SCSI tapes)4. Tape library or disk backup

The sales team and Operations Services must carefully analyze the customer’s current Tivoli system to ensure that the above components are present and will support the addition of a Teradata system. The customer may need to procure additional Tivoli hardware in order to support the addition of Teradata.

Additional Required Components for Tivoli

The customer will have to add the following components to connect the Teradata System into the Tivoli infrastructure. 1. BAR server(s) dedicated to Teradata2. Gigabit switch3. Cables - Fibre-channel, Gigabit Ethernet, Ethernet, UW SCSI4. Tape drives for the tape library

Tivoli ConfigurationsThe following diagrams illustrate Tivoli configuration options for Teradata systems.

Tivoli SMP Configuration:Figure 40: Configuration Illustration for SMP and Single-Node MPP Configurations



Tivoli Dual Node MPP Configuration:Figure 41: Configuration Illustration for Dual Node MPP Configuration

Tivoli Four Node MPP ConfigurationFigure 42: Configuration Illustration for a Four-Node System with One Tape Drive per Node


4: PERFORMANCE VARIABLESThe numbers supplied in this chapter were generated in laboratory conditions. The actual results in a customer data center may vary significantly and are dependent on many factors. Examples cited or described in this chapter are presented as illustrations of what may be achieved; no warranties or guarantees are either expressed or implied.

TERADATATeradata Platform

Node processorTeradata offers a one-stop shop solution for customers’ data warehouse needs. It sells the hardware platform where Teradata DBMS is optimized to run. The operating systems that run on the Teradata nodes are also optimized to take advantage of the hardware. The Teradata hardware platform is certified and released with the fastest and most reliable industry-standard components such as processors, disk storage, and I/O peripherals.In looking at data backup and restore performance, one has to be aware of the hardware platform and the operating system where the data reside. The demands of the Teradata active data warehouse run contrary to the normal practice of having a backup window with a minimum system load. As customers expand globally, the more need there is for BAR to co-exist with an active data warehouse running 7/24 operations. This is especially true with the direct-attached BAR architecture, since the Teradata utilities and the BAR applications are running on the same nodes as the Teradata DBMS. In the LAN-based BAR architecture, the impact is lessened, since the Teradata utilities and BAR applications are running on multiple BAR servers. In some respects, the data backup and restore performance is only as good as what the Teradata platform and DBMS can supply to the input-output units present in the Teradata nodes. Fortunately, as new generations of hardware are released, Teradata hardware platforms will be powerful enough to catch up with the bandwidth available through the multiple fibre-channel or Gigabit Ethernet ports in the node. For the purpose


of this document, we are only going to provide information on newer generations of Teradata platforms.

Platform(MPP)

Year Released

Chipset CPU I/O Slots Supported DB Releases

5380 2003 Intel E7501/533-MHz FSB/HT

2x3.06 Ghz

3 High profile PCI slots

3 low profile PCI slots

1 Gigabit Ethernet port

v2r4.1.0 through v2r8.0

5400 2005 Intel E7520/800-MHz FSB/HT

2x3.60 Ghz

3 High profile PCIX slots

3 low profile PCIX slots

2 Gigabit Ethernet ports


5450 2006 Intel E7520/800-MHz FSB/HT

2x3.80 Ghz

3 High profile PCIX slots

3 low profile PCIX slots

2 Gigabit Ethernet ports


Disk StorageThe type of disk storage is an important factor in determining the overall performance of the Teradata system. The fact that data warehouse system operations are disk-intensive and are capable of storing and manipulating terabytes of data contributes to the challenge of being able to complete data backups and restore operations in the shortest time possible. Teradata storage systems are certified and optimized for the Teradata parallel DBMS. The following table lists the latest generation of disk storage systems released for Teradata.Table 26: Teradata Disk Storage Systems

NS 6.0 NS 6.1 NS 6.2 NS7.0Controllers 5884 5885 5885 6091Drive Trays JBOD JBOD SBOD SBODDAP -1 No Yes Yes YesDAP-3 No No No YesDrives X15.3 (36

and 73GB)

Cheetah

X15.3 (36 and 73 GB)

Cheetah

X15.4 (36, 73 and 146 GB)

X15K.4 (73 and 146 GB) * 4Gb



10.6 (146GB)

10.6 (146GB)

drive speed

Drives/array 56 56 56 144Arrays/cabinet 2 2 2 1

Operating SystemTeradata DBMS runs on MP-RAS, SUSE Linux and the Windows operating systems. By far the most widely-installed of the three is MP-RAS. The advent of 64-bit processors, installed on 5400 and newer platforms, necessitated the development of a 64-bit-capable Teradata system. The first 64-bit Teradata system was released on the Linux SUSE 64-bit operating system. This occurred in 2005 with Teradata DBMS v2r6.1.1. As with other databases and applications, there are operating system tunables that may help enhance the Teradata backup and restore performance. These tunables will require different values for dissimilar platform environments. For example, values for direct-attached BAR systems may be different from a LAN-based system. Also, the number of nodes versus the number of BAR servers and backup storage devices are important factors in determining these values. Each operating system has its own method of system tuning. This section will describe the method of accessing the operating system tunables. For specific tuning parameters and values, please refer to the remaining sections in this chapter.

WindowsWindows system tunables reside in the System registry. The utility that is used to modify these tuneables is either regedit or regedit32. These utilities will open a Microsoft Explorer-type window that you can use to traverse the registry’s hierarchical structure.

MP-RASMP-RAS UNIX tuneables are compiled into the kernel via the utility idbuild. Kernel tunables reside in the file, /etc/conf/cf.d/mtune. Each line contains four fields, namely: Parameter name, Default value, Minimum value, and Maximum value. The mtune file must not be changed.To adjust the current value of a tunable, use the command, idtune. The format of this command is as follows:

/etc/conf/bin/idtune <parameter name> <value>



This will place the parameter and its new value in the /etc/conf/cf.d/stune file.When you have made all the tuning changes via idtune, you need to rebuild the kernel:

/etc/conf/bin/idbuildThis will take several minutes. All of the changes you made using idtune will be built into the new kernel.

SUSESUSE Linux tunables can be dynamically changed in two ways: Using the sysctl command Viewing/changing the tunable directly via the ‘cat/echo x

>parm’ command strings in the /proc/sys subdirectoriesOf the two methods, the safer of the two is the sysctl command. To view all the tunables, perform the following:

# sysctl -a >/tmp/tunables.outYou can then view the file via ‘more’, ‘vi’ or ‘view’.To change a parameter, use the following sysctl format:

# sysctl –w <Path.parameter>=<value>In most cases, this is a dynamic change. To make the change permanent, add the <Path.parameter>=<value> to the /etc/sysctl.conf file. Note that the /etc/sysctl.conf file may not exist if your changes are the first since the operating system was installed.

Backup Strategy Impacts on Performance

All-AMP

Backup and Restore

Backups and restores are limited to the speed of the backup devices and other variables affecting delivery of data to the devices.

Multiple All-AMP

Backup

Multiple backups can be run in parallel so that backups can reach full throughput across multiple drives.Dividing work equally to each of the parallel all AMP jobs requires extra user intervention (or development of automatic



scripts). The longest running of the parallel jobs determines the backup window needed.

Restore

Multiple restores can be run in parallel (assuming different user IDs are used for each restore).There may be lock contention issues with the parallel jobs (for example, only one job can restore dictionary rows at a time).

Cluster

Backup

Multiple backups can be run in parallel so that backups can reach full throughput across multiple drives. There is a minor additional overhead for starting each object on each thread (it is only significant for large numbers of small objects).

Restore

Multiple restores can be run in parallel (with different user IDs) but only to the same configuration system. A configuration change requires: Either that the cluster archives be restored one at a time Or the extra work to copy to temporary tables (which

requires the user to build ARC scripts)

Multi-ARC

Backup

Multiple backups can be run in parallel so that backup can reach full throughput across multiple drives. There is a minor additional overhead for large numbers of small objects (streams must synchronize on object boundaries).

Restore

Multiple restores can be run in parallel with the same user ID. A configuration change does not prevent parallel restore as in the cluster case.



Online Archive (GROUP READ LOCK)

Backup

Backup requires extra time to checkpoint and back up the change journal after the online archive.The impact depends on the number of rows changed while the backup was in progress.

Restore

Extra time is required to restore and roll forward the change journal after the data restore. The impact depends on the number of rows changed during the backup.

Overall

Tables that are backed up online require journaling to be active. Journals can impact the overall Teradata system performance.

Selected Partitioned Archive (BAR for PPI)

Backup

Selected partitioned archive potentially reduces the amount of data to back up (allowing backups to complete sooner), if only a subset of partitions on each table will change.This procedure requires that tables have partitioned primary indexes (PPI) defined, and that the PPI definition is such that only a known subset of the partitions will change between backups. Also, you cannot use cluster archive - you must use multiple all-AMP or Multi-ARC to run multiple devices in parallel.

Restore

Multiple-step restore will generally be required, increasing restore time. The overall impact depends on the incremental backup strategy: restore time may increase as the time between full-table backups increases. This may also require considerable user effort to ensure that the restore runs correctly (all incremental archives must be processed/restored for the table data to be restored correctly; in some cases, partitions may need to be explicitly specified in the ARC restore scripts).



Teradata Database Factors

PPI Tables Restores of PPI tables can run significantly slower than restores of non-PPI tables. The degradation is much worse when restoring to a system with a different configuration from when the archive was taken. In the worst case, the reduction of the restore throughput of PPI tables can be as high as 90% when compared to normal restore throughput (for example, for non-PPI tables).

Configuration ChangesRestores of archives to a machine with a different configuration will run slower due to the requirement of redistributing rows to the proper AMPs for the new configuration. The degree of impact depends on the size of rows in each table: smaller rows generally have a greater impact. The impact to restore throughput to a different configuration can be as high as 50-80% when compared to the impact of restoring throughput to the same configuration.

RehashingChanging the hash function will require the recalculation of row hash values; this will result in a redistribution (50-80%) similar to restoring throughput to a different configuration.Restore impact will also be similar to the changed configuration case.

Size and Number of ObjectsThere is a per-object overhead in both archive and restore (for example, placing locks, retrieving DBS configurations, and setting up dump tasks). Large numbers of small objects will result in lower tape throughput for both archive and restore. The overhead depends on the level of object specified by the user - specifying a full-database backup or restore will have much lower overhead than specifying a table-level backup for all tables in the database.

IndexesIndexes do not generally impact backup performance.



On restore, indexes must be rebuilt once the primary data for a table is restored. The build time depends on the number of indexes on each table, and on the number of rows in each table. Join and hash indexes are not rebuilt automatically by ARC: they must be recreated by the user manually after a restore is complete.

ARC CHECKSUM FeatureARC has a feature to calculate and verify checksum values for each block of data rows received from DBS (or tape on a restore. There are two levels for the CHECKSUM feature:Level 1: Checksum values are calculated by the Teradata DBS during an archive, and are written to tape by ARC. During restore, the checksum value is included with the data block sent to the DBS; the checksum is verified prior to writing the rows to the table.Level 2: Checksum values are calculated by Teradata DBS during an archive, and are verified by ARC prior to writing the block to the tape. On restore, both ARC and DBS verify the checksum value for each block.In general, checksum validation of archives consists of running an archive using checksum level 1, followed by an ANALYZE of the archive using checksum level 2. Archive and restore jobs at checksum level 2 are generally only used to diagnose problems in the data communication path (network/channel).

Teradata Virtual Storage ArchitectureThe Teradata Virtual Storage Architecture (TVSA) feature of Teradata V2R7.0 (now Teradata Version 12.0) will change how table data is stored on the Teradata DBS disks. This change may impact backup and restore performance; however, since the feature is not available as of this writing, the degree of impact is still unknown.

Disk Speed and FragmentationOverall Teradata disk speed can impact the performance of archive and restore jobs.



Performance impacts include both the speed of the disk used and the number of disks per AMP (and/or the number of disks for a given data size): more disks per AMP / terabyte will usually result in better performance.Disk fragmentation will negatively impact archive/restore performance. The degree of disk fragmentation on a normal system and the typical impact on backup/restore performance is currently not fully known.Both of the factors above will impact overall Teradata system performance as well. In general, changes that improve overall system performance (for example, adding more or faster disks and reducing fragmentation) will also improve backup/restore performance.

Teradata Database Performance VariablesObject (Table, Views, and Macros) backup speed The larger the table the higher the backup rate The fewer the objects the higher the backup rate

Each object has associated data dictionary rows The fewer the data dictionary entries, the higher the backup

rate Compressibility of data

Compression via tape drive hardwareTeradata Nodes Number of nodes Amount of data behind each node BAR topology Workload mix: Backup+SQL+Load jobs

Where is the Bottleneck?CPU MIPS / Mhz / Ghz QuantityMemory Quantity SpeedI/O Subsystem Interface (SCSI/Fibre/Network)



Throughput Quantity

I/O bus contention/bandwidthWorkload MixStorage Tape Drive

Availability Throughput Mount Frequency

o Tape Cartridge Capacity Disk

Controller Throughput Disk Revolution Rate

Network Bandwidth (10/100/1000 Mbits/s) Hub, Bridge, Router, and Switch Capacity Access Contention Maximum Transmission Unit (mtu) Packet Size Subneting and Trunking

Data Rate to/From Teradata Teradata interfaces and BAR/LAN infrastructureSessions are connected between ARC and Teradata – made via CLI, TCP/IP and Teradata Gateway

NETWORKSNetwork

A number of things related to the jumbo packets can have an impact on performance. Explicit guidelines and impacts are being investigated and tested. As information becomes available, it will be added to future versions of this guide. Some of the areas to be aware of include:

Jumbo Packets Device Settings Receive/Transmit description



LAN Tuning

Linux TCP Tuning for Gigabit LAN

System Tuning

Most of the SUSE Linux 9 tuning defaults are acceptable for good data transfer performance over a gigabit LAN connection. The following should be adjusted via sysctl for immediate activation and placed in the /etc/sysctl.conf file to span reboots.# sysctl –w net.core.rmem_max=8388608# sysctl –w net.core.wmem_max=8388608# sysctl –w net.core.rmem_default=65536# sysctl –w net.core.wmem_default=65536# sysctl –w net.ipv4.tcp_rmem='4096 87380 8388608'# sysctl –w net.ipv4.tcp_wmem='4096 65536 8388608'

or# cat/etc/sysctl.conf

net.core.rmem_max=8388608net.core.wmem_max=8388608net.core.rmem_default=65536net.core.wmem_default=65536net.ipv4.tcp_rmem='4096 87380 8388608'net.ipv4.tcp_wmem='4096 65536 8388608'

Interface Tuning

Ensure that the TCP segmentation offload is disabled for each Ethernet interface. To display (example uses the first interface defined):# ethtool -k eth0

Offload parameters for eth0:rx-checksumming: ontx-checksumming: onscatter-gather: ontcp segmentation offload: on

To set TCP segmentation off:# ethtool -K eth0 tso: off



Check the TCP transmit queue length:# ifconfig eth1eth1

Link encap: Ethernet HWaddr 00:04:23:A9:19:E8inet addr:192.168.15.124 Bcast:192.168.15.255 Mask:255.255.255.0inet6 addr: fe80::204:23ff:fea9:19e8/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1RX packets:4436833 errors:0 dropped:0 overruns:0 frame:0TX packets:323764 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:300RX bytes:8332856367 (7946.8 Mb) TX bytes:659371608 (628.8 Mb)Base address:0xdc80 Memory:dfbc0000-dfbe0000

For a gigabit LAN, the txqueuelen should be at minimum 1000:# ifconfig eth1 txqueuelen 1000

TCP parameters

TCP TimedWaitDelay

Key: Tcpip\ParametersValue Type: REG_DWORD—time in secondsValidRange: 30-300 (decimal)Default: 0xF0 (240 decimal)Description: This parameter determines the length of time that a connection stays in the TIME_WAIT state when being closed. While a connection is in the TIME_WAIT state, the socket pair cannot be reused. This is also known as the 2MSL state because the value should be twice the maximum segment lifetime on the network. See RFC 793 for further details.Set this to 30.

TCP MaxDataRetransmissions

Key: Tcpip\Parameters



Value Type: REG_DWORD—numberValidRange: 0–255 (decimal)Default: 2Description: This parameter determines the number of times that TCP retransmits a connect request (a SYN segment) before aborting the attempt. The retransmission time-out is doubled with each successive retransmission in a given connect attempt. The initial time-out is controlled by the TcpInitialRtt registry value.Set this to 5.

Key: Tcpip\Parameters

Value Type: REG_DWORD—numberValid Range: 0–0xFFFFFFFFDefault: 5Description: This parameter controls the number of times that TCP retransmits an individual data segment (not connection request segments) before aborting the connection. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The Retransmission Timeout (RTO) value is dynamically adjusted, using the historical measured round-trip time (Smoothed Round Trip Time) on each connection. The starting RTO on a new connection is controlled by the TcpInitialRtt registry value.Set this to 10.

CLI tunablesThe CLI tunables in the CLI SPB (System Parameter Block) file (e.g. 'clispb.dat') generally do not apply to ARC. The ARC application will override most values with those that are expected by the application. In particular, request/response buffer sizes are set to the maximum size expected by ARC (64KB).

Network EncryptionThis feature enables encryption on the network link between the Teradata nodes and the BAR Server(s). For an ARCHIVE operation, all data sent from Teradata will be encrypted prior to being sent on the network, and will be decrypted on the client prior to it being received by ARC. For RESTORE, the data is



encrypted prior to leaving the BAR Server, and is decrypted by Teradata. Note that data is not written to tape while encrypted - the encryption only applies to the traffic across the network.This feature has a very high performance impact (50-80% or more), so it should only be used in cases where the BAR network cannot be isolated and/or secured.

Gateway Selection through COP EntriesThe Gateway is the interface between Teradata and CLI. A COP (Communication Process) contains a gateway process for communicating with workstations via the network. In the /etc/services file the entry tdmst -1025/udp is specifying that COPS/nodes communicate with the Gateway on port 1025, which is the default. The entry is tdmst is the port alias, 1025 is the port number, and udp is the protocol. If there was a second protocol, there would have to be a second entry. If the Gateway is modified to listen on a different port, the tdmst entry will then need to be changed. The alternative is to set the TDMSTPORT environment variable to the new port address.

COP ConfigurationA COP is one kind of interface processor on the Teradata Database. COP entries can be found in /etc/hosts on UNIX and Program Files\NCR\Teradata Client\cliv2\drivers\etc\hosts on Windows. If a Teradata Database has four COPs that can be connected to, the COP entries in the hosts file should look as follows:Note: NODENAME should be the same for all the nodes.[IP address of NODE1] NODENAMEcop1[IP address of NODE2] NODENAMEcop2[IP address of NODE3] NODENAMEcop3[IP address of NODE4] NODENAMEcop4

** If an SMP node, the entry will be [IP address of NODE] NODENAMEcop. There is no longer a need for a number for the sequence.

CLI assumes that the COP entries are all serial, and CLI will continue connecting to COPS until the environmental variable value is reached for a certain TDPID. So if you put an environmental variable NODENAME followed by an integer value n, then CLI tries to connect to the first n cop entries/nodes. So if



you have ODIN=4* CLI would look for odincop1, odincop2, odincop3, and odincop4 but not odincop5.

* The environment variable has to be in capitals.

Parallel LAN Guidelines Guidelines are being developed on how to set up parallel LANs per node in relation to the number of devices and device types (TBA).

BAR SERVERA number of things related to the BAR server can have an impact on performance. Explicit guidelines and impacts are being investigated and tested. As information becomes available, it will be added to future versions of this guide. Some of the areas to be aware of include: BAR server processing speed Data rate through server(s) OTB BAR application and Teradata 9203 platform Distribution of data streams across nodes and servers Number of data streams

Operating System Dependencies (Tunables)

Windows BAR Servers TCP TunablesThese parameter recommendations apply to all interfaces used by the Windows BAR Server. These instructions will make the tuning changes global (in other words, they will apply to all interfaces).1. Start -> Run -> regedit2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ Parameters



3. Check the settings/existence of the three parameters at the bottom of this document. If they exist and have the same values as the

recommendations below, you are done. If they exist and need to be changed, right-click on the

value name, select modify, and change the value. If they do not exist:

a. Select Edit -> New -> DWORDb. Type in the parameter name and hit enterc. Right-click on the new parameter and select Modifyd. Select the decimal radio button and type in the

recommended value.e. Select the OK button to save the new value.

4. Reboot when the changes have been made.

Shared memory tunablesShared memory is used differently between each of the OTB products. Please refer to the guidelines for specific OTB products in the Performance Tunables section of this chapter under Software/OTB Utilities.

Windows

Shared memory is not tunable in a Windows Operating System.

Linux

As a rule, the default tuning parameters in Linux will accommodate the requirements of the specific OTB product.



After calculating your product’s shared memory requirements, compare it against the maximum shared memory segment size:# sysctl kernel.shmmaxkernel.shmmax = 33554432#In this case, the maximum size is 32 megabytes. Unless your calculation is greater, no tuning is necessary. To immediately change the value:# sysctl –w kernel.shmmax=<your_new_value>To ensure the change will span rebooting the system, add the following to /etc/sysctl.conf:kernel.shmmax=<your_new_value>

MP-RAS

The default for maximum shared memory segment size may not be large enough for your NetVault calculation. If it does need to be increased, you will need to use the command idtune, rebuild the kernel, and then reboot the system, as follows:# /etc/conf/bin/idtune SHMMAX <your_new_value>Then, rebuild the kernel:# /etc/conf/bin/idbuild.Once the kernel build is completed, reboot the system.

Basic BAR Server ConfigurationThe BAR server is preconfigured. However, the following recommendations from the BAR Server Configuration and Use Orange Book may be useful.Backup via Ethernet requires careful tuning on both the Teradata and the tape server (BAR) to achieve maximum throughput. Be sure that the TPA nodes are tuned to support the throughput required by the BAR server. This involves both TCP/IP and kernel tunables.Be sure that the BAR server is configured correctly and that the applications are tuned for maximum throughput.On the TPA nodes, be sure that the Gigabit Ethernet is configured properly. The Teradata e1000 driver supports the Intel PRO/1000

series of network adapters.



Some TPC/IP and other kernel tuning will be required. On BAR servers, the Intel PRO/1000 driver tuning settings

need to be adjusted. During job execution, ARC parameters will affect performance and need to be checked. For best performance, there may also be some OTB application tuning required. See the Software/OTB/Utilities section of this chapter.The most basic BAR server configuration is standalone drives attached to the BAR servers. Most customer installations will include a library, and some may also include a SAN or an ACSLS (shared library).FROM: Introduction to the BAR Server Configuration Guide:The Teradata BAR server installation differs from previous configurations in that the BAR processes and hardware are moved off of the Teradata TPA nodes, and onto dedicated BAR servers. This results in better BAR performance - the processes no longer have to compete with Teradata for CPU resources. Unfortunately it is not the case that the load on the Teradata nodes is reduced, because the overhead previously needed by the BAR processes is now needed by the TCP/IP processes to move the data off of the node.The BAR Server Configuration Guide covers both configuration and trouble-shooting of a BAR server installation. The information in it reflects our knowledge as of March, 2005, and is based on both lab and field experiences.



Table 27: Basic Teradata BAR Server Configuration

SOFTWARE/OTB/UTILITIESCheckpointing: Advantages and Disadvantages

Checkpointing Overview

Checkpointing is a technique for inserting fault tolerance into computing systems. It basically consists of storing a snapshot of the current application state, and then using it for restarting the execution in case of failure.

Both archive and restore/copy operations take checkpoints in the data phase. Every time the specified number of data blocks are processed, Teradata ARC saves the tape positioning and other processing information in the restart log. The frequency of checkpoint operations is controlled by the number of data blocks processed.Because checkpoint operations cause I/Os and additional processing overhead, too many checkpoints might adversely impact performance. Each Teradata ARC data block contains up to 32K.The CHECKPOINT parameter also controls the frequency of VERBOSE display, if active. To see the amount of data processed every minute with an approximate archive rate of 1MB/second, set the CHECKPOINT value between 2500 and 4500.


http://www.answers.com/topic/failure

http://www.answers.com/topic/application-software

http://www.answers.com/topic/fault-tolerant-system


Setting a checkpoint frequency too high (a low CHECKPOINT value) might impact performance.

Setting a checkpoint frequency too low (a high CHECKPOINT value) causes Teradata ARC to reprocess a large number of data blocks in case of a restart.

Customers will weigh the advantages and disadvantages of checkpointing and decide whether or not they want to use it. Think of it in terms of an insurance policy: it has a cost.

Advantages

Checkpointing can save time if a DBS restart occurs during a large backup.

Disadvantages

Checkpointing only applies if the error is a DBS restart. It can be costly in NetVault: each checkpoint is a segment on

the tape. Since there can be several hundred segments in a large backup, it can cause a tape scan and/or a restore to be very slow.

It is also costly in NetBackup: each checkpoint causes the existing NBU job to terminate and a new NBU job to be launched in both the backup job and the restore job.

NetVaultBackup operations on a large Teradata database system can potentially require a significant amount of time, during which the database is unavailable. Since the database must be made available to users as soon as the backup process is complete, you may not have the time to repeat the backup process in its entirety if a failure should occur. NetVault can apply checkpoints to the backup process, assuring that data is backed up if a failure occurs during the process. Checkpoint Restart allows a job to resume the backup at the last successfully completed increment without having to restart the process from the beginning once the problem is identified and resolved (This option can be set from the backup window’s Backup Options tab for the Teradata plug-in. If, during a backup, the RDBMS crashes, suffers a power failure, or is reset, the job will not be aborted. NetVault waits for the DBS to be brought back on-line, rewinds the backup media to the last agreed safe location, or checkpoint, and continues the backup from that point. At intervals during backup operations, the Teradata ARCMAIN client software instructs NetVault when the job has reached a checkpoint location. NetVault assures that all data



transferred up to this point is physically stored on the backup medium and not cached in any volatile memory buffers before responding to the ARCMAIN client. This procedure ensures that in the case of a database failure, the data transferred up to the most recent checkpoint location is known to be good. Flushing these buffers is detrimental to the performance of the backup, depending on the type of backup device being used. Because of this, the checkpoint restart facility may be enabled or disabled on a job-by-job basis, by choosing the appropriate backup options. Whether the use of checkpoint restart is beneficial should be decided on a case-by-case basis. An important factor is the length of time the backup job takes to execute and the amount of time left if the backup were to fail towards the end of the job. It is worth noting that the performance impact of checkpoint restart is greater in cases where many small databases and tables are present as opposed to fewer larger objects.

NetBackup

SEE: NetBackup Performance Tunables

TSMTivoli checkpointing is the same as ARC, but only for restores, not for backups. Backups are not restartable.

Performance Tunables

NetVaultThis annotated information is from the NetVault Administrator's Guide, the NetVault Configurator Guide, and the Getting Started Guide.

Performance - The Device Management Window

The Device Management window of NetVault (available in the Edit Drive Window) can be used to enhance overall performance in several ways. Predominantly, two methods are used to: Increase block size Increase the transfer buffer spaceSelect the Configuration tab and locate the Media Block Size (Kb) field and increase this value (in increments of 32).



With this value increased, larger blocks of data will now be allocated for a backup, thereby reducing the overall number of times a backup will need to read data and write it to media. The end result is a faster overall backup.While still in the Edit Drive window, access the Performance tab. Locate the Amount of Memory to Assign for Transfer Buffers (Kb) field. Increase this amount from its default of 257 Kb (e.g., to 4,097 approx. 4 MB). By increasing this value, a larger amount of buffer space will be created through the use of system memory. As an end result, this increased space can be used by a NetVault job in order to speed up the overall process.Amount of Memory to Assign for Transfer Buffers (Kb) - This value represents the amount of buffer space that is to be shared between the two transfer functions, and is allocated in blocks of 32Kb. It is recommended that you increase this amount from its default of 257 Kb (e.g., to 4,097, or approx. 4 MB). By increasing this value, a larger amount of buffer space will be created through the use of system memory. As an end result, this increased space can be used by a NetVault job in order to speed up the overall process.Important:1. The field amount of memory to assign to transfer buffers (Kb)

is often referred to as the “shared memory setting.” Shared memory is usually allocated in 32Kb blocks. The default value in this field, 257 is actually eight buffers of 32Kb (plus a byte). Therefore, the formula used to determine a valid setting for this field is as follows:(<Total number of buffers> x 32Kb) + 1 byteWhen increasing the clock size, this value should also be increased accordingly:<buffer> x <block size> + 1Shared memory parameters are OS tunables vs. the buffer space in NetVault, which is a user of shared memory.

2. Configuring total shared memory size depends on the operating system and physical memory available in the target machine. Be familiar with the memory available on a NetVault Server before attempting to increase this value.

3. The maximum allowable value in the Media Block Size (Kb) field depends on the operating system and SCSI Adapter in use. Therefore, unless configuring on an optimal machine that can handle large block size transfers, it is recommended



that this value not exceed 64 Kb on a Windows-based system or 128 Kb on a Linux/UNIX-based system. If this value is set too high, NetVault operations may “hang” while attempting a data transfer.

4. It is important to realize that setting a large Media Block Size (Kb) value could negatively affect overall media capacity. For example, if set above the recommended value to a high value such as 512Kb, whenever a small backup is performed (for example, text files) 512Kb of space is allocated on the tape for that specific backup, even if the intended files are considerably smaller. Therefore, only a portion of this space is used, and the rest is lost.

5. Block size changes made in this manner in the Performance tab will only take effect on blank media. If planning to back up to a tape with existing data and these new settings are desired, the tape must be blanked first (via the Blank command accessed by right clicking on media in the Devices tab -- please see the section, Blanking Media on page 108 for complete details on the use of this command).

6. It is strongly recommended that the Lock Transfer Buffer in Memory option be left selected unless told otherwise by a BakBone Technical Support representative.

In the General Tab of the NetVault Configurator: Minimum Network Send Buffer Size (Kb): Controls the minimum size of kernel memory NetVault can use to buffer data on network sockets. If the minimum buffer size is increased, performance may increase.

NetBackup This section recommends a starting point of tunable adjustments for a NetBackup environment. After installation and basic backup/restore tests, further tuning may be necessary. This process, from measuring performance to testing tuning changes, is covered in detail in the Symantec publication, “NetBackuptm Performance Tuning Guide.”

Using Shared Memory

Each BAR server is configured as both a backup client and a media server. One of the main reasons for this is the speed of using shared memory for transferring data between the backup client process, ARCMAIN, and the media manager process, bptm. Two shared memory tunables are the shared memory



buffer size (SIZE_DATA_BUFFERS) and the number of shared memory buffers (NUMBER_DATA_BUFFERS).SIZE_DATA_BUFFERS: This will depend on the type of tape device. This size must not be greater than the maximum allowable size by the device. In addition, this value must not exceed the maximum allowable I/O buffer size of the operating system. Since the intent of good performance is to keep a steady stream of data to the tape drive (in other words, reduce the number of stop/starts of the drive), the best initial value to try is the maximum buffer size of the tape drive or operating system (whichever is the lesser value. For example, this would be 262144 (256k) for an LTO3 tape drive on a Linux system.)Warning: Some Windows-drivers cannot manage a block size greater than 64K for the tape devices without a registry change.NUMBER_DATA_BUFFERS: This will depend on the amount of shared memory available. For BAR servers that have more than one stream (tape drive), the product of SIZE_DATA_BUFFERS * NUMBER_DATA_BUFFERS. For Linux, ensure that this value does not exceed the maximum segment size of shared memory. To check this, perform the following:

cat/proc/sys/kernel/shmmaxThe shmmax value should be greater. However if it is not and you wish to increase it, add a line to /etc/sysctl.conf:

kernel.shmmax=nnnnnnwhere nnnnnn is the number of bytes (decimal) you want the maximum shared memory segment to be.

Using Sockets

There should not be a shared memory override (in other words, the use of sockets) in a BAR server, unless directed by Global Support. Check to be sure that that there is not a file named NOSHM in /usr/openv/netbackup (Linux) or \Program Files\Veritas\NetBackup (Windows) directory.

To set NET_BUFFER_SIZE:Create a file in /usr/openv/netbackup/NET_BUFFER_SIZE (Linux or …\Program Files\VERITAS\NetBackup\NET_BUFFER_SIZE (Windows)



Edit the file, then add a line containing the desired value. For example, the line for 128k would read 131072.

Backup performance with

Teradata TARA (Linux) does not use checkpointing. However, the NetBackup Teradata Extension (Windows) has checkpointing automatically enabled. This checkpointing should be greatly increased, in that it will not provide any backup restart capability other than a TPA restart occurrence. In order to change it, add the following line to the …\NetBackup\DbExt\NCR_Teradata\TDconfig and each backup “*.bch” file under …\NetBackup\DbExt\NCR_Teradata\scripts directory:

CHECKPOINTINC 1000000This will increase it from the default (20 gigabytes) to 1 terabyte.We do not recommend checkpointing with the normal Teradata extension. It is disabled by ensuring that the CHECKPOINTINC parameter is in the .bch file with a value much larger than the maximum size of the backup.

Creating backup data sets that provide optimum performance on restores

When a NetBackup Teradata restore job is created and run, NetBackup will mount the proper tape and position it to the start of the tape image. The image is read from that point on. In other words, there is no fast positioning of the desired object within the backup image. In addition, when the object (database or table) is finally found and restored, the job remains active—the entire image must be read to the end for the job to complete successfully.These characteristics should drive backup dataset strategy. The optimum strategy would break the backup jobs into several manageable datasets. For example, if a Teradata System contained four large tables averaging 500 gigabytes, and 20 tables whose total is 100 gigabytes, it would be better for potential restores to have at least five backup jobs: one for each of the large tables and at least one more for the remainder of the small databases/tables. The latter could be broken into smaller jobs, so that a restore would do less “reading-for-positioning.” But the main points of this example are 1) by isolating the large tables in their own backup data set, “read-for-position” will not occur at the beginning or the end of the job, and 2) smaller tables have



overhead in creating table headers, and potentially stop the tape from streaming data.While ARCMAIN is waiting for Teradata to set up a “new” table, no I/Os are done to the tape drive, hence the tape drive stops reading. Once Teradata notifies ARCMAIN to proceed, a new read I/O request is sent to the tape drive. The tape drive, however, has startup latency before the read can be satisfied. It takes streaming read I/Os in order to approach the maximum data transfer rate of the tape drive, and streaming reads do not occur in processing small tables.

TSMThe only things we can do on our side is to use jumbo packets and tweak the gigabit networks (the TCIP settings) set to jumbo packets. For any other possible settings, see the IBM Red Book documents.

SEE: http://www.redbooks.ibm.com/Redbooks.nsf/portals/TivoliTivoli Storage ManagerClient Performance TuningDave Daun, IBM Advanced Technical Support, [email protected]

Cluster CountsCluster counts affect the balance of clusters per device or stream (for example, if you have 37 clusters and 7 streams, then five streams will be archiving five clusters and two streams will be archiving six clusters, which would create an unbalanced ARC job where some streams are transferring more data than others).Some clusters may be bigger than others, which would also affect how much data needs to be transferred per cluster (this could occur if you have differing models of nodes in your system that have different transfer rates).

Number of session attributes in setting up ARC jobsIn general, run no more than one session per AMP. If there are many AMPs, you may not want to have one

session for every AMP because it will take a long time to start up all of the sessions.

If there are many AMPs, you can specify a number of sessions that is an even multiple of the number of streams that your job will be running (for example, if there are five


http://www.redbooks.ibm.com/Redbooks.nsf/portals/Tivoli


streams, run with two sessions per stream for a total of 10 sessions).

A starting point would be to specify the number of sessions per ARC job to be equal to the number of AMPs per node.

Software Encryption

ARCUsing software encryption (e.g. Protegrity BAR Encryption with ARC) will impact backup and restore throughput. Overall impact depends on the algorithm and/or key strength used. Typical impact will be between 20-40% when compared to unencrypted backup/restore.

TSM

How to Set and Use TSM 5.3.x API AES 128 Transparent Encryption

When using a 5.3 TSM Server and the TSM API version 5.3, it is possible to use transparent encryption for the data. When setting up encryption to work with the TSM API, only transparent encryption can be used. There is no way for the TSM API client to prompt for an encryption key during the processing within the TDP and thus the encryption must be transparent.To enable transparent encryption, the following options need to be set in the dsm.opt file:1. Specify ENABLECLIENTENCRYPTKEY=YES in the option file.2. Determine the ENCRYPTIONTYPE AES128 or DES56 (AES128

is recommended).3. Set the include.encrypt for the objects to encrypt. For

example, to encrypt all data: include.encrypt \...\*

Thus the encryption parameters in the options file would be such as:enableclientencryptkey yesENCRYPTIONTYPE AES128include.encrypt *When using ENABLECLIENTENCRYPTKEY for encryption, the encryption key is stored in the TSM server database. This means that for objects using this transparent encryption method, the server database must exist and have the proper values for the objects to be restored. Transparent encryption is different than the encryption for the BA client where the key must be entered.



If lost, the data cannot be restored or retrieved. For the transparent encryption, the only way to lose the key would be some sort of disaster where the TSM server database was lost. Thus, ensure that you back up the server database frequently to prevent data loss.Please note that even though the TDP does not prompt for an encryption key, the encryption of the data is secure. During the backup processing, the client sends the encryption key along with the encrypted data for the backup; the encryption key is itself encrypted during transmission. The TSM server then stores the encryption key in inventory entries for each bitfile object. The encryption key is re-encrypted before being stored in the database. The TSM server stores the encryption key in inventory entries for each bitfile object. The encryption key is re-encrypted before being stored in the database.After the node is authenticated to the TSM Server (whether using a password or not), then it can access the data it has stored on the TSM server. Since the reason to encrypt the data is for security issues, it would not be recommended to have the TSM server authentication disabled. It is the client authentication processing that allows the data to be read. Thus, even if the restore is being performed to a different machine, you would go to the other machine and log on as the TSM node that did the backup and then restore; this should work even when transparent encryption is in effect.Additionally, when using encryption, this is CPU intensive.There is no easy way to tell that the objects are encrypted. A trace could be performed to show that encryption is occurring. This is put in place with the "service encrypt" traceflags. The following trace parameters would be specified in the dsm.opt file that is being used for the TSM API backup.tracefile C:\fully\Qualified\path\filename.txttraceflags service api encryptThe tracefile specified will need to be in a location that has write permissions for the user performing the backup. Then run an encrypted backup to capture the trace information. A small backup is sufficient. DES-56 encryption was not tested or suggested by Tivoli to be used.

SAN/DEVICESA number of things related to the SAN devices can have an impact on performance. Explicit guidelines and impacts are being investigated and tested. As information becomes



available, it will be added to future versions of this guide. Some of the areas to be aware of include: SAN tunables zoning Compressibility of the data I/O Datablock size Number of buffers Encryption Devices Number of devices and load leveling Type of devices Tape and Disk

A Word about Tape Drive Speeds Do not confuse the rated speed of the tape drive (MB/s) with the actual throughput of the whole BAR solution. Other factors must be taken into account, such as the throughput speed of the node and the amount of compression. For example, if you propose Ultrium 3 tape drives to the customer, you cannot guarantee 80 MB/s performance of the entire BAR solution.It also may be possible to exceed the rated tape drive speed. In other words, with highly compressible data, a T9840C drive may yield better than 30 MB/S.Table 28: Relative Speeds and Maximum Capacities of Tape Drives

Device Cartridge capacity (GB)

Speed (MB/s) MB per second

STK T9840C 40 30STK T9940B 200 30Ultrium 1 (LTO 1) 100 15-16Ultrium 2 (LTO 2) 200 32-35Ultrium 3 (LTO 3) 400 80

Disk to tape copies Disk to tape copies are limited by the slowest device involved.


APPENDIX FREQUENTLY ASKED QUESTIONSBackups

Question How does data file size impact backup performance?Answer The larger the number of smaller files there are, the larger the

overhead there is associated with backing them up. The worst-case scenario for backup is large numbers of small files. While we can’t control file size, customers should at least understand that full performance cannot be achieved under these circumstances.In general, Teradata objects are large and can take good advantage of high speed tapes.

Question What should I check first when a backup gets stuck?Answer Whenever a backup gets stuck, the first thing you generally

think of is the OTB logs, but you should check the database for locks. This is especially true when you have been doing multiple backups and restores. With TARA, if you cancel out of a backup or restore, the next time you try to do that function, you’ll find that the database has put a lock on it.

Question What are the backup options available for Teradata strategies and how do I decide what option to use?

Answer Overview Available backup options

Parallel Online Incremental

Backup scenarios Table size Update rate Availability requirements

All-AMP Backup


Uses a single backup process and a single output device to fully archive a set of objects

Benefits Simple to use – no extra options required for backup or

restore Drawbacks

Throughput limited to a single process or device Archives all data (including unchanged) for all objects Requires a read lock

Parallel All-AMP Backups Address throughput limitations by running multiple backup

processes in parallel Benefits

Utilize multiple devices for greater overall throughput Drawbacks

Additional setup required – need to create scripts which divide objects among the parallel processes

Requires multiple BAR user accounts for restore Other all-AMP backup drawbacks (read lock, archive

unchanged data)Cluster Backups Address throughput limitations by running multiple archives,

dividing data for each object at cluster level Benefits

Increased throughput Easier to set up than parallel all-AMP

Drawbacks Restore limitations (e.g. change in AMP configuration) Requires multiple BAR user accounts for restore Other all-AMP backup drawbacks (read lock, archive

unchanged data)Online Backup (GROUP READ LOCK) Use permanent journals and the GROUP READ LOCK feature

of ARC to eliminate the read lock Benefits

Allows updates during the backup process Compatible with all-AMP or parallel backup types



Drawbacks Requires use of PJ – extra setup, some performance

penalty Extra complexity of backups – need to archive journals Compatibility of journal backups (cannot be restored

across major Teradata release) Rollforward slow for large update volume

Selected Partition BackupArchive individual partitions of tables instead of all data Limit archive to only partitions that have changed data Benefits

Don’t archive old data repeatedly Drawbacks

Extra complexity to create partition backup Extra restore complexity – restore partitions incrementally Requires date-based partitioning on table No partition update indicator – must track changed

partitions manually No cluster-level parallelism

Permanent Journal Backup Archive base table once, then archive permanent journal

table only Benefits

Incremental – archives only changed rows Online – updates can continue during journal backup

Drawbacks Overall system performance hit from journaling Complexity in managing incremental journal archives Incompatibility issues across major release No cluster-level parallelism DDL changes are difficult to accommodate

Backup Scenarios Three basic attributes:

Size o Small (< 1GB)o Medium (1 GB – 1 TB)o Large (> 1 TB)



Change volumeo Low (< 1%)o Medium (1-10%)o High (> 10%)

Load typeo Batch load – Updates occur at specific times, and may

be scheduled around a backup windowo Trickle load – Updates occur continuously

Small Tables Impact of backup for these objects is typically low

Short locking time – very small backup window needed Low throughput requirement

Generally prefer simpler backup method Less complexity in backup, restore Some backup features add overhead

Solution: All-AMP Optional – Parallel All-AMP for a very large number of

small objects (process large number of objects in parallel) Optional – Online (GROUP READ LOCK) backup if even

short backup window is not possibleMedium Tables – Batch Load Increased object size requires additional throughput to

complete backup in a reasonable time Solution: Parallel options (cluster or parallel all-AMP)

Both options add throughput at the cost of additional complexity

Which solution to use depends on other conditionso Use parallel all-AMP when restore will be done to

different configuration system (but only if database objects can be divided into groups of roughly equal size)

o Use clusters when restore will be done to same systemMedium Tables – Trickle Load Continuous update means that read lock directly impacts

system availability Load processes would need to be stopped for a backup

window Solution: Parallel solution with GROUP READ LOCK



Same conditions for selecting which parallel solution to use

Adds permanent journal complexity to backup and restore process

High update volume may impact journal backup time and overall restore time

Large Tables – Batch Load Very large table size may make full object backup impractical

Backups for some objects may take hours Solution: Incremental solution

Permanent journals probably only useful for low update volume

Selected partition backup for other cases Both solutions increase backup complexity Incremental restore can be difficult to manage Neither solution supports parallel archive via clusters

Large Tables – Trickle Load Continuous update makes read lock undesirable Solution: Online and Incremental solutions

Permanent journals for low update volume Selected partition backup with GROUP READ LOCK for

other cases Adds complexity for both partition and journal archive

management Very high update rate can impact backup and restore

times considerably (due to increase in journal size)



Backup Solution Matrix TablesTable 29: Backup Solution Matrix – Small Tables

Backup Solution Matrix – Small TablesUpdate Type Low Volume Medium Volume High VolumeBatch All-AMP All-AMP All-AMP

TrickleAll-AMP

(Optionally online)

All-AMP + Online

All-AMP + Online

Table 30: Backup Solution Matrix – Medium TablesBackup Solution Matrix – Medium Tables

Update Type Low Volume Medium Volume High Volume

Batch Parallel All-AMPor Cluster

Parallel All-AMP or Cluster

Parallel All-AMPor Cluster

TrickleParallel

(optionally Online)

Parallel + Online Parallel + Online

Table 31: Backup Solution Matrix – Large TablesBackup Solution Matrix – Large Tables

Update Type Low Volume Medium Volume High Volume

BatchPermanent Journal or Selected Partition

Selected Partition

Selected Partition

Trickle

Permanent Journal or Selected

Partition + Online

Selected Partition +

Online

Selected Partition +

Online

Support and CompatibilityQuestion What are the rules for support and compatibility between

releases?Answer See the Open Teradata Backup Products Release Matrices at: \\

sdfs601\ttu\TSM\OpenTeradataBackup\OTB Certification\OTB_Release_Matrix060515.doc

Certified: In general, TTU releases are certified with a specific RDBMS release and function with their current release plus the two previous releases. Supported: However, the only TTU releases that are candidates for Efixes are the current version and the previous version only.Teradata-Specific Restore and Version Compatibility



Check with the release matrices for any recent changes.Rule 1: If you have backed up a Teradata database from one release, you cannot restore to an older Teradata version.Rule 2: Backups from older releases can be restored to two releases forward. For example, backups made from version 4.0 can be restored to 5.0 and 6.0 but not to 7.0.This comes into play in situations where the customer is running multiple Teradata systems and they want to use ARC to copy data from one Teradata system to another. It will also come into play when the need arises to restore older archived backups. If the customer’s planned Teradata upgrade will put their oldest archived backups beyond this point, the recommended solution is an intermediate step, restoring them with the current system and backing them up again so that the customer is not left with archived backups that can no longer be restored on their Teradata system.ARCEnsure that your customer upgrades ARC when they upgrade their Teradata database.The TTU utility ARC (ARCMAIN), used by these OTB products, function with the RDBMS version with which they were released, plus the next two older versions of RDBMS. However, an older version of ARCMAIN will not function with a newer version of RDBMS.ARC (and its dependencies – CLIv2, data connector), ASF2 Tape Reader, Teradata ODBC Driver for Windows and SQLPP2 are all bundled together on the Tape Storage Enabler CD (CD-5). This CD cannot be ordered individually, but is shipped with the order of NetVault, NetBackup or Tivoli. When ordering one of these products, ensure that the TTU version of CD-5 is a version that upholds the general rules stated above.TTU 8.1.00.02 or later must be used in conjunction with TARA 1.0.0.0. Arc 8.1.00.02 contains DR 103153 that enables TARA functionality.

NetBackupQuestion What are some general guidelines to follow when working in the

NetBackup environment?Answer These are generally good ideas to follow:



Create all archive jobs separated by database Create clusters archive scripts as single-stream jobs with

cluster numbers specified on the ARCMAIN scripts Even distribution of SATA across all tape drive Define a maximum wasted time in case of failure Generate the archive scripts using the optimal number of

tape drives based on the maximum wasted time At least one spare tape drive available in case of a failure Create individual policies for each storage unit based on the

archive process (monthly, weekly, daily, and ad hoc) Create individual volume pools for each archive process

(monthly, weekly, daily, and ad hoc)

NetBackup Migration Questions and AnswersQuestion Why do we need a migration program and what is different from

the typical software upgrade process when updating a customer from one software version to another?

Answer There is a requirement to change the configuration architecture from MP-RAS direct-attached to a new LAN-based architecture with Gigabit switches and BAR servers (Windows or SUSE Linux).This architecture change not only requires the license transfer from MP-RAS to Windows or SUSE Linux, but also introduces new licensing methodology and new components (Gigabit switches and BAR servers) to complete the migration.This migration and license transfer will require a Certificate of Destruction to be processed for all MP-RAS licenses removed from the system. The Certificate of Destruction can be found in QuickLook under Forms. The title of the required form is “Credit & Reshipment Request Form” and should be filled out and sent to IPP. The reason code is “08 Other” and you write in “Symantec (Veritas) Migration.”Some of the new hardware components will need to be provided by the customer. It is mandatory that Operational Services BAR Pre-Sales be utilized in your respective region to ensure that proper planning is done for the migration.Each migration and license transfer will have a combination of gratis software, chargeable software, new hardware, and services.



A special “migration” product ID has been created to assist in the proper identification of the “gratis” portion of the migration.Due to limitation of the Teradata ordering system and the need to ensure proper royalty payments, the Symantec order needs to be submitted in two parts. Part A would include the transfer of the MP-RAS licenses to NetBackup 6.0 Windows/Linux and requires the inclusion of F902-0MGR-6000. Part B would include all new components and would include F902-0ADD-6000. Each part must be submitted separately for proper processing.

Question What are the key elements of this migration activity?Answer Migration and configuration planning is the most important

activity for completing a successful implementation of the new architecture.Identification and separation of gratis and revenue order segments of the legacy and new configurations. (See final bullet for question number 1).Communication, expectation-setting, and management of this required activity with each of your respective accounts.Working with Operational Services BAR Pre-Sales Support to coordinate Gigabit adapters, Gigabit switches, BAR server requirements, and other architectural requirements.

Question What are the rules and guidelines for this migration program?Answer All current Teradata/Symantec customers using all versions of

NetBackup prior to 5.0 are included in this migration. The following chart gives the migration requirements.Table 32: Customer Requirements for NetBackup Migration

Customer Status: RequirementUpgrades and/or expansions of existing NetBackup implementation

Entire system must be migrated to NetBackup 5.0/5.1 or 6.0 with LAN-based architecture

No change to existing system in 2005

Upgrades to NetBackup 5.0/5.1 or 6.0 and install LAN-based architecture should have been completed by June 30, 2006.

Adds new system Must order NetBackup 5.0/5.1 or 6.0.

Gratis license transfers from MP-RAS to Windows/SUSE Linux only apply to customers who have a current maintenance contract for the existing NetBackup product ids and are properly recorded in the Customer Support D1 system.



The special migration product ID, F902-0MGR-6000, must be on all orders which are associated product ids that are entitled to the “gratis” transfers. See question 1 final bullet for details. This designation is extremely important as it ensure that the customer is not charged for the license transfer and relieves Teradata from any royalty obligation to Symantec for these transfers.A Certificate of Destruction (COD) must be processed for NetBackup 3.4 or 4.5 MP-RAS product IDs within 30 days of the shipment of NetBackup 5.0/5.1 or 6.0.Failure to process a COD in a timely manner will result in a charge-back to the sales team within 60 days of the NetBackup 5.0/5.1/6.0 order processing.

Question What are some of the known problems and pitfalls for NetBackup TARA?

Answer

1. For NetBackup (and in general), for efficient use of the network, the MTU has to be set to 9000 for SUSE Linux and 9014 for Windows.

2. On SUSE Linux for NetBackup, inetd/xinetd services must be activated. Before doing any installation, be sure to read the latest knowledge articles so as to have the benefit of the latest lessons learned.

3. If you uninstall and then reinstall NetBackup, or if you upgrade NetBackup, then you have to re-run nbubar_postinstall.sh.

4. You cannot have one policy for two streams. If you do, the error will be in the ARC log and the message will be: “805 error 34, BAM 0020 unrecognized field name

starting at =” followed by the server name.5. When reinstalling the TARA server, one must stop and start

NetBackup services, and then close and open the TARA GUI. 6. The NetBackup “Make SCSI Device” command is commented

out after the initial configuration: if a drive drops out and you restart NetBackup, you lose the SCSI target address.

7. Be sure to install Maintenance Pack 4 (MP4) before installing NetBackup 5.1, otherwise the “Make SCSI Device” command will hang.



8. If you keep non-TARA files in the Job Information Repository (JIR), it will cause an error popup.

9. When doing TARA setup, “localhost” is the default name given for the server. Problems have been encountered when this is not changed. We strongly suggest that you change this to the actual server name.

10. A pitfall with SUSE Linux is that the default installation does not load all of the libraries that NetBackup needs to operate. This is especially apparent when trying to run the GUIs. You can either select the Custom install if you know which libraries to load, or select All less the SUSE Linux games.

11. There is an SSH pitfall with TARA: When you rerun teraserver_postinstall.sh it creates a new SSH key, requiring that nbubar_postinstall.sh needs to be rerun on all the clients to update the hosts/keys. If the hosts are not updated, the job will remain in a connecting state and never do the backup or restore.

12. Do not manually modify the defaults file unless you are a Teraserver user. If you are root user and manually modify the defaults file, you will change the server configuration: the changes will remain, but you won’t be able to change the server settings/configurations from the GUI again since the permissions will have changed.

13. When creating a NetBackup scheduled job, the scheduled policy must have Teraserver as the client.

14. The TARA clients/BAR server names must not be changed or altered, since the TARA server will then no longer be able to communicate with the altered server.

NPARCQuestion What is NPARC, and how is it used?Answer NPARC (Named Pipes and ARC) is a way to copy or transfer

data directly from one Teradata system to another through a network connection without first going to disk or tape. The effect on the source system is the same as a normal backup, but because the procedure is automated, doing the migration in this way is more efficient than if the system were to be backed up and then restored to the new system. Just as with backup and restore, all users, access rights, passwords, and data will be



identical on the target system when the full Data Migration NPARC procedure has been used.NPARC is sold as a Data Migration Service (DMS) and a Continuous Migration Service by Ops Services. It is typically used by customers who are installing a new Teradata system and must migrate their data from the old system to the new one. It is also used by some customers to periodically move data from one system to another (Ex. Prod to Dev). Questions should be directed to Mark Newton or Randy Bell.

Tape DrivesQuestion How many tape drives do I need per BAR server?Answer Our normal recommendation is two tape drives per BAR server

since the servers cannot typically take advantage of the performance for more. As far as physical limits, both NetVault and NetBackup can have many tape drives attached to each server. With Tivoli, one BAR server will support up to four tape drives. A second BAR server is required when configuring two tape drives per node.

TERADATA SERVICESWe should document a flow for handling problems/questions that exceed the scope of this guide – organizational responsibilities only

Availability Assessment Detailed assessment Focuses on the issues you should consider for raising the

availability of your Teradata environment. Technical issues Operational best practices Helps you understand which products, services, and features

are best suited for your environment. Compare your processes and procedures to Teradata best

practices. Future view of how certain types of incidents will affect the

availability of your data warehouse.



Business Impact Analysis Determine the impacted applications and related financial

assumptions Determine the impact of downtime; planned and unplanned Determine the impact of degraded performance Determine the requirements to protect, archive, and restore

data. Recommend the appropriate Business Continuity Solutions

for the business.

Disaster Recovery Planning Service (Fee-based consulting)

BAR AND BUSINESS CONTINUITYRequirement BAR

OnlyCold Standby &Recovery Center

Cold Standby(Daily Restore)

Dual Active(Active/Active&Active/Standby)

Recovery Point Objective - Typical

Last Backup (24 hours)



Less than 1 minute

Recovery Point Objective - Worst

Last recoverable Backup




Recovery Time Objective

30-60 days 2-4 days 12 hours Less than 1 hour

Backups 4-8 hours of downtime for tape backup

(None – 2H2007)

4-8 hours of downtime for tape backup

(None – 2H2007)

4-8 hours of downtime for tape backup

(None – 2H2007)

No downtime with Target side backups

System Maintenance

Production Down Production Down Production Down Less than 1 hour for switchover

Performance ImpactOverhead

None None None < 10%

DR System Utilization

NA 0% 0% 10-100%

Operational Complexity

Low Low - Moderate Low - Moderate Moderate


GLOSSARY

AACSLS The Automated Cartridge System Library Software is the

software set that control and manages the robotics of mid-to-large robotic tape systems and enables the consolidation and centralization of data backup/archive/restore. Housed on its own server, ACSLS enables multiple systems, each with different tape management software (such as NetVault and NetBackup), to share a single library or modular library system. ACSLS is required for the Teradata 9202.

administrative This term is typically only used in relation to human involvement; for example, an administrative console panel.

AEF Active Engine Failover is the ability to continue backups if one of the servers in a DL720 or DL740 configuration fails.

AMP Access Module Processors are virtual processors (vprocs) that receive steps from PEs (Parsing Engines) and perform database functions to retrieve or update data. Each AMP is associated with one virtual disk (vdisk), where the data is stored. An AMP manages only its own vdisk, not the vdisk of any other AMP.

AMP file system

The file system software accesses the data on the virtual disks. Each AMP uses the file system software to read from and write to the virtual disks.

AWT The AMP Worker Task functions in the AMP perform a number of operations, including: o Locking tables to ensure data consistency. o Executing AMP step operations such as select, insert, update,

delete and sort. o Joining tables as required. o Executing end transaction steps as required to support multi-

AMP operations. ANSI The Teradata Database is an open system, compliant with

American National Standards Institute standards. API Application Programmer Interfaceapplication An application is software that accesses the Teradata Database. It

can run on various platforms: o Channel-attached client o LAN-attached client o Node


ARC The Teradata Archive/Recovery utility is included with Teradata BAR. Teradata provides ARC to perform backup and restore operations on tables, databases, and other objects. In addition, ARC interfaces to two third-party products to support backup and restore capabilities in a network-attached environment. There are several scenarios where restoring objects from external media may be necessary: Restoring non-Fallback tables after a disk failure. Restoring tables that have been corrupted by batch processes that may have left the data in an uncertain state. Restoring tables, views, or macros that have been accidentally dropped by the user. Miscellaneous user errors resulting in damaged or lost database objects. With the ARC utility you can copy a table and restore it to another Teradata Database. It is scalable and parallel, and can run on a channel-attached client, network-attached client, or a node.

architecture We might reduce this complicated subject to the following simple definition: The design of a computer system that sets the standard for all devices that connect to it and all the software that runs on it.For the purposes of the BAR Solutions Guide, since the term gets used quite broadly, we have used the word “architecture” only to refer to (1) LAN-based and direct-attached BAR solutions, (2) Teradata itself, and (3) the enterprise architecture at customer sites.

ARCMAIN ARC program module, used to start the program ARCNET ARCNET is a widely-installed local area network (LAN) technology

that uses a token-bus scheme for managing line sharing among the workstations and other devices connected on the LAN. The LAN server continuously circulates empty message frames on a bus (a line in which every message goes through every device on the line and a device uses only those with its address). When a device wants to send a message, it inserts a "token" (this can be as simple as setting a token bit to 1) in an empty frame in which it also inserts the message. When the destination device or LAN server reads the message, it resets the token to 0 so that the frame can be reused by any other device. The scheme is very efficient when traffic increases since all devices are afforded the same opportunity to use the shared network. ARCNET can use coaxial cable or fiber optic lines. ARCNET is one of four major LAN technologies, which also include Ethernet, Token Ring, and FDDI.


http://searchNetworking.techtarget.com/sDefinition/0,,sid7_gci213957,00.html




http://searchDataCenter.techtarget.com/sDefinition/0,,sid80_gci211806,00.html




assign To make a virtual tape library or drive available to a backup server (see SAN client). Similar to Access Logix™, tape assignment allows only specified WWPNs to use the devices.

ATA Advanced Technology Attachment is the official name that ANSI group X3T10 uses for what the computer industry calls Integrated Drive Electronics (IDE).Both ATA and SCSI interfaces are traditional parallel architectures that transfer commands and data across multiple data lines simultaneously. ATA offered lower data rates and was mainly employed in personal computers, while SCSI provided faster data rates and appeared in workstations and servers.

auto archive When enabled on a virtual tape library, automatically initiates an export request when a tape is ejected from the library by backup software.

Bback up (v) To run backup software.backup (n) Copy of data in an alternate location and usually in an

alternate form. A backup requires backup software in order to read and restore the backup (see backup software).

backup client The system being backed up.backup server System that runs the backup software and controls when each

backup client runs its backup. The backup server obtains metadata from backup clients and stores the information in its database or catalog.

backup management software

The software running on the Teradata system, backup server, or BAR server that controls the flow of backup data from backup clients to the backup media. Backup agent software usually runs on the backup clients as well. Examples are: Bakbone NetVault, Symantec NetBackup, and IBM Tivoli Storage Manager.

BSP A backup software provider is company that writes backup software such as NetVault, NetBackup, and Tivoli Storage Manager (TSM).

bandwidth The amount of data that can be passed along a communications channel in a given period of time.The transmission capacity of an electronic pathway such as a communications line, computer bus or computer channel. In a digital line, it is measured in bits per second or bytes per second (see Mb/sec). In an analog channel or in a digital channel that is wrapped in a carrier frequency, bandwidth is the difference between the highest and lowest frequencies and is measured in Hertz (kHz, MHz, GHz).


http://searchstorage.techtarget.com/gDefinition/0,294236,sid5_gci212949,00.html

http://searchstorage.techtarget.com/gDefinition/0,294236,sid5_gci213788,00.html

http://searchStorage.techtarget.com/gDefinition/0,,sid5_gci214013,00.html



batch sessions in BTEQ

In a batch session, the user saves BTEQ commands and SQL statements in a scripted file. The file can be run directly, or a system with the ability to execute files can run it at a defined time.

batch window A period of time during which a table or database is locked for maintenance (inserting, updating, or deleting data). This is a traditional and commonly used method for maintaining data in a relational database with changes such as:This month's customer service records This week's sales from all retail stores in the region Today's transactions from all branches in the bank During a batch window, users are temporarily unable to access the data in the locked tables and databases that are being processed. The batch processing usually occurs at regular intervals, such as every night, at the end of each week, or at the end of each month. In the time periods between batch windows, the data in the database may not reflect all updates up to the minute.

BCS Business Continuity Strategy (Teradata) blocksize Number of bytes in a tape block. Unlike disks, which have 512-

byte sectors, tapes do not have pre-allocated fixed-size blocks.BOS BAR Operational Services (Teradata); Pre-sales bridge A device that connects two local-area networks (LANs), or two

segments of the same LAN that use the same protocol, such as Ethernet.

BTEQ The Basic Teradata Query (pronounced “BEE-teek”) is a Teradata database tool used for submitting SQL queries on all platforms.

bus In a computer or on a network, a bus is a transmission path on which signals are dropped off or picked up at every device attached to the line. Only devices addressed by the signals pay attention to them; the others discard the signals. According to Winn L. Rosch, the term derives from its similarity to autobuses that stop at every town or block to drop off or take on riders In general, the term is used in two somewhat different contexts: (1) A bus is a network topology or circuit arrangement in which all devices are attached to a line directly and all signals pass through each of the devices. Each device has a unique identity and can recognize those signals intended for it. (2) In a computer, a bus is the data path on the computer's motherboard that interconnects the microprocessor with attachments to the motherboard in expansion slots (such as hard disk drives, CD-ROM drives, and graphics adapters).

BYNET The BYNET (banyan network) is a combination of hardware and software that provides high performance networking between the nodes of a Teradata Database system. A dual-redundant, bi-


http://searchSMB.techtarget.com/sDefinition/0,,sid44_gci212594,00.html



directional, multi-staged network, the BYNET enables the nodes to communicate in a high speed, loosely-coupled fashion. It is based on banyan topology, a mathematically defined structure that has branches reminiscent of a banyan tree.The BYNET (pronounced, "bye-net") is a high-speed interconnect (network) that enables multiple nodes in the system to communicate. The BYNET handles the internal communication of the Teradata Database. All communication between PEs and AMPs is done via the BYNET. When the PE dispatches the steps for the AMPs to perform, they are dispatched onto the BYNET. The messages are routed to the appropriate AMP(s) where results sets and status information are generated. This response information is also routed back to the requesting PE via the BYNET. Depending on the nature of the dispatch request, the communication between nodes may be to all nodes (Broadcast message) or to one specific node (point-to-point message) in the system. Scalable: As you add more nodes to the system, the overall network bandwidth scales linearly. This linear scalability means you can increase system size without performance penalty -- and sometimes even increase performance. High performance: An MPP system typically has two BYNET networks (BYNET 0 and BYNET 1). Because both networks in a system are active, the system benefits from having full use of the aggregate bandwidth of both the networks. Fault tolerant: Each network has multiple connection paths. If the BYNET detects an unusable path in either network, it will automatically reconfigure that network so all messages avoid the unusable path. Additionally, in the rare case that BYNET 0 cannot be reconfigured, hardware on BYNET 0 is disabled and messages are re-routed to BYNET 1. Load balanced: Traffic is automatically and dynamically distributed between both BYNETs. Hardware: The nodes of an MPP system are connected with the BYNET hardware, consisting of BYNET boards and cables. Software: The BYNET driver (software) is installed on every node. This BYNET driver is an interface between the PDE software and the BYNET hardware. SMP systems do not contain BYNET hardware. The PDE and BYNET software emulate BYNET activity in a single-node environment.



CCAP A Cartridge Access Port is a location within a tape library to hold

one or a limited number of tape cartridges for purposes of adding and removing tapes.

catalog or index

A collection of metadata that identifies the details of a backup (for example, the names of the backup clients (hosts) backed up; the names, sizes, and dates of the files backed up; the location on the backup media). This information is examined when restoring files.

CDL CLARiiON® Disk Library The EMC appliance that presents virtual tape drives and libraries to the SAN for use by backup software. A physical tape drive or tape library may be connected to the CLARiiON Disk Library for exports and imports.The EMC CLARiiON Disk Library is an appliance consisting of one or more hardware controllers, and one or more RAID disk subsystems. Virtual tape libraries are created and can be used as direct plug-and-play replacements for physical libraries.

CLARiiON disk library console (CDL console)

The graphical administration tool, also known as a graphical user interface (GUI), used to configure and manage the CLARiiON Disk Library.

CLI Call-Level Interface, a library of routines that are the lowest-level interface to the Teradata Database.

client parallelism

The number of concurrent backup sessions a particular client can send to a NetWorker server or storage node.



clique A clique (pronounced, "kleek") is a group of nodes that share access to the same disk arrays. Each multi-node system has at least one clique. The cabling determines which nodes are in which cliques -- the nodes of a clique are connected to the disk array controllers of the same disk arraysIn the event of a node failure, cliques provide for data access through vproc migration. When a node resets, the following happens to the AMPs: When the node fails, the Teradata Database restarts across all remaining nodes in the system. The vprocs (AMPs) from the failed node migrate to the operational nodes in its clique. Disks managed by the AMP remain available and processing continues while the failed node is being repaired. Vprocs are distributed across all nodes in the system. Multiple cliques in the system should have the same number of nodes. The diagram below shows three cliques. The nodes in each clique are cabled to the same disk arrays. The overall system is connected by the BYNET. If one node goes down in a clique the vprocs will migrate to the other nodes in the clique, so data remains available. However, system performance decreases due to the loss of a node. System performance degradation is proportional to clique size.

CLIv2 Call-Level Interface, version 2 is a library of routines that enable an application program to access data stored in the Teradata Database. When used with network-attached clients, CLIv2 contains the following components: CLI (Call-Level Interface) MTDP (Micro Teradata Director Program) MOSI (Micro Operating System Interface)

cluster A group of AMPs that provides Fallback capability in case of an AMP failure. A cluster is typically made up of four AMPs, but can be as large as sixteen AMPs.

compression The ability to store more usable data on the media by compacting the data. Most real tape drives support compression. If enabled via the Console, the CDL can compress data stored on virtual tapes.

configuration o The way in which a computer system is set up: changed the configuration by resetting the parameters.

o The set of constituent components, such as memory, a hard disk, a monitor, and an operating system that make up a computer system.

o The way that the components of a computer network are connected.



CPU Central Processing Units are not physically associated with vprocs.

DDBMS Database Management Systemdedicated tape drive

A tape drive within a library that is statically and permanently associated with one backup client (see shared tape drive).

device file The name by which an operating system refers to a device. For a tape drive (real or virtual), the name might be \\.\Tape0 on a Windows system or /dev/rmt/0cbn on a Solaris system.

DR Deficiency Report

EEBCA EISA Bus-to-Channel Adapter connectionsEMC disk drives

EMC is the company that owns CLARiiON®, the maker of the Teradata 9205 virtual tape library.

encryption A procedure that renders the contents of a computer message or file unintelligible to anyone not authorized to read it. The message is encoded mathematically with a string of characters called a data encryption key. Two widely used encryption methods are DES (Data Encryption Standard), developed by the U.S. National Bureau of Standards and used by the government and many financial institutions, and PGP (Pretty Good Privacy), developed by Philip Zimmerman and adopted by many private users.The coding of a clear text message by a transmitting unit so as to prevent unauthorized eavesdropping along the transmission line; the receiving unit uses the same algorithm as the transmitting unit to decode the incoming message. The reversible transformation of data from the original (the plaintext) to a difficult-to-interpret format (the ciphertext) as a mechanism for protecting its confidentiality, integrity and sometimes its authenticity. Encryption uses an encryption algorithm and one or more encryption keys.

ESCON Enterprise Systems Connection, or Enterprise Systems Connectivity, is an IBM fiber optic connection technology that interconnects S/390 mainframe computers, workstations and network-attached storage devices across a single channel and supports half duplex data transfers. One of the key elements of ESCON is the ESCON Director, an I/O switch capable of providing dynamic, nonblocking, any-to-any connectivity for up to 60 fiber optic links operating at 200 Mb/s.

ESM EMC Support Matrix.



Ethernet The standard local area network (LAN) access method. A specification for "LAN," "LAN connection" or "network card" automatically implies Ethernet without saying so. Ethernet connects devices to a company or home network as well as to a cable modem or DSL modem for Internet access. Ethernet is defined by the IEEE as the 802.3 standard (see 802.3).

Ethernet card and LAN cables

An Ethernet card enables communication between a network-attached client (on the LAN) and the Teradata Gateway. Ethernet cards are located in system bus slots. LAN cables connect the Ethernet cards in the system bus to the LAN.

export The process of removing a cartridge from a physical tape library.The process of writing the contents of a virtual tape to a physical tape.

export request

Request made through the CDL Console. If configured in the Console for auto archive, the process that occurs when backup software ejects a tape from a virtual library.

extensions Teradata Extensions (TDE)

Ffabric (or switched fabric)

Switched Fabric is a Fibre-channel topology where many devices connect with each other via Fibre-channel switches.


http://www.answers.com/topic/ieee-802-3


fallback Fallback is a Teradata Database feature that protects data in the case of an AMP vproc failure. Fallback guarantees the maximum availability of data. You can specify Fallback protection at the table or database level. It is especially useful in applications that require high availability. Fallback protects your data by storing a second copy of each row of a table on a different AMP in the same cluster. If an AMP fails, the system accesses the Fallback rows to meet requests. Fallback provides AMP fault tolerance at the table level. With Fallback tables, if one AMP fails, all data is still available. Users may continue to use Fallback tables without any loss of available data. During table creation or after a table is created, you may specify whether or not the system should keep a Fallback copy of the table. If Fallback is specified, it is automatic and transparent. Fallback guarantees that the two copies of a row will always be on different AMPs. If either AMP fails, the alternate row is still available on the other AMP.

fallback: software tools

The following Teradata utilities are used to recover a failed AMP: Vproc Manager: Enables you to: Display and modify vproc states. Initiate Teradata Database restarts. Table Rebuild: Reconstructs tables on an AMP from data on other AMPs in the cluster. Recovery Manager: Lets you monitor recovery processing.

FC-AL Fibre-channel-Arbitrated Loop



fibre-channel Fibre-channel is a technology for transmitting data between computer devices at data rates of up to 4 Gbps. Fibre-channel is especially suited for connecting computer servers to shared storage devices and for interconnecting storage controllers and drives. Fibre-channel offers point-to-point, switched, and loop interfaces. (Answers.com)A high-speed transport technology used to build storage area networks (SANs). Although Fibre-channel can be used as a general-purpose network carrying ATM, IP and other protocols, it has been primarily used for transporting SCSI traffic from servers to disk arrays. The Fibre-channel Protocol (FCP) serializes SCSI commands into Fibre-channel frames. IP, however, is used for in-band SNMP network management. Fibre-channel not only supports singlemode and multimode fiber connections, but coaxial cable and twisted pair as well. Fibre-channel can be configured point-to-point, via a switched topology or in an arbitrated loop (FC-AL) with or without a hub, which can connect up to 127 nodes (see below). It supports transmission rates up to 4 Gbps in each direction. Fibre-channel uses the Gigabit Ethernet physical layer and IBM's 8B/10B encoding method, where each byte is transmitted as 10 bits. Fibre-channel provides both connection-oriented and connectionless services.

fibre-channel-to-SCSI bridge or router (fibre-SCSI bridge)

A device that connects one or more Fibre-channel (FC) links to one or more SCSI buses. The primary purpose of such a device is to connect other SCSI devices to nodes with fibre-channel. It is also for SCSI cable extensions.

FICON Fiber Connection, or Fiber Connectivity, IBM’s fiber optic channel technology that extends the capabilities of its previous fiber optic channel standard, ESCON. Unlike ESCON, FICON supports full duplex data transfers and enables greater throughput rates over longer distances. FICON uses a mapping layer that is based on technology developed for Fibre-channel and multiplexing technology, which allows small data transfers to be transmitted at the same time as larger ones.

Ggateway The Teradata Gateway software is the means of communication

between the PEs (on the node) and applications running on: Network-attached clients A node in the system

GDO Globally distributed object



gigabit Ethernet

Gigabit Ethernet, abbreviated GbE or Gigabit, is a version of Ethernet that supports data transfer rates of 1 Gigabit (1,000 megabits) per second. The first Gigabit Ethernet standard (802.3z) was ratified by the IEEE 802.3 Committee in 1998.

GSC Global Support CenterGSC analyst A technical specialist in one area of Teradata, i.e. Hardware, OS,

PDE, TDBMS. Client Software, ApplicationsGSC Duty Manager

An on-call manager and escalation point for Critical Incidents

Hhamming code

An error correction method that intersperses three check bits at the end of each four data bits. At the receiving station, the check bits are used to detect and correct one-bit errors automatically.

hash map A hash map is an array that associates hash bucket numbers with specific AMPs. While it has a limited number of hash buckets, there are enough hash buckets to minimize the number of hash collisions (when the hashing algorithm calculates the same row hash value for two different rows). The hash map is a GDO (globally distributed object), which is a file that is copied and distributed to every node in the system. If an AMP is executing a request that requires information in a GDO, it can access the copy of the GDO on its node.

hash table A lookup table that is designed to efficiently store non-contiguous keys (account numbers, part numbers, etc.) that may have wide gaps in their alphabetic and numeric sequences. Hash tables are created by using a hashing function (algorithm) to hash the keys into hash buckets. Each bucket is a list of key value pairs. Since different keys may hash to the same bucket, the goal of hash table design is to spread out the key-value pairs evenly with each bucket containing as few key-value pairs as possible. When an item is looked up, its key is hashed to find the appropriate bucket. Then, the bucket is searched for the right key-value pair. If access to the values is desired other than through the keys, an indexing system can be built on top of a hash table. Such user-level search engines can be made to handle imprecise queries and misspellings.

HBA Host Bus Adapter. Refers to the Fibre-channel or SCSI interface adapter through which BAR storage drives are connected to the BAR application host processor devices. SCSI interfaces provide for data transmission rates of up to 80 megabytes per second. In addition, one can attach many devices to a single SCSI port, so that SCSI is really an I/O bus rather than simply an interface. Although SCSI is an ANSI standard, there are many variations of it, so two SCSI interfaces may be incompatible.



help session To see information about your SQL session, use the HELP SESSION command with the formatting specifications:

HELP SESSIONSET FOLDLINE ONSET SIDETITLES ON;

Example Output:User Name DBC Account Name DBC Log on Date 96/09/18 Log on Time 11:54:46 Current DataBase DBC Collation ASCII Character Set ASCII Transaction Semantics Teradata

host channel adapter and channel connection

The channel adapter boards and connection enable communication between a node and a channel-attached (mainframe) client. A channel adapter board is located in a system bus slot. The physical channel connection can be one of two types: ESCON (Enterprise Systems Connection) fiber optic cable - connects the node directly to the mainframe. ESCON cables support: PBSA (PCI Bus-to-ESCON Adapter) connectionsTwisted-pair shielded cable - connects the channel adapter board in the node to a Tailgate box (an adapter) located outside of the node cabinet. This Tailgate box is then connected to the mainframe through "bus and tag" cables. Bus and tag cables support: PBCA (PCI Bus-to-Channel Adapter) connectionsEBCA (EISA Bus-to-Channel Adapter) connections

Iimport The process of making the contents of a physical tape available to

a virtual tape library.import request

Request made through the CDL Console.

import/export slot

See CAP.

incident A customer problem ticketinitiator port A CDL Fibre-channel port that is connected to the internal

CLARiiON storage system or to a customer-supplied fibre tape library.

ISL Inter Switch Link



Jjournals The Teradata Database has Permanent Journals and Recovery

Journals that are used for specific types of data or process recovery.

LLAN A Local Area Network is a network that links computer systems

within a limited geographical area.locks Locks can be placed on database objects to prevent multiple

users from simultaneously changing them. The four types of locks are: o Exclusive o Write o Read o Access

LPAR (Logical PARtition) A logical segmentation of a mainframe's memory and other resources that allows it to run its own copy of the operating system and associated applications.

LUN A logical unit is composed of a region of space from each of the physical disk drives in a rank. The operating system sees the LUN as its "disk," and is not aware that it is actually writing to spaces on multiple disk drives.This technique helps to use RAID technology in a system to provide data availability, without affecting the operating system.The disk array controller in the disk drive cabinet handles the communication between the operating system and the ranks of disk drives.

Mmedia server In a VERITAS NetBackup configuration, a system that is connected

to and directly writes (and reads) backup media such as tape drives. The connection may be local SCSI or ATAPI, or through a SAN.

memory The free memory pool is a collection of memory available to the node. The vprocs on the node use the free memory pool. As needed, segments of memory are allocated to a vproc for its use. When the vproc no longer needs the memory segments, the segments are returned to the memory pool for use by other vprocs. During the time that a segment of memory is assigned to a vproc, it is not accessible to any other vproc. This use of memory segments supports the Teradata Database's shared-nothing architecture.

metadata Control, status, error, and file index information exchanged between the backup server and backup client.



MIPS Millions of instructions per secondMPP Massively parallel processing - Multiple SMP nodes working

together comprise a larger, MPP implementation of a Teradata Database. The nodes are connected using the BYNET, which allows multiple virtual processors on multiple nodes to communicate with each other. The Teradata Database is a linearly expandable database system because as additional nodes and vprocs are added, the system capacity scales in a linear fashion.See also: SMP

MP-RAS UNIX MP-RAS is one of the operating system platforms that the Teradata Database runs on. It includes enhancements that Teradata made to the UNIX MP kernel to make it more Reliable, Available, and Serviceable (RAS).

NNBU NetBackup backup, archive, and restore software from Bakbone.NIC Network interface card – relates to the LANNPARC Named Pipe ARC

“Named Pipes” is a very fast mechanism for transferring data between systems because the data never ends up on a physical device such as tape or disk. In this case, ARC is the utility that reads the data out of Teradata on the old system, when doing a backup, and sends it to the Named Pipe. On the new system, a simultaneous ARC job, running a restore, reads the data from the Named Pipe and restores it. It's a continuous send and read operation: if the Pipe gets full, the send side has to wait for the read side to empty the Pipe before it can send more data to the Pipe. If the pipe becomes empty, the read side has to wait for more data before it can continue.

NPARC service offering

Most references to NPARC (particularly when involving use at a customer site) are to the full NPARC Service Offering from Operational Services. Operational Services owns additional scripts and resources for automatically writing the ARC scripts, performing load balancing, etc.

NUPI Non-unique Primary Index NUSI A Non-unique Secondary Index is usually specified to prevent

full-table scans, in which every row of a table is read. The Optimizer determines whether a full-table scan or NUSI access will be more efficient, then picks the best method. Accessing a row with a NUSI requires all AMPs.

NV NetVault backup, archive, and restore software from Symantec



OODBC Open Database Connectivity is an application programming

standard that defines common database access mechanisms to simplify the exchange of data between a client and server. ODBC-compliant applications connect with a database through the use of a driver that translates the application's ODBC commands into database syntax.

ODS Operational data store OLAP On-line Analytical Processing

OLAP is a modern form of analytic processing within a DSS environment. OLAP tools (e.g. from companies like Microstrategy and Cognos) provide an easy to use Graphical User Interface to allow “slice and dice” analysis along multiple dimensions (e.g. products, locations, sales teams, inventories, etc.). With OLAP, the user may be looking for historical trends, sales rankings or seasonal inventory fluctuations for the entire corporation. Usually, this involves a lot of detail data to be retrieved, processed and analyzed. Therefore, response time can be in seconds or minutes.

OLE A compound document technology from Microsoft based on its Component Object Model (COM). OLE allows an object such as a graphic, video clip, spreadsheet, etc. to be embedded into a document, called the "container application. An object can be linked instead of embedded, in which case the container application does not physically hold the object, but provides a pointer to it. If a change is made to a linked object, all the documents that contain that same link are automatically updated the next time you open them. An application can be both client and server.OLE was originally known as "Object Linking and Embedding." However, with version 2.0, OLE's infrastructure was built on a new component architecture known as COM (Component Object Model) that went beyond compound documents. New capabilities such as OLE automation and Network OLE were widely promoted. Later, Microsoft dropped the use of the term as a marketing brand, although it is still used in technical documentation.

OLE DB OLE DataBase) - A programming interface for data access from Microsoft. It is a COM object that functions in a similar manner to ODBC, but for every type of data source, not just SQL databases. Applications can use OLE DB to access data sources directly or they can use OLE DB to call ODBC to access ODBC databases. OLE DB for OLAP is used to access OLAP databases. Microsoft's ActiveX Data Objects (ADO) is a set of COM objects that provides a simpler interface to OLE DB.



operating system

The Teradata Database is an open system, compliant with ANSI standards. The Teradata Database is built on the UNIX or Microsoft Windows operating systems for an open environment:Teradata added MP-RAS extensions to UNIX to facilitate a multiple CPU environment.Microsoft Windows supports a multiple CPU environment.

OS See Operating SystemOTB Open Teradata Backup is a set of Teradata backup products for

MP-RAS/UNIX, NT, and Windows 2000 platforms. It consists of Backbone NetVault (NV), Symantec NetBackup (NBU), and IBM Tivoli Storage Manager (TSM). The concept exists to give Teradata customers the broadest possible choice of backup, archive, and restore software products.

Pparent A parent user or parent database (also known as an owner) owns

all databases and users below it in the hierarchy. Every user or database above a child in the hierarchy is a parent to that child.

parity checking

An error detection technique that tests the integrity of digital data in memory or on disk. Parity checking adds an extra parity cell to each byte of memory and an extra parity bit to each byte transmitted. The value of the ninth bit (0 or 1) depends on the pattern of the byte's eight bits. Each time a byte is transferred or transmitted, the parity bit is tested by memory controller circuits on the motherboard. "Even" parity systems make the parity bit 1 when an even number of 1 bits are in the byte. "Odd" parity makes it 1 when an odd number of 1 bits are present. Parity checking cannot detect the condition in which two data bits are in error, because they would cancel themselves. The parity bit would still be correct for that sequence of 0s and 1s. ECC is a much more robust memory checking system (see ECC memory). There are 12% more memory cells in 9-bit parity chips than there are in 8-bit non-parity memory. To shave costs, many computers are built with non-parity memory. It is truly a miracle that the data in the hundreds of millions of non-parity computers in the world are maintained as perfectly as they are considering the trillions upon trillions of bits moved daily. See RAID and ECC memory.

partitioned primary index

Partitioned Primary Index (PPI) is an indexing mechanism in the Teradata Database. PPI is used to improve performance for large tables when you submit queries that specify a range constraint. PPI allows you to reduce the number of rows to be processed by using partition elimination. PPI will increase performance for incremental data loads, deletes, and data access when working with large tables with range constraints.


http://www.answers.com/topic/ecc-memory


http://www.answers.com/topic/raid-technology



PPI See Partitioned Primary IndexPBCA PCI Bus-to-Channel Adapter connectionsPE A Parsing Engine is a vproc that receives SQL requests from the

client and breaks the requests into steps. The PE sends the steps to the AMPs and subsequently returns the answer to the client.The PE manages the dialogue between a client application and the Teradata Database, once a valid session has been established. Each PE can support a maximum of 120 sessions. The PE handles an incoming request in the following manner: The Session Control component verifies the request for session authorization (user names and passwords), and either allows or disallows the request. The PE does the following: Interprets the SQL statement received from the application. Verifies SQL requests for the proper syntax and evaluates them semantically. Consults the Data Dictionary to ensure that all objects exist and that the user has authority to access them. The Optimizer is cost-based and develops the least expensive plan (in terms of time) to return the requested response set. Processing alternatives are evaluated and the fastest alternative is chosen. This alternative is converted into executable steps, to be performed by the AMPs, which are then passed to the Dispatcher. The Optimizer is "parallel aware," meaning that it has knowledge of the system components (how many nodes, vprocs, etc.), which enables it to determine the fastest way to process the query. In order to maximize throughput and minimize resource contention, the Optimzer must know about system configuration, available units of parallelism (AMPs and PEs), and data demographics. The Teradata Database Optimizer is robust and intelligent, and enables the Teradata Database to handle multiple complex, ad-hoc queries efficiently.The Dispatcher controls the sequence in which the steps are executed and passes the steps received from the optimizer onto the BYNET for execution by the AMPs. After the AMPs process the steps, the PE receives their responses over the BYNET.The Dispatcher builds a response message and sends the message back to the user. PE Calculation for 1700 Sessions: 1700 sessions / 120 sessions per PE = 14.2PE Calculation for 500 Sessions: 500 sessions / 120 sessions per PE = 4.2(shorter version)



The Parser is a component of the PE and performs the following tasks: Interprets an incoming Teradata SQL request and checks the syntax, evaluating the request semantically. Consults the Data Dictionary to ensure that all the objects exist and that the user has authority to access them. Decomposes the request into manageable pieces of work called AMP steps. Sends the optimized steps to the Dispatcher.

PE optimizer The Optimizer is a component of the PE that develops the "least expensive" plan (in terms of time and system resources) to return the requested response set. Processing alternatives are evaluated, and the fastest alternative is chosen. The selected alternative is converted to executable steps that will performed by the AMPs.

PE session control

When you log on to the Teradata Database through your application, the session control software on the PE establishes that session. Session control also manages and terminates sessions on that PE

physical tape In the context of the CDL, a real tape in a physical tape drive or physical tape library. It is the destination of an export or the source of an import.

physical tape drive

In the context of the CDL, a real tape drive directly connected to the CDL’s SCSI or fibre initiator port.

physical tape library

In the context of the CDL, a real tape library directly connected to the CDL’s SCSI or fibre initiator port.

PIOM Teradata Data connector (Parallel I/O Module)

RRAID Redundant Array of Inexpensive Disks (RAID) is a storage

technology that provides data protection at the disk drive level. It uses groups of disk drives called "arrays" to ensure that data is available in the event of a failed disk drive or other component. The word, "redundant," implies that data, functions, and/or components have been duplicated in the array's architecture. The industry has agreed on six RAID configuration levels (RAID 0 through RAID 5). The classifications do not imply superiority of one mode over the other, but differentiate how data is stored on the disk drives. With the Teradata Database, the two RAID technologies that are supported are RAID 1 and RAID 5. On systems using EMC disk drives, RAID 5 is called RAID S.



Disk arrays contain the following major components:SCSI bus Physical disks Disk array controllers For maximum availability and performance, the Teradata Database uses dual redundant disk array controllers. Having two disk array controllers provides a level of protection in case one controller fails, and provides parallelism for disk access.RAID (redundant array of independent disks; originally redundant array of inexpensive disks) is a way of storing the same data in different places (thus, redundantly) on multiple hard disks. By placing data on multiple disks, I/O (input/output) operations can overlap in a balanced way, improving performance. Since multiple disks increase the mean time between failures (MTBF), storing data redundantly also increases fault tolerance. A RAID appears to the operating system to be a single logical hard disk. RAID employs the technique of disk striping, which involves partitioning each drive's storage space into units ranging from a sector (512 bytes) up to several megabytes. The stripes of all the disks are interleaved and addressed in order. In a single-user system where large records, such as medical or other scientific images, are stored, the stripes are typically set up to be small (perhaps 512 bytes) so that a single record spans all disks and can be accessed quickly by reading all disks at the same time. In a multi-user system, better performance requires establishing a stripe wide enough to hold the typical or maximum size record. This allows overlapped disk I/O across drives. Disk-to-disk backup systems provide a very fast restore capability compared with tape backup. But, using standard disk alone creates other challenges, especially when longer term retention is required.Failover is a backup operational mode in which the functions of a system component (such as a processor, server, network, or











database, for example) are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. Used to make systems more fault-tolerant, failover is typically an integral part of mission-critical systems that must be constantly available. The procedure involves automatically offloading tasks to a standby system component so that the procedure is as seamless as possible to the end user. Failover can apply to any aspect of a system: within a personal computer, for example, failover might be a mechanism to protect against a failed processor; within a network, failover can apply to any network component or system of components, such as a connection path, storage device, or Web server. Originally, stored data was connected to servers in very basic configurations: either point-to-point or cross-coupled. In such an environment, the failure (or even maintenance) of a single server frequently made data access impossible for a large number of users until the server was back online. More recent developments, such as the storage area network (SAN), make any-to-any connectivity possible among servers and data storage systems. In general, storage networks use many paths - each consisting of complete sets of all the components involved - between the server and the system. A failed path can result from the failure of any individual component of a path. Multiple connection paths, each with redundant components, are used to help ensure that the connection is still viable even if one (or more) paths fail. The capacity for automatic failover means that normal functions can be maintained despite the inevitable interruptions caused by problems with equipment.

RAID levels The industry has agreed on the following RAID configuration levels:RAID 0 - Data stripingRAID 1 - Disk mirroringRAID 2 - Parallel array, hamming codeRAID 3 - Parallel array with parityRAID 4 - Data parity protection, dedicated parity driveRAID 5 - Data parity protection, interleaved parity

RCA Remote Customer Advocate - A technical account manager assigned to larger sites to track and manage a site’s issues

RDAC A Redundant Disk Array Controller consists of hardware and software that protects your system from a SCSI bus failure or array controller failure. RDAC Release 4.0 uses both disk array controllers simultaneously in a normal operating environment for better performance.







RDBMS A Relational Database Management System is a system that supports a relational data structure, including commands to manipulate the data tables.

recovery journals

The Teradata Database uses Recovery Journals to automatically maintain data integrity in the case of: An interrupted transaction (Transient Journal) An AMP failure (Down-AMP Recovery Journal) Recovery Journals are created, maintained, and purged by the system automatically, so no DBA intervention is required. Recovery Journals are tables stored on disk arrays like user data is, so they take up additional disk space on the system. Transient Journal A Transient Journal maintains data integrity when in-flight transactions are interrupted (due to aborted transactions, system restarts, and so on). Data is returned to its original state after transaction failure. A Transient Journal is used during normal system operation to keep "before images" of changed rows so the data can be restored to its previous state if the transaction is not completed. This happens on each AMP as changes occur. When a transaction is started, the system automatically stores a copy of all the rows affected by the transaction in the Transient Journal until the transaction is committed (completed). Once the transaction is complete, the "before images" are purged. In the event of a transaction failure, the "before images" are reapplied to the affected tables and deleted from the journal, and the "rollback" operation is completed. Down-AMP Recovery Journal The Down-AMP Recovery Journal allows continued system operation while an AMP is down (for example, when two disk drives fail in a rank or mirrored pair). A Down-AMP Recovery Journal is used with Fallback-protected tables to maintain a record of write transactions (updates, creates, inserts, deletes, etc.) on the failed AMP while it is unavailable. The Down-AMP Recovery Journal starts automatically after the loss of an AMP in a cluster, Any changes to the data on the failed AMP are logged into the Down-AMP Recovery Journal by the other AMPs in the cluster. When the failed AMP is brought back online, the restart process includes applying the changes in the Down-AMP Recovery Journal to the recovered AMP. The journal is discarded once the process is complete, and the AMP is brought online, fully recovered.

Resource contention

When more than one device requests access to a resource at the same time.

Restore The process of replacing backed up data on a client machine.Robot VERITAS NetBackup refers to libraries as robots. See tape library.



RTS A Regional Technical Specialist typically has deeper technical knowledge than a typical SSR.

Sswitched fabric (or fabric)

Switched Fabric is a Fibre-channel topology where many devices connect with each other via Fibre-channel switches.

SAN A Storage Area Network, as used for tape backup and restore, is synonymous with shared tape devices. This means that the SAN attached tape devices are available to more than one host system, and their utilization is managed by the backup and restore application. The following terms are useful in describing the SAN.

SAN client A system on the SAN that will use the virtual tape drives or virtual tape libraries the CDL makes available. A SAN client is a backup server. (See storage node and media server.)

saveset A single backup. There may be several savesets on a given tape, or a saveset may span multiple tapes.

SCAM SCSI configured automatically - A subset of Plug and Play that allows SCSI IDs to be changed by software rather than by flipping switches or changing jumpers. Both the SCSI host adapter and peripheral must support SCAM.

SCSI A small computer system interface (pronounced skŭz'ē) is used for connecting peripheral devices, such as external disk drives and scanners, as used on personal computers.

serialization The process some backup software packages use to automatically configure tape libraries. Serial numbers are read from tape drives individually and through the library device in order to determine which device file refers to the each tape drive in the library.

server parallelism

The total number of concurrent backup sessions that the NetWorker storage node can write to simultaneously.



SET Teradata System Emulation Tool (Teradata SET) simplifies the task of emulating a target system by providing the ability to export and import all information necessary to fake out the optimizer in a test environment. This information can be used along with the Target Level Emulation feature to generate query plans on the test system as if they were run on the target system. This feature is useful for verifying queries and reproducing optimizer related issues in a test environment. Teradata SET allows the user to capture the following by database, query, or workload:

System cost parameters Object definitions Random AMP samples Statistics Query execution plans Demographics

This tool does not export user datashared tape drive

A tape drive within a library that is dynamically and temporarily associated with a backup client. (See dedicated tape drive.)

skewed data Unevenly distributed data, also called "skewed data," causes slower response time as the system waits for the AMP(s) with the most data to finish their processing. The slowest AMP becomes a bottleneck. If distribution is skewed, an all-AMP operation will take longer than if all AMPs were evenly utilized.

slot Location within a tape library to hold a tape cartridge when not in a drive.

SMP A Symmetric multiprocessing Teradata Database has a single node that contains multiple CPUs sharing a memory pool. An SMP platform consists of a single Teradata Database node. An SMP system has multiple CPUs that work together. All applications run under a single operating system on the node.The AMPs and PEs on an SMP system communicate through the BYNET software that handles the message queuing and flow control.

SNMP Simple Network Management Protocol. A standard method of monitoring and controlling devices that adhere to the protocol. See the separate white paper Utilizing SNMP Capabilities of CLARiiON Disk Library Version 2.0.

SPL Procedural statements in the Teradata Database are referred to as Stored Procedure Language.

SSR Site Support Representatives provide local support; mostly hardware and software maintenance. These Teradata generalists are assigned to one or more sites in a region.



stacker Usually a small library with 20 or fewer tapes, one drive, and no mailslot. (See tape library or autochanger.)

switch In networks, a device that filters and forwards packets between LAN segments. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs.

system bus A system bus connects peripherals to the CPUs. The Teradata Database supports two kinds of system buses:PCI (Peripheral Component Interconnect) MCA (Micro Channel Architecture) Slots on the system bus are used for the following types of connections: LAN connections Mainframe channel connections Connections to the external disk array cabinets Depending on the platform (such as Teradata 4800, Teradata 5100, etc.), the system bus can also be used to connect the CPUs to: Local peripheral board (LPB) Internal RAID disk arrays

system disks System disks are contained on the node used for the following:Operating system softwareTeradata Database software Application software System dump space Teradata Database tables are stored on disk arrays, not on the system disks.

TTACC Teradata Americas Care Center takes customer and SSR calls to

create incidents, gather information, and search knowledge for known problems/solutions.

tape cartridge (or tape)

Tape cartridges are the removable media used as the destination of tape backup.

tape drive A tape drive is a device that can write and read tape cartridges: it writes the data to tape, one tape at a time.

tape library A tape library is a device that houses one or more tape drives, a number of slots to hold tape cartridges, and a robotic picker mechanism that moves tapes between slots and drives under programmatic control of backup software.

TARA Teradata Tiered Archive/Restore Architecture



target port A target port is a CDL Fibre-channel port that is connected to the SAN and presents the virtual tape drives and libraries to SAN clients.

TCO Total Cost of OwnershipTCP/IP Transmission Control Protocol/Internet Protocol

Standard Internet communications protocols that allow digital computers to communicate over long distances. The Internet is a packet-switched network, in which information is broken down into small packets, sent individually over many different routes at the same time, and then reassembled at the receiving end. TCP is the component that collects and reassembles the packets of data, while IP is responsible for making sure the packets are sent to the right destination. TCP/IP was developed in the 1970s and adopted as the protocol standard for ARPANET (the predecessor to the Internet) in 1983.

TDBMS Teradata Database Management SystemTDE The Teradata Extension includes the ARC utility.Teradata Database

The Teradata Database is a relational database management system (RDBMS) that runs as a Trusted Parallel Application (TPA) on the operating system.A TPA implements virtual processors (vprocs) and runs on the operating system with PDE. The software components of the Teradata Database include: o Channel Driver o Teradata Gateway o AMP o PE A Teradata Database system can have some nodes with the Database software, and some nodes without it.Nodes that contain the Teradata Database software are called "TPA nodes." Nodes that do not contain Teradata Database software generally have applications installed on them. They are called "non-TPA nodes," with the software label "NOTPA" (pronounced, "no TPA").



topography Topography (I/O) The primary/secondary bus can be fiber optic, Ethernet, Arcnet, RS232, or RS485, depending on the system.Most controllers are proprietary. Each company has their own controllers which meet specific applications. Some are designed with limited control, example: Package Roof Top Unit. Others are designed to be flexible. Most have a proprietary software that will work with Bacnet, Lontalk and Ashrae standards.Inputs and outputs are either analog of digital (some companies say binary).Analog inputs are used to read a variable measurement. Examples are temperature, humidity and pressure sensors which could be thermistors, 4-20MA, 0-10V or Platinum RTD (resistance temperature detector), or wireless sensors which usually have an IP address.A digital input indicates if a device is turned on or not. Some examples of a digital input would be a 24VDC relay or air flow switch.Analog outputs control the speed or position of a device, such as a variable frequency drive, a pneumatic I-P transducer, or an actuator. An example is a hot water valve opening up 25% to maintain a setpoint.Digital outputs are used to open and close relays and switches. An example would be to turn on the parking lot lights when a photocell indicates it is dark outside.This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)

TPA A Trusted Parallel Application uses PDE to implement virtual processors (vprocs). The Teradata Database is classified as a TPA. The four components of the Teradata Database TPA are:

o AMP (Top Right) o PE (Bottom Right) o Channel Driver (Top Left) o Teradata Gateway (Bottom Left)

TSM Tivoli Storage Manager is backup, archive, and restore software from IBM.


http://en.wikipedia.org/wiki/Wikipedia:General_disclaimer

http://www.answers.com/topic/photoresistor

http://www.answers.com/topic/electric-light

http://www.answers.com/topic/switch

http://www.answers.com/topic/relay

http://www.answers.com/topic/setpoint

http://www.answers.com/topic/actuator

http://www.answers.com/topic/frequency

http://www.answers.com/topic/device

http://www.answers.com/topic/ip-address

http://www.answers.com/topic/wireless

http://www.answers.com/topic/thermistor

http://www.answers.com/topic/humidity

http://www.answers.com/topic/temperature

http://www.answers.com/topic/measurement

http://www.answers.com/topic/variable-1

http://www.answers.com/topic/binary

http://www.answers.com/topic/digital-1

http://www.answers.com/topic/analog-signal


TTU Teradata Tools and Utilities

Vvaulting The process of sending data off-site, where it can be protected

from hardware failures, theft, and other threats. Vaults may feature auxiliary power supplies, powerful computers, and security personnel.

Vdisk A Virtual Disk (pronounced, "VEE-disk") is the logical disk space that is managed by an AMP. Depending on the configuration, a vdisk may not be contained on the node; however, it is managed by an AMP, which is always a part of the node.The vdisk is made up of 1 to 64 pdisks (user slices in UNIX or partitions in Windows NT, whose size and configuration vary based on RAID level). The pdisks logically combine to comprise the AMP's vdisk. Although an AMP can manage up to 64 pdisks, it controls only one vdisk. An AMP manages only its own vdisk, not the vdisk of any other AMP.

virtual tape cartridge (or virtual tape)

Logical representation of a tape. Virtual tapes logically reside in virtual libraries. Data stored on virtual tapes is located on the CLARiiON storage system within the CDL appliance.

virtual tape drive

Logical equivalent of a physical tape drive. May logically reside in a virtual tape library. Operating systems and backup software cannot tell the difference between a virtual tape drive and a real tape drive.

virtual tape drive type

The type of real tape drive that the virtual tape drive looks like (for example, a DLT7000 or LTO).

virtual tape library

Logical equivalent of a tape library. Operating systems and backup software cannot tell the difference between a virtual tape library and a real tape library.

virtual tape library type

The type of real tape library that the virtual tape library emulates (for example, an ATL P1000 or STK L700).

VNET Virtual BYNET is a software emulation of the BYNET, used on an SMP system.

Vproc A virtual processor, often pronounced "VEE-prawk," is a group of one or more software processes running under the operating system's multi-tasking environment:On the UNIX operating system, a vproc is a collection of software processes.On the Windows operating systems, a vproc is a single software process.The two types of Teradata Database vprocs are:AMP (Access Module Processor) PE (Parsing Engine)



WWAN Wide area networkwrite-cache consolidation

A technique employed by CDL 2.0 hardware servers and software to achieve higher aggregate backup throughput. See the separate CSPEED white paper.

WWN World Wide Name is the 64-bit address assigned to a host bus adapter (HBA) in a Fibre-channel network. Assigned by the vendor at the time of manufacture, it is similar to the MAC address in an Ethernet network. Also known as a World Wide Identifier (WWID), it is a unique identifier in a Fibre-channel storage network. Each WWN is an 8-byte number derived from an IEEE OUI (for the first 3 bytes) and vendor-supplied information (for the rest).There are two formats of WWN defined by the IEEE:Original format: addresses are assigned to manufacturers by the IEEE standards committee, and are built into the device at build time, similar to Ethernet MAC address. First 2 bytes are either hex 10:00 or 2x:xx (where the x's are vendor-specified) followed by the 3-byte vendor identifier and 3 bytes for a vendor-specified serial number New addressing schema: first half-byte is either hex 5 or 6 followed by a 3-byte vendor identifier and 4 bytes and a half for a vendor-specified serial number Port AddressDomain ID: 1 Byte, represents the unique identifier of the switch itself. One byte allows 256 possible addresses, but because some of these are reserved only 239 addresses are actually available. Area Port List of a few WWN company identifiers00:60:69 Brocade Communications Systems 00:05:1E Brocade Communications Systems, formerly owned by Rhapsody Networks 00:60:DF CNT Technologies Corporation 00:50:76 IBM 08:00:88 McDATA Corporation



INDEX

66533...........................................................38, 47, 48, 49, 646534.................................................................47, 48, 49, 646535...........................................................35, 37, 45, 46, 47

99200.............................48, 50, 51, 52, 53, 54, 55, 58, 62, 669201.................................................................55, 62, 63, 659202.........48, 50, 53, 55, 56, 58, 59, 60, 61, 62, 63, 66, 1019203..............................................ix, xii, xv, 35, 38, 40, 1299204.....................22, 26, 27, 39, 73, 74, 75, 76, 77, 78, 1079205.......22, 26, 27, 38, 39, 48, 79, 81, 82, 83, 96, 107, 165

Aaccess modules.................................................................111accurate records.................................................................29ACSLS.39, 56, 58, 62, 63, 65, 92, 94, 98, 99, 101, 131, 157adaptability........................................................................25adapters.....xvii, 37, 38, 42, 44, 74, 90, 101, 108, 151, 161advantages..................................................................20, 133Advantages, direct-attached...............................................21advantages, LAN-based.....................................................23advantages, NetBackup....................................................101advantages, NetVault.........................................................89advantages, Teradata integration.......................................30advantages, Tivoli............................................................108advantages, two-tiered strategy.........................................28advocated solution...............................................20, 22, 102ARC 20, 36, 85, 86, 87, 88, 94, 98, 101, 106, 108, 109, 119,

120, 121, 122, 124, 127, 131, 132, 133, 134, 139, 144, 148, 149, 152, 153, 158, 172, 183

architecture19, 20, 21, 22, 23, 24, 25, 26, 28, 30, 35, 37, 39, 46, 48, 51, 55, 66, 90, 98, 105, 109, 115, 150, 151, 158, 171, 173, 176, See configuration

archive19, 20, 25, 51, 55, 64, 73, 85, 86, 87, 88, 92, 94, 98, 101, 105, 109, 119, 120, 121, 122, 132, 144, 145, 147, 149, 155, 157, 159, 166, 172, 174, 186

Bbackup strategy......................................26, 27, 73, 120, 143backup to disk. xvii, 22, 23, 24, 26, 27, 28, 39, 42, 50, 65,

73, 74, 79, 89, backup windows................................................................29BakBone (see NetVault)..xvii, 25, 89, 90, 92, 102, 108, 136

BAR applications.......................................................30, 115BAR Pre-Sales.....................................................ii, 150, 151BAR SANs.........................................................................25BAR server............................................................................19, 21, 22, 24, 26, 35, 36, 37, 38, 39, 40, 41, 42, 44, 46, 48,

51, 55, 56, 63, 66, 74, 77, 82, 90, 92, 94, 98, 101, 105, 106, 108, 109, 111, 113, 115, 117, 131, 136, 137, 150, 151, 153, 154, 160

Brocade......................................................xvii, 48, 49, 187BYNET......................................................................22, 186

Ccartridges.........................xvii, 49, 55, 60, 61, 68, 162, 183CDL 48, 79, 80, 81, 163, 164, 166, 170, 176, 180, 183, 186,

187certified......22, 23, 26, 29, 30, 48, 88, 92, 94, 115, 116, 148checkpointing...........................................133, 134, 137, 138Clariion..............................................................xvii, 48, 107CLI tunables.....................................................................127compatibility..............................................................71, 148complementary..................................................................26configuration xii, 27, 28, 30, 46, 48, 51, 54, 55, 59, 62, 63,

65, 74, 76, 87, 88, 95, 102, 103, 105, 110, 113, 119, 120, 121, 131, 144, 146, 150, 152, 153, 157, 163, 164, 171, 175, 176, 179, 181, 186

controllers......................26, 74, 75, 163, 167, 176, 179, 185COP entries......................................................................128cost20, 21, 24, 26, 27, 29, 73, 81, 109, 133, 146, 175, 181, cost-effective........................................................20, 26, 73customer investment..........................................................19customer service........................................................29, 160

Ddedicated server...........................................................23, 81Dell....................................................xvii, 39, 40, 41, 42, 46description........................................................................124Description

StorageTek Fibre Channel Drives.................................69Ultrium (LTO) Fibre Channel Drives...........................67

devices, storage. .20, 22, 30, 33, 48, 88, 92, 94, 102, 117, 165, 167

direct-attached....ix, 19, 20, 21, 22, 24, 25, 33, 35, 51, 52, 55, 58, 63, 85, 90, 92, 93, 102, 115, 117, 150, 158

Direct-Attached..................................................................19direct-attached BAR architecture..............................21, 115disadvantages without Teradata integration......................31Disadvantages, direct-attached..........................................22



disadvantages, LAN-based................................................24disadvantages, NetBackup...............................................101disadvantages, NetVault....................................................89disadvantages, Tivoli.......................................................108disadvantages, two-tiered strategy.....................................29disk arrays..................26, 42, 65, 74, 79, 163, 167, 179, 182Disk Library, Clariion......................................xvii, 48, 107disk-based..................................................26, 70, 74, 79, 94disks.................26, 65, 73, 79, 122, 123, 157, 160, 176, 182disks and tapes.............................................................26, 73documents, related..............................................................ixdowntime............................................................22, 24, 155drives, SATA....................................................................27drives, tape xvii, 20, 22, 42, 49, 50, 52, 53, 54, 55, 58, 59,

60, 61, 63, 64, 65, 66, 68, 69, 71, 72, 79, 90, 101, 106, 108, 111, 141, 149, 154, 164, 171, 181, 183

EEMC......................................xvii, 76, 79, 82, 163, 165, 176encryption..................................24, 127, 139, 140, 141, 165end-to-end solution............................................................23engineering........................................................................30enterprise. xvii, 19, 23, 24, 40, 50, 69, 70, 87, 89, 91, 102,

104, 105, 106, 108, 158Ethernet....19, 24, 35, 38, 40, 44, 45, 46, 53, 113, 115, 116,

125, 131, 159, 160, 165, 167, 168, 182, 185, 187

Ffailure, media...................................................................27Fibre Channel.........................................................................xvii, 40, 42, 43, 47, 49, 52, 56, 58, 66, 69, 70, 71, 72, 75,

81, 82, 113, 166, 167, 168, 170, 180, 183, 187flexibility..........................................................22, 24, 25, 89function................................xv, 79, 121, 143, 148, 149, 169Future Growth....................................................................25

Ggeneral guidelines, NetBackup........................................149gigabit switch...........................................44, 46, 51, 56, 111global hot spares................................................................27Global Sales Support (GSS)................................................iiGlobal Support Center (GSC)..................ii, xv, 29, 30, 168igrowth......................................................viii, 24, 25, 30, 50

Hhardware failures...........................................................186HBA...............................39, 40, 42, 43, 44, 74, 89, 169, 187Hewlett Packard (HP)................................................xvii, 68high performance.............................26, 40, 50, 58, 127, 161

IIBM......xvii, 25, 68, 87, 110, 111, 138, 160, 165, 167, 168,

174, 186, 187IBM Tivoli Storage Manager...........................................107impact of BAR events........................................................24

improved performance.......................................................20incident...............................................................30, 31, 170integrated.....26, 29, 30, 31, 32, 37, 43, 74, 87, 90, 92, 97,

101, 108, 111integrated software.............................................................26IntelPro...........................................................................xviiinteroperability...................................................................30

LLAN switch.....................................37, 38, 44, 90, 101, 108LAN-based...viii, ix, 19, 20, 21, 22, 23, 24, 25, 26, 28, 29,

33, 35, 39, 46, 48, 51, 52, 55, 56, 66, 90, 92, 93, 95, 98, 102, 103, 104, 106, 115, 117, 150, 151, 158

legacy......................................ix, 20, 21, 24, 35, 52, 58, 151libraries, tape...xvii, 19, 26, 39, 42, 48, 50, 64, 66, 79, 95,

111, 163, 180, 181Linux 20, 22, 26, 32, 40, 63, 75, 85, 87, 88, 90, 92, 94, 101,

102, 103, 105, 108, 117, 118, 124, 130, 135, 137, 150, 151, 152

Mmainframe............................................20, 88, 165, 170, 171maintenance. xi, 22, 29, 60, 109, 110, 111, 151, 160, 176,

182McData...............................................................xvii, 48, 49mechanical failure..............................................................27media failure....................................................................27modular tape library.....................................................26, 50MP-RAS. .20, 21, 22, 25, 32, 58, 63, 86, 89, 90, 92, 94, 95,

101, 102, 108, 117, 130, 150, 151, 172, 174Multi-ARC.........................................................87, 119, 120

NNBU...........................................................25, 133, 172, 174NetBackup xvii, 25, 27, 32, 56, 58, 62, 74, 87, 88, 101, 102,

103, 104, 105, 106, 107, 133, 134, 136, 137, 138, 149, 150, 151, 152, 153, 154, 157, 160, 171, 172, 174, 180

NetVaultxvii, 19, 20, 21, 25, 32, 35, 56, 58, 62, 74, 87, 88, 89, 90, 91, 92, 93, 94, 95, 97, 98, 99, 102, 108, 130, 133, 134, 135, 136, 149, 154, 157, 160, 172, 174

network. xvii, 20, 21, 24, 38, 42, 44, 85, 90, 101, 102, 108, 122, 126, 127, 131, 136, 152, 153, 158, 159, 161, 164, 165, 167, 170, 176, 183, 187

network adapters..............................................................131networking................................................................48, 161networks.......................43, 57, 138, 160, 161, 167, 176, 182nodes. .19, 20, 22, 25, 26, 36, 37, 38, 46, 55, 61, 65, 93, 94,

95, 115, 117, 123, 127, 128, 131, 139, 161, 163, 167, 172, 175, 184

non-compliance..................................................................31NPARC....................................................................153, 172NV......................................................................25, 172, 174

Ooff-site.............................................................................186offsite media storage..........................................................26



Operational Services. .ii, viii, 102, 108, 109, 111, 150, 151, 160, 172

Options Overview..............................................................33options, backup................................................................143OTB. .viii, ix, xi, xii, xv, xvi, 19, 22, 24, 25, 36, 38, 85, 86,

88, 90, 129, 130, 131, 132, 143, 149, 174OTB release matrix..........................................................148overview, ARC terminology..............................................86overview, backup archive and restore...............................19overview, BAR hardware concepts...................................33overview, checkpointing..................................................132overview, NetBackup......................................................101overview, NetVault............................................................89overview, software concepts..............................................32overview, Tivoli...............................................................108

Pparallel 22, 29, 30, 37, 85, 87, 98, 116, 118, 119, 120,

128, 144, 146, 147, 158, 159, 172, 175partner sites...............................................................xiperformanceix, 20, 30, 36, 37, 46, 60, 61, 65, 66, 69,

81, 86, 87, 89, 90, 109, 110, 115, 116, 117, 120, 121, 122, 124, 131, 132, 134, 136, 137, 138, 141, 143, 145, 154, 155, 163, 175, 176, 179

performance variables..............................................87performance, high...................26, 40, 50, 58, 127, 161planned downtime....................................................24Platform, Teradata..................................................115popular................................................................26, 54protect.................................................19, 26, 155, 176

QQlogic......................................................................xvii

RRAID..27, 40, 75, 76, 77, 79, 163, 171, 174, 176, 179, 182,

186Rationale for LAN-based architecture...............................24records, accurate............................................................29redundancy........................................19, 27, 44, 61, 76, 77related documents...............................................................ixreleases, compatibility between.......................................148reliability............................................19, 26, 27, 29, 70, 115resource contention......................................................175risk...................................................................19, 29, 30, 76

SSAN switch...................................xvii, 38, 41, 48, 108, 111SANs, BAR.......................................................................25SATA drives......................................................................27scalability.............................................................24, 30, 161SCSI......20, 42, 43, 67, 112, 113, 123, 135, 152, 159, 167,

169, 171, 176, 179, 180, 181see also, architecture...xii, 27, 28, 30, 46, 48, 51, 54, 55,

59, 62, 63, 65, 74, 76, 87, 88, 95, 102, 103, 105, 110,

113, 119, 120, 121, 131, 144, 146, 150, 152, 153, 157, 164, 171, 175, 176, 179, 186

see also, configuration. 19, 20, 21, 22, 23, 24, 25, 26, 28, 30, 35, 37, 39, 46, 48, 51, 55, 66, 90, 98, 105, 109, 115, 150, 151, 158, 171, 173, 176

server, BAR..19, 21, 22, 24, 26, 35, 36, 37, 38, 39, 40, 41, 42, 44, 46, 48, 51, 55, 56, 63, 66, 74, 77, 82, 90, 92, 94, 98, 101, 105, 106, 108, 109, 111, 113, 115, 117, 131, 136, 137, 150, 151, 153, 154, 160

server, dedicated.......................................................23, 81serversviii, 19, 22, 35, 36, 38, 41, 46, 81, 82, 95, 102, 104,

105, 106, 131, 154, 157, 159, 167, 176, 187service....................................................29, 61, 81, 141, 172Silkworm...................................................................xvii, 49single source......................................................................29software encryption.........................................................139solution, advocated...........................................20, 22, 102statement of work..............................................................31storage..xvii, 19, 20, 22, 26, 30, 32, 33, 36, 38, 39, 43, 48,

49, 50, 55, 71, 73, 74, 75, 76, 77, 81, 88, 90, 92, 93, 94, 95, 96, 98, 99, 102, 105, 106, 107, 108, 111, 115, 116, 117, 149, 163, 165, 167, 169, 170, 176, 180, 181, 186, 187

storage devices. . .20, 22, 30, 33, 48, 88, 92, 94, 102, 117, 165, 167

StorageTekxvii, 48, 53, 55, 62, 68, 69, 71, 74, 75, 90, 101, 108

strategies, backup.............................................................143strategy...............................................20, 26, 28, 29, 79, 138strategy, backup.............................................26, 27, 73, 120strategy, two-tiered......................................................26, 73Sun................................................................xvii, 48, 63, 68support. ii, viii, xiv, xvii, 19, 20, 23, 24, 25, 29, 30, 31, 38,

40, 43, 44, 48, 50, 53, 67, 76, 77, 81, 82, 85, 87, 90, 91, 92, 94, 101, 102, 106, 108, 109, 110, 111, 112, 131, 148, 150, 154, 157, 158, 164, 170, 175, 180, 182

SUSE 26, 32, 40, 63, 75, 85, 87, 88, 92, 94, 101, 102, 103, 105, 108, 117, 118, 124, 150, 151, 152

SUSE Linux.......................................................................26switch, gigabit..........................................44, 46, 51, 56, 111switch, LAN....................................37, 38, 44, 90, 101, 108switch, SAN..................................xvii, 38, 41, 48, 108, 111switched mode...................................................................24switches35, 37, 38, 41, 44, 46, 48, 49, 57, 64, 82, 150, 151,

166, 180, 182, 185Symantec. . .xvii, 25, 101, 102, 136, 150, 151, 160, 172, 174

Ttape drives. xvii, 20, 22, 42, 49, 50, 52, 53, 54, 55, 58, 59,

60, 61, 63, 64, 65, 66, 68, 69, 71, 72, 79, 90, 101, 106, 108, 111, 141, 149, 154, 164, 171, 181, 183

tape libraries....xvii, 19, 26, 39, 42, 48, 50, 64, 66, 79, 95, 111, 163, 180, 181

tape library, modular.......................................................50tape, virtual. .79, 94, 95, 104, 106, 159, 163, 164, 165, 166,

170, 180, 183, 186tapes.......26, 49, 64, 112, 143, 160, 162, 180, 182, 183, 186tapes and disks.............................................................26, 73TCP..........22, 38, 39, 62, 124, 125, 126, 127, 129, 131, 183TD Platform.....................................................................115



Teradata Services.............................................................154TD-TSM BAR client.........................................................25technologies, emerging......................................................24Teradata 6533 and 6534 SAN switches.............................47Teradata 9200................................39, 50, 51, 53, 54, 55, 64Teradata 9202..................28, 39, 50, 55, 59, 60, 62, 64, 157Teradata 9204 Backup 2 Disk................................73, 74, 96Teradata 9205 Virtual Tape...............................................79Teradata availability..........................................................24Teradata BAR History.......................................................20Teradata Database Performance Variables......................123Teradata DBMS...............................98, 106, 109, 115, 117Teradata downtime............................................................22Teradata Integration................................................ix, 29, 30Teradata nodes 19, 20, 22, 24, 26, 35, 36, 38, 46, 51, 52, 55,

58, 63, 66, 77, 89, 90, 92, 101, 102, 108, 115, 127, 131Teradata TARA.................................88, 102, 103, 105, 137Teradata Tools and Utilities.......................xvi, 85, 103, 186testing...................................................................30, 65, 136throughput. .37, 38, 75, 118, 119, 120, 121, 131, 139, 141,

144, 146, 168, 175, 187Tivoli Storage Manager..xvii, 25, 88, 107, 108, 109, 110,

111, 112, 113, 114, 134, 138, 149, 154 160, 174, 186total cost of ownership.......................................................24transmission control protocol............................................22TSM.....25, 32, 88, 108, 109, 110, 111, 134, 138, 139, 140,

141, 148, 160, 174, 186

TSM BAR client................................................................25tunables............................117, 118, 130, 131, 135, 136, 141tunables, CLI....................................................................127tuning..........89, 90, 101, 108, 117, 124, 129, 130, 131, 136turnkey solution.................................................................29two-tier.................................................26, 27, 28, 29, 73, 79two-tiered.....................................................................26, 28

UUltrium............xvii, 51, 54, 58, 60, 65, 66, 68, 69, 141, 142

Vvendor...................................................30, 31, 67, 102, 187vendors...............................................................................30Veritas..................................xvii, 25, 88, 101, 103, 137, 150virtual tape...79, 94, 95, 104, 106, 159, 163, 164, 165, 166,

170, 180, 183, 186

WWhy LAN-based architecture............................................24Windows. .20, 22, 25, 32, 40, 63, 75, 82, 85, 87, 88, 89, 90,

92, 94, 101, 102, 103, 105, 108, 109, 111, 117, 128, 129, 130, 135, 137, 149, 150, 151, 152, 164, 174, 186, 187

windows backup..............................................................29


123userdocs.s3-website-eu-west-1.amazonaws.com123userdocs.s3-website-eu-west-1.amazonaws.com/d/80/fc... ·...

Documents

Transcript of 123userdocs.s3-website-eu-west-1.amazonaws.com123userdocs.s3-website-eu-west-1.amazonaws.com/d/80/fc... ·...