Dell PowerVault NX3500 Administrator's Guide - Page 72

Migrate Immediately, Migrate Automatically, Migrate Manually, Setting the Migration Policy

Get Dell PowerVault NX3500 PDF manuals and user guides View all Dell PowerVault NX3500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

Setting the Migration Policy In case of a controller failure, the system automatically migrates each connection from the failed controller to another controller to allow clients to continue their work. This causes disconnections to CIFS clients. When the failed controller revives, the system can rebalance the load, by migrating clients back to the revived controller automatically. This operation is called fail-back. Clients that use NFS are stateless and are not affected during fail-back. Clients that use connection-based protocols (CIFS), may be disconnected during fail-back. To optimize the fail-back operation, the system provides you with the following policies for migration on recovery, which affect the loadbalance and disconnections: Migrate Immediately Always keep the system well balanced, at the cost of possibly disconnecting CIFS clients during work time. Migrate Automatically Always keep the system well balanced if the controller failure is very short, at the cost of disconnecting CIFS clients. This option causes the system to remain unbalanced for a period of several days, if the failure remains for long time. This mode overcomes short controller failures because clients have not created new material during the short time failure. The best practice is to therefore rebalance them as soon as possible. If the failure is longer than 10 minutes, the system remains unbalanced until you rebalance it manually. Migrate Manually Never migrates clients automatically. This requires manual intervention to rebalance the system. If the system requires manual intervention to rebalance it after fail-over, the system sends an appropriate message by email to the administrator. You can configure the fail-back policy, as described above, per protocol and LAN/client network. 72 Monitoring PowerVault NX3500

  • 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
72
Monitoring PowerVault NX3500
Setting the Migration Policy
In case of a controller failure, the system automatically migrates each
connection from the failed controller to another controller to allow clients to
continue their work. This causes disconnections to CIFS clients. When the
failed controller revives, the system can rebalance the load, by migrating
clients back to the revived controller automatically. This operation is called
fail-back.
Clients that use NFS are stateless and are not affected during fail-back.
Clients that use connection-based protocols (CIFS), may be disconnected
during fail-back. To optimize the fail-back operation, the system provides you
with the following policies for migration on recovery, which affect the load-
balance and disconnections:
Migrate Immediately
Always keep the system well balanced, at the cost of possibly disconnecting
CIFS clients during work time.
Migrate Automatically
Always keep the system well balanced if the controller failure is very short, at
the cost of disconnecting CIFS clients. This option causes the system to
remain unbalanced for a period of several days, if the failure remains for long
time.
This mode overcomes short controller failures because clients have not
created new material during the short time failure. The best practice is to
therefore rebalance them as soon as possible.
If the failure is longer than 10 minutes, the system remains unbalanced until
you rebalance it manually.
Migrate Manually
Never migrates clients automatically. This requires manual intervention to
rebalance the system.
If the system requires manual intervention to rebalance it after fail-over, the
system sends an appropriate message by email to the administrator.
You can configure the fail-back policy, as described above, per protocol and
LAN/client network.