BAR Solutions Guide

2: Hardware

Bar Solutions Guide

Bar Solutions Guide

COMMENTS \* MERGEFORMAT

Teradata BAR Solutions Guide

January 12, 2007

Teradata Research and Development

THIS DOCUMENT AND INFORMATION HEREIN ARE THE PROPERTY OF

NCR 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 Confidential

Unpublished Property of NCR Corporation

NCR Confidential

This 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: teradata-books@lists.ncr.com

Any 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 Revision

Revision

Reviewer Name

Function(s) Represented by Reviewer

A01

Cyrus Afkhampour

BAR SME

Jeremy Davis

BAR SME

Anita Jones

BAR SME

Steve Kahle

BAR SME

Jerry Kong

BAR SME

Marc Mundt

BAR SME

Dexter Oliver

BAR SME

Jefferson Uy

BAR SME

Other Interested People

Revision

Name

Function(s) Represented

A01

Engineering group

BAR SMEs

Don Klarner

Technical Sales Consultant

Josh Mereminsky

Technical Sales Consultant

Simon Martinelli

Technical Sales Consultant

Eddie Tan

Technical Sales Consultant

Ysbrand Bergman

Operational Service Consultant

Randy Bell

Operational Service Consultant

David Hardy

Customer Services

David VandenBrink

Customer Services

William Brennan

Customer Services

Craig McPhie

Customer Services

Art Spickerman

Customer Services

Chris McClure

BAR and Data Migration Service Offer Manager

James Crouse

Solution Account Manager

Rex Miller

Senior Product Manager

Reier Torgerson

Product Management Manager

Approver

Dennis Glover

Support Information

Operational Services, BAR Pre-Sales

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

Contact

Phone Number

Director

Mark Newton

1-858-485-3260

Project Manager

Fred Denham

1-858-485-3652

Post-Sales

Randall Bell

1-512-853-9492

Region

Contact

Phone Number

Americas

Don Klarner

1-858-794-1621

Josh Mereminsky

1-858-314-2957

EMEA

Ysbrand Bergman

31-228-52-47-15

Simon Martinelli

+612-9935-3615

Asia/Pacific/Australia

Eddie Tan

(65) 6240-6261

Dean Frost

+64-9-3566742

Global Sales Support (GSS)

GSS XE "Global Sales Support (GSS)" provides Teradata sales support XE "support" and validations for all configurations.

Primary Support Contact

Global Sales Support – Online Assistance Center

Location

San Diego, CA

E-mail address

GSS, Teradata Help Desk@ncr.com

Phone number

1-858-485-3888

Fax number

1-858-485-4015

Global Support Center (GSC)

The Large Systems Global Support Center XE "Global Support Center (GSC)" provides customer support for all Teradata and Teradata BAR solutions.

Support Organization

Large Systems Global Support Center

Location

San Diego, CA

E-mail address

GSC. RB@ncr.com

Phone number

1-800-322-1012 or 1-858-485-3700

Fax number

1-858-485-3666 or 1-858-485-3400

Table of Contents

iPreface

iRevision History

iiSupport Information

iiOperational Services, BAR Pre-Sales

iiGlobal Sales Support (GSS)

iiGlobal Support Center (GSC)

viList of Figures

viiList of Tables

viiiIntroduction to the BAR Solutions Guide

viiiBackground

viiiPurpose

viiiAudience

viiiWhat You Can Expect from this Guide

xiRelated Documents

xiiInternal Sites

xvExternal Sites

xviiPartner Sites

191: Concepts

19Introduction to Backup, Archive and Restore

19Overview

20Teradata BAR History

20Legacy Direct-Attached BAR Architecture

20How it Works

21Advantages

22Disadvantages

22LAN-Based BAR Architecture

22How it Works

23Advantages

24Disadvantages

24Why the Change was Made to LAN-Based Architecture

26Tapes and Disks: The Two-Tiered Strategy

26How it Works

28Advantages

29Disadvantages

29Teradata Integration

29How it Works

30Advantages

31Disadvantages

32Software Concepts Overview

33BAR Hardware Concepts Overview

33Options Overview

352: Hardware

35The Teradata 9203 BAR Server

35BAR Server Function

37BAR Server Connectivity

39BAR Server Description

40BAR Server Components

42Adapters

42Fibre-channel HBAs

44Network Adapters

44Switches

45LAN Switch: Teradata 6535 Gigabit Switch (Copper Ethernet)

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

49Tape Libraries

50Choosing a Library

51Teradata 9200

55Teradata 9202

62Teradata 9201 (StorageTek ACSLS)

64Tape Drives

64Sharing Tape Drives

65Tape Drive Function

66Tape Drive Connectivity

67Description: Ultrium (LTO) Fibre-channel Drives

69Description: StorageTek Fibre-channel Drives

73Teradata 9204 Backup 2 Disk

739204 Function

749204 Connectivity

749204 Description

769204 Components

78Typical Teradata 9204 Configuration

79Teradata 9205 Virtual Tape Library

799205 Function

799205 Connectivity

799205 Description: CDL 710, 720, and 740

819205 Components

83Typical Teradata 9205 Configuration

853: Software

85Teradata Tools and Utilities

85ARC

87Multi-ARC

88Teradata TARA

88Access Modules

89NetVault (BakBone)

89NetVault Overview

93NetVault Components

101NetBackup (Symantec, formerly Veritas)

101NetBackup Overview

104NetBackup Components

107Tivoli Storage Manager (IBM)

108Tivoli Storage Manager Overview

110Tivoli Components

1154: Performance Variables

115Teradata

115TD Platform

118Backup Strategy Impacts on Performance

120TD Database Factors

123Teradata Database Performance Variables

124(TBA)Data Rate to/From Teradata

124Networks

124(TBA)Network

124LAN Tuning

127CLI tunables

127Network Encryption

127Gateway Selection through COP Entries

128COP Configuration

128(TBA)Parallel LAN Guidelines

128BAR Server

128(TBA)Bar server processing speed

128(TBA)Data Rate through server(s)

129(TBA)Distribution of Data Streams across Nodes and Servers

129(TBA)Number of data streams

129Operating System Dependencies (Tunables)

