Compaq ProLiant 1000 Guide de référence rapide

White Paper

Help us improve our technical communication. Let us know what you think

about the technical information in this document. Your feedback is valuable

and will help us structure future communications. Please send your

comments to: [email protected]

October 1998

ECG064/1198

Prepared by CustomSystems

Enterprise High Availability

Segment

Compaq Computer Corporation

Contents

Introduction 3

Determining Availability

Requirements 3

What is the Cost of Downtime? 4

Recovery Point and Recovery

Time 5

What Causes Downtime? 6

Vulnerable Technologies 7

Availability Technologies 8

Architecting High-Availability

Systems 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 availability is growing. Long required for

mission-critical applications in industries such as finance, process

manufacturing, and telecommunications, high availability today is fast

becoming a requirement in many other industries as well.

This white paper provides an overview of the combination of factors that

defines high-availability computing requirements. It describes

methodologies that can assist you in architecting and deploying the right

level of availability across your information-technology environment. And

it describes how Compaq can assist organizations of any size in achieving

their high-availability computing goals.

Architecting and Deploying High-Availability Solutions 2

ECG064/1198

Notice

The information in this publication is subject to change without notice and is provided “AS IS” WITHOUT

WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS

INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR

ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE OR OTHER DAMAGES

WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS

PROFITS, BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION), EVEN IF

COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The limited warranties for Compaq products are exclusively set forth in the documentation accompanying

such products. Nothing herein should be construed as constituting a further or additional warranty.

This publication does not constitute an endorsement of the product or products that were tested. The

configuration or configurations tested or described may or may not be the only available solution. This test

is not a determination or product quality or correctness, nor does it ensure compliance with any federal

state or local requirements.

Product names mentioned herein may be trademarks and/or registered trademarks of their respective

companies.

Compaq, Contura, Deskpro, Fastart, Compaq Insight Manager, LTE, PageMarq, Systempro, Systempro/LT,

ProLiant, TwinTray, ROMPaq, LicensePaq, QVision, SLT, ProLinea, SmartStart, NetFlex, DirectPlus,

QuickFind, RemotePaq, BackPaq, TechPaq, SpeedPaq, QuickBack, PaqFax, Presario, SilentCool,

CompaqCare (design), Aero, SmartStation, MiniStation, and PaqRap, registered United States Patent and

Trademark Office.

Netelligent, Armada, Cruiser, Concerto, QuickChoice, ProSignia, Systempro/XL, Net1, LTE Elite,

Vocalyst, PageMate, SoftPaq, FirstPaq, SolutionPaq, EasyPoint, EZ Help, MaxLight, MultiLock,

QuickBlank, QuickLock, UltraView, Innovate logo, Wonder Tools logo in black/white and color, and

Compaq PC Card Solution logo are trademarks and/or service marks of Compaq Computer Corporation.

Microsoft, Windows, Windows NT, Windows NT Server and Workstation, Microsoft SQL Server for

Windows NT are trademarks and/or registered trademarks of Microsoft Corporation.

NetWare and Novell are registered trademarks and intraNetWare, NDS, and Novell Directory Services are

trademarks of Novell, Inc.

DIGITAL and OpenVMS are trademarks of Digital Equipment Corporation.

Pentium and Intel are registered trademarks of Intel Corporation.

Architecting and Deploying High-Availability Solutions

White Paper prepared by CustomSystems Enterprise High Availability Segment

First Edition (October 1998)

Architecting and Deploying High-Availability Solutions 3

ECG064/1198

Introduction

When the systems that run your organization1are down the costs can be devastating. Lost opportunities.

Lost revenues. Failure-to-perform fees. Non-compliance penalties. Plus stranded fixed costs you have to

keep on paying whether your people are productive or not.

Potentially more damaging is a nearly incalculable loss: the loss of good will. Customers, partners, and

suppliers affected by system shutdowns perceive your organization as poorly run and ill-suited to meeting

their needs.

Thus, the starting point for any discussion of availability has to be the cost of information system downtime

to your organization. The higher the cost of downtime, the more robust the availability environment needs

to be. And the more successful your environment is in delivering the level of availability required by the

organization, the faster the return on your investment.

The purpose of this white paper is to provide an overview of the factors that – taken together – define your

availability needs and how Compaq Computer Corporation can meet them.

Definitions

Before proceeding with a discussion of high availability, it is helpful to define a few terms.

Availability: The ratio of the total time a functional unit is capable of being used during a given interval to

