HP NetServer AA 4000 HP AA HP Netserver 4000 Reference Guide - Page 111

Last Known Good Control Set

Get HP NetServer AA 4000 PDF manuals and user guides View all HP NetServer AA 4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 111 highlights

Disaster recovery procedures Ch 6: Backp and Restore In the event of a disaster or an operator's error, it is possible that the CE OS can be put in an inoperable state. When this occurs it may be possible to recover the system without restoring from backup tapes. Below is a set of procedures to assist system administrators to recover systems with minimum downtime. The procedures must be followed in order listed below. 1. Last Known Good (Control Set) Some failures of a CE OS to boot (after a reconfiguration) can be recovered from by selecting the "Last Known Good" configuration. This functionality is exactly the same as the reference machine (standard NT) case where you strike the space bar on the keyboard when prompted - and prior to the first log on following the configuration change. Follow the steps below: a. Boot both IOPs in Marathon Operation Mode and observe if both CE NOS disks are up-to-date (i.e., both should be green on the Marathon Management GUI). If so, select one of the two tuples as the "booting tuple." If only one of them is upto-date, select the tuple containing the the up-to-date NOS disk as the "booting tuple." b. Set the monitor/keyboard switch to enable keyboard on the "booting tuple" side. c. Set the monitor switch on SSDL of the "booting tuple" to CE. d. Power on only the CE in the "booting tuple". e. System will initialize itself. When you receive the message on the CE "Initiating Marathon Boot", followed by MIC BIOS: CE Boot will be serviced by IOP1 or IOP2 (verify this IOP is indeed in the "booting tuple.") f. After several moments, NTLDR program will starts and you will receive a message to depress the space bar to load the "Last Known Good" configuration. (Note that the time window allowed for depressing of space bar can be rather short. Be ready.) Then boots NT with "Last Known Good" configuration. g. Power on the other CE to join the Marathon system. Network Server Division 6-11

  • 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
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
Ch 6: Backp and Restore
Network Server Division
6-11
Disaster recovery procedures
In the event of a disaster or an operator's error, it is possible that the
CE OS can be put in an inoperable state. When this occurs it may be
possible to recover the system without restoring from backup tapes.
Below is a set of procedures to assist system administrators to
recover systems with minimum downtime. The procedures must be
followed in order listed below.
1.
Last Known Good (Control Set)
Some failures of a CE OS to boot (after a reconfiguration) can be
recovered from by selecting the
“Last Known Good”
configuration.
This functionality is exactly the same as the
reference machine (standard NT) case where you strike the space
bar on the keyboard when prompted – and prior to the first log
on following the configuration change. Follow the steps below:
a.
Boot both IOPs in Marathon Operation Mode and observe if
both CE NOS disks are up-to-date (i.e., both should be green
on the Marathon Management GUI). If so, select one of the
two tuples as the "booting tuple."
If only one of them is up-
to-date, select the tuple containing the the up-to-date NOS
disk as the "booting tuple."
b.
Set the monitor/keyboard switch to enable keyboard on the
"booting tuple" side.
c.
Set the monitor switch on SSDL of the "booting tuple" to
CE.
d.
Power on only the CE in the "booting tuple".
e.
System will initialize itself. When you receive the message
on the CE "Initiating Marathon Boot", followed by MIC
BIOS: CE Boot will be serviced by IOP1 or IOP2 (verify
this IOP is indeed in the "booting tuple.")
f.
After several moments, NTLDR program will starts and you
will receive a message to depress the space bar to load the
"Last Known Good" configuration. (Note that the time
window allowed for depressing of space bar can be rather
short. Be ready.) Then boots NT with "Last Known Good"
configuration.
g.
Power on the other CE to join the Marathon system.