Computer Associates BABWBR1151S38 Implementation Guide - Page 154

Perform CA ARCserve Backup r16 upgrade installation for Node A. See

Page 154 highlights

Deploy CA ARCserve Backup Server on MSCS 1. Delete the ARCserve cluster resources for r12/r12.5/r15 as follows: a. Access the Cluster Administrator. The Cluster Administrator dialog appears. Note: Cluster Administrator is a utility provided by Microsoft and is accessed from the Administrative Tools group of the Start menu. b. Select the ARCserve Group that the ARCserve server is deployed in, and locate the corresponding ARCserve cluster resources. Right-click on each ARCserve cluster resource and from the pop-up menu, select Delete. The ARCserve cluster resources for r12/r12.5/r15 are deleted. 2. Copy the CA ARCserve Backup r12/r12.5/r15 installation directory files into a temporary location. A backup copy of the CA ARCserve Backup r12/r12.5/r15 files is located in another location from the original files. 3. Perform CA ARCserve Backup r16 upgrade installation for Node A. See Upgrade CA ARCserve Backup from a Previous Release (see page 101). - The installation path location for CA ARCserve Backup r16 upgrade must be the same location where r12/r12.5/r15 is currently located. CA ARCserve Backup for Node A is upgraded from r12/r12.5/r15 to r16. Do not set up new ARCserve cluster resources at this time. 4. Move the active node from Node A to Node B, as follows: a. Access the Cluster Administrator. The Cluster Administrator opens. b. Select the ARCserve Group for Node A, right-click on the group name from the shortcut menu and select Move Group. ■ If there are only two nodes in the cluster, the active node status is automatically transferred from the initial active node (Node A) to the other node (Node B), making Node B the active node, and Node A the passive node. ■ If there are more than two nodes in the cluster, a pop-up screen opens, allowing you select the node to which you want to transfer the active status. When you select the node for transfer, the node you specified becomes active and the previously-selected node becomes passive. Repeat this procedure for each node in the cluster. 154 Implementation 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
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359

Deploy CA ARCserve Backup Server on MSCS
154
Implementation Guide
1.
Delete the ARCserve cluster resources for r12/r12.5/r15 as follows:
a.
Access the Cluster Administrator.
The Cluster Administrator dialog appears.
Note:
Cluster Administrator is a utility provided by Microsoft and is accessed
from the Administrative Tools group of the Start menu.
b.
Select the ARCserve Group that the ARCserve server is deployed in, and locate
the corresponding ARCserve cluster resources. Right-click on each ARCserve
cluster resource and from the pop-up menu, select Delete.
The ARCserve cluster resources for r12/r12.5/r15 are deleted.
2.
Copy the CA ARCserve Backup r12/r12.5/r15 installation directory files into a
temporary location.
A backup copy of the CA ARCserve Backup r12/r12.5/r15 files is located in another
location from the original files.
3.
Perform CA ARCserve Backup r16 upgrade installation for Node A. See
Upgrade CA
ARCserve Backup from a Previous Release
(see page 101).
The installation path location for CA ARCserve Backup r16 upgrade must be the
same location where r12/r12.5/r15 is currently located.
CA ARCserve Backup for Node A is upgraded from r12/r12.5/r15 to r16. Do not set
up new ARCserve cluster resources at this time.
4.
Move the active node from Node A to Node B, as follows:
a.
Access the Cluster Administrator. The Cluster Administrator opens.
b.
Select the ARCserve Group for Node A, right-click on the group name from the
shortcut menu and select Move Group.
If there are only two nodes in the cluster, the active node status is
automatically transferred from the initial active node (Node A) to the other
node (Node B), making Node B the active node, and Node A the passive
node.
If there are more than two nodes in the cluster, a pop-up screen opens,
allowing you select the node to which you want to transfer the active
status. When you select the node for transfer, the node you specified
becomes active and the previously-selected node becomes passive. Repeat
this procedure for each node in the cluster.