Sft hardware Updates



Download 56.64 Kb.
Page1/16
Date29.12.2017
Size56.64 Kb.
  1   2   3   4   5   6   7   8   9   ...   16

Customer Best Practices for Teradata Hardware Upgrades






Customer Best Practices for Teradata Upgrades

Major Hardware Upgrades

Revision History





Summary of Changes

Date

Description of Change

Rev #

Author

August 15, 2008

Version for publication

1.0

SFT Members















Important Notes

Date










Table of Contents

1. Introduction 1

2. The Upgrade Process for Teradata Hardware 3

Upgrade Process Overview Diagram 3



3. Project Management 4

4. Upgrade Planning 4

Plan for capacity 4

Research environmental requirements 4

Review network requirements 5

Pre-upgrade Benchmarking 5

5. User Communication 6

6. Change Control 6

7. Environment Changes 7

Data Center: 7

MVS Environment: 7

Node OS Environment: 7

Network Environment: 8

8. BAR Implications 8

9. Pre-Upgrade Preparations with Teradata 9

10. Teradata Upgrade 10

11. Post-Upgrade Steps 11

12. Project Closeout 12

13. Closing 12



1.Introduction


A successful upgrade of any computing environment requires careful planning, coordination, and execution. A Teradata computing environment is no different. There are many factors that need to be considered and brought together for a successful plan. The success you experience is in part dependent on the success of your efforts throughout the process.

In general, there are three things that influence the success or failure of an upgrade:



  • The quality of the product being added/upgraded

  • The service procedures followed by Teradata associates

  • The planning and execution of operational procedures by the customer

All three need to come together without flaw during the upgrade process in order to achieve success. The first two are the responsibility of Teradata. For the purposes of this paper, they are considered out of scope, but assumed to be present and bear no negative impact on the upgrade process.

In the case of hardware upgrades and expansions, it is also critical that the customer provide Teradata with enough information to ensure they are buying sufficient capacity and the appropriate hardware to meet their workload demand. There are many configuration options and choosing the best for each situation must be informed by accurate workload analysis and capacity planning.

This paper will focus on those operational procedures which are the responsibility of the customer. They include, but are not limited to:


  • Planning

  • Coordination

  • Communication

  • Testing

  • Benchmarking

  • Project management

Upgrades can include database software (major, minor, maintenance) and database hardware (upgrade, expansion, migration). This white paper will focus only on hardware upgrades. It will cover upgrades, expansions (including coexistence) and floor sweeps. The assumption is that software will remain static and sites have procured current site installation guides from their CSR and have reviewed them. We suggest that you perform software and hardware upgrades separately if possible to avoid too many moving parts at one time. This will help you identify causes of problems that may occur and is considered best practice for both customers and Teradata Customer Services.

Teradata upgrades are different now than in the past. Server technology is advancing at such a fast pace that upgrades are actually requiring fewer nodes and smaller footprints. This has obvious benefits, but there are potentially negative implications to be aware of.

These new servers are smaller and faster, and they are pushing considerably more AMPs per node. With fewer nodes and less parsing engines, you may have fewer overall sessions available. Depending on your workload, you may need plans to mitigate this, such as purchasing extra memory or PE-only nodes.

Make sure you take the necessary precautions to prevent load and user problems. For example, make sure your load users are not asking for maximum sessions on load utilities. They will get a session for every AMP. This could be very bad if you have several utilities running, 2 or 3 times the number of AMPS and half the number of available sessions that you had previously.




Note to the reader. This guide is provided as a courtesy of the Teradata Partners Service Focus Team (SFT). It comes as is; with no implied support. The procedures represent the combined learning of the customer members who contributed to it. The procedures are meant to be high level guides and do not represent step-by-step procedures. They are accurate to the best combined knowledge of the team, but should always be followed with caution and good judgment as they are not guaranteed to be free from flaws.
Visit the Service Focus Team website to provide feedback on this whitepaper, download additional whitepapers, or learn more about the SFT.

http://www.teradata-partners.com/About/ServiceFocusTeam





Share with your friends:
  1   2   3   4   5   6   7   8   9   ...   16


The database is protected by copyright ©psyessay.org 2017
send message

    Main page
mental health
health sciences
gandhi university
Rajiv gandhi
Chapter introduction
multiple choice
research methods
south africa
language acquisition
Relationship between
qualitative research
literature review
Curriculum vitae
early childhood
relationship between
Masaryk university
nervous system
Course title
young people
Multiple choice
bangalore karnataka
state university
Original article
academic performance
essay plans
social psychology
psychology chapter
Front matter
United states
Research proposal
sciences bangalore
Mental health
compassion publications
workplace bullying
publications sorted
comparative study
chapter outline
mental illness
Course outline
decision making
sciences karnataka
working memory
Literature review
clinical psychology
college students
systematic review
problem solving
research proposal
human rights
Learning objectives
karnataka proforma