Comment about running keybuild utility

[BarbieGirl]

I was wondering if anyone can help me out on this one. I have been running out of disk space because the arcserve log files are so big. So, I have run through the steps of pruning etc. with no great success. I read the other thread on this issue and initializing the db was my next option.

Recently I stumbled across a 'solution' but I am not sure if I am wrecking my database (I would have to initialize anyway because of the space issue). On the surface it does not appear to harm the DB, because my restores have never been better.

What I did:
1. Ran full dbcheck on astpsdat db
2. Ran full dedefrag on astpsdat db
3. Ran keybuild on astpsdat db until the first record showed up and then stopped it (ctrl + c). My free space went from 100 MB to 1.12GB in less than 10 seconds (instead of waiting 2 days)! All the information appears intact, and all my restores are working. I did notice that when I left the keybuild to run for 2 days it used up all the space again.

Does anybody have any comments?

 

[Guest_imported]

For light to moderate ARCserve use:

Set pruning to 14 days. Reinitialize the DB every 6 weeks or so depending on use. Merge your last full backup after every reinitializtion.

For heavy users:

... who run elaborate rotations schemes and backup tons and tons of data, use SQL as your ARCserve DB. This is especially important in scenarios where restores must be done VERY quickly and VERY often. SQL all the way!

The DB utilities are for diagnostic purposes and have never and will never be a realistic way of maintaining the VLDB. They take far too long to run and if and when they do come up with errors you will spend FAR more time trying to slavage the DB than what it takes to reinitialize the DB and merge the tapes back in.

Best of luck!