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

Testing Plans and Assumptions, Planning for Catastrophe

Page 52 highlights

Planning for Catastrophe Restrictive media-selection criteria and extensive off-site storage can increase your need for media well beyond the minimums calculated above. Finally, the overall size of the data you need to back up usually increases over time. Data piles up faster in some organizations than it does in others, but the pile almost always grows. The preceding calculations assume a more-or-less constant amount of data. So, when you estimate how much you need to back up (1 Terabyte in the examples), always allow for growth. Then check periodically to be sure that you always have enough extra storage to accommodate emerging needs. Testing Plans and Assumptions After you have made the required estimates, performed all the necessary calculations, and formulated a plan that should work for your organization, you should test it. Set up a pilot test configuration using a scaled down environment and run tests. Using the BrightStor ARCserve Backup logs, you can see how good your rough estimates are. You can see if you estimated the amount of backup data correctly by checking the size of a full backup generated by your plan. You can check your estimate of the average percent change in your data by checking the size of the incremental backups. You can make sure that all the data that should be backed up is backed up, and you can see if your data and network segmentation tactics have worked as intended. Planning for Catastrophe So far, we have focused on the major threat to your data-routine losses due to equipment failure or operator error-and on the processes common to all backup and recovery efforts. But there are some additional considerations when you are planning your organization's recovery from a major catastrophe. For our purposes, a catastrophe is a natural or man-made disaster, such as a fire or flood, that results in the loss of multiple hosts, a data center, or an entire network, including locally stored backup media and hardware. To handle this sort of extreme emergency, you must provide secure, off-site storage for some of your backup media, and you must keep the off-site data current. 2-14 Administrator 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
  • 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
2–14
Administrator Guide
Restrictive media-selection criteria and extensive off-site storage can increase your
need for media well beyond the minimums calculated above.
Finally, the overall size of the data you need to back up usually increases over time.
Data piles up faster in some organizations than it does in others, but the pile almost
always grows. The preceding calculations assume a more-or-less constant amount
of data. So, when you estimate how much you need to back up (1 Terabyte in the
examples), always allow for growth. Then check periodically to be sure that you
always have enough extra storage to accommodate emerging needs.
Testing Plans and Assumptions
After you have made the required estimates, performed all the necessary
calculations, and formulated a plan that should work for your organization, you
should test it. Set up a pilot test configuration using a scaled down environment
and run tests.
Using the BrightStor ARCserve Backup logs, you can see how good your rough
estimates are. You can see if you estimated the amount of backup data correctly by
checking the size of a full backup generated by your plan. You can check your
estimate of the average percent change in your data by checking the size of the
incremental backups. You can make sure that all the data that should be backed up
is backed up, and you can see if your data and network segmentation tactics have
worked as intended.
Planning for Catastrophe
So far, we have focused on the major threat to your data—routine losses due to
equipment failure or operator error—and on the processes common to all backup
and recovery efforts. But there are some additional considerations when you are
planning your organization’s recovery from a major catastrophe.
For our purposes, a catastrophe is a natural or man-made disaster, such as a fire or
flood, that results in the loss of multiple hosts, a data center, or an entire network,
including locally stored backup media and hardware. To handle this sort of
extreme emergency, you must provide secure, off-site storage for some of your
backup media, and you must keep the off-site data current.