HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 114

VLS Warm Failover, Storage Pool Load Balancing on the VLS

Page 114 highlights

Figure 45 Storage Pool Load Balancing on the VLS . As Figure 45 shows, the VLS storage pool: • Provides clustered virtual cartridge file system across one or more arrays. • Automatically load-balances incoming backup data across all available array LUNs (in 32MB extents). • Prevents performance and capacity hot-spots. If a virtual cartridge is overwritten by the backup application (e.g., because it reached the end of the retention period and was reused for new backups), all of its existing blocks are freed up and then new writes are dynamically assigned array LUNs as usual. When a new array is added to the VLS, the load balancing system will automatically start using this new storage on subsequent virtual cartridge writes (i.e., backups performed after the array was added will automatically load balance across all storage including the new array). Any existing data that was present before the new array was added will be rebalanced as virtual cartridges are recycled/expired and then overwritten by the backup application. VLS Warm Failover A VLS feature (in firmware version 3.2 or higher) provides an automatic mechanism for faster recovery from node0 failures, which is the ability to automatically restore the previous virtual library configuration and licenses after a complete node0 replacement. This warm failover feature works as follows: 114 Virtual Library Systems

  • 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
  • 215
  • 216
  • 217
  • 218

Figure 45 Storage Pool Load Balancing on the VLS
.
As
Figure 45
shows, the VLS storage pool:
Provides clustered virtual cartridge file system across one or more arrays.
Automatically load-balances incoming backup data across all available array LUNs (in 32MB
extents).
Prevents performance and capacity hot-spots.
If a virtual cartridge is overwritten by the backup application (e.g., because it reached the end of the
retention period and was reused for new backups), all of its existing blocks are freed up and then
new writes are dynamically assigned array LUNs as usual. When a new array is added to the VLS,
the load balancing system will automatically start using this new storage on subsequent virtual cartridge
writes (i.e., backups performed after the array was added will automatically load balance across all
storage including the new array). Any existing data that was present before the new array was added
will be rebalanced as virtual cartridges are recycled/expired and then overwritten by the backup
application.
VLS Warm Failover
A VLS feature (in firmware version 3.2 or higher) provides an automatic mechanism for faster recovery
from node0 failures, which is the ability to automatically restore the previous virtual library configuration
and licenses after a complete node0 replacement. This warm failover feature works as follows:
Virtual Library Systems
114