Computer Associates BABNWUP900NE6 Administration Guide - Page 253

Configuring Your Firewall to Optimize Communication, Discovery Configuration for the SAN Option

Page 253 highlights

Configuring Your Firewall to Optimize Communication Discovery Configuration for the SAN Option The Discovery service configuration for servers in a SAN environment require additional modifications in order for all servers to be discovered. The following options are available to ensure that all SAN servers are enabled for discovery: ■ Select the All auto discovered subnets (may increase network traffic) option in the Enable Discovery using TCP/IP Subnet sweep field in the Configuration dialog. Or, ■ Add other remote SAN machine names/IP addresses by accessing the Windows Domain tab. Note: The configuration for each remote SAN server must be consistent to ensure accurate discovery. If you only configure one SAN server, other servers may still fail in discovery. Configuring Your Firewall to Optimize Communication In an environment where you are using multiple BrightStor ARCserve Backup servers that reside across a firewall, or there is a firewall within a Storage Area Network (SAN) fibre loop, you must configure your servers to ensure the use of fixed ports and interfaces. The configuration on your BrightStor ARCserve Backup servers must match your firewall configuration so that BrightStor ARCserve Backup servers can communicate with each other. A BrightStor ARCserve Backup server communicates with other BrightStor ARCserve Backup servers using a set of Remote Procedure Call (RPC) services. Each service can be identified by an interface (IP address) and a port. When you share data and tape libraries between BrightStor ARCserve Backup servers, the services communicate with each other using the interface and port information provided by the RPC infrastructure. RPC infrastructure, however, does not ensure specific port assignment. Therefore, you must know your RPC infrastructure and port number assignments to configure your firewall properly. To achieve static binding, additional configuration is required. You can customize your environmental port communication settings by modifying the ports configuration file (PortsConfig.cfg) located in the CA\SharedComponents\BrightStor directory. Administering the Backup Server 9-29

  • 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
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382

Configuring Your Firewall to Optimize Communication
Administering the Backup Server
9–29
Discovery Configuration for the SAN Option
The Discovery service configuration for servers in a SAN environment require
additional modifications in order for all servers to be discovered. The following
options are available to ensure that all SAN servers are enabled for discovery:
Select the All auto discovered subnets (may increase network traffic) option in
the Enable Discovery using TCP/IP Subnet sweep field in the Configuration
dialog.
Or,
Add other remote SAN machine names/IP addresses by accessing the
Windows Domain tab.
Note:
The configuration for each remote SAN server must be consistent to ensure
accurate discovery. If you only configure one SAN server, other servers may still
fail in discovery.
Configuring Your Firewall to Optimize Communication
In an environment where you are using multiple BrightStor ARCserve Backup
servers that reside across a firewall, or there is a firewall within a Storage Area
Network (SAN) fibre loop, you must configure your servers to ensure the use of
fixed ports and interfaces. The configuration on your BrightStor ARCserve Backup
servers must match your firewall configuration so that BrightStor ARCserve
Backup servers can communicate with each other.
A BrightStor ARCserve Backup server communicates with other BrightStor
ARCserve Backup servers using a set of Remote Procedure Call (RPC) services.
Each service can be identified by an interface (IP address) and a port. When you
share data and tape libraries between BrightStor ARCserve Backup servers, the
services communicate with each other using the interface and port information
provided by the RPC infrastructure. RPC infrastructure, however, does not ensure
specific port assignment. Therefore, you must know your RPC infrastructure and
port number assignments to configure your firewall properly. To achieve static
binding, additional configuration is required.
You can customize your environmental port communication settings by
modifying the ports configuration file (PortsConfig.cfg) located in the
CA\SharedComponents\BrightStor directory.