Question about database maintenance 1

[FunkiMunki]

This is more of a question than a problem (I hope). I have just had to repair a corruption in an ARCServe VLDB database, and have set a maintenance routine in place to try and prevent corruption in the future.

The actual maintenance is taking a very long time to run. It's a 7GB database and Keybuild alone has taken over 4 days to run. Is this normal? What are other peoples experience with the database maintenance tools?

I really just want to know if this is normal, I'm concerned that there may still be problems with the database.

Thanks

 

[peeky1323]

Hi,

I have nearly the same size DB as you. keybuld also takes days. DBckeck takes about 30 hours. I now just bite the bullet and initialise just the astpsdat database when it blows up. The I just merge tapes as needed

Although I really need the DB to be intacted for the amount of restores I do, I can not afford any downtime on the backups to I can not wait for the tools to run over the 4 days.

Good luck!

 

[davidmichel]

Yes it is normal, however the more often it is run the quicker it will go.

It is better to run dchain prior to keybuild.

Also you can try using the -p parameter, sometimes increasing the # of pages will help it to go faster. see faq478-4386.

Defrage the drive prior to running the utilities, sometimes that also helps.

 

[mohamdr]

Don't waste your time maintining this database from my experiance I recommand you to use convert to sql database it is more stable ,or just initialise just the astpsdat database when it become large this the best thing.