SUNGARD SUMMIT 2007 | sungardsummit.com 1
High-Availability and Scalability
Presented by: Gary Fitzgerald SunGard Higher Education
March 21, 2007 Course ID 1239
Introduction
Session goal:
• To understand the various options for high
availability (failover) and scalability in the Unified Digital Campus (UDC) environment.
Session objectives:
• Differences between horizontal and vertical
scalability
• High Availability options that are currently available • Limitations
Topics of Discussion
• Discussion of current options for providing failover and
scalability for the UDC environment.
• Horizontal vs Vertical scaling • Load Balancing
• Clustering
• High Availability and Failover • Oracle RAC
SunGard Summit 2007
In what ways would you like to
measurably improve
SUNGARD SUMMIT 2007 | sungardsummit.com 5
What is Scalability?
• The ability to increase capacity without redesign or
replacement.
• For example,
• Add RAM
• Add additional CPUs to same server (or turn on COD) • Add additional application servers in a load-balanced
environment
• Add additional database servers to a RAC cluster. • Add additional cards to a network switch.
Scalability: Definitions
• Vertical scaling (or “scale up”) generally means adding
more processors (CPUs) and memory (RAM) to a server.
• Horizontal scaling (or “scale out”) generally means
adding more small servers in a load-balanced or clustered environment.
• Diagonal scaling is a combination of both methods,
whereby multiple mid-size computers could be used.
Scalability: Diagram
Scalability: Advantages
• Acquire lower cost hardware
• Add additional hardware when/if needs dictate • Take advantage of latest technology
Vertical scaling
• Server has expandability • Add processing power
incrementally
• “COD” or CPU On Demand
Horizontal scaling
• Many small servers (or blades)
• Add servers when needed
• Load Balancing
Diagonal Scaling
• Multiple mid-size servers
• Add processors or servers when necessary
• Load Balancing
SUNGARD SUMMIT 2007 | sungardsummit.com 13
High Availability: Definition
• In the context of the Unified Digital Campus
environment, this means a hardware infrastructure that is resilient and redundant. It should quickly recover from a component failure.
• For example,
• Redundant components (power supplies, fans, etc.) • Hardware load balancing for application servers. • Clustered database or resource servers.
• Failover firewalls, switches, routers, etc. • Dual-path to disk storage
High availability: Advantages
• Maintain uptime during equipment or software failure • Provide for smoother transition to new software
UDC High Availability Options
• Redundant components in a server.
• Two (or more) servers in a high availability cluster, such
as Sun Cluster, IBM HACMP, HP Serviceguard, Veritas Cluster Sever, RedHat Cluster Suite, Microsoft Cluster Server
• Oracle RAC (Real Application Clusters)
SUNGARD SUMMIT 2007 | sungardsummit.com 18
High Availability and
Scalability examples
High availability and scalability examples
• Multiple application servers in a Network Load Balanced
environment
• Multiple database servers in a High Availability (failover)
cluster.
• Oracle Real Application Clusters (RAC) optional –
provides load balancing and high availability for databases
Banner Self Service Network Load Balanced
Banner Core Application Network Load Balanced
Banner and ODS Database Servers Failover Cluster Students Employees INTERNET Router Internet Firewall
Luminis Servers Reporting Applications Internal Firewall Students Workflow Load Balanced Secure Network Secure Network Campus Network
Web Servers File Servers
Sample High Availability
Architecture
Luminis Parallel Deployment Option
Managed
Browser Browser Browser Browser
Calendar Server Portal
Web ServerPortal Web ServerPortal
Web Server Load BalancerLoad BalancerLoad Balancer Resource Tier
Load Balancing Tier
Portal Tier
Secured Network
Oracle Real Application Clusters (RAC) Architecture Database Files Database Files Redo Redo Logs (1) Logs (1) Redo Redo Logs (N) Logs (N) LGWR LGWR Shared Shared Servers Servers DBWR DBWR Node N Node N Shared Shared Servers Servers LGWR LGWR DBWRDBWR Node 1 Node 1 Cluster Cluster Ware Ware Cluster Cluster Ware Ware
Shared Disk Subsystem Shared Disk Subsystem
SGA SGA SGA
SGA
Instance 1
Instance 1 Instance NInstance N
Quorum Quorum Service Service Quorum Quorum Service Service Interconnect Interconnect GCS GCS GES GES GCS GCS GES GES
Cache Fusion
Oracle RAC Database Components
• Multiple Oracle instances running on multiple nodes
• Multiple instances share a single physical database
• All instances have common data, control, and initialization files
• Each instance has individual, shared log files and undo tablespaces
• All instances can simultaneously execute transactions against the single database
SUNGARD SUMMIT 2007 | sungardsummit.com 25
Summary
• Scalability (vertical, horizontal, diagonal) solutions are
available to reduce hardware costs and provide failover options.
• High Availability (or failover) options are available to
reduce downtime in the event of equipment failure.
• Not all UDC components support all options.
• No one solution is right for all clients – use Sungard
SunGard Summit 2007
In what ways would you like to
measurably improve
Thank You!
Gary Fitzgerald
Please complete the online class evaluation form Course ID 1239
SunGard, the SunGard logo, Banner,, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks referenced herein are trademarks or registered trademarks of their respective owners.
