1. The Stratus® ftServer® Family

2. Platforms Differentiated by Superior Availability
Stratus Confidential
Platforms Differentiated by Superior Availability
Industry-standard ftServer® platform
>99.999% availability across fleet
Choice of hardened operating system
Automatic availability; no application modification
Red Hat® Enterprise Linux®
Red Hat Certified Hardware Catalog
VMware® Infrastructure 3
Global Alliance Partner
Microsoft® Windows Server™ 2003
Microsoft Hardware Compatibility List
The Stratus ftServer family is based on industry-standard Intel processors and a choice of the Microsoft Windows 2003 operating system or Red Hat Enterprise Linux 4, along with many other standard hardware and software components. ftServer systems are listed on the Microsoft Hardware Compatibility List and Red Hat Certified Hardware Catalog, ensuring that all standard Windows and certified Red Hat Linux software will run flawlessly on all ftServer models.

3. Technology Partners Joint program to insure processor determinism
Stratus Confidential
Technology Partners
Joint program to insure processor determinism
Early access to new processors
ftServer® Series systems in Intel labs
Collaborate on OS availability features
Hardened drivers
Memory resynchronization
Support for mission-critical applications
Collaborative support model
ftServer systems in partner test labs
Reseller of CLARiiON® storage systems
ftServer Series systems in EMC Qualification lab
Collaborative support model

4. Continuous Availability – 99.999%
Stratus Confidential
Continuous Availability – %
Track record of success
Trusted availability partner for over 27 years to enterprises, government agencies and telecommunications service providers worldwide
Pioneer in continuous availability solutions
Clients in 70 countries on 6 continents
Global world-class expertise
Specialized availability experts
Unrivaled troubleshooting expertise

5. Stratus® ftServer® Family
Stratus Confidential
Stratus® ftServer® Family
2500 Family
4400 Family
6200 Family
Dual-core
Quad-core
Positioning
Highly affordable, entry-level, fault-tolerant server
Versatile, expandable Price/performance leader for applications that must not fail
Enterprise-class server delivering maximum performance & availability for mission-critical computing
Deployment Model
Replicated remote
locations
Departmental
business processing
Critical enterprise
business/operations processing
Workload
Standalone
Fixed configurations
Stable
Sophisticated SMB environments
General purpose
Growing or unpredictable
Transaction-intensive
Database server
Server consolidation
The current ftServer family consists of the entry-level 2500, the price/performance leading 4400 and the enterprise-class quad-core 6200.

6. ftServer® Architecture: Lockstep Technology
Stratus Confidential
ftServer® Architecture: Lockstep Technology
Duplex hardware components
Fault Detection
&
Isolation
Embedded I/O
PCI
Disks
CPU
Chipset
Memory
Fault Detection
&
Isolation
Lockstepped CPUs
Multi-path I/O
Fault Detection
&
Isolation
Embedded I/O
PCI
Disks
CPU
Chipset
Memory
Fault Detection
&
Isolation
Lockstep technology uses replicated, fault-tolerant hardware components that process the same instructions at the same time. In the event of a component malfunction, the partner component provides an active spare that continues normal operations and prevents system downtime. The system also eliminates transient hardware errors that, in-turn, could cause software failure.
ftServer systems use a standard DMR (Dual Modular Redundancy) configuration which includes two CPU/memory units.
The fault-tolerant I/O system is logically separated from the CPU-memory system. Hardware logic, in the form of custom ASICs, acts as a PCI bridge between the CPU and I/O, and also provides the core error detection, fault isolation and synchronization logic for the lockstep architecture. Fault-tolerant I/O is implemented using replicated PCI buses, replicated I/O adapters and replicated devices. Multiple paths are available to any logical I/O operation, including both internal and external storage operations. Any I/O operation failure will result in a retry using an alternate path ensuring successful completion of the I/O operation.
Eliminates single points of failure
Detects and isolates errors
Presents single software image
Delivers zero switchover time
4400
2500
6200

7. Stratus Lockstep Technology: Automatic Availability
Stratus Confidential
Stratus Lockstep Technology: Automatic Availability 
Redundant components execute same instructions in lockstep
Self-checking logic detects and isolates errors to the component level and notifies Stratus of problems
Stratus systems are designed to handle hardware problems automatically, with no failover delay or data loss. Lockstep technology uses replicated fault-tolerant hardware components that process the same instructions at the same time. Hardware logic, in the form of Stratus chipsets, provides the core error detection, fault isolation, and synchronization logic for the lockstep architecture.
Errors are detected and isolated to the component level and the system itself then notifies Stratus of any problems so that corrective action can be initiated immediately.
Stratus systems are also built to withstand unpredictable transient errors that can lead to system downtime or cause silent data corruption on conventional systems and clusters.
In the event of a component malfunction, the redundant component acts as an active spare that continues normal operation, thus averting system downtime.
While other servers may offer duplicated power supplies, fans, and disk drives, only Stratus provides protection for core system components including motherboards, processors, memory, I/O buses, and I/O adapters.
In-memory data is protected from hardware failures by the ftServer lockstep architecture which maintains at least two copies of all memory data.
System distinguishes between transient and hard errors; withstands transient errors
If hard error occurs, faulty component is taken out of service; duplicate component continues normal processing
In-memory data and disk data are protected

