Computer Associates ARB6002700WF0. ..... Administration Guide - Page 53

Assessing the Risk, Selecting an Off-site Repository, Security, Accessibility

Page 53 highlights

Planning for Catastrophe Assessing the Risk Before going further, decide what sorts of disaster you can realistically prepare for, given the importance of your data, the expense of protecting it, the magnitude of the risk, and the corporate policies that apply to your sites. Consider the following questions. ■ What is the likelihood that your organization will face a large-scale disaster that affects the whole region or metropolitan area? Such catastrophes might include earthquakes, large floods, or acts of war. ■ What is the likelihood of smaller disasters, such as building fires, localized flooding, or vandalism? ■ How much data would you lose in a large disaster? In a small disaster? ■ How severely would the loss affect your organization in each case? ■ How much is your organization prepared to spend to defend against each of the risks you identify? Selecting an Off-site Repository Like everything else in storage management, the selection of an off-site repository or vault is the result of a series of trade-offs. Security The vault should be isolated enough from your main facility to protect the off-site data from the kind of catastrophes you are prepared to guard against. If earthquakes are the biggest threat you need to deal with, the vault should be in an earthquake-resistant building at some distance from your main site or even in another city or a different seismic zone. On the other hand, if fire or local flooding is the danger, a storage room in an upper floor of the building across the street might be enough. Accessibility Unfortunately, measures that isolate your data repository from your primary site also make it harder (and more expensive) to keep the data in the remote repository current. To be of use, off-site data has to be reasonably up-to-date, which means it has to be reasonably accessible. A vault in a distant city might protect the data against even the most extreme disasters, but it might be impractical to ship media there on a daily basis. Planning 2-15

  • 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

Planning for Catastrophe
Planning
2–15
Assessing the Risk
Before going further, decide what sorts of disaster you can realistically prepare for,
given the importance of your data, the expense of protecting it, the magnitude of
the risk, and the corporate policies that apply to your sites. Consider the following
questions.
What is the likelihood that your organization will face a large-scale disaster
that affects the whole region or metropolitan area? Such catastrophes might
include earthquakes, large floods, or acts of war.
What is the likelihood of smaller disasters, such as building fires, localized
flooding, or vandalism?
How much data would you lose in a large disaster? In a small disaster?
How severely would the loss affect your organization in each case?
How much is your organization prepared to spend to defend against each of
the risks you identify?
Selecting an Off-site Repository
Like everything else in storage management, the selection of an off-site repository
or
vault
is the result of a series of trade-offs.
Security
The vault should be isolated enough from your main facility to protect the off-site
data from the kind of catastrophes you are prepared to guard against. If
earthquakes are the biggest threat you need to deal with, the vault should be in an
earthquake-resistant building at some distance from your main site or even in
another city or a different seismic zone. On the other hand, if fire or local flooding
is the danger, a storage room in an upper floor of the building across the street
might be enough.
Accessibility
Unfortunately, measures that isolate your data repository from your primary site
also make it harder (and more expensive) to keep the data in the remote repository
current. To be of use, off-site data has to be reasonably up-to-date, which means it
has to be reasonably accessible. A vault in a distant city might protect the data
against even the most extreme disasters, but it might be impractical to ship media
there on a daily basis.