Skip to content

Consolidation in the Data Center Simplifying IT Environments to Reduce Total Cost of Ownership

Best in textbook rentals since 2012!

ISBN-10: 0130454958

ISBN-13: 9780130454959

Edition: 2003

Authors: David Hornby, Ken Pepple, Bill Walker

List price: $58.00
Blue ribbon 30 day, 100% satisfaction guarantee!
what's this?
Rush Rewards U
Members Receive:
Carrot Coin icon
XP icon
You have reached 400 XP and carrot coins. That is the daily max!

Description:

This book presents the case and methodology for optimizing your computing infrastructure through proven consolidation techniques. It steps you through the consolidation process from the initial business justification, through project planning, architecture, deployment, and management. It provides real-world recommendations for consolidating your infrastructure, as well as avoiding numerous pitfalls along the way. Book jacket.
Customers also bought

Book details

List price: $58.00
Copyright year: 2003
Publisher: Prentice Hall PTR
Publication date: 9/19/2002
Binding: Paperback
Pages: 240
Size: 6.75" wide x 9.00" long x 0.75" tall
Weight: 1.034

Acknowledgements
Preface
Sun BluePrints Program
Who Should Use This Book
Before You Read This Book
How This Book Is Organized
Ordering Sun Documents
Accessing Sun Documentation Online
Evolution of the Data Center
Consolidation Defined
History of the Data Center
The Role of Mainframes
The Strength of Mainframes
The Problem With Mainframes
The Introduction of Minicomputers
The Rise of Distributed Computing
UNIX Operating System
Complexity in the Data Center
Causes and Effects of Server Sprawl
Summary
Business Aspects of Consolidation
Establishing a Business Justification for Consolidation
Reducing IT Costs
Reduce Costs Associated With Complexity
Reduce Staffing Costs
Reduce Building Costs
Keeping Up With Business Challenges
Improving Service Levels and Availability
Minimizing the Impact of External Pressures
Estimating the Cost of Complexity
Understanding Total Cost of Ownership
Following an Established TCO Methodology
Gartner's Definition of TCO
Gartner TCO Software
Simulate TCO
Avoiding Common Pitfalls and Failures
Convincing Business Units to Surrender Their Servers
Gaining and Maintaining Executive Sponsorship
Managing Politics
Applying Best Practices and Adhering to Standards
Developing and Adhering to Well-Defined Processes
Relying on Established Consolidation Methodologies
Considering Prohibitive Bandwidth Costs of High Data-Traffic Applications
Selecting Appropriate Applications to Consolidate Together
Identifying Application or Middleware Coexistence Problems
Considering Legal Requirements to Keep Data Locally
Summary
Types of Consolidation
Consolidating Servers
Applying Vertical and Horizontal Scalability
Identifying Patterns in an End-to-End Architecture
Presentation Tier
Business Tier
Resource Tier
Identifying Types of Consolidation
Physical Consolidation
Logical Consolidation
Rationalization
Consolidating Applications
Eliminating Consolidation Candidates
Applying Backward and Forward Consolidation Strategies
Consolidating Application Sets
Consolidating Multiple Database Instances
Consolidating Similar Workloads
Consolidating Storage
Consolidating Servers and Their Associated Storage
Connecting Heterogeneous Environments to a Single Storage Component
Consolidating With Storage Area Networks
Consolidating Shared Services
Consolidating Networks
Consolidating Data Centers
Consolidating People Resources and Processes
Summary
Consolidation Methodology
Following a Consolidation Methodology
Determining the Feasibility of the Project
Assessing the Current Environment
Assess Application Requirements
Assess Platform Requirements
Assess Storage Requirements
Assess Networking Requirements
Assess Security Requirements
Assess Infrastructure and Operations Requirements
Document Requirements and Dependencies
Designing an Architecture for a Consolidated Environment
Implementing the Consolidation
Managing the Consolidated Environment
Completing Project Phases
Summary
Performing a Consolidation Feasibility Study
Defining Business Objectives
Sample Business Objectives
Defining Success Criteria
Sample Success Criteria
Defining Project Scope
Identifying the Inventory
Compiling a Starting Inventory
Inventory From the Bottom, Up
Inventory From the Top, Down
Simulating Total Cost of Ownership Savings
Sample TCO Analysis
Project Assumptions
Business Assumptions
Consolidation Scenarios
Results of the TCO Analysis
ROI Analysis for Scenario One--33 Percent Reduction
ROI Analysis for Scenario Two--50 Percent Reduction
ROI Analysis for Scenario Three--67 Percent Reduction
Conclusions From the Sample Project
Establishing a Proof of Concept
Identifying a Group of Servers to Consolidate
Identifying the Initial Storage to Consolidate
Summary
Planning a Consolidation Project
Creating a Project Plan
Defining Consolidation Objectives
Clarifying Project Scope
Assessing Consolidation Candidates
Estimating and Documenting Time Lines
Identifying High-Level Project Phases
Setting Major Milestones
Developing a Project Plan
Define the Assessment Phase
Define the Architecture Phase
Define the Implementation Phase
Define the Management Phase
Complete the Project Cycle
Estimating Realistic Durations
Reporting Project Status
Identifying Resource Profiles
Identifying a Project Manager
Identifying Resources to Assess Requirements and Architect Solutions
Identifying Resources to Implement and Administer a Project
Organizing Your Project
Summary
Assessing Technical Feasibility
Preparing for the Assessment
Profiling Applications
Documenting Data Flow
Identifying Dependencies
Use Process Accounting Tools
Interview Developers and Architects
Assessing Application Portability
Documenting the Profile
Assessing Platforms
Verifying Inventories
Assessing Technical Configurations
Automate the Assessment Process
Estimating Utilization
System Activity Reporter
Performance Software Suites
Assessing Storage
Analyzing Online Data
Analyzing Near-Line Data
Analyzing Offline Data
Automating Storage Assessment
Assessing Networking Requirements
Assessing Security
Assessing Infrastructure and Operations
Revaluating Total Cost of Ownership
Assessing Risk
Summary
Designing a Consolidated Architecture
Creating an Architecture
Extracting Requirements From Data
Addressing Common Consolidation Design Issues
Reduce Downtime With Redundant Hardware
Isolate Failures
Improve Time to Recover With Clustering
Addressing Specific Consolidation Architectures
Considerations for Horizontally Scaled Architectures
Considerations for Vertically Scaled Architectures
Considerations for Architectures With Centralized Databases
Considerations for Architectures With Consolidated Clusters
Considerations for Architectures With Collapsed Tiers
Considerations for Architectures That Utilize Time Shifting
Considerations for Development, Testing, and Training Environments
Sizing the Consolidated Architecture
Construct a System Performance Model
Project Changes in the Model
Prototyping the Initial Solution
Building the Prototype
Testing the Prototype
Revising the Solution
Documenting the Solution
Summary
Implementing a Consolidated Solution
Preparing for the Consolidation
Creating a Build Specification
Building the Environment
Prepare the Physical Environment
Install Arrays and Servers
Install the Software Infrastructure
Install the Application Software
Identify Temporary Hardware Requirements
Defining a Data Migration Strategy
Create a Back-Out Process
Practicing the Consolidation
Become Familiar With the New Environment
Backing Up Old Environments
Implementing the Consolidation
Migrating Applications
Testing the Consolidation
Tuning the Configuration
Documenting the Results
Training the Administration Staff
Summary
Managing a Consolidated Environment
Managing Availability
Identifying Potential Availability Problems
Implementing Disaster Recovery
Management Frameworks
FCAPS
Information Technology Infrastructure Library
Sun Ready Availability Assessment
Execution Management
Change Management
Implementation Management
Improvement Management
Asset Management
Staff Management
Service Management
Problem Management
Account Management
Program Management
Summary
Sample Feasibility Study
Introduction
Management Summary
Business Objectives
Criteria for Success
TCO Assessment Details
Other Assumptions
Scenarios
Results of TCO Analysis
ROI Analysis: Scenario One
ROI Analysis: Scenario Two
ROI Analysis: Scenario Three
Conclusions
Sample Application Profile
Revision Information
Application
Production Environment
End-User Overview
System Uptime Requirements
End-User Log In
Batch Cycles
Sign On During Batch Cycles
Maintenance Windows
Dependencies--Application Interfaces
Performance Requirements
Expected Typical User Response Time
Batch Processing Window
Peak Processing Periods
Current Server Operation Overview
Monitoring Needs
Network and Infrastructure Services Used by Application
Naming Service Requirements
Project Constraints
Security Requirements
Application Failover Configuration Requirements
Prerequisite Software Components
Kernel Configuration Changes
Miscellaneous
Database Sizing Information
Portability Issues
Existing Deficiencies
Printing Architecture
Network Architecture
Detailed TCP/IP Port Requirements
File System Requirements
Hardware Requirements
Storage Requirements
Network Requirements
CPU Requirements
Memory Requirements
Other Requirements
Non-UNIX Infrastructure Components
Glossary
Index