8. Failsafe ftServer® System Software
Stratus Confidential
Failsafe ftServer® System Software
Prevents, diagnoses, and resolves
software issues
Hardened drivers prevent software failures
ftServer hardware and software combine to shield operating system, middleware and application from the impact of transient errors
Software issues are reliably captured, analyzed and corrected
Extensive integration / error insertion testing
In-memory data and disk are protected
Failsafe software runs concurrently within the system to prevent many software errors and to capture, analyze, and correct other software issues that might disrupt processing. Even in-memory data is constantly protected and maintained.
Unlike standard servers or clusters, ftServer hardware and software handles many errors transparently, shielding errors from the operating system, middleware or application software, thus eliminating many potential software problems.
Stratus-supported device drivers include software extensions for full hot-plug operation, transparent failover, and added diagnostic and service capabilities, along with additional integration testing and reliability improvements. Stratus hardened drivers add considerable reliability to the Windows environment on ftServer systems.
Stratus uses a rigorous test process that targets fully-integrated systems including all hardware and software options in a variety of configurations including maximum configurations. Systems are tested under extreme processing and I/O loads and errors are continuously simulated during the test process. Finding and resolving these integration and error-insertion test issues results in a higher level of software reliability for ftServer systems.
ftServer management and diagnostic features ensure that software issues are reliably captured. With Stratus Assured Availability Plus Service, a user can count on Stratus to take responsibility for diagnosis and resolution of any system crash, including issues within the Window operating system.
In-memory data is protected from hardware failures by the ftServer lockstep architecture which maintains at least two copies of all memory data.

9. Stratus Failsafe Software: Automatic Availability
Stratus Confidential
Stratus Failsafe Software: Automatic Availability 
Reliably distinguishes software issues from hardware issues to speed problem resolution
Driver hardening ensures uninterrupted processing if an I/O interface fails
Rapid disk resynchronization transparently mirrors disks and protects data integrity
Accurate error data capture enables root-cause analysis to prevent problem recurrence
Management and diagnostic features also capture, analyze and notify Stratus of software issues.
Unlike standard servers or clusters, ftServer Series hardware and software combine to handle many errors transparently, shielding the operating system, middleware and application software, thus eliminating many potential software problems.
Stratus-supported device drivers include software extensions for full hot-plug operation, transparent failover, and added diagnostic and service capabilities, along with additional integration testing and reliability improvements. Stratus hardened drivers add considerable reliability to the operating system on ftServer Series systems.
Stratus uses a rigorous test process that targets fully-integrated systems including all hardware and software options in a variety of configurations including maximum configurations. Systems are tested under extreme processing and I/O loads and errors are continuously simulated during the test process. Finding and resolving these integration and error-insertion test issues results in a higher level of software reliability for ftServer systems.
RDR continually monitors the integrity of the RDR-enabled disks, scouting for bad blocks. RDR then fixes bad disk blocks, and copies the correct data from the partner. This online bad block correction maintains data integrity and system availability, key components to the mission-critical functions of Stratus’ ftServer systems.
ftServer Series management and diagnostic features ensure that software issues are reliably captured. With Stratus Assured Availability Plus Service, a user can count on Stratus to take responsibility for diagnosis and resolution of any system crash, including issues within the operating systems.

10. ActiveService™ Architecture: Automatic Availability
Stratus Confidential
ActiveService™ Architecture: Automatic Availability
Component fails. System ISOLATES fault and notifies Stratus that a CPU has failed
System automatically orders
CORRECT replacement part
Next Day
Delivery Service
Hot-pluggable components are EASY to replace
The ActiveService Architecture has its foundation in the design of the hardware and its technology-enabled Access features.
The system's self-monitoring and diagnostics features are capable of correctly identifying the specific hardware or software component that causes an abnormal condition. The elimination of guesswork and trial-and error-part swapping clearly sets ftServer systems apart from alternative high-availability solutions.
In the event of component failure, the system automatically opens a call with the Stratus Customer Assistance Center that supplies information on exactly what action is needed.
Most replacement components arrive within 24 hours. .
The hot-pluggable components are easy to replace by users without special tools, commands or a visit from a field engineer. Once in place, the new component is automatically integrated into the running system.
Throughout this entire process, you system and application will continue to run normally.
System synchronizes with replacement component
Normal processing continues throughout process!