the length of that interval. It is the proportion of time a system is productive which implies performance.

Mission Critical: A term applied to information systems upon 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 may reasonably expect a

component, device, or system to work between two incapacitating failures.

Reliability: A measure of how dependable a system is once you actually use it. Reliability can also be

considered the sum of availability and data integrity.

Determining Availability Requirements

Determining an organization’s availability requirements and architecting a system to meet them is a multi-

step process.

1. Determine the cost of downtime. (Page 4)

2. Understand recovery in terms of point and time. That is, when is recovery necessary in the system’s

operations and how long a time exists between the point of failure and recovery. (Page 5)

3. Focus on the events that can have a negative impact on the ability to keep an application -- and an

organization -- up and running. Understanding these events is essential for developing the right high-

availability environment for your organization. (Page 6)

4. Understand the vulnerability of various systems with respect to the above. (Page 7)

5. Once you understand the events that lead to downtime, determine which technology areas you will need

to focus on to achieve the level of availability required. (Page 8)

6. When all these factors are understood, architect and deploy the availability environment. (Page 9)

1As used in this white paper, organization means any entity that requires computing technology to achieve its goals and conduct its

operations. Examples include businesses, departments of businesses, academic institutions, research facilities, or military units.

Architecting and Deploying High-Availability Solutions 4

ECG064/1198

Many of our customers find it more cost-effective to engage Compaq for architectural and deployment

activities.

1. What is the Cost of Downtime?

You need your Information System to survive in a world fraught with risk. A world where off-chance and

down-right failure can bring your operations grinding to a halt.

What happens to your organization when the system goes down? The range of answers runs from

“inconvenient” to “catastrophic.”

If your answer is closer to “catastrophic” than to “inconvenient” then you should read on. If your answer is

closer to “inconvenient” then perhaps you should read on to see if things are really as rosy as they seem.

In fact, most organizations underestimate -- or have not calculated -- the impact of downtime on their

business. The Gartner Group (1998) studied downtime costs for a variety of industries. The table below

summarizes the findings.

Industry Application Average Cost per

Hour of Downtime

Financial Brokerage Operations $6,500,000

Financial Credit Card Sales $2,600,000

Media Pay-per-View $1,150,000

Retail Home Shopping (TV) $ 113,000

Retail Catalog Sales $ 90,000

Transportation Airline Reservations $ 89,500

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 business processes may be interrupted, lost, corrupted, or even changed. Such processes

might include order management, inventory management, financial reporting, transactions, manufacturing,

human resources, life-sustaining medical systems, extended 911 identification, ATM operations, and more.

Programs: Both long- and short-term revenue can be affected. Key employee or customer activities might

be missed or lost.

Business itself: In this age of electronic commerce, if prospects or customers can’t access your site, chances

are they’ll never come back. And the chances are good that they’ll end up with your competitor. Customers

lost forever!

People: Lives can be lost; employee benefits missed with adverse impact on morale; governmental

program problems might harm citizenry; and even battles can be adversely affected if vital information is

lost, corrupted, or late.

Projects: Hundreds of thousands of person-hours of work can be lost, deadlines can be missed, change-

orders might be skipped with devastating results.

Operations: Those who manage the daily activities of an organization may find themselves without needed

data, with lost information, with standard activities lost, or with key reports missing or corrupted.

Architecting and Deploying High-Availability Solutions 5

ECG064/1198

Loss can be measured in more than money. But if money is the measure then the figures can be astounding.

In a recent study, the Standish Group (1998) reports that costs of downtime typically range from $1,000 to

$27,000 per minute. What’s more, they report that in some cases, the cost of downtime for a single incident

has exceeded $10,000,000. And if you consider the estimates of the Gartner Group as noted, the costs can

be in the Billions! Think about what downtime means to your organization.

2. Recovery Point and Recovery Time

High availability means different things to different people. At the high end it is called “continuous

availability” or “nonstop computing” and has come to mean something on the order of 99.999% uptime,

some five minutes a year of downtime. Pretty impressive. But what is your definition of high availability?

Perhaps you don’t need “five-nines” but you’d like to come as close as you can. Your requirement may not

be for continuous computing 24 hours per day, 365 days per year, but you may require that when your

system is in operation it cannot go down. An airborne surveillance and target acquisition system might be

in operation for only eight hours over the forward edge of battle but it better be available every second that

it’s there. Or a retail operation that does 90% of its business during a holiday season had better not go 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 terms of

