Download Customer Best Practices

SFT - Customer Best Practices
October 16th, 2009
Jerry Blevins
Summary of the Topic - The Plan (Spring 2008)
Summary
There is a need and opportunity for Teradata customers to have a
Testing Best Practices Document
Goal
Publish article in the TD Magazine
Provide a BP White Paper accessible to all customers
Winter / Spring 2009 TUG presentations
Approach
Charter a joint team of SFT Members / TD Interface / PM
-
2 >
TD interface who accesses engineering and TCS experts
SFT Best Practices Project Plan
Project Plan
1. Create draft of White Paper
2. Use White Paper as basis for Abstract & Presentation
3. All SFT members to send best practice examples to Team
Leads for as many sections as possible
4. Sub-teams are responsible for their respective sections:
 White Paper
 Presentation
5. Integration Team
 Responsible for integrating the sub-team submissions from the
White Paper and Presentation. Designates to be interviewed for
magazine article.
6. Review progress during SFT monthly meetings
3 >
The Deliverables: By Customers for Customers
Customer Best Practices for Teradata Upgrades
Major Software Upgrades
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
4 >
Table of Contents
Introduction
The Upgrade Process
Major Database Software Upgrades, Defined
Upgrade Process Overview Diagram
Project Management
Upgrade Planning
Research the new version
Identify your dependent applications
Pre-upgrade Benchmarking
Regression Testing
User Communication
Change Control
Upgrade Client Software
Upgrade Teradata Tools and Utilities
Upgrade BAR Software
Teradata Pre-Upgrade Preparations
Teradata Upgrade
Post-Upgrade Steps
Project Closeout
Closing
Customer Best Practices for Teradata Major Software Upgrades
Presentation
Agenda
• Who We Are
• Document Introduction and Highlights
> Upgrade Process Overview
> Project Management and Upgrade Planning
> Communication and Change Control
> Upgrade Client and BAR Software
> Pre-upgrade Steps
> The Upgrade Window
> Post Upgrade Steps
• Closing
2 >
5 >
The Deliverables: Teradata Magazine Article
Ask the Experts
Take It
From Us
9 tips for a smooth upgrade
By the Teradata Service Focus Team
Whether they're called "minor" or "major," all database
software upgrades must be completed hitch-free and be
smoothly integrated with client software and third-party
applications.
Members of the Teradata Service Focus Team work with Teradata
to address your support-related issues.
As members of the Service Focus Team (SFT), a committee that's part of the PARTNERS User Group,
we work closely with Teradata on issues related to support services and other areas that fall beyond the
scope of product enhancements. From our collective experience we've developed a list of nine tips that
we hope you will find helpful in your next upgrade endeavor.
6 >
The Deliverables: By Customers for Customers again
Customer Best Practices for Teradata Upgrades
Major Hardware Upgrades
7 >
Table of Contents
1.
Introduction
2.
The Upgrade Process for Teradata Hardware
Upgrade Process Overview Diagram
3.
Project Management
4.
Upgrade Planning
Plan for capacity
Research environmental requirements
Review network requirements
Pre-upgrade Benchmarking
5.
User Communication
6.
Change Control
7.
Environment Changes
Data Center:
MVS Environment:
Node OS Environment:
Network Environment:
8.
BAR Implications
9.
Pre-Upgrade Preparations with Teradata
10.
Teradata Upgrade
11.
Post-Upgrade Steps
12.
Project Closeout
13.
Closing
Customer Best Practices for Teradata Hardware Upgrades
Presentation
Customer Best Practices for
Teradata Hardware Upgrades
Agenda:
• Who We Are
• Document Introduction and Highlights
> Upgrade Process Overview
> Project Management and Upgrade Planning
> Communication and Change Control
> Upgrade Client and BAR Software
> Pre-upgrade Steps
> The Upgrade Window
> Post Upgrade Steps
• Closing
8 >
Upcoming TUG Meetings: Presentations Owners?
•
•
•
•
•
•
•
Sept 30 - Turkey – Istanbul –
Oct 27 - Australia - Canberra –
Oct 28 - Australia - Melbourne –
Oct 29 - Australia - Sydney –
Nov 5 - UK & Ireland - London –
Nov 11 - Germany - Frankfurt Nov 12 - Scandinavia - Stockholm -
•
•
•
•
•
Nov
Nov
Nov
Nov
Nov
13
17
17
18
19
–
–
–
–
–
Finland & the Baltics - Helsinki Egypt – Cairo Netherlands – Amsterdam France - Paris Spain – Madrid -
•
•
•
•
Nov
Nov
Nov
Nov
25
26
26
27
–
–
–
–
Austria – Vienna Italy – Rome Japan – Tokyo UK & Ireland – Dublin -
• US/Canada will have 10 meetings from March 1 - May 31
> 6 more in August/early September
9 >
Teradata Magazine Article
• Submitted a proposal to the magazine team to do a
second in a series of articles from the SFT.
Ask the Experts
Take It
From Us
Tips for a smooth hardware upgrade
By the Teradata Service Focus Team
10 >
Going Forward Approach?
1. What topic is next on the priority list for best practices?
•
Software – done
•
Hardware – done
•
Testing and Benchmarking before/after upgrades (ties SW & HW together) – Next?
•
Teradata Operations Guide?
•
BAR - FUTURE
•
Security - FUTURE
•
T@YS Education – FUTURE
2. How should we structure the current and next document?
•
Make next topic a new, separate document?
•
Consolidate the Software & Hardware documents into a single upgrades document?
•
Should we review and update existing documents on an annual basis?
3. Do we continue to develop PPT decks for presentation at TUG’s?
11 >
•
Update existing Software Upgrades deck to include Hardware?
•
Create a separate Hardware Upgrades deck?
Possible Whitepaper - Teradata Operations Guide
Possible Contents
Ongoing Maintenance
•
•
•
•
•
•
•
Perform Teradata Space Monitoring, Assignment and Maintenance
Perform Teradata Database Integrity Validation
Perform Teradata Resource Usage Set-up, Support and Reporting
Monitor Technical Alerts
Perform Initial Problem Isolation / Identification / Documentation
Perform Initial Problem Research via Support Link
Provide Incident / Problem Management
Operating System Administration
•
•
•
•
•
Perform Space Monitoring and Assignment (Disks and Other Devices)
Perform Resource Usage Set-up, Support and Reporting (Memory, CPU and
Storage)
Provide User Access and Set-up
Start-up, Shut-down and Reboot Teradata Server Operating System
Data Backup and Recovery
•
•
•
•
•
•
Develop Backup/Recovery Strategy and Procedures
Perform Periodic Backups of Operating System Nodes
Restore Operating System on Teradata Server Nodes
Perform Periodic Backups of Database and Applications
Restore Teradata Database
Perform Disaster Recovery Procedures Administration
System Performance
•
•
•
•
•
•
•
•
•
12 >
Perform Capacity Planning
Perform Availability Tracking, Measurement and Reporting
Develop Performance Monitoring System Procedures
Establish / Maintain Proper Job / User Priorities
Perform Operating System Tuning
Perform Teradata System Level Tuning
Perform General Application Tuning (Data Block Size, Defrag)
Provide Ongoing System Performance Monitoring and Reporting
Monitor Network Usage / Performance
Possible Whitepaper - Teradata Operations Guide
Functionality / Applications
•
•
•
•
•
•
Perform Query Management
Perform ApplicationDesign / Development / Testing
Monitor Application Space
Investigate Application Problems / Performance Issues
Perform Application Tuning
Provide Multivendor Management
Operations
•
•
•
•
•
•
•
•
Perform Real-time Fault Error Monitoring / Trending
Perform System Health Checks
Develop / Maintain Operations Run Book
Monitor Production Job Flow
Monitor System Utilization
Effect Job Recovery When Needed
Manage Host / LAN Connectivity
Perform Network Administration (Support, Reporting and Monitoring)
Database Administration / Security
•
•
•
•
•
13 >
Provide User Access and Set-up (Accounts)
Maintain Account Passwords and Resource Limits
Perform Security Log Reviews / Reporting
Establish / Maintain Access Rights to Database Objects
Start-up, Shutdown and Restart Teradata Database System