11. ftServer® Family User Benefits
Stratus Confidential
ftServer® Family User Benefits
Continuous
Availability
Operational Simplicity
Financial Advantage
> % uptime for a suite of enterprise Operating Systems
Operating System availability enhancements
Space-efficient fault-tolerant design
Quick to deploy
Simple to operate
Easy to maintain
Technology-enabled services
Low TCO
Cuts cost of downtime
Minimizes business disruption
Better resource utilization
With the ftServer family, Status provides a practical and affordable way to achieve the highest levels of availability for Microsoft Windows and Red Hat Enterprise Linux environments.
Our ftServer line delivers Continuous Processing through Stratus’ lockstep technology, failsafe software, and the ActiveService Architecture. These key features automatically work together to prevent downtime in the easiest way possible.
Our newest generation of systems expands on these inherent strengths with superior price-performance, greater space efficiency, and simpler serviceability.
Stratus' Smarter Approach to Uptime also rewards users with a tangible financial advantage over competing approaches. This superior technology reduces the costs associated with complicated deployment, unplanned downtime, and ongoing support expenses.

12. Operational Simplicity
Stratus Confidential
Operational Simplicity
Designed for the most demanding local, remote, and lights-out computing environments
Stratus industry-standard
platforms are as easy to install, use, and maintain as conventional servers
Day in and day out, organizations deal with the reality that neither their in-house IT staff nor vendor service professionals will be close at hand to every site or able to respond quickly to every situation.
This includes centralized computing operations where IT resources are becoming more and more constrained, remote sites where there may not be immediate access to engineers or parts, as well as lights out environments where IT resources may be non-existent.
We respond to these needs with systems that have proactive remote service capabilities and are easy to install, use and maintain.

13. Stratus Confidential
Easy to Install 
Rapid deployment: applications typically up and running in less than a day
Single system; single software licenses
Customer Response
“I like the Stratus ftServer system because of its simplicity. With clustering, the typical approach to high availability, comes other issues including complex configuration and management, as well as software compatibility.” Vaughn Book, Senior Vice President and Chief Technology Officer Arrowhead Credit Union
Because fault-tolerant ftServer systems supply uptime protection automatically, without added effort, they eliminate the time consuming and people-intensive work needed to implement high-availability clusters. Applications running on an ftServer system are unaware of any unique hardware or software elements of the ftServer architecture.
Typically, an ftServer Series system can be installed - with the application loaded and ready for operation in less than a day.
By contrast, applications should be modified to use cluster APIs in order to operate optimally in a cluster environment.

14.  Easy to Use Streamlines day-to-day operations Customer Response
Stratus Confidential
Easy to Use 
Streamlines day-to-day operations
Minimal operator intervention required
No need to think about failure scenarios
Remote monitoring, physical indicators; and hot-pluggable components simplify serviceability
Reduces workload of IT support staff; enables redeployment of scarce resources
Customer Response
“One of the reasons for a change to the ftServer system was to increase operational simplicity. Considering the limited size of our IT team, the easy management of the new server will also allow us to save a lot of costly human effort." Diego Bertazzi, Operations Manager Information Technology Group, Casino de la Vallee
ftServer systems effectively streamline your day-to-day operations.
We've significantly eliminated operator intervention for routine management or when a hardware failure occurs because the system is designed to handle and report problems without disrupting your normal computing operations. And, there is no need to even think about failure scenarios or rewrite scripts which can change any time you make changes in your computing environment.
A problem on other systems also means your staff must spend precious time finding the problem first and then figure out the best way to fix it. Our remote monitoring and 24 x 7 diagnostics means we often know about potential problems before you do! Customers often tell us that the first time they are aware of any issues is when they receive a call from us telling them exactly what problem has occurred along with the recommended remedial action.
When necessary, our service personnel can also dial into your Stratus system, regardless of where it is located, and take corrective action (even if it is offline). In fact, more than 95% of the time issues are resolved remotely.
Should a replacement part be necessary, the system's colored status LEDs indicate exactly what component is affected. Our components are designed to be customer-replaceable.

15.  Easy to Maintain Integrates with standard management tools,
Stratus Confidential
Easy to Maintain 
Integrates with standard management tools,
existing staff skills, operational procedures
Managed as a single, industry-standard server
Customer Response
“Because the ftServer system runs in a Windows environment, we are able to leverage technical expertise that's plentiful throughout our staff. This is a big change from the special knowledge needed to work with the ATM/EFT controller that we replaced." Gomer Jones, Senior Vice President Texas State Bank
ftServer Series systems are administered as single systems. Your organization can use standard management tools and procedures.
And, you save even more on operational costs because you can leverage existing skills and staff training.
In contract, managing clusters involves special skills as well as additional configuration and management procedures beyond those needed to manage standard servers.