Recovery Point and Recovery Time.

While the inherent reliability of Information Systems has been increasing, things still do happen that cause

applications to stop. Disaster Recovery specialists tend to examine the impact possibilities in terms of

Recovery Point -- the amount of “acceptable” loss -- and Recovery Time -- the amount of time needed to

get back in operation. Recovery Point is most important in data-centric operations where the loss of data is

unacceptable. Recovery Time is most important in transaction-centric operations where realtime continuity

is key.

Do you need fast recovery, or recovery to the exact state prior to the failure… or both? What is the impact

on your operations measured by a Recovery Point standard? If you don’t resume processing right where

you left off will it be inconvenient? Damaging? Catastrophic? What is the most effective and efficient

method to use to recover the information? What is the impact on business measured in Recovery Time? If

you don’t resume processing within a second will it be inconvenient? Damaging? Catastrophic?

Thus the recovery strategy you use depends on this assessment of Recovery Point and Recovery Time. The

diagram below displays four availability options measured in those terms.

Availability Options

On-Line

Hot Backup

Remote Hot Sites

Electronic

Vaulting

Weeks

Machine

Cycles

1000’s of

Transactions

Recovery

Time

Recovery Point

24 x 365

Transactions

Architecting and Deploying High-Availability Solutions 6

ECG064/1198

Remote Hot Sites (functional locations geographically distant from the primary operations center) are an

option if the Recovery Point and Recovery Time for an application are not very critical. An example might

be a billing application where the monthly statements could be delayed in mailing with minimum impact on

a business

Electronic Vaulting (method of electronically storing, managing, and protecting data in a computer "vault"

which is located off-site in a physically secure location) is an option if Recovery Point is more important

than Recovery Time; if, for instance, an indeterminate amount of data cannot be lost or historical data

needs to be available online for reference. An example might be an inventory application where the most

current transactions are recoverable by other means and the application can be restarted where it left off

using the historical data as a basis for inventory status. This is a good example of a data-centric operation.

On-line Hot Backup (data backup that is conducted while the system is in full operation) is necessary if the

Recovery Time is more critical than the Recovery Point A good example is an on-line traffic or production

control system where history is not as important as the current state of the situation. In air-traffic control,

where the planes were five minutes ago is not as critical as where they are now, because in five minutes

they may have moved 50 miles each, but in what directions? This is a classic example of a transaction-

centric operation.

24 x 365 (continuous availability) is the only viable option where both the Recovery Point and Recovery

Time are critical for an application.

Using the criteria of Recovery Point and Recovery Time, which state of availability is right for your

organization?

3. What Causes 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 have a negative

impact on your ability to keep an application – and an organization – up and running.

Component faults due to hardware, software, or interoperability issues. While the industry has come a long

way in reducing Mean Time Between Failure (MTBF) rates for individual hardware, packaging , and

mechanical components, the interdependent nature of today's multivendor and networked solutions makes

them vulnerable to hardware, software, and network interoperability problems.

Administrative intervention. Just because it's planned downtime doesn't mean it's not downtime.

Management tasks like system maintenance, database backups, index builds, table reorganizations, cache

changes, application/operating system updates, system re-configuration, and a physical move may require

that a system be brought down. Or the intervention itself may cause a failure.

Building-level incidents. In addition to system problems, disasters affecting a site or building, such as fire,

power loss, or flooding, can interrupt service by damaging systems, robbing them of power, or preventing

access to them.

Metropolitan area disaster. Disasters, such as floods, fire, and blackouts, can also affect whole cities,

impacting systems located throughout the metropolitan area.

Regional events. Computing can also be interrupted by disasters that affect systems across an even a larger

region. Hurricanes, earthquakes, or geopolitical disruptions can cause outages over hundreds of square

miles.

Do you know the probability of each of these events affecting your operation? Do you know what will

happen to your applications, particularly those in the “24 x 365” zone in each of these cases? Do you know

it can cost less than the alternative to minimize the negative impact that could occur? Understanding these

factors is crucial to determining the level of availability required by your organization.

Architecting and Deploying High-Availability Solutions 7

ECG064/1198

4. Vulnerable Technologies

Once you’ve looked at risk and cost, recovery, and failure events, you then need to turn your attention to

the following technology areas.

Hardware: Is the concern uninterruptible power supply, memory integrity, I/O, or processor failure?

Operating system: Some operating systems tend to be more stable than others, nevertheless, problems do