132Software/OTB/Utilities

132Checkpointing: Advantages and Disadvantages

134Performance Tunables

139Cluster Counts

139Number of session attributes in setting up ARC jobs

139Software Encryption

141SAN / 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

142(TBA)Disk to tape copies

143Appendix

143Frequently asked Questions

143Backups

148Support and Compatibility

149NetBackup

153NPARC

153Tape Drives

154TD Services

154BAR and Business Continuity

157Glossary

189Index

List of Figures

21Figure 1: Example of a direct-attached BAR architecture with NetVault

21Figure 2: The legacy layout for the direct-attached architecture

23Figure 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

27Figure 5: The two-tiered backup strategy

28Figure 6: Example of a two-tiered backup-to-disk configuration

33Figure 7: LAN-based BAR components

34Figure 8: Direct-attached BAR components

37Figure 9: BAR Server Types

39Figure 10: Typical Backup to Tape Architecture

43Figure 11: HBA and NIC fibre-channel connectivity

52Figure 12: 9200 Fibre-channel Connectivity - LAN-based Architecture

52Figure 13: 9200 Fibre-channel Connectivity - Direct Connect Architecture

56Figure 14: 9202 Fibre-channel Connectivity - Indirect

57Figure 16: LAN-Based Homogeneous Library for Teradata

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

58Figure 18: Fibre-channel Connectivity

Error! Bookmark not defined.Figure 19: Direct-Attached Homogeneous Library for Teradata

59Figure 15: The Teradata 9202 Modular Library System

65Figure 20: Shared Library Comparisons

77Figure 21: Library Controller Module

78Figure 22: Disk Array Expansion Modules

78Figure 23: Typical Teradata 9204 Configuration

83Figure 24: Typical Teradata 9205 Configuration

89Figure 25: Access Module/Data Connector API Linkage

91Figure 26: Storage Management System

91Figure 27: The NetVault Enterprise

93Figure 28: NetVault with a LAN-based Library

93Figure 29: NetVault with a Direct-Attached Library

96Figure 30: Dynamically Shared Devices - Tape Drive Configurations

97Figure 31: Dynamically Shared Devices - Disk Backup

99Figure 32: VaultShare Diagram for Teradata

100Figure 33: VaultShare Diagram for Open Systems

104Figure 34: LAN-based Configuration

106Figure 35: Teradata extension ordering examples for NetBackup

110Figure 36: TSM Configuration

112Figure 37: Tivoli Requirements Diagram

113Figure 38: Configuration Illustration for SMP and single-node MPP configurations

114Figure 39: Configuration Illustration for Dual Node MPP Configuration

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

List of Tables

23Table 1: Advantages of LAN-Based BAR Solutions

30Table 2: Advantages with and disadvantages without Teradata Integration

32Table 3: Operating system, storage, and software options

40Table 4: 2950 BAR Server

46Table 5: 6535 Gigabit LAN Switch Feature Chart

49Table 6: Fibre-channel Switch Matrix

50Table 7: Library Comparison Matrix

54Table 8: 9200 library-to-tape matrix

60Table 9: 9202 Library-to-Tape Matrix

66Table 10: Library to Tape Matrix

67Table 11: LTO2/LTO3 Tape Drive Common Features

67Table 12: LTO2/LTO3 Tape Drive Differing Features

69Table 13: LTO2/LTO3 Tape Media Common Features

69Table 14: LTO2/LTO3 Tape Media Differing Features

70Table 15: Fibre-channel Tape Drive Comparison Chart

72Table 16: Fibre-channel Tape Media Comparison Chart

75Table 17: 9204 Features

76Table 18: RAID-5 Factoring

80Table 19: CDL Library Comparison Chart

81Table 20: CDL library components

89Table 21: NetVault with Direct-attached Architecture

90Table 22: NetVault with LAN-based Architecture

101Table 23: NetBackup with LAN-Based Configuration

103Table 24: NetBackup Operating System Support

108Table 25: TSM (LAN-Based Architecture Only)

132Table 26: Basic Teradata BAR Server Configuration

142Table 27: Relative Speeds and Maximum Capacities of Tape Drives

147Table 28: Backup Solution Matrix – Small Tables

147Table 29: Backup Solution Matrix – Medium Tables

148Table 30: Backup Solution Matrix – Large Tables

151Table 31: Customer Requirements for NetBackup Migration

Introduction to the BAR Solutions GuideBackground

The Teradata BAR solutions have evolved from standard tape backup to include LAN-based XE "LAN-based" media servers XE "servers: media" , both disk and tape BAR devices, and the concept of OTB XE "OTB" (Open Teradata Backup) software. These ongoing support XE "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.

Purpose

While 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 XE "Technical Sales Consultants" , Operational Services XE "Operational Services" , and Customer Services XE "Customer Services" to assess a customer’s BAR needs and recommend the appropriate BAR solution from Teradata’s offerings.

Audience

The 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 Guide

Since 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 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 Chapter

Preface

· 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) sites

Chapter 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 integration

Chapter 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 to

Chapter Three: OTB Software

· Advantages and Disadvantages of each OTB product

· How each OT product fits into the BAR architectures

Chapter Four: Performance Variables

· Information about the many things that can affect the BAR system performance and what can be done to optimize them

Appendix

· Some FAQs collected to date, and additional Teradata services that relate to BAR

Glossary

· The Teradata BAR-specific meaning for BAR-related terms

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 Document

Definitions – 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 WordNavigation

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 Map

Turn 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

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 Guide

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

Related Documents

XE "related documents"

XE "documents, related" To ensure that optimum benefits are received from the OTB XE "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 Sites

Internal 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.cfm

There 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 Definition

Before beginning any OTB XE "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=061770009

This document covers all three OTB products and is downloadable in PDF format.

The Employee Portal

Some 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. XE "Ordering and Configuration Information (OCI)" XE "OCI" 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 XE "CSNetI" and SalesNet XE "SalesNetI" from “Intranet Sites” as shown below.

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

OR

http://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 Process

Or go directly there at: http://www.csnet.ncr.com/level4download.asp?navIDVar=&DocSpec=1319&DocType=3

BAR Delivery Process Guide

