Lacie 131018 User Manual - Page 141

Failover, Performance, and Additional Functions

Page 141 highlights

Failover and Performance Chapter 12 Failover, Performance and Additional Functions 12.1 Overview In this chapter you will find more information on the following: • How StorView failover operates • Performance optimization processes • Additional Functions - About - Take Control Monitoring - Rescan - Alarm Mute and Enable/Disable 12.2 How StorView Server Failover Works The failover feature of the StorView RAID Module must have one of the following setups. If you are using the host-based version of StorView, two or more host servers must be directly connected to the RAID storage system enclosure and each host must have a copy of StorView installed with a Global Access license. If you are using the embedded version of StorView, you must have dual controllers installed (duplex topology) each with embedded StorView installed. At startup, each StorView server will create a device list of all the attached storage systems. It then sends the list out on the network as a device list packet. The other StorView servers on the network will then respond with their device list packets. Since the StorView servers are attached to the same storage solution, they will have the same or similar devices in their device list packet. The identical devices in each device list packet will be flagged. After analysis, the StorView server with the lowest serial number or address will take control of those devices. The other StorView server will indicate on its interface that another StorView server is monitoring the storage solution. 133

  • 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
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214

Failover and Performance
133
Chapter
12
Failover, Performance
and Additional Functions
12.1 Overview
In this chapter you will find more information on the following:
How StorView failover operates
Performance optimization processes
Additional Functions
About
Take Control Monitoring
Rescan
Alarm Mute and Enable/Disable
12.2
How StorView Server Failover Works
The failover feature of the StorView RAID Module must have one of the following setups.
If you are using the host-based version of StorView, two or more host servers must be directly
connected to the RAID storage system enclosure and each host must have a copy of StorView
installed with a Global Access license.
If you are using the embedded version of StorView, you must have dual controllers installed (duplex
topology) each with embedded StorView installed.
At startup, each StorView server will create a device list of all the attached storage systems. It then sends
the list out on the network as a device list packet. The other StorView servers on the network will then
respond with their device list packets. Since the StorView servers are attached to the same storage
solution, they will have the same or similar devices in their device list packet. The identical devices in
each device list packet will be flagged. After analysis, the StorView server with the lowest serial number
or address will take control of those devices. The other StorView server will indicate on its interface that
another StorView server is monitoring the storage solution.