occur that can affect an operating system and cause it to corrupt a process. Once the operating system is in

failure everything above it such as databases, applications, processes, and more can be lost.

Storage: Is your business data-centric, transaction-centric, or both? If it is data-centric you do not want to

lose what is in your storage system; you don't want to lose access to that vital data; and, perhaps worst of

all, what happens if that data becomes corrupted?

Database: Whether your business is data-centric or transaction-centric the loss or corruption of a database

can spell disaster. This brings up the question about the need to replicate data.

Network: Whether it is backing up data over wide-area connections, the high-speed connections needed for

transaction processing, or the continuous availability of information already gathered, a robust network

infrastructure is a foundation on which to build truly high-availability environments.

Management: How much does it cost to manage this 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 operates at peak profitability?

Application: Is the application always there for you? Can you upgrade it without taking your system down?

Can the application take advantage of the underlying high-availability elements? Interdependencies are also

a concern. Storage failure, for example, can corrupt a database leading to operating system hang-up.

Looking at the Causes and Vulnerable Technologies Together

Once you have gained an understanding of which causes of downtime are of most concern and which

technologies are most at risk, you can begin to analyze your total environment and architect the high-

availability system that is right for you. This can be done in-house or with the assistance of a third party.

Compaq has considerable experience in this area and stands ready to assist you.

Availability Matrix

The matrix below is a simple yet effective way to quantify your availability requirements. The top row

displays the locations where failure events occur and the leftmost column lists the technology areas that

must be addressed to minimize the loss of availability.

Component Administrative Building Metropolitan Regional

Hardware

Operating System

Storage

Database

Network

Management

Applications

Recovery Point and Recovery Time are implicit to the Availability Matrix because there are products and

capabilities to help with the analysis, and to establish and implement the practices necessary to assure that

Architecting and Deploying High-Availability Solutions 8

ECG064/1198

the high-availability goals, once met, are maintained. These capabilities are very often described as

Availability Reviews, Disaster Recovery Services, or Business Impact Analyses and are primarily consulting

services to help you understand and/or implement a high-availability environment. In addition, at each

intersection in the matrix there are specific products designed to address the level of availability you

require.

What is most critical to know is that these technologies are available and that they play key roles in

implementing high-availability solutions. Your choice of an appropriate partner that has “been there, done

that” can make the difference in implementing the solution.

5. Availability Technologies

As we have seen thus far, there are a number of important elements to consider in architecting a high-

availability solution: the cost of downtime; trade-offs between recovery point and time; potential negative

events. Only after these elements have been qualified and quantified can the next step be taken: choosing a

technical strategy for achieving the level of availability required by a particular environment. The next few

paragraphs provide a quick overview of some availability technology options.

Power supply

Implementing solutions for any of the situations described requires some element of redundancy. At the

component level the most basic element is the power supply to the system. Uninterruptible Power Supplies

(UPS) are a common tool to deal with the possibility of power outages. Multiple power sources, dual

battery feeds, and power connections should also be considered in planning for component failures.

Storage

Once the power supply is assured, the next element to consider in a particular environment might be

storage. The ability to maintain redundancy of the data 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.

Database

Database replication is a combination of hardware and software implementations specifically focused at

protecting the data in your database. It may, or may not, require redundant physical storage. It provides

application-transparent database backup and may also provide for use of multiple storage media.

Backup and Restore is typically a capability that integrates a number of database and storage technologies

and media with the intent of providing both database backup and fast restoration capabilities.

Among other things, a TP monitor manages system resources, replication, load balancing, and failover

capabilities. TP monitors also enhance security and assure that transactions are completed before

confirming their completion by using a two-phase commit process.

Processors, operating systems, and interconnects

Fault-tolerant (FT) is a term used to describe the ability of a server or solution to tolerate failures. FT

includes both Hardware and Software components.

Hardware fault-tolerant: The ideal fault-tolerant solution is where the recovery point is instantaneous

through the use of alternate data paths to deliver continuous availability. To deliver continuous availability,

the components of the system need to operate in a fast-fail mode, that is, to identify the problem quickly,

isolate it from the integrity of operation of the total solution, and recover by using alternate paths. (Note

that this ability to route around failures allows the user to select a lower level of support response time as

mean-time-to-repair (MTTR) is not a critical component in ensuring the availability of the solution.)

Software fault-tolerant: The ability to recover from software failures. The main cause of server failures in

today’s architectures is software. The ability to tolerate software failures is a key requirement for the