Or go directly there at:

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

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

https://myc.gateway.ncr.com/Site00EC/level3.asp?ResultType=1&ResFlag=1&rbSearchType=Quick&strAND_OR=And&SortFlag=1&search=BAR&strAND=And

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

CSDeliveryNet

XE "CSDeliveryNet" The Teradata Customer Services Delivery Intranet is where the support XE "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 XE "OTB" issue may have been recently posted as a Tech Alert or Knowledge Article XE "Knowledge Articles" , so you will want to know where they are. Find them on the GSC XE "GSC" site at:

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

Repositories

Teradata Realization-Information Repositories XE "Repository: Information-Realization" are located at:

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

External Sites

External sites can be accessed by employees and customers alike.

NCR Information Products Publishing RepositoryBAR 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 XE "Repository: Information Products Publishing" , 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 XE "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 XE "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 XE "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.

Partner Sites XE "partner sites" Hardware

Sun XE "Sun" /StorageTek XE "StorageTek" : SAN switches, backup to disk, tape libraries, drives, and cartridges

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

Dell XE "Dell" Servers, Storage, and Networking

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

Qlogic XE "Qlogic" Fibre-channel Adapters

http://qlogic.com

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

Brocade XE "Brocade" Silkworm XE "Silkworm" SAN switch (through Sun/StorageTek)

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

McData XE "McData" SAN Switch (through Sun/StorageTek)

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

EMC XE "EMC" Clariion XE "Clariion" Disk Library

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

HP XE "HP" Ultrium XE "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

Software

BakBone XE "BakBone (see NetVault)" NetVault XE "NetVault"

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

Symantec XE "Symantec" (Veritas XE "Veritas" ) NetBackup XE "NetBackup"

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

IBM XE "IBM" Tivoli XE "Tivoli" Storage Manager XE "Tivoli Storage Manager"

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

1: Concepts Introduction to Backup, Archive, and Restore

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

Overview XE "overview: backup archive and restore"

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 XE "reliability" and redundancy XE "redundancy" . Unexpected conditions, however, can put a customer's most crucial asset, its data, at risk XE "risk" . Although disasters can strike, the need to restore XE "restore" data most often comes from user-related failures: either operator error XE "operator error" or the introduction of corrupted data XE "corrupted data"

XE "data, corrupted" . Recognizing the need to protect XE "protect" and also archive XE "archive" data, Teradata has developed world-class backup/archive/restore (BAR) solutions that have been optimized for operation with the Teradata nodes XE "Teradata nodes" and database.

Also recognizing that customers use the Teradata Database in different enterprise XE "enterprise" operating environments, we have provided multiple BAR solutions to best match each customer's environment.

Teradata BAR solutions using OTB XE "OTB" software can be viewed as two possible XE "architecture" \t "See also configuration" architectures. The most recent (and now advocated) solution is XE "LAN-based" LAN-based, where Teradata nodes XE "Teradata: nodes" are connected to BAR server XE "server, BAR"

XE "BAR server" s using gigabit XE "Gigabit Ethernet" Ethernet LAN connections. The XE "BAR Servers" BAR servers XE "servers: BAR" initiate and run the backup XE "backup/archive/restore" /archive/restore. The traditional solution is the direct-attached XE "direct-attached" architecture XE "architecture" where tape libraries XE "tape libraries"

XE "libraries, tape" and drives XE "drives, tape" XE "tape 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 XE "support" the XE "customer investment" \i investment of our customers using NetVault XE "NetVault" with direct-attached architecture.

Teradata BAR History XE "BAR History" XE "History, BAR"

In its earliest days, Teradata backup and restore shared a mainframe along with the Teradata Database, using ARC XE "ARC" and sending the data over the XE "mainframe" \i mainframe channels to the tape storage devices XE "storage devices"

XE "devices, storage" .

Although this is not the best approach for performance XE "performance" or cost-effective XE "cost-effective" ness, some of this early backup architecture XE "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 XE "LAN-based" BAR architecture XE "architecture" offers so many advantages XE "advantages: LAN-based BAR architecture" that it has become the advocated XE "advocated solution" Teradata BAR solution.

Legacy Direct-Attached BAR Architecture

The direct-attached solution has been the traditional approach for Teradata systems. In this architecture, XE "architecture" the tape drives XE "tape drives"

XE "drives, tape" and library are directly attached to the Teradata system and the Teradata nodes XE "Teradata nodes" initiate and run the backup/restore.

The newer LAN-based XE "LAN-based" architecture XE "architecture" is the XE "advocated solution" \i

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

How it Works

In the legacy XE "legacy" direct-attached XE "direct-attached" architecture XE "architecture" , one of the Teradata nodes XE "nodes" has a tape library connection and each node has a tape drive, the ARC XE "ARC" utility, and the NetVault XE "NetVault" client module. The data travels over a direct SCSI XE "SCSI" * or fibre connection rather than over a network XE "network" . The recommended XE "strategy" 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 XE "direct-attached" architecture XE "architecture" . This new architecture moves the management functions of the NetVault XE "NetVault" Server off of the Teradata node and improves the XE "improved backup performance" 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 XE "direct-attached BAR architecture" with NetVault XE "NetVault"

Figure 2: The Legacy XE "legacy" Layout for the Direct-Attached XE "direct-attached architecture" Architecture

Advantages XE "Advantages: direct-attached"

The advantage of the direct-attached XE "direct-attached" architecture XE "architecture" , for some configurations, is the lower initial cost XE "initial cost" XE " cost, initial " because the network XE "network" of XE "BAR server" BAR server XE "server, BAR" s and interconnections are not needed.

Another advantage of the direct-attached XE "direct-attached" architecture XE "architecture" is that it provides legacy XE "legacy" investment protection for existing Teradata customers with MP-RAS XE "MP-RAS" operating systems that are using NetVault XE "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 XE "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 adequate windows of time to do backups XE "backup window" XE " window backup " when the system is quiet or not doing other workloads.

Disadvantages XE "Disadvantages: direct-attached"

