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

Using a Microsoft SQL Server Database, Before installing BrightStor ARCserve Backup - error 3719

Page 204 highlights

Using a Microsoft SQL Server Database To run the keybuild utility, enter the following syntax: keybuild -k -L casdb;admin;secret [DBNAME] DBNAME is the name of the database that you want to repair (asjob, asmedia, asobject, asrhost, astape, astpdrv, astpsdat, asmsg, asmsgdat, or aslogerr). As keybuild runs, the status of the operations is displayed, ending with a final summary of the rebuilding process. ■ Dbfix-Use this utility to check each entry in the database for corruption and repair any errors found. To run the dbfix utility, enter the following syntax: dbfix -a -L casdb;admin;secret [DBNAME] DBNAME is the name of the database that you want to repair (asjob, asmedia, asobject, asrhost, astape, astpdrv, astpsdat,asmsg, asmsgdat, or aslogerr). As dbfix runs, the status of the operations is displayed, ending with a final summary of the repair process. Using a Microsoft SQL Server Database You have two database options when you install BrightStor ARCserve Backup- the standard VLDB database or Microsoft SQL Server (7.0 or 2000). By default, BrightStor ARCserve Backup installs VLDB on the server. If you want to use the Microsoft SQL Server database, your machine must have a minimum of 256 MB of RAM and meet the following requirements: ■ MS SQL version 7.0: - Service Pack 3 - ODBC Manager version v2.50.3006, v3.0.28.22, v3.510.3002.13, v3.510.3002.23, v3.510.3711.0, v3.520.3719.9, or v3.5204314.0 - SQL Server driver version v2.65.0201, v2.65.0252, v3.60.0319, v3.70.0623, v3.70.6.90, or v3.70.8.12 ■ MS SQL 2000: - ODBC Manager version v3.520.6526.0 or higher Note: Before installing BrightStor ARCserve Backup, verify that Microsoft SQL is installed. If you select Microsoft SQL server during the setup by running the SETUPSQL.EXE utility after the installation, BrightStor ARCserve Backup creates a database under the SQL server and uses it as the backup and restore depository. Note: For the SQL database to function properly, it must be started using Microsoft SQL Service Manager. 8-18 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

Using a Microsoft SQL Server Database
8–18
Administrator Guide
To run the keybuild utility, enter the following syntax:
keybuild -k -L casdb;admin;secret [
DBNAME
]
DBNAME is the name of the database that you want to repair (asjob, asmedia,
asobject, asrhost, astape, astpdrv, astpsdat, asmsg, asmsgdat, or aslogerr). As
keybuild runs, the status of the operations is displayed, ending with a final
summary of the rebuilding process.
Dbfix—Use this utility to check each entry in the database for corruption and
repair any errors found.
To run the dbfix utility, enter the following syntax:
dbfix -a -L casdb;admin;secret [
DBNAME
]
DBNAME is the name of the database that you want to repair (asjob, asmedia,
asobject, asrhost, astape, astpdrv, astpsdat,asmsg, asmsgdat, or aslogerr). As
dbfix runs, the status of the operations is displayed, ending with a final
summary of the repair process.
Using a Microsoft SQL Server Database
You have two database options when you install BrightStor ARCserve Backup—
the standard VLDB database or Microsoft SQL Server (7.0 or 2000).
By default, BrightStor ARCserve Backup installs VLDB on the server. If you want
to use the Microsoft SQL Server database, your machine must have a minimum of
256 MB of RAM and meet the following requirements:
MS SQL version 7.0:
Service Pack 3
ODBC Manager version v2.50.3006, v3.0.28.22, v3.510.3002.13,
v3.510.3002.23, v3.510.3711.0, v3.520.3719.9, or v3.5204314.0
SQL Server driver version v2.65.0201, v2.65.0252, v3.60.0319, v3.70.0623,
v3.70.6.90, or v3.70.8.12
MS SQL 2000:
ODBC Manager version v3.520.6526.0 or higher
Note:
Before installing BrightStor ARCserve Backup, verify that Microsoft SQL is
installed.
If you select Microsoft SQL server during the setup by running the
SETUPSQL.EXE utility after the installation, BrightStor ARCserve Backup creates
a database under the SQL server and uses it as the backup and restore depository.
Note:
For the SQL database to function properly, it must be started using
Microsoft SQL Service Manager.