delivery of continuous availability.

Architecting and Deploying High-Availability Solutions 9

ECG064/1198

Clusters should be able to overcome the administrative failures described above. Specifically included is

the fact that the application should be available while items like maintenance, hardware upgrades, software

upgrades, and database updates are going on. Then there is the question of how many nodes a cluster can

support as well as where the nodes physically reside.

Fibre Channel, SCSI 2, UltraSCSI, and ServerNet technologies improve storage throughput and allow

storage devices to be separated by greater distances while providing for the efficient, protected movement

of data between clusters and storage subsystems.

Channel Extenders do for CPUs what Fibre Channel and Ultra SCSI do for storage -- they provide for

greater separation enhancing tolerance for disasters.

Wide-Area and Global Clusters are separated by greater distances. The 500-miles-and-beyond capabilities

that exist today easily qualify them for dealing with Regional events.

Networks

By their very nature, networks are capable of spanning enough distance. When you look at the redundancy

and virtual capabilities that are available, they qualify as Regional solutions in the Availability Matrix. A

network in which a two-phase commit process assures a transaction is not complete until the remote node

confirms it certainly makes this high availability.

The Compaq Technology Brief entitled Eliminating Single Points of Failure and Enabling Rapid Recovery

in Server Subsystems (ECG0094/1197) provides more detail on increasing availability in basic components

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 environment that meets your unique

needs is not a trivial process. Add to that the challenges of solution deployment and the task can seem

overwhelming because -- in addition to issues surrounding availability -- other factors must be

considered, such as:

Performance and scalability: Can the solution deliver the performance required? Can it scale

appropriately to meet the size of the application?

Affordability: Is the cost of purchasing, implementing, or managing the solution prohibitive or consistent

with the operational loss you wish to prevent?

Manageability: Does the organization have the knowledge and resources necessary to manage the

solution over the long run?

Service and support: What level of service and support is available? Is the infrastructure in place to

support the solution reliably and affordably – wherever it is located?

Turn to Compaq for the Answers

Compaq unquestionably has the broadest range of availability products and solutions on the market

today. We can provide better answers anywhere on the Availability Matrix with open, reliable solutions

and technologies from hand-held PCs to the most scalable and available fault-tolerant and clusters

systems.

The professionals in the Compaq Enterprise Computing division helped invent the concepts of disaster

tolerance, fault tolerance, and continuous availability almost two decades ago and have been delivering and

supporting systems in the most demanding mission-critical environments ever since. The combined

development, delivery, and support experience of Compaq, DIGITAL, and Tandem personnel is

unsurpassed in the marketplace.

Architecting and Deploying High-Availability Solutions 10

ECG064/1198

Consider these compelling facts: Among customers with the highest levels of availability requirements –

those with an hourly cost of outage of $100,000/hour or more—the choice is Compaq by a factor of nearly

three times that of our nearest competitor.

Our line of availability platforms is recognized2as the most robust set of offerings in the industry. And

through Compaq integration programs, we are extending the high levels of availability found in these high-

end servers to the Microsoft Windows NT environment. Compaq is the leader and major driving force in

the acceleration of Windows NT Server as an enterprise solutions platform.

Deployment Options

As we have seen, the process of architecting a high-availability environment involves the understanding

and analysis of multiple factors, many of which may be unique to your organization. While the majority of

a solution might be based on Compaq’s wide range of off-the-shelf products, unique factors require unique

deployment solutions attained through some level of tailoring or customization. The CustomSystems

organization at Compaq specializes in tailoring off-the-shelf products to meet complex needs.

Pre-packaged Systems

Most vendors ship systems with little or no up-front testing. But Compaq is different. Our Ready to Go

clusters, for instance, are factory-configured and tested solutions. They eliminate the need for the

consolidating, compiling, testing, and tuning steps typically associated with building and debugging a

complex system from scratch. As a result, cluster solutions are online faster and ready to run your choice of

applications.

Tailored Solutions

High-availability systems interoperate within increasingly complex software, hardware, storage, and

networking environments. Your requirements may go beyond a standard solution. In that case, the proven

engineering 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 example, we can help you determine how your application will perform on large-scale configurations.

Working together, we can do a one-time assembly and test in our labs to validate the entire system solution.

You’ll have the answers you need prior to committing valuable time and precious resources. What’s more,

if you’re developing or planning to deploy a specialized application, we can give you a detailed look at all