With the BAR hardware and software directly on Teradata nodes XE "nodes" , the disadvantage is the contention XE "resource contention" with Teradata resources that results in a less than optimal parallel XE "parallel environment" environment. BAR exceptions and maintenance XE "maintenance windows" XE " windows, maintenance " windows can also cause XE "Teradata downtime" Teradata downtime.

The direct-attached XE "direct-attached" architecture XE "architecture" also provides less flexibility XE "flexibility" for customers to re-utilize their existing hardware components or to utilize hardware that is not Teradata- XE "Teradata-certified" certified.

The direct-attached XE "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 Architecture

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

XE "devices, storage" .

The LAN-based XE "LAN-based" architecture XE "architecture" is the advocated solution XE "solution, advocated"

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

How it Works

LAN-based XE "LAN-based" BAR is built around a private LAN system that is used to move data between the Teradata nodes XE "nodes" and the BAR server XE "server, BAR"

XE "BAR server" s. The OTB XE "OTB" software initiates and runs the backup/restore from the BAR servers XE "BAR servers" XE "servers, BAR" , which are also connected to the XE "tape drives" tape drives XE "drives, tape" and XE "storage devices" \b storage devices XE "devices, storage" . This frees up duty cycles for the Teradata nodes XE "nodes" .

Transmission control protocol ( XE "TCP"TCP XE "transmission control protocol" ) overhead is essentially the same for both architectures, but direct-attached XE "direct-attached" TCP sessions are configured for the BYNET XE "BYNET"and rob CPU time from Teradata processes.

Figure 3: Example of LAN-Based XE "LAN-based" BAR Architecture XE "architecture, LAN-based" with Backup 2 Disk

Figure 4: Another Example of LAN-Based BAR Architecture with Backup XE "backup" to Disk XE "backup to disk"

XE "advantages: LAN-based" Advantages

There are a number of reasons to move the BAR activity to a XE "dedicated server" dedicated server XE "server, dedicated" , and LAN-based XE "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 Solutions

Advantages of LAN-Based BAR Solutions

Improves fit into standard enterprise XE "enterprise" architectures

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

Reduces XE "planned downtime" XE " downtime, planned "planned downtime

Having BAR processes on the BAR server XE "server, BAR"

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

Avoids operating system restrictions

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

Increases XE "Teradata availability" \b Teradata availability

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

Lowers costs

Moving the BAR application workload from the Teradata nodes XE "nodes" to low-cost XE "low cost" server platforms reduces XE "total cost of ownership"total cost of ownership.

Better supports emerging t XE "technologies, emerging" \b echnologies

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

Better supports customer growth XE "growth"

Improved XE "flexibility"flexibility: LAN-based XE "LAN-based" solutions detach devices from the direct-attached XE "direct-attached" mode, attaches them in a XE "switched mode" switched mode, and allows them to be shared resources.

Improved XE "scalability" \b scalability: LAN-based XE "LAN-based" solutions detach devices from the direct-attached XE "direct-attached" mode, attaches them in a switched mode, XE "switched mode" and allows for incremental XE "growth"growth at a component level.

XE "disadvantages: LAN-based" Disadvantages

The only disadvantage of the LAN-based XE "LAN-based" architecture XE "architecture" is the additional initial cost XE "cost, initial" for BAR server XE "server, BAR"

XE "BAR server" s and network XE "network" interconnections. A dedicated Gigabit Ethernet XE "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 XE "LAN-based" architecture XE "architecture" .

Why the Change was made to LAN-Based Architecture XE "Why LAN-based architecture"

XE "Rationale for LAN-based architecture"

The change to the LAN-based XE "LAN-based" architecture XE "see also, configuration"

XE "architecture" at Teradata spans at least three years of careful planning. Here is some of the background XE "background" and rationale:

OTB XE "OTB" Software

The 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 XE "NetVault" , Symantec XE "Symantec" NetBackup XE "NetBackup" , and IBM XE "IBM" Tivoli XE "Tivoli" Storage Manager XE "Tivoli Storage Manager" . The LAN-based architecture XE " LAN-based architecture" was seen as the correct path to pursue in order to support XE "support" this objective because it provides the greatest XE "flexibility" flexibility and XE "adaptability" 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 XE "OTB" \b OTB software offers.

XE "BakBone" \b BakBone XE "BakBone (see NetVault)" XE "NetVault" \b NetVault XE "NV" \b (NV): The Advocated Solution

· The LAN-based architecture XE " LAN-based architecture" is available for use with BakBone XE "BakBone (see NetVault)"

XE "BakBone" NetVault XE "NetVault" .

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

XE "Symantec" \b Symantec (previously XE "Veritas" \b Veritas) XE "NetBackup" \b NetBackup XE "NBU" \b (NBU)

· With the evolution of the relationship with NetBackup XE "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 XE "support" and growth of our current NetBackup customers.

IBM XE "Tivoli" \b Tivoli Storage Manager XE "TSM" \b XE "Tivoli Storage Manager"

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

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

Future Growth

The continued growth XE "future growth" of the LAN-based XE "LAN-based" BAR solution will come from several areas of interest within our customer base and new prospects:

· All XE "BAR SANs" \b BAR SANs XE "SANs, BAR" (Storage Area Networks) are implemented and supported via the LAN-based XE "LAN-based" architecture XE "architecture" . This means that BAR SANs will not be supported when attached directly to XE "MP-RAS nodes" \b MP-RAS nodes.

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

· All Teradata XE "SUSE Linux" \b SUSE Linux systems are supported via the LAN-based XE "LAN-based" architecture.

Tapes and Disks: The Two-Tiered Strategy XE "tapes and disks"

XE "strategy, two-tiered"

XE "disks and tapes"

XE "modular tape library" \b \i Modular-tape-library-systems are an integral component of the Teradata BAR environment, providing a XE "protect" \b \i protected repository for the customer’s data. Connected either to a BAR server XE "server, BAR"

XE "BAR server" in LAN-based XE "LAN-based architecture " architecture or directly to the XE " nodes" \b \i Teradata nodes, Teradata tape XE "tape libraries" \b \i libraries XE "libraries, tape" provide XE "high performance" \b \i high performance XE "performance, high" backups, archives, and restores.

