Compaq ProLiant 1200 White Paper Download Page 13

Architecting and Deploying High-Availability Solutions

13

ECG064/1198

Study your needs

As we have discussed in this paper, architecting a high-availability environment requires a methodical
approach beginning with an understanding of your needs. The definition of your needs includes the cost of
downtime to your organization and your requirements in terms of Recovery Point and Recovery Time.
Consider also the ramifications of managing your high-availability environment in a multi-year time frame.

Identify the right compromise

What is the opportunity cost of downtime versus the price of the solution over the life of the system?
Should you spend less now for a short term fix or make the major investment that will carry you well into
the future?

Architect the right compromise

Once a balance has been struck among the issues described above, the next task is to turn that compromise
into a design with the appropriate weight given to the individual availability technologies.

Commit to a given result

With design in hand, an organization must commit itself to carrying through on the plan whose end result is
nothing less than the level of availability deemed necessary. This requires some degree of systems
engineering – solutions modeling, characterization, proof of concept.

Deliver to spec

At this point, the vendor or vendors supplying the components of the availability solution must be equally
committed to the end result. A vendor with strong internal technical project management and quality
control is essential in this endeavor.

Verify in the factory

Don’t wait until the solution is delivered to your site and installed to see if it works. A competent solutions
provider will have the capability to factory pre-stage, integrate, and test the complete solution.

Start up on site

If the solution has been factory integrated and tested in a tightly controlled technical environment the on-
site start-up should be a low-risk and non-disruptive exercise that accelerates the pace of implementation.

Manage for the long term

After implementation, the challenge is to maintain the level of availability originally architected. This is
accomplished through a program of consistent internal controls and long-term relationships with support
and service providers.

Study
Your
Needs

Identify the
Right
Compromise

Manage
for the
long term

Start up
on site

Architect the
Right
Compromise

Commit to
a Given
Result

Verify in the
Factory

Deliver
to Spec

Summary of Contents for ProLiant 1200

Page 1: ...9 Deployment Options 10 Service and Support Options 10 Putting it all Together 12 List of Sales Offices 14 Architecting and Deploying High Availability Solutions Abstract The demand for high availabi...

Page 2: ...respective companies Compaq Contura Deskpro Fastart Compaq Insight Manager LTE PageMarq Systempro Systempro LT ProLiant TwinTray ROMPaq LicensePaq QVision SLT ProLinea SmartStart NetFlex DirectPlus Qu...

Page 3: ...n which the success of an organization depends and the loss of which results in unacceptable functional or financial harm Mean Time Between Failure MTBF a statistically derived length of time a user m...

Page 4: ...In order to measure the impact of downtime let s ask a basic question that helps quantify the level of availability you might need Who and what gets hurt when a system goes down Processes Vital busin...

Page 5: ...down during those few weeks or months Each type of availability may demand very different requirements The first thing to keep in mind though is that defining availability depends on your needs in te...

Page 6: ...es Downtime After looking at your information systems the user community and the cost of downtime you can determine the level of availability you need Now it is time to focus on the events that can ha...

Page 7: ...is whole system What happens if you are no longer able to deal with intrusions How can you easily or at least with minimum disruption upgrade expand or tune your system to ensure that your enterprise...

Page 8: ...ata and applications is key to any recovery situation After all physical storage devices are electromechanical and that in itself makes them more failure prone than other elements in the environment D...

Page 9: ...including processor expansion memory primary and secondary storage power cooling and management 6 Architecting High Availability Systems Analyzing and defining the requirements for a high availability...

Page 10: ...gineering and testing principles employed by Compaq deliver a reassuring measure of certainty that your systems will work reliably in the real world and meet your definition of mission critical For ex...

Page 11: ...ability Review offers unique value through a combination of expertise innovative tools and experience that produces a proactive solution for high availability needs Compaq availability consultants tra...

Page 12: ...Solutions start with comprehensive planning Information gathered in the planning phase helps you identify and prioritize the areas of your business that would require the fastest recovery You then se...

Page 13: ...ess than the level of availability deemed necessary This requires some degree of systems engineering solutions modeling characterization proof of concept Deliver to spec At this point the vendor or ve...

Page 14: ...All other countries 954 360 6470 On the web at www compaq com customsystems In Europe the Middle East Africa Country City Region Belgium 32 2 729 71 49 Denmark 45 45 17 23 16 France 33 4 50 09 41 14 G...

Reviews: