Computer Associates BABWBR1151S38 Implementation Guide - Page 60

Data Migration from a Previous Release, Product License Requirements

Page 60 highlights

Product License Requirements Data Migration from a Previous Release When you upgrade CA ARCserve Backup from a previous release, you can retain most of your current settings and migrate the information stored in the previous CA ARCserve Backup database to the new CA ARCserve Backup database. After the upgrade is complete, CA ARCserve Backup migrates the following types of data to the new CA ARCserve Backup database: ■ Authentication--The upgrade process migrates all CA ARCserve Backup System Account data from the previous database to the new database, such as user names, passwords, and so on. Note: For upgrades to member servers, CA ARCserve Backup does not migrate user accounts and passwords if they already exist in the domain that the member server joins. ■ Jobs--The upgrade process migrates all job scripts, such as rotation jobs, GFS rotations, and custom jobs from the previous database to the new database. Note: The upgrade process does not migrate Database pruning job settings from your previous installation. For information about specifying Database pruning job settings, see the Administration Guide. ■ Core database data--The upgrade process migrates all core data from the previous database to the new database. Core data can consist of information about jobs, media, sessions, devices, media pools, file path names, file names, and so on. ■ Log data--The upgrade process migrates Activity Log data from the previous database to the new database. ■ Session data--The upgrade process lets you migrate the session data from the previous database to the new database. Note: The process of migrating session data can take a lot of time. However, you can perform file-level and session-level restores immediately after the upgrade and migration process is complete. ■ Catalog data--The upgrade process lets you migrate the catalog database data from the previous database to the new database. Note: The process of migrating catalog data can take a lot of time. A progress dialog does not display. Product License Requirements CA ARCserve Backup requires you to license your product to receive authorized and uninterrupted access to the components, options, and agents. If you do not license CA ARCserve Backup, it stops working 31 days after you begin using it. 60 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

Product License Requirements
60
Implementation Guide
Data Migration from a Previous Release
When you upgrade CA ARCserve Backup from a previous release, you can retain most of
your current settings and migrate the information stored in the previous CA ARCserve
Backup database to the new CA ARCserve Backup database.
After the upgrade is complete, CA ARCserve Backup migrates the following types of data
to the new CA ARCserve Backup database:
Authentication--
The upgrade process migrates all CA ARCserve Backup System
Account data from the previous database to the new database, such as user names,
passwords, and so on.
Note:
For upgrades to member servers, CA ARCserve Backup does not migrate user
accounts and passwords if they already exist in the domain that the member server
joins.
Jobs--
The upgrade process migrates all job scripts, such as rotation jobs, GFS
rotations, and custom jobs from the previous database to the new database.
Note:
The upgrade process does not migrate Database pruning job settings from
your previous installation. For information about specifying Database pruning job
settings, see the
Administration Guide
.
Core database data--
The upgrade process migrates all core data from the previous
database to the new database. Core data can consist of information about jobs,
media, sessions, devices, media pools, file path names, file names, and so on.
Log data--
The upgrade process migrates Activity Log data from the previous
database to the new database.
Session data--
The upgrade process lets you migrate the session data from the
previous database to the new database.
Note:
The process of migrating session data can take a lot of time. However, you
can perform file-level and session-level restores immediately after the upgrade and
migration process is complete.
Catalog data--
The upgrade process lets you migrate the catalog database data from
the previous database to the new database.
Note:
The process of migrating catalog data can take a lot of time. A progress dialog
does not display.
Product License Requirements
CA ARCserve Backup requires you to license your product to receive authorized and
uninterrupted access to the components, options, and agents. If you do not license CA
ARCserve Backup, it stops working 31 days after you begin using it.