16. Immediate Application Availability
Stratus Confidential
Immediate Application Availability 
Application transparency
Applications load and go
Instant fault-tolerance
Customer Response
“Standard Windows server-based applications run without a problem, operating transparently on the fault-tolerant platform."
The Stratus approach to applications availability is both automatic and transparent.
The ftServer Series family meets qualification for the Microsoft Hardware Compatibility List (HCL), VMware HCL Systems Compatibility Guide, and Red Hat Certified Hardware Catalog. This is your assurance that standard compatible software will run flawlessly on ftServer Series models without ANY modification.
You simply power up the server and load your application to benefit from our Continuous Processing technology.
This immediate access to application availability is another clear advantage that Stratus servers offer compared with clusters, which recommend (and in some cases require) that applications be modified for cluster operation. In addition, the loss of memory and application state during a cluster failover often dictates design changes within the application to prevent unacceptable data loss.

17. Remote Problem Resolution that Goes Beyond the Hardware
Stratus Confidential
Remote Problem Resolution that Goes Beyond the Hardware
When You call ...
... an availability expert answers.
The types of problems we resolve daily
Operating system
Network
Database
Multi-vendor issues
Hardware
Application
Patches
Security
Hot fixes
Stratus ActiveService Network is a secure, fault-tolerant worldwide network that enables instantaneous, around-the-clock monitoring and troubleshooting of systems regardless of physical locations.
The Stratus Customer Assistance Center (CAC) provides the critical support necessary to ensure continuous operation. At Stratus 24x7 support is the norm, not the exception. And whenever you call, an availability expert is there to help you immediately.
The server's remote support capabilities – made possible by Stratus out-of-band management technology and our global ActiveService Network – also enable service engineers to diagnose, troubleshoot, and resolve problems online as if they were on-site.
Running on independent power and network connections, the out-of-band management device allows remote communication to take place between Stratus’ ActiveService Network and the customer’s module — regardless of the system’s state. This allows a service engineer to remotely power on/off or reset/ reboot the system and manages the security of incoming and outgoing communications through the ActiveService Network.
But, we don't limit ourselves to solving Stratus server problems. Our customers consistently credit us with understanding availability at every level -- from the server to the operating system to the network to the ongoing managed services needed to maintain optimal performance.
Customer Response
“You need immediate help when you have a 911 systems issue, and Stratus understands that. Your call doesn't go into a phone tree. You speak to a problem-solver right away." Douglas Bolton, Information Systems Analyst
San Diego Fire & Life Safety Services

