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

OSCRO Planning Implications

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 31 highlights

3-3 OSCRO Planning Implications There are several things to consider before installing OSCRO. They include thinking about your current environment in terms of the following: The Recovery Server Option /U kit contains parts for three different high-availability option solutions. Because these are mutually exclusive options, if you are going to implement OSCRO and you already have either Standby Recovery Server or On-Line Recovery Server installed on your existing server, you need to de-install the Recovery Server Option now in place. If you have a duplexed ProLiant Storage System/F or /U, you may not want to implement OSCRO, because OSCRO does not support duplexed storage systems. If you decide to implement OSCRO, you will need to de-install the duplexed ProLiant Storage System and potentially rebuild all of your disk arrays and logical drives. If you have an older ProLiant Storage System, you need to upgrade to the ProLiant Storage System/F or /U. For each upgrade of Windows NT or device drivers, the OSCRO controller pairs must be dissolved before the upgrade, and re-established after the upgrade is completed. Upgrading controllers requires dissolving and re-merging OSCRO controller pairs only when you are upgrading the device drivers or switching from single-channel to dual-channel controllers. Upgrading from SMART-2/P to SMART-2DH, for example, has no direct impact on an OSCRO controller pair. Moving controllers to different PCI or EISA slots, on the other hand, requires dissolving and re-merging a controller pair. 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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-3
Online Storage Controller Recovery Option User Guide
OSCRO Planning Implications
There are several things to consider before installing OSCRO. They include
thinking about your current environment in terms of the following:
■
The Recovery Server Option /U kit contains parts for three different
high-availability option solutions. Because these are mutually exclusive
options, if you are going to implement OSCRO and you already have
either Standby Recovery Server or On-Line Recovery Server installed
on your existing server, you need to de-install the Recovery Server
Option now in place.
■
If you have a duplexed ProLiant Storage System/F or /U, you may not
want to implement OSCRO, because OSCRO does not support duplexed
storage systems. If you decide to implement OSCRO, you will need to
de-install the duplexed ProLiant Storage System and potentially rebuild
all of your disk arrays and logical drives.
■
If you have an older ProLiant Storage System, you need to upgrade to
the ProLiant Storage System/F or /U.
■
For each upgrade of Windows NT or device drivers, the OSCRO
controller pairs must be dissolved before the upgrade, and re-established
after the upgrade is completed.
Upgrading controllers requires dissolving and re-merging OSCRO controller
pairs only when you are upgrading the device drivers or switching from
single-channel to dual-channel controllers. Upgrading from SMART-2/P to
SMART-2DH, for example, has no direct impact on an OSCRO controller
pair. Moving controllers to different PCI or EISA slots, on the other hand,
requires dissolving and re-merging a controller pair.