XE "backup to disk" \b \i Backup-to-disk storage systems are XE "disk-based" \b \i disk-based data management solutions that include XE "controllers" \b \i controllers, XE "disk arrays" \b \i disk arrays, and XE "integrated software" \b \i integrated XE "integrated" software that manages and controls the disk system. Backup-to-disk technology is gaining XE "popular" \b \i popularity due to its greater reliability XE "reliability" , and in some cases, higher performance XE "performance" . However, tape remains the most XE "cost-effective" \b \i cost-effective technology for long term archiving and for sending data to offsite locations.

In the LAN-based XE "LAN-based architecture " architecture, Teradata advocates a XE "complementary" \b \i complementary approach using both technologies: a XE "two-tier" \b two-tier backup XE "strategy" \b \i strategy XE "strategy, backup"

XE "backup strategy" using both disk and tape.

How it Works

Concept

When a backup is initialized, data flows from Teradata through the XE "BAR server" \b BAR server XE "server, BAR" to the XE "disk array" \b disk array. The Teradata 9204 XE "9204" or Teradata 9205 XE "9205" backup to XE "disk arrays" \b disk XE "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 XE "storage, short-term" (measured in hours or days).

The BAR server XE "server, BAR"

XE "BAR server" s 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 XE "storage, intermediate" (measured in weeks or months).

For XE "offsite media storage" \b off-site media storage XE " storage, offsite " , also called vaulting XE "storage, 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 XE "mechanical failure" \b mechanical tape drive and tape media failure XE "media failure"

XE "failure, media" by using global hot spares and disk drives ( XE "SATA drives" \b SATA drives XE "drives, SATA" for the Teradata 9204 XE "9204" and low-cost XE "cost" fibre-channel disk drives for the Teradata 9205 XE "9205" ) in a XE "RAID" \b RAID-5 configuration. If a disk fails, the controller activates a XE "global hot spares" \b global hot spare and continues the backup XE "backup" , thereby ensuring protection against failure. This built-in XE "redundancy" \b redundancy and reliability XE "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 XE "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 XE "NetBackup" , a tape copy can be made concurrently with backup XE "backup" to disk XE "backup to disk" .

Figure 5 shows the various possibilities for backup XE "backup" and restore XE "restore" in a backup-to-disk XE "backup to disk" -to-tape XE "configuration" \b configuration.

Figure 5: The two-tier XE "two-tier" ed backup XE "backup" strategy XE "strategy, backup"

XE "backup strategy"

Figure 6 shows the XE "two-tiered strategy " \b XE " strategy, two-tiered " \b two-tiered strategy in the LAN-based XE "LAN-based architecture " architecture using the Teradata 9202 XE "Teradata 9202" SL8500.

Figure 6: Example of a Two-Tiered Backup XE "backup" To Disk XE "backup to disk" Configuration

XE "advantages: two-tiered strategy" \i Advantages

Reliability

The 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 XE "backup windows" \b backup XE "backup" windows XE "windows, backup" and those who have situations where it is absolutely critical to have backups XE "backups, scheduled" at a certain time of the day have a more XE "reliable" \b reliable XE "reliability" solution with the two-tiered strategy.

XE "cost savings" \b Cost Savings

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

Disadvantage XE "disadvantages: two-tiered strategy" \i

As with the LAN-based XE "LAN-based" solution, there are the initial and ongoing XE "maintenance" \b maintenance costs XE "cost" 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 Integration XE "Teradata Integration"

An integrated XE "integrated solution" Teradata BAR solution is optimized for a Teradata XE "parallel environment" \b parallel environment: all of its elements are XE "certified" \b certified, sold, and supported by Teradata.

How it Works

Teradata as the Single Source

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

Customer Service

The best outcome in a XE "customer service" \b customer service XE "service" situation is to have an integrated XE "integrated" solution. Without a completely Teradata-integrated system, the most advantageous situation is to have XE "accurate records" \b accurate records XE "records, accurate" about where the non-Teradata-c XE "certified" \b ertified components are in the customer system so that we are not attempting to XE "support" \b support components that we did not provide. XE "GSC" \b GSC can only provide support up to the customer-provided component and then the incident XE "incident" must be turned back over to the customer to take to the other vendor XE "vendor" .

Also be aware that when problems come up after the installation of a non- XE "non-integrated" \b integrated system, customers may still turn to the GSC XE "GSC" because of an existing support XE "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.

XE "advantages, Teradata integration" \i Advantages

Table 2: Advantages with and disadvantages without Teradata Integration XE "Teradata Integration"

Advantages of Teradata Integration

Disadvantages without Teradata Integration

Overall Issues

· There is very low risk XE "risk" .

· Customers get one-stop shopping and support XE "support" .

· Customers get realistic performance XE "performance" and capacity planning.

· Customers benefit from Teradata scalability XE "scalability" with system growth XE "system growth" .

· Customers get a full family of XE "storage devices" \b storage devices XE "devices, storage" and XE "BAR applications" \b BAR applications. XE "applications"

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

· The customer has to coordinate planning and installation with multiple XE "vendors" \b vendors.

Startup Issues

· Teradata XE "engineering" \b engineering puts all the disparate pieces together and runs extensive interoperability XE " interoperability testing" \b testing, optimizing the whole BAR solution for the Teradata XE "parallel environment" \b parallel environment.

· All components of each specific BAR solution are fully XE "integrated" \b integrated, tested, and certified XE "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 XE "parallel architecture" 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 XE "configure" \b configure the components themselves and take responsibility for integration, installation, setup, testing XE "testing" , and support XE "support" .

· It takes longer to install.

· The customer has to troubleshoot problems between XE "vendor" \b vendors.

· Even if the customer uses a TERADATA-specified manufacturer and part number, what the vendor ships can be different enough that something does not work.

· The customer will have a unique configuration XE "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 XE "non-integrated" components since they have no knowledge of the entire solution.

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

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

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

XE "disadvantages: without Teradata integration" \i 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 XE "vendor" “X” for certain applications XE "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 XE "vendor" that the customer is not familiar with

· Purchasing all of their equipment from Teradata might jeopardize the existing relationship with other vendors

This 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 Overview XE "overview: software concepts"

