3Ware 9550SXU-16ML User Guide - Page 184

About Migration, Moving a Unit to Another Controller During Migration

Page 184 highlights

Chapter 9. Maintaining Units rewrites the redundant data to the error location to force the drive to reallocate the error location. A notification of repair is posted. The result is a restoration of drive and data integrity; the primary and redundant data are again both valid. If the array is not redundant, a file-system check is recommended to correct the issue. If the errors persist and cannot be overwritten from a backup copy, perform a final incremental backup. You will need to replace the defective drive, recreate the array, and reinstall the data. About Migration Migration allows on-line units to be reconfigured. You can make two types of configuration changes: „ RAID Level „ Unit Capacity Expansion RAID level migration and unit capacity expansion tasks can be done together or separately. Migration tasks follow the same schedule as rebuild and initialization tasks. Because of the controller and disk resources required during migration, when migration is active, it has priority over other background tasks. When migration starts, it will take the highest priority over rebuild, initialize and verify. Once a unit is put into the migration state, it must be allowed to complete the process. While migrating, rebuilds or verifies to the unit are not permitted. Migrate tasks are always done in the background, and can be initiated through either 3DM or the CLI. (Foreground migrations through 3BM are not supported.) A unit be migrated can still be used (I/O still continues), however the performance will be affected while the migrating task is active. You can control how much affect this has on performance by setting the background task rate. For more information, see "Setting Background Task Rate" on page 175. Moving a Unit to Another Controller During Migration Moving a unit to another controller while the unit is in the migration state is supported with one restriction. If the unit was in the middle of the migration process and the controller was shutdown uncleanly, the unit cannot be moved to another controller until the unit has recovered from the unclean shutdown. For more information about migration, see "Changing An Existing Configuration" on page 144. 174 3ware 9550SX Serial ATA RAID Controller 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
  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260

Chapter 9. Maintaining Units
174
3ware 9550SX Serial ATA RAID Controller User Guide
rewrites the redundant data to the error location to force the drive to reallocate
the error location. A notification of repair is posted. The result is a restoration
of drive and data integrity; the primary and redundant data are again both
valid.
If the array is not redundant, a file-system check is recommended to correct
the issue. If the errors persist and cannot be overwritten from a backup copy,
perform a final incremental backup. You will need to replace the defective
drive, recreate the array, and reinstall the data.
About Migration
Migration allows on-line units to be reconfigured. You can make two types of
configuration changes:
RAID Level
Unit Capacity Expansion
RAID level migration and unit capacity expansion tasks can be done together
or separately.
Migration tasks follow the same schedule as rebuild and initialization tasks.
Because of the controller and disk resources required during migration, when
migration is active, it has priority over other background tasks. When
migration starts, it will take the highest priority over rebuild, initialize and
verify.
Once a unit is put into the migration state, it must be allowed to complete the
process. While migrating, rebuilds or verifies to the unit are not permitted.
Migrate tasks are always done in the background, and can be initiated through
either 3DM or the CLI. (Foreground migrations through 3BM are not
supported.)
A unit be migrated can still be used (I/O still continues), however the
performance will be affected while the migrating task is active. You can
control how much affect this has on performance by setting the background
task rate. For more information, see “Setting Background Task Rate” on
page 175.
Moving a Unit to Another Controller During Migration
Moving a unit to another controller while the unit is in the migration state is
supported with one restriction. If the unit was in the middle of the migration
process and the controller was shutdown uncleanly, the unit cannot be moved
to another controller until the unit has recovered from the unclean shutdown.
For more information about migration, see “Changing An Existing
Configuration” on page 144.