Compaq ProLiant 1000 User Guide: Online Storage Controller Recovery Option - Page 19

Functionality and Configuration, Options

Get Compaq ProLiant 1000 PDF manuals and user guides View all Compaq ProLiant 1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 19 highlights

2-1 Chapter 2 Functionality and Configuration Options There are three high-availability option solutions in the Recovery Server Option /U kit: Standby Recovery Server On-Line Recovery Server Online Storage Controller Recovery Option (OSCRO) The first two option solutions minimize server downtime by automatically transferring operations from a failed server to a backup server. OSCRO, on the other hand, provides a way to reduce or eliminate downtime associated with mass storage controller failure. In this chapter, we examine how OSCRO provides this benefit. Redundancy at the Mass Storage Controller Level In the past, the effort to improve the reliability of I/O subsystems focused on redundant arrays of independent disks (RAID). RAID protects data if a disk drive fails but offers no protection against mass storage controller failure. Windows NT provides the option to implement a fully redundant I/O subsystem in a configuration called Disk Duplexing. Disk Duplexing implemented at the software level provides protection against failure of the disk as well as the mass storage controller. Disk Duplexing requires complete redundancy of all I/O subsystem components, however, which makes it very costly to implement and limits the extensibility of the system. With the introduction of OSCRO and its two-way switching capability, Compaq offers fault tolerance for mass storage controllers implemented at the hardware level, providing increased reliability without the need for complete I/O subsystem redundancy. Online Storage Controller Recovery Option User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-1
Online Storage Controller Recovery Option User Guide
Chapter 2
Functionality and Configuration
Options
There are three high-availability option solutions in the Recovery Server
Option /U kit:
■
Standby Recovery Server
■
On-Line Recovery Server
■
Online Storage Controller Recovery Option (OSCRO)
The first two option solutions minimize server downtime by automatically
transferring operations from a failed server to a backup server.
OSCRO, on the other hand, provides a way to reduce or eliminate downtime
associated with mass storage controller failure. In this chapter, we examine how
OSCRO provides this benefit.
Redundancy at the Mass Storage
Controller Level
In the past, the effort to improve the reliability of I/O subsystems focused on
redundant arrays of independent disks (RAID). RAID protects data if a disk
drive fails but offers no protection against mass storage controller failure.
Windows NT provides the option to implement a fully redundant I/O subsystem
in a configuration called Disk Duplexing. Disk Duplexing implemented at the
software level provides protection against failure of the disk as well as the mass
storage controller. Disk Duplexing requires complete redundancy of all I/O
subsystem components, however, which makes it very costly to implement and
limits the extensibility of the system.
With the introduction of OSCRO and its two-way switching capability,
Compaq offers fault tolerance for mass storage controllers implemented at the
hardware level, providing increased reliability without the need for complete
I/O subsystem redundancy.