Pruning Purging Woes

[jvonkorff]

We've been having troubles associated with our ARCSERVE 6.6 for months. We think we have traced them to pruning and purging operations. We have an outside vendor, but it does not seem to have any insight on this problem at all.
We are Novell 5.1. We have an NT server running a cache database and application (lots of data), a 2000 server running remote access (very little data), a server running Groupwise 6, and our Novell Server which basically stores lots of documents. Our vendor has set up several batches to backup the data beginning at 11:30 PM nightly. It takes until about 5AM onto one tape: full backup.

Some time ago, our vendor turned on automatic pruning and purging, presumably because our database was getting too large. Since that time, we have had a series of issues, which manifest themselves in occasional server lockups or backup failures. On the weekend, we run a document index procedure (dtsearch), and that procedure cannot run with the pruning and purging operation turned on. It seems like pruning and purging go on constantly. If we turn off the pruning and purging option, then we get clear sailing. But eventually, we cannot drill down to files to restore, because the database, apparently, is too large. So we try turning on the pruning and purging manually, and then we lock up. What a nightmare.

I've run a search on pruning on this forum. I've read all that I can find. Two threads refer to a technical document, but that document says that it is for NT only. It seems like the dang pruning and purging operation is like the monster that devoured Cleveland; it never wants to stop and leave us alone. Any ideas. Is there diagnostic information we should be reviewing, etc.

Thanks for listening.

 

[susantci]

Hi there. I can sympathize with you. I have been dealing with Arcserve and Netware for years and years.

How large is you database? Have you tried running any repair process through btrieve? It sound to me like there is a corrupt record in your database that is causing you not to be able browse the tree.

There is the ability to set the time of the prune and purge to start. Will fine tuning that help? HOw old are the records bring pruned and purged? Why don't you do some manual deleteing of records you don't need in the databse with the pruning and purging turned off?

Just some suggestions!!

Good luck,
Susan

 

[ddaily]

If you have the resources, you might think about switching to SQL server database. I did that 2 years ago and I could let the database get as big as I wanted and the pruning took only minutes as opposed to all day. It was very easy to setup. Directory trees expanded immediatley.

 

[jvonkorff]

Are we talking MS SQL here; don't have it currently on our system.
I'm a lawyer by day and IS manager by all the rest of the time.
I program in Delphi--dbase and COM, but have limited SQL experience. Is there a technical document on setting up SQL
Thanks for your help and thanks Susan for your commiseration.
I'll check out the repair idea as well.
Yesterday, our vendor said what about trying Backup Exec. But it seems to me we'd be better getting this problem solved, rather than starting all over from scratch.

 

[zille]

do we talk about arcserve it/nw?
did you try exchanging folder \emptydb and \database folder (make a backup of emptydb before) and set new or no pruning/purging options?

the arcserve "database" is imho not really a database because you can not handle or find any specific in it in an acceptable time a year later when enlarged to several 100 mbytes.

sorry @CA.
sorry natives.

 

[jvonkorff]

Thanks for the answer. Only one year and 12 days after my last post. I'd forgotten about this post. In the meantime, we found that we could not backup Groupwise 6 on arcserve, so we have switched to Backup Exec. That has solved our pruning purging problem completely. Who knows, maybe we'll discover some other nefarious problem on BE.