18. Select the Support Offering that Matches your requirements
Stratus Confidential
Select the Support Offering that Matches your requirements
Service
Tier
Offering
Your Business Environment
Stratus Value Add
Assured
Availability
Plus
Extremely risk adverse
High cost of downtime
Mission-critical applications
Require highest level of 24/7 support
Immediate response from an expert
Single point of contact
Priority issue escalation
Root-cause analysis and permanent fix
Availability partnership
Premium operating system services
Availability program guarantee
System
Traditional service levels are adequate
Competitive with traditional vendors break/fix services
Premium
Stratus offers two tiers of service offerings Premium” and “Basic”
Premium support service customer business concerns include:
• Extremely risk adverse
• High cost of downtime
• Mission-critical applications
• Require the highest level of 24/7 support
Premium Value-added service components include:
An immediate response from an expert
Single point of contact when they have a serious/critical problem
Priority management issue escalation
Root cause and permanent fix
Manage OS kernel issues directly with Microsoft or Red Hat
Availability partnership (take ownership even when vendor ownership is not immediately clear
Assured Availability Program Guarantee
Basic maintenance customer business concerns include:
• Initial acquisition cost
• Traditional service levels are adequate
Basic maintenance customer service components include:
Be competitive with traditional vendor break/fix services
Basic

19. Availability Alternatives
Stratus Confidential
Availability Alternatives
Standalone Systems
some duplicate components
Clustered Systems
ftServer Systems
Reduce failure
Recover from failure
Prevent failure
Cost of downtime negates advantage of low purchase price
Unpredictable availability - varies by vendor / model
When it fails, it fails hard
Success depends on correct planning and implementation
Satisfactory operation highly dependent on skilled personnel
Lockstep technology, failsafe software, and ActiveService™ architecture provide continuous availability
No special skills required to implement and manage
Some of today's servers offer subsets of availability features in the form of duplicated components but these vary greatly by vendor and model. The notion is to reduce the probability of failure - but when a standalone server fails, it fails. Such servers aren't designed to prevent downtime or data loss, nor are they able to recover quickly from problems.
Clusters are built by assembling hardware and software from multiple vendors. Physical connections and software programs link two or more servers so that when a failure occurs on one, its workload fails over to a server that is still operating. These configurations are described as high availability because they speed recovery from problems. They are not, however, designed to eliminate downtime altogether. They are also complex to build and maintain and require highly skilled staff throughout the lifecycle of the system. Whenever changes are made to hardware or software, its failover capabilities (software scripts) must be updated and retested to make sure that failover will work as planned.
Stratus fault-tolerant ftServer systems provide continuous uptime because they are designed to prevent downtime from ever occurring. Normal processing continues without transaction or data loss should component failures or software faults that generally cause other servers to fail occurs.
These systems give you the best of all worlds. Operationally they are comparable to a standalone system. They protect applications as well or better than clusters and standalone systems and from a technology availability standpoint they are superior to either alternative.
We’ve graphically displayed how each effective each alternative is at addressing Gartner Group’s mix of the causes of unplanned downtime. We believe that the ftServer scores highest in all three categories for the following reasons::
-Technology Failures. The combination of lockstepped CPUs, redundant components, ability to detect and ride thru transient errors, Fail Safe software, and the insertion detection process used in the development of the system delivers the.
-2- Application Failure. Many failures blamed on the OS or application are actually transient hardware problems that the ftServer will ride thru. Also, OS and applications are deployed with no modification further decreasing the likelihood of problems.
-3- Operations Errors. The complexity of clusters demands expert-level administration and management. Conversely, the ftServer can be managed without specialized training.
Operations
Application
Technology
Effectiveness at addressing downtime

20. Value Comparison Features ftServer® System >99.999%
Stratus Confidential
Value Comparison
Features
ftServer® System >99.999%
>Clusters 99.9%
System
Architecture
Lockstep Technology
Zero failover time
Failure prevention
Minutes of failover
Failure recovery
Resource
Protection
Failsafe Software
Protects memory & disk data
Shields SW from transient HW errors
Protects ONLY disk data
HW errors cause OS and application failures
Service technology
ActiveService™ Architecture
Fault detection and isolation Hot-swappable components
Built-in serviceability
Limited self diagnostics
Limited hot-swappability
Add-on serviceability
Deployment
Immediate
Script development/testing
Application Modification
None
Recommended
Operation
Single system image
Lights out operation
Multiple system images
Requires IS Support
Continuous
Availability
Operational
Simplicity
Financial Advantage
The recovery time comparison assumes hardware failure. For a software failure, both ftServer and a cluster will recover in minutes (ftServer reboots while a cluster fails over).
A cluster failover always loses all memory contents, while ftServer preserves all memory contents in the event of a hardware failover, and preserves data in the event of a system software failure. Applications can take advantage of memory persistence to both improve performance and reduce complexity.
It is recommended that applications be modified to work best in a cluster environment, although this is not an absolute requirement.

21. Ease of Implementation: Availability Alternatives Comparison
Stratus Confidential
Ease of Implementation: Availability Alternatives Comparison
Implementation Process
Standalone
some duplicate components
Clustered
systems
ftServer
system
Planning and design
None
Extensive
Addresses single points of failure
Extra work required
Yes; it's built-in
Sizing / load balancing
Nodes must be properly sized for adequate performance
Application modification
Highly recommended to ensure failover, SW compatibility, data integrity
Develop and test failover scripts No
Yes; must repeat with each change
Test for effectiveness
Yes
Document procedures
Extensive documentation
The Stratus ftServer and competitive standalone servers compare almost identically when it comes to ease of implementation. Essentially, it’s “load and go”. The main difference of course, is that the level of availability (99.999% and greater) delivered by ftServer systems.
Ease of implementation has been, and continues to be one of the major drawbacks to high availability clusters. Customers who choose to implement a cluster should be aware of the amount of effort and time it takes to properly plan and test the solution before implementation can occur. Even after the cluster is deployed, the work isn’t over. In fact, it never ends because every time a change is made to the configuration, the cluster needs to be tested to insure proper failover will occur.

22. Problem Handling Effectiveness: Availability Alternatives Comparison
Stratus Confidential
Problem Handling Effectiveness: Availability Alternatives Comparison
Problem Handling Features
Standalone
some duplicate components
Clustered
systems
ftServer
system
Recovery time
from failure
Minutes to days
Minutes to hours
Zero
In-flight data
All lost on failure
All lost on failover
No data loss
Fault detection and isolation
Limited
Yes, to the component level
Transient errors
May cause failure; lead to silent data corruption
Withstands transient errors; no data corruption
Hard errors
Varies by HW configuration; possible failure
System failover
System continues normal processing
Integrity of database transactions
Varies by HW configuration
Yes
Driver hardening No
While the availability characteristics of standalone servers are – as a rule –increasing, they are still extremely vulnerable to catastrophic hardware crashes. Depending upon configuration, failures to components including processors, memory, disks and their controllers, voltage regulators, power supplies, and fans can all result in an outage. And, depending on the type of failure, a standalone server can be offline until the service provider arrives hours or even days later (hopefully with the right replacement part).
High availability clusters – if implemented and managed correctly – will deliver a higher level of availability than a standalone server. (Think of this increase in availability as a reward for all of the effort that goes into the set up and care-taking of the cluster).
However, even with expert setup and management, the best a cluster can hope for is “speedy” recovery from a failure. When a failure does occur, any in-memory data that was being worked on is lost and the amount of time that the application is unavailable is highly dependent on such things as the time it takes to recognize that the failure has occurred, the time it takes to fail over to an available server and the time associated with database and application recovery.
Both standalone servers and clusters are also susceptible to problems caused by transient errors and misbehaved drivers.

23. Solutions Management: Availability Alternatives Comparison
Stratus Confidential
Solutions Management: Availability Alternatives Comparison
On-going Management
Standalone
some duplicate components
Clustered
systems
ftServer
system
Server platform
Single system view;
no special skills
Complex; requires specialized personnel
Single system view; no special skills
Failover testing when changes are made No
Required
System monitoring, reporting, diagnostics
Varies by vendor and platform
Integrated 24 x 7 system monitoring, status reporting tied to ActiveService Network
Remote problem identification / repair
Limited. Varies by vendor and platform
Yes: even when server is offline
Memory data capture in event of OS outage
Yes, default feature; does not delay application restart
Change management
Changes easily tracked
Complex documentation
A particular strength of the ftServer is the ease with which the system can be managed on a daily basis and repaired when a problem does occur. The ftServer appears to the administrator as a single system and requires no special testing or change management procedures thereby greatly reducing the likelihood of administrative errors.
Because the ftServer’s ActiveService Architecture is engineered into the systems’ design – not added on as an afterthought –problems are instantly identified and reported and problem resolution can commence immediately. While competitors offer “phone home” technology to identify certain classes of problems, none can match Stratus’ ability to diagnose, root-cause, and remedy most problems remotely.
Stratus value-add features include the ability to capture the contents of memory after a failure occurs while simultaneously bringing the system back online. Competitive servers are faced with a choice of either bringing the system back online or delaying the system restart in order to harvest the contents of memory in order to analyze the cause of the failure.

24. Managing Planned Downtime (Windows® only)
Stratus Confidential
Managing Planned Downtime (Windows® only)
Challenges
Availability
risk
Ease of use
Minimize downtime
Clusters
Prone to synchronization and recovery issues _
Cluster expertise required
Minimal (1 to 3 short duration) outages 
Stratus Active Upgrade™
Automatic synchronization between production and update
System can be restored to its original state at any time
Automatic pre-upgrade readiness check
Single OS and Single Application
Intuitive user-interface guides you through every step
No Application modification
Single Application outage
Upgrade completed in seconds  
Prior to Active Upgrade, the only option for minimizing planned downtime was cluster rolling upgrades, where one node of the cluster is updated while all users are connected to the other node. While this does accomplish the task of minimizing downtime, it is challenging to insure both systems are the correct configurations, and perhaps more daunting is the recovery required if an issue is encountered during the update. This often requires multiple restores and application check pointing before starting all over again .
In contrast, Active Upgrade automatically insures that production and update versions are the same. In addition, if issues are encountered during the update, the system may be returned to its original state by the press of a button with no downtime at any step of the upgrade.
From a simplicity standpoint, Active Upgrade requires only a single upgrade to the Operating or application, since there is only one copy of the ftServer, Operating System, and application. Unlike clusters, which may require application modifications to make them cluster aware so that they operate properly in a rolling upgrade, applications may operate on a system with the Operating System or application being upgraded by Active Upgrade with no modification whatsoever.
Last but not least, Active Upgrade requires only a single application outage while clusters may require as many as 3 depending on the cluster type (Active-Active or Active-Passive). 

25. Cluster Customer Experience
Stratus Confidential
Cluster Customer Experience
Implementation Process
Failure Recovery
Process
Requires
specialized skills:
Planning
Designing
Building
Scripting
Configuring
Measuring
Testing
Process must repeated with each change!
Notify service provider
Wait for arrival
Problem analysis
Replace failed component
Reboot OS
Recover file system
Recover database
Restart network software
Restart application
Time-consuming, labor-intensive

26. Stratus Customer Experience
Stratus Confidential
Stratus Customer Experience
Automatic Availability
Implementation Process
Failure Prevention
Stratus Continuous Processing® technology prevents failures from occurring
24 x 7 monitoring and reporting integrated into every system
Root-cause analysis to prevent problem recurrance
Load-and-go deployment
Maximizes existing IT skills

27. ftServer® Product Specifications
Stratus Confidential
ftServer® Product Specifications
ftServer 2500 system
ftServer system
ftServer 6200
system
Processors
1-socket
1- and 2-socket
2-socket
CPU/FSB
Frequency
Dual-core 2 GHz CPU
1333 MHz FSB
Quad-core 2.66 GHz CPU
CPU Cache
4MB L2
4MB L2
2 x 4MB L2
Memory
2GB–6GB DDR667 FBDIMM
2GB–12GB DDR667 FBDIMM
4GB–24GB DDR667 FBDIMM
PCI Slots
6 x PCI-X, or 4 x PCI-X and 2 x PCIe
RAID 1 Disk
3 Enterprise SAS or SATA Disks
Embedded
SAS, 2x ENET (10/100/1000) ,
3x USB2.0, 2x COMM, VGA, BMC, R/W DVD
Operating Systems
Windows® Server 2003 Standard Edition or Red Hat® Enterprise Linux®
Windows® Server 2003 Enterprise Edition VMware ® Virtual Infrastructure 3
Red Hat® Enterprise Linux®
Form Factor
4U Rack and Pedestal
4U Rack
Note: All I/O options specified in logical count, physical count is 2 times numbers specified

28. Building Blocks of the ftServer® Family
Stratus Confidential
Building Blocks of the ftServer® Family
2500
4400
6200
CPU / IO CRU
Blindmate Backplane
The ftServer family is based upon modular building blocks which are combined to build a fault-tolerant platform. The CPU/IO are rack-optimized CRU’s that are paired for fault-tolerance and inserted in a blindmate backplane.

29. ftServer® Modular Family Components
Stratus Confidential
ftServer® Modular Family Components
CPU/IO
2U Blindmate Enclosure, front removable
1 or 2-socket CPU
6 DIMM Slots
1333 MHz Front Side Bus
4 GHz Memory Bus
Up to 3 Hot plug, SAS or SATA Drives, front removable
Power On button, front accessible & protected
6 Customer Configurable PCI-X/PCI-Express slots, rear accessible
2 10/100/1000 Com port, rear accessible
The CPU-I/O is the main a module in all ftServer systems. Each CPU-I/O contains the equivalent of a single server including disk, PCI slots, memory, and processor(s), as well as integrated USB, SCSI, Serial, and Ethernet in a 1U form-factor.
The CPU-I/O contains a variety of LED’s that provide the status of the CPU-I/O status, disk activity and status, PCI slots status, system management status, and Ethernet status, activity, and speed

30. ftServer® Modular Family Components
Stratus Confidential
ftServer® Modular Family Components
Passive
Backplane
Passive backplane for seamless component interconnect
Blind mates power and signal to CRU’s
Standard 19” EIA compatible
Adjustable rail – fits cabinet depth range 24” to 30”
Shared connectors located in rear
The blindmate backplane is a single unit into which the CPU-I/O units plug. While configuring a typical cluster may require configuring a myriad of data, heartbeat, and power cables; the ftServer interconnect is achieved by simply sliding in the CRU into the VHDM (Very High Density Metric) connection on the backplane. The backplane provides power and signals (data, clock, system management) to each CRU. In addition to the clock card the backplane contains an IO-Card containing the ports for the embedded Ethernet, USB, Serial, and VGA.
The fact that the backplane is passive versus active dramatically improves the MTBF.
The backplane mounts in a standard 19” rack and its sliding rails support virtually any rack depth.

31. ftServer® 2500 Systems Workloads and Attributes Specifications
Stratus Confidential
ftServer® 2500 Systems
Workloads and Attributes
Highly affordable fault-tolerance
Easy to deploy and simple to manage
Ideal for replicated deployment at remote locations
Entry-level
1-socket server
Specifications
4U rack-optimized form factor
Pedestal option
1-way CPU
2.0 GHz dual-core Intel® Xeon™ processor with 4MB cache
Dual modular redundancy
SAS/SATA storage supporting 6 internal disks
Optional external JBOD or RAID (Windows only)
2GB – 6GB memory
6 PCI-X slots, or 4 PCI-X and 2 PCI-Express slots
Integrated 10/100/1000 Ethernet
Windows® 2003 Standard Edition or
Red Hat Enterprise Linux

32. ftServer® 4400 Systems Workloads and Attributes Specifications
Stratus Confidential
ftServer® 4400 Systems
Workloads and Attributes
Price / performance leader
Dedicated business processing application server
Ideal for departmental business processing; ideal for space-constrained data centers
Mid-range
1- or 2-socket system
Specifications
4U rack-optimized form factor
Pedestal option
2.0 GHz dual-core Intel® Xeon™ processor with 4MB cache
Dual modular redundancy
2GB – 12GB memory
SAS/SATA, storage supporting 6 internal disks
Optional EMC (Windows/VMware only) or ftScalable Storage
6 PCI-X slots, or 4 PCI-X and 2 PCI-Express slots
Integrated dual 10/100/1000 Ethernet
Windows® 2003 Enterprise Edition VMware® Infrastructure Red Hat® Enterprise Linux®

33. ftServer® 6200 Systems Workloads and Attributes Specifications
Stratus Confidential
ftServer® 6200 Systems
Workloads and Attributes
Enterprise-class, quad-core system for transaction-intensive workloads
Top-of-the-line 2-socket server
Specifications
4U rack-optimized form factor
Quad-core 2-way SMP
2.66 GHz dual-core Intel® Xeon™ processor with 2 x 4MB cache
Dual modular redundancy
4GB – 24GB memory
SAS/SATA, storage supporting 6 internal disks
Optional EMC (Windows/VMware only) or ftScalable Storage
6 PCI-X slots, or 4 PCI-X and 2 PCI-Express slots
Integrated dual 10/100/1000 Ethernet
Windows® 2003 Enterprise Edition VMware® Infrastructure Red Hat® Enterprise Linux®

34. Storage Options Fault-tolerant protection of critical data Internal
Stratus Confidential
Storage Options
Fault-tolerant protection of critical data
Internal
Software-based RAID 1 and 1+0; 6 disk capacity
SAS/SATA
73 GB, 146 GB 15K RPM SAS
250 GB, 500 GB 7200 RPM SATA
3.0 TB
ftScalable Storage
Hardware RAID
Fibre Channel (Direct or SAN attach)
27 TB
Stratus’ storage portfolio is designed to protect customer’s crucial data while complementing our fault-tolerant server architecture. Whether customers need to optimize the availability of their critical information, improve their storage utilization, protect information from disaster or reduce costs through simplicity, Stratus offers world-class storage options to meet any need. Stratus delivers the reliability and capability customers demand for their data storage environments.
This slide depicts the range of capability offered for Stratus ftServer systems, from simple internal disks to an external fault-tolerant storage subsystem ..
The internal ftServer storage subsystem supports 2, 4, or 6 or SAS or SATA hot-pluggable disk drives.
The ftScalable Storage subsystem is designed to address the cost-sensitive, entry-level and mid-range data storage market segments while offering enterprise-class product attributes.
Stratus Hardware Assisted Software Mirrors (HASM)
HASM provides RAID Level 1 functionality through software, but exploits the Stratus ftServer system design to deliver maximum availability. HASM uses the fully redundant components within the Stratus system – controllers, busses, power supplies, additional error checking on all operations, hot-swap, SSN remote management - as well as the Stratus hardened device driver/SCSI Disk controller combination to ensure that the maximum amount of work is off-loaded from the main system to maximize overall performance.
Stratus ftServers running the Windows Operating System can connect with our EMC attachment kit to either the EMC Symmetrix or CLARiiON family of products. This provides fibre channel connected hardware based RAID capability with comprehensive failover and management software capabilities.

35. ftScaleable Storage: Feature Set
Stratus Confidential
ftScaleable Storage: Feature Set
Availability
Redundant, hot-plug
Active-Active controllers
Rolling firmware upgrades
EnviroStor™ Battery-free cache protection
ASN Integration
Snapshots
Hot spares
Performance
15K RPM SAS
DupliCache: Patented redundant cache optimization
Switched drive topology
Capacity
Dynamic expansion: up to 3 shelves
27TB maximum
Dedicated, dual-host DAS, and SAN topologies

36. Stratus Tape Backup Family
Stratus Confidential
Stratus Tape Backup Family
VS160 Tape
80GB/160GB native/compressed capacity
8MBps/16MBps native/compressed data-transfer rates
External 1U rack-mount enclosure with single or dual tape drives available
Output read-compatible with SDLT600
Available as standalone tape or with autoloader
All ftServer platforms can connect to an external VS160 drive, either as a rack-mountable standalone unit or as an autoloader with a capacity of up to 16 cartridges.