Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ARCserve 2000 central database
- Thread starter pharos
- Start date
We moved to SQL server running locally on the Central DB server, and have the DB Engines start with the ARCserve account (not LocalSystem). Install all available patches (if still using VLDB, then do this before running SetupSQL). Maintenance is run once a week on the database. No more db problems.
The Raima/VLDB is very unstable, and should be avoided on everything but small servers.
The Raima/VLDB is very unstable, and should be avoided on everything but small servers.
I am an Arcserve user since version 6. I have had lots of problems with the Raima/VLDB, moreso as my database has grown. Now, when my database grows to nearly 4GB or so, my jobs will fail upon attempting to merge into the database. My only resolution is to re-initialize the database. This is a pain. Here are my questions:
1) I don't want to buy a SQL license, can I use MSDE instead?
2) If I move to a bigger, better, faster server will my problems with this database subside?
3) What exactly does pruning remove from the db? Doesn't seem to do much for us. What's a good rule (or rules) of thumb for pruning?
Any help is much appreciated!!!
1) I don't want to buy a SQL license, can I use MSDE instead?
2) If I move to a bigger, better, faster server will my problems with this database subside?
3) What exactly does pruning remove from the db? Doesn't seem to do much for us. What's a good rule (or rules) of thumb for pruning?
Any help is much appreciated!!!
I don't know if you can use MSDE. Test it out and let us know. 
There are limitations that could prevent it from being a solution. See
No, a faster machine does not make a difference. The database starts to choke once past 2GB, and forget trying to run any of the utilies, unless you don't need to backup for a couple of days.
Prune deletes out the details of a backup job (which is the bulk of the data). The details are a record 150 to 200 bytes per file/directory/registry value that is backed up.
If you do not have the entire machine selected, I recommend _not_ backing up the registry. It only provides for restoring individual keys, but consumes a lot of database space.
There are limitations that could prevent it from being a solution. See No, a faster machine does not make a difference. The database starts to choke once past 2GB, and forget trying to run any of the utilies, unless you don't need to backup for a couple of days.
Prune deletes out the details of a backup job (which is the bulk of the data). The details are a record 150 to 200 bytes per file/directory/registry value that is backed up.
If you do not have the entire machine selected, I recommend _not_ backing up the registry. It only provides for restoring individual keys, but consumes a lot of database space.
- Status