or part of your development efforts. This enables you to recognize any potential problems and compare

design alternatives.

A key advantage to you is Compaq’s ability to integrate the complete system in our factories. This ensures

that you receive a fully functioning, characterized, and tested system that is ready to be installed and turned

on as soon as it arrives at your door. Factory integration reduces your risk and accelerates your

implementation speed. What’s more, the disruption to your operation that might be caused by extended

installation, testing, and pre-functioning repair is greatly reduced.

The result for you is reduced risk and a high degree of confidence that the combination of applications and

enterprise computing platforms you plan to deploy will work together to meet your mission-critical

requirements.

Service and Support Options

Compaq also offers our customers one of the most powerful IT service and support organizations in the

world -- including 27,000 IT experts in 114 countries and a network of over 30,000 highly skilled resellers.

We offer a suite of proactive and reactive services that will keep your Windows NT, OpenVMS, UNIX,

Intel, Alpha, NonStop Himalaya, Integrity/XC, and Integrity S-series environments highly available and

operating at peak performance. Our service capabilities include

2The Real McCoys: Enterprise Clustering. The Standish Group International, Inc. 1998

Product Analysis, MCSC: Can this Wolf Lead the Pack? DataQuest, April 27, 1998

Autres manuels pour ProLiant 1000

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels Compaq Serveur

Compaq

Compaq ProLiant DL580 Manuel utilisateur

Compaq

Compaq ALPHA GS320 Guide de configuration rapide

Compaq

Compaq AlphaServer DS20 Manuel utilisateur

Compaq

Compaq ProLiant 8000 Manuel

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Instructions d'utilisation et de sécurité

Compaq

Compaq 2500 - ProLiant - 64 MB RAM Manuel

Compaq

Compaq 108164-003 - ProLiant - 800 Guide de référence rapide

Compaq

Compaq ProSignia 500 Manuel

Compaq

Compaq ProLiant 3000 Manuel

Compaq

Compaq ProLiant 5500 Instructions d'utilisation et de sécurité

Compaq

Compaq 108164-003 - ProLiant - 800 Guide de démarrage rapide

Compaq

Compaq ProLiant DL380 G2 Manuel utilisateur

Compaq

Compaq 234664-002 - ProLiant - ML330T02 Instructions d'utilisation et de sécurité

Compaq

Compaq DS10L - AlphaServer - 256 MB RAM Manuel utilisateur

Compaq

Compaq AlphaServer GS80 Manuel utilisateur

Compaq

Compaq TruCluster Server AA-RHGWB-TE Manuel utilisateur

Compaq

Compaq DL760 - ProLiant - 1 GB RAM Guide d'installation

Compaq

Compaq AlphaServer 4100 s Mode d’emploi

Compaq

Compaq 222863-001 - TaskSmart W2200 Model 10 Mode d’emploi

Compaq

Compaq DL360 - ProLiant - Photon Guide de référence rapide

Compaq

Compaq DS20E - AlphaStation - 1 GB RAM Manuel utilisateur

Compaq

Compaq 108164-003 - ProLiant - 800 Manuel utilisateur

Compaq

Compaq ML350 - ProLiant - G2 Manuel utilisateur

Compaq

Compaq 108164-003 - ProLiant - 800 Guide de référence rapide

Manuels Serveur populaires d'autres marques

HP AlphaServer ES47 Manuel utilisateur

Dell

Dell PowerEdge R410 Manuel utilisateur

PowerNAS

PowerNAS CMA Manuel utilisateur

Supero

Supero FatTwin F617R3-FT Manuel utilisateur

MSI

MSI P1-109N-L70 Manuel utilisateur

Dell

Dell PowerEdge XE9640 Manuel

Dell

Dell PS4100 Instructions de montage

EtroVISION

EtroVISION EV3151 Manuel utilisateur

NEC

NEC Express5800/T110j Manuel utilisateur

HP ProLiant Gen9 Manuel utilisateur

Dell

Dell PowerEdge 3YPMN Manuel utilisateur

iRobo

iRobo IPC2U Manuel utilisateur

Nortel

Nortel 1000 Con?guration guide Manuel utilisateur

Asus

Asus AP7500 Manuel d'utilisation et d'entretien

Avid Technology

Avid Technology AirSpeed 5000 Manuel utilisateur

HP Integrity rx2600 Guide d'installation

Milestone

Milestone Husky IVO 350T Manuel utilisateur

Planet

Planet NAS-7410 Manuel utilisateur