BAR Backup and Recovery Software schedules and sets up the backup XE "backup" and restore, XE "restore" and manages drive availability.

SEE ALSO: Chapter Three, BAR Software

Table 3 shows the different operating systems, storage XE "storage media" XE " media, storage " media, and software that can be used with each of the two BAR architectures.

Table 3: Operating System, Storage XE "storage" , and Software Options

Architecture

Teradata Database Operating Systems

BAR Server OS

Storage Media

Data Backup and Recovery Software

NetVault XE "NetVault"

Tightly XE "integrated" \b Integrated

NetBackup XE "NetBackup"

Loosely Integrated

TSM XE "TSM"

Non-Integrated

LAN-Based BAR

Windows XE "Windows" 2000/2003

XE "MP-RAS" \b MP-RAS (UNIX)

XE "SUSE" \b SUSE XE "Linux" \b Linux

Windows XE "Windows"

Tape

(

(

(

Disk

(

(

(

SUSE XE "SUSE" Linux XE "Linux"

Tape

(

(

Expected by 2007

Disk

(

(

Expected by 2007

Direct-Attached BAR

MP-RAS XE "MP-RAS" (UNIX)

N/A XE "Windows" \b

Tape

(

NO

NO

N/A XE "Linux"

Disk

NO

NO

NO

BAR Hardware Concepts Overview XE "Overview: BAR hardware concepts"

The LAN-based XE "LAN-based" BAR environment includes not only data-storage XE "storage" devices XE "storage devices" , XE "devices, storage" 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 XE "Options Overview" XE " Overview: hardware options "

Figure 7 and Figure 8 show the difference between the components required for the LAN-based XE "LAN-based architecture" and direct-attached XE "direct-attached architecture" architectures.

Figure 7: LAN-Based XE "LAN-based BAR components" BAR Components

Figure 8: Direct-Attached BAR Components XE "direct-attached BAR components"

2: HardwareThe Teradata 9203 XE "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 XE "9203" BAR Server/6535 XE "6535" Gigabit Switch OCI

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

9203 XE "9203" BAR Server (2950)/6535 XE "6535" Gigabit Switch OCI

https://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 FunctionArchitecturesLegacy Direct-Attached

In the legacy XE "legacy" direct-attached XE "direct-attached architecture " architecture, a BAR server XE "server, BAR"

XE "BAR server" can host the NetVault XE "NetVault" Server (management) software and TTU software to provide better functionality and resource usage. The Teradata nodes XE "Teradata nodes" are used as client servers XE " client servers " XE "servers, client" to host and run the client software.

LAN-Based

BAR server XE "server, BAR"

XE "BAR server" s and LAN gigabit Ethernet XE "Gigabit Ethernet" switches XE "switches" are the foundation of the LAN-based XE "LAN-based architecture " architecture. The BAR servers XE "servers, BAR" can be used as management server or as data servers.

In a typical BAR LAN-based XE "LAN-based" environment, a BAR controller infrastructure is created with switches XE "switches" and servers XE "servers" placed in the BAR controller rack. The management functions are placed on one server and the data movement functions are placed on the other servers. Management and data movement functions must be on separate servers, since performance XE "performance" suffers if both of those functions are combined on the same BAR server XE "server, BAR"

XE "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 FunctionsBAR Management Server

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

The BAR management server is sometimes referred to as the BAR master server.

BAR Data Server

The other BAR server XE "server, BAR"

XE "BAR server" s, known as BAR data servers XE "servers, data" , run the OTB XE "OTB" client software components and the TDE (Teradata Extension) XE "TDE" 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 XE "backup and restore" and restore operations.

Once the management server has started a job, the ARC XE "ARC" utility then initiates on the data servers XE "servers, data" to retrieve data from the Teradata nodes XE "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 XE "6535" Gigabit LAN switch XE "switch, LAN"

XE "LAN switch" optimizes the data path to and from the Teradata system.

The Teradata 6535 XE "6535" Gigabit Ethernet LAN switch XE "switch, LAN"

XE "LAN switch" optimizes the data paths to and from each Teradata node. Since Teradata is a parallel XE "parallel architecture " architecture, the more nodes XE "nodes" there are with connections to the Gigabit Ethernet switches XE "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 XE "throughput" .

Each BAR Server

· Each BAR server XE "server, BAR"

XE "BAR server" has two dedicated fibre-channel HBAs (host bus adapters XE "HBAs" ) with two ports on each adapter.

· Each BAR server XE "server, BAR"

XE "BAR server" has one NIC XE "NIC" adapter with two ports.

These must be installed in each BAR server XE "server, BAR"

XE "BAR server" to ensure proper data flow during backup XE "backup and restore " and restore operations. If they are not installed, the system will not work. If they are not properly integrated XE "integrated" , the system performance XE "performance" will be degraded.

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

NOTE: Gigabit Ethernet XE "Gigabit Ethernet" LAN should be a privately mapped network XE "network" or subnet and support XE "support" jumbo packets (9000 MTU – maximum transfer units). Gigabit Ethernet switches XE "switches" should support maximum aggregate throughput XE "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 server XE "server, BAR"

XE "BAR server" s via a separate public-LAN (not shown in Figure 10) through the OTB XE "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 XE "nodes" for browser purposes when creating backup XE "backup" jobs and for administering the LAN switch XE "switch, LAN"

XE "LAN switch" (es). The master is typically not involved in data transfer to tape.

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

BAR Data (Client) Servers

· The data (client) servers XE "servers" communicate with the management (master) server through the OTB XE "OTB" client software, passing control information.

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

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

SEE ALSO: The Teradata BAR Solution with 9203- XE "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 Connectivity

Storage connectivity may include either of the following options:

· The Teradata 6533 XE "6533" SAN switch XE "switch, SAN"

XE "SAN switch" (required for the Teradata 9205 XE "9205" )

· A single fibre-channel HBA XE "HBA" port on the server connected directly to a fibre-channel port on the device

Tape Backup and Storage Connectivity

Backup and storage XE "storage" may be connected to automated tape libraries XE "tape libraries"

XE "libraries, tape" .

· Teradata 9200 XE "Teradata 9200" : Fibre-channel, from the BAR management server)

· Teradata 9202 XE "Teradata 9202" : From the BAR management server across TCP XE "TCP" through the Automated Cartridge System Library Software (ACSLS XE "ACSLS" )

The BAR server XE "server, BAR"

XE "BAR server" may also connect to:

· Tape drives XE "drives"

· Tape library robotic control (implemented by an additional connection from a BAR server XE "server, BAR"

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

· Tape backup XE "tape backup" and storage XE "tape storage" (used alone or together with a disk backup system).

Disk Backup Connectivity

Most disk backup XE "disk backup" systems are used together with tape storage XE "tape storage" systems. Disk storage is only available for LAN-based XE "LAN-based" architectures and includes both B2D (backup-to-disk XE "backup to disk" ) and virtual options:

· Teradata 9204 XE "9204" (B2D)

· Teradata 9205 XE "9205" (Virtual)

Figure 10 illustrates the possible connection paths within the BAR system.

Figure 10: Typical Backup to Tape Architecture

BAR Server Description

The Teradata BAR Server is built by Dell XE "Dell" and customized for the LAN-based XE "LAN-based architecture " architecture. Only one model is available and it is sold fully preconfigured and optimized to support XE "support" the Teradata BAR LAN-based architecture. The customer has the choice of two operating systems; a Windows XE "Windows" 2003 server or a SUSE XE "SUSE Linux " Linux enterprise XE "enterprise server" XE " server, enterprise " server.

The Teradata 9203 XE "9203" BAR server XE "9203 BAR server" (Dell XE "Dell" PowerEdge 2950), with Intel® Xeon® processors and a balance of internal expandability and rack density, gives our customers both the high performance XE "performance, high"

XE "high performance" and drive capacity they need for their growing applications XE "applications" . It is recommended for any Teradata system.

Table 4: 2950 BAR Server

Features

Dell XE "Dell" PowerEdge 2950

Form Factor

2U rack height

Processor

Two 3.0-GHz Intel® Xeon™ Core Duo with 4-MB of cache

Front side Bus

1333 MHz

Memory

2-GB DDR-2 400 MHz SDRAM

Disk Drive

Two 73-GB 10K RPM SAS drives, XE "drives" with RAID- XE "RAID" 1

Ethernet XE "Ethernet"

Intel® Pro1000PT dual port Gigabit – copper adapter

Embedded two Gigabit ports on motherboard

Fibre-channel XE "Fibre Channel"

Two QLogic 2462 dual port 4-Gigabit fibre-channel XE "Fibre Channel" adapters

CD-ROM

48X IDE CD-ROM

Floppy Drive

1.4- MB floppy drive

Power

Redundant power supply with Y-CORD

Operating System

Windows: XE "Windows Server" Windows Server 2003 R2 Standard EditionLinux: SUSE XE "SUSE Linux " Linux Enterprise Server

RoHS

Compliant

BAR Server ComponentsStandard BAR Server Components

The BAR server XE "server, BAR"

XE "BAR server" rack and the following components are delivered with each BAR server:

· Two fibre-channel HBAs

· One Gigabit Ethernet XE "Gigabit Ethernet" HBA XE "HBA"

· Two disk drives XE "disk drives"

BAR Server Rack

The BAR server XE "server, BAR"

XE "BAR server" rack (A Dell XE "Dell" 4210 PowerEdge 42U Cabinet) is an industry-standard 42U rack that can hold up to 13 BAR servers XE "BAR servers" XE " servers, BAR " , 3 Gigabit switches XE "Gigabit switches" , 2 SAN switch XE "switch, SAN"

XE "SAN switch" es, 1 1U rack console, a 0U KVM XE "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 features

Rack Console

· Rack console allows the system administrator’s control station to mount directly into the rack without sacrificing the rack space needed for servers XE "servers" and other peripherals XE "peripherals"

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

· Required when there are more than two BAR server XE "server, BAR"

XE "BAR server" s

· 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

PDU

The power cords XE "power cords" XE " cords, power " for the power distribution unit are region specific. All run at 16 AMPs and 208V.

· Americas/AsiaNEMA L6-20 power cord

· Europe/AsiaIEC 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 XE "server, BAR"

XE "BAR server" .

Console Switch

Form factor:

0U in a Dell XE "Dell" Rack

Rack console:

1 per KVM switch

Port expansion

Up to 8 port expansion

Modules:

modules; supports a total of 64 BAR Servers

System ports:

8 CAT-5 slots

Power:

Voltage: 100-240V AC, freq. 50-60Hz

Video:

1600x1200, VGA, SVGA, XGA

Adapters

Adapters 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 XE "NIC" interface adapters (NICs) and fibre-channel host adapters.

Fibre-Channel XE "fibre channel" HBAsFibre-Channel HBA XE "HBA" Function

In the Teradata BAR environment, the HBAs transport SCSI XE "SCSI" (small computer system interface) traffic from the BAR server XE "server, BAR"

XE "BAR server" to the disk arrays XE "disk arrays" . An HBA XE "HBA" interfaces with fibre-channel-connected peripheral devices (including BAR tape drives XE "tape drives"

XE "drives, tape" , tape libraries XE "tape libraries"

XE "libraries, tape" , 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 XE "fibre Channel" HBA XE "HBA" Connectivity

The BAR server XE "server, BAR"

XE "BAR server" s connect to the tape libraries XE "tape libraries"

XE "libraries, tape" and/or backup XE "backup" to disk XE "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 XE "HBA" .

Figure 11: HBA and NIC Fibre-channel Connectivity

SEE: Network Adapter Connectivity in this chapter.

Fibre-channel XE "Fibre Channel" HBA XE "HBA" Description

The fibre-channel adapter used for Teradata BAR solutions is the QLogic XE "QLogic" 2462.

Dual-port fibre-channel adapter

· 266 MHz

· 4 Gigabit

· PCIe

· Multi-mode optic LC connectors

· 64-bit

· Single-integrated XE "single-integrated" fibre-channel

· Auto-negotiation of fibre-channel speed bit rate (1 Gbps or 2 Gbps)

· Automatic topology detection

· Concurrent support XE "concurrent support" for SCSI XE "SCSI" and IP XE "IP" protocols

· Simultaneous initiator and target mode support XE "initiator support" XE " support, initiator "

XE "target mode support"

XE " support, target mode "

· Easy detection of activities through an LED panel

· 300,000 IOPS delivers high I/O (input/output) transfer rates for storage XE "storage applications " 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 XE "logical networks" XE " networks, logical "

· Universal boot support XE "universal boot support" XE " support, universal boot "

· Overlapping protection domains for continuous protection of internal data paths

· T10 cyclic redundancy XE "cyclic redundancy check" 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 Adapters

Every BAR Server includes an Intel Pro1000 PT Gigabit Ethernet XE "Gigabit Ethernet" adapter.

Network Adapter Function

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

Network Adapter Connectivity

Network adapters XE "network adapters" XE " adapters, network " connect the Teradata node to the gigabit switch XE "switch, gigabit"

XE "gigabit switch" , and the gigabit switch to the BAR server XE "server, BAR"

XE "BAR server" .

SEE: Figure 11: HBA and NIC Fibre-channel Connectivity

Network Adapter Description

The Network Interface Card (NICs) in use for Teradata BAR solutions is the Intel Pro 1000. It has four Gigabit Ethernet XE "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

Switches

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

LAN Switch: Teradata 6535 XE "6535" Gigabit Switch (Copper Ethernet XE "Ethernet" )

SEE ALSO: 6535 XE "6535" OCI

https://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 Function

In the LAN-based XE "LAN-based architecture" architecture, the Teradata 6535 XE "6535" Gigabit switches XE "switches" provide the connectivity and data paths between the Teradata nodes XE "nodes" and the BAR server XE "server, BAR"

XE "BAR server" s. The Teradata 6535 gigabit switch XE "switch, gigabit"

XE "gigabit switch" plays an important role by optimizing the data flow between the Teradata nodes XE "nodes" and the BAR servers XE "servers" .

LAN Switch Connectivity

Figure 12: LAN Switch Connectivity

The Teradata node is connected to the BAR server XE "server, BAR"

XE "BAR server" via two private Gigabit Ethernet XE "Gigabit Ethernet" LAN connections.

LAN Switch Description XE "Description: LAN Switch "

This high-performance XE "high-performance" XE " performance, high " gigabit Ethernet XE "Gigabit Ethernet" switch (Dell XE "Dell" ™ PowerConnect™ 5324) is customized for the BAR LAN-based XE "LAN-based architecture " architecture. It features robust security capabilities and easy remote Management. It is a Managed Switch XE "managed switch"

XE " switch, managed " 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 XE "6535" Gigabit LAN Switch Feature Chart

Features

Teradata BAR Gigabit Switch

Total Switch Capacity

48 Gbps

Maximum Forwarding Rate

35.6 Mpps

Built-in Gigabit Ethernet XE "Gigabit Ethernet" Ports

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

Fibre-Capable Gigabit Ethernet XE "Ethernet" Ports

4

Edge Authentication via 802.1x

Supports single and multiple host access

802.1Q VLAN

Up to 247 VLANs

802.1p Priority

Yes

Management Access Profiles

Yes

GVRP

Yes

Quality of Service

Yes, L2/L3-aware

Priority Queues

4

Link Aggregation

Yes, LACP and manual (IEEE 802.3ad)

Multicast Support

IGMP Snooping

Spanning Tree Support

Spanning Tree and Rapid Spanning Tree w/FastLink

Remote Management

Yes

Authentication Support

RADIUS and TACACS+

MAC-based Port Security

Yes

Management Traffic Encryption

SSLv3 and SSHv2

Dual Firmware Image Support

Yes

Configuration File Management

File upload and download

SNMP Support

SNMPv2c

Remote Logging

Syslog

Industry-standard CLI

Yes

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

· The 6535 XE "6535" -0002-8090 Teradata BAR Gigabit Switch is RoHS compliant.

· The older version of the Gigabit Switch, 6535- XE "6535" 0001-8090, is not RoHS compliant and has been discontinued.

SAN Switches: Teradata 6533 and 6534 XE "Teradata 6533 and 6534 SAN switches" SAN Switches (Fibre-channel XE "Fibre Channel" )

SEE ALSO: Teradata 6533 XE "6533" /6534 XE "6534" Fibre-channel XE "Fibre Channel" SAN Switches

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

SEE ALSO: Instructions for accessing OCIs through the Employee Portal

SAN Switch Function

In a LAN-based XE "LAN-based" BAR configuration XE "configuration" , the Teradata 6533 XE "6533" and 6534 XE "6534" switches XE "switches" are storage XE "storage" area networking XE "networking" (SAN) products for data storage backup XE "backup and recovery applications" and recovery applications in a shared storage environment. We also use them to connect storage devices XE "storage devices"

XE "devices, storage" to BAR server XE "server, BAR"

XE "BAR server" s. SAN Switches are required for all 9205 XE "9205" CDL XE "CDL" installations.

NOTE: SAN switch XE "switch, SAN"

XE "SAN switch" es are not advocated in the Teradata BAR direct-connect architecture XE "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 switch XE "switch, SAN" e XE "SAN switch" s are required for all 9205 XE "9205" CDLs (Clariion XE "Clariion" Disk Libraries). Due to limited slots on the 9205 CDL, XE "CDL" SAN Switches are needed to provide connectivity between the BAR Servers and the CDL.

SAN Switch Description

Teradata 6533 XE "6533" and 6534 XE "6534" are industry-standard, RoHS-compliant, fibre-channel SAN switch XE "switch, SAN"

XE "SAN switch" es that provide basic SAN functionality. They support XE "support" both the FC-AL (fibre-channel arbitrated loop) and “fabric” operation of the SAN as well as the use of “zoning” XE "zoning" where necessary or desired to partition the SAN. They are certified XE "certified" for use with the following systems:

The 6533 XE "6533" and the 6534 XE "6534" fibre-channel switch are sourced from Sun XE "Sun" StorageTek XE "StorageTek" and manufactured by Brocade XE "Brocade" and McData XE "McData" .

· 9200 XE "9200" SL500 Modular Tape Library

· 9202 XE "9202"