HP 12000 HP 12200 Gateway Virtual Library System User Guide (BW403-10001, June - Page 165

Disaster Recovery, Recovering from Operating System Failure - driver

Page 165 highlights

15 Disaster Recovery This section details the VLS disaster recovery procedures. It includes recovering from operating system failures, disk array failures, and node failures. Recovering from Operating System Failure Re-install the operating system if it becomes corrupted or is lost as a result of node RAID volume failure. CAUTION: Only install the VLS operating system on the node hard drives. Installing any other operating system on the node hard drives voids the warranty. NOTE: The VLS operating system contains all the hardware device drivers, firmware, and utilities required to operate the VLS. To re-install the operating system: 1. When restoring a primary node, power down all of the secondary nodes. 2. Connect a keyboard to the keyboard connector. 3. Connect a monitor to the video connector. 4. Insert the VLS Quick Restore CD into the CD-ROM or DVD-CD drive. The VLS Quick Restore CD auto starts. 5. Press R on the keyboard to start the re-installation. The re-installation takes 30 minutes or less to complete. The screen may freeze during the last 10 minutes of the re-installation. This is normal. The VLS Quick Restore CD is ejected and the system reboots when the re-installation is complete. 6. Restore the VLS. The warm failover process automatically restores the node to its previous configuration including the serial numbers, front-end Fibre Channel WWPNs, virtual device configuration, and licenses. No reconfiguration is required. See Restoring the System by Warm Failover. If the warm failover process does not restore the system, you can manually restore using a configuration file. See Manually Restoring the System. If you are restoring a primary node: a. Power up the secondary nodes once the primary node fully reboots. b. Set it as the master node in Command View VLS. See Configuring Primary Node 0. (The final step of setting the IP address and other public network configurations is not necessary.) c. Re-enter the IP addresses of the secondary nodes. See Setting the Network Settings using Command View VLS. Restoring the System with Warm Failover After any configuration or license change, the VLS automatically saves (within one hour) the updated configuration and licenses to a hidden virtual cartridge stored on the back-end disk arrays. When you replace the node or node hard drives, or re-install the operating system, the VLS uses this information to automatically restore the system to a configuration identical to what it had before. This automated process eliminates the need to manually restore the configuration. Manually Restoring the System After re-installing the operating system, the warm failover feature restores the licenses and configuration settings. However, if the warm failover does not occur (for example, due to a corrupt or missing file), the VLS virtual library configuration and network settings can be quickly restored Recovering from Operating System Failure 165

  • 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
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205

15 Disaster Recovery
This section details the VLS disaster recovery procedures. It includes recovering from operating
system failures, disk array failures, and node failures.
Recovering from Operating System Failure
Re-install the operating system if it becomes corrupted or is lost as a result of node RAID volume
failure.
CAUTION:
Only install the VLS operating system on the node hard drives. Installing any other
operating system on the node hard drives voids the warranty.
NOTE:
The VLS operating system contains all the hardware device drivers, firmware, and utilities
required to operate the VLS.
To re-install the operating system:
1.
When restoring a primary node, power down all of the secondary nodes.
2.
Connect a keyboard to the keyboard connector.
3.
Connect a monitor to the video connector.
4.
Insert the VLS Quick Restore CD into the CD-ROM or DVD-CD drive.
The VLS Quick Restore CD auto starts.
5.
Press
R
on the keyboard to start the re-installation.
The re-installation takes 30 minutes or less to complete. The screen may freeze during the last
10 minutes of the re-installation. This is normal.
The VLS Quick Restore CD is ejected and the system reboots when the re-installation is complete.
6.
Restore the VLS.
The warm failover process automatically restores the node to its previous configuration including
the serial numbers, front-end Fibre Channel WWPNs, virtual device configuration, and licenses.
No reconfiguration is required. See
Restoring the System by Warm Failover
.
If the warm failover process does not restore the system, you can manually restore using a
configuration file. See
Manually Restoring the System
.
If you are restoring a primary node:
a.
Power up the secondary nodes once the primary node fully reboots.
b.
Set it as the master node in Command View VLS. See
Configuring Primary Node 0
. (The
final step of setting the IP address and other public network configurations is not necessary.)
c.
Re-enter the IP addresses of the secondary nodes. See
Setting the Network Settings using
Command View VLS
.
Restoring the System with Warm Failover
After any configuration or license change, the VLS automatically saves (within one hour) the updated
configuration and licenses to a hidden virtual cartridge stored on the back-end disk arrays. When
you replace the node or node hard drives, or re-install the operating system, the VLS uses this
information to automatically restore the system to a configuration identical to what it had before.
This automated process eliminates the need to manually restore the configuration.
Manually Restoring the System
After re-installing the operating system, the warm failover feature restores the licenses and
configuration settings. However, if the warm failover does not occur (for example, due to a corrupt
or missing file), the VLS virtual library configuration and network settings can be quickly restored
Recovering from Operating System Failure
165