6.61 "update database" takes FOREVER and other problems

[jonno32]

We are running Arcserve 6.61 SP2a.. and my backups are taking 16-20 hours to complete. It updates the database for hours. The problem has gotten worse since installing the CA service pack. I'm also getting "read/write error in named pipes" when backing up individual mailboxes in Exchange. How do I convert to the VLDB database? The documention is non-existant. I did not install SP1(to my knowledge), we went straight to SP2a. Are there any other utilities I should be using on a regular basis to keep the dbase size down? The prune job runs every night, 4 hours prior to the backup. BTW... our dbase size is almost a gig. Should it be that big? I'm only backing up about 40GB per night. Thanks!

 

[monkeylizard]

Jonno32, I posted this in a new Tip Thread, but thought you might find it here easier. And no, your database should NOT be almost a Gig.

-----

Since there seem to be lots of database and performance related questions out there right now, I'm making this post to try to help out as many of you as I can.

I use ArcServeIT Advanced Edition 6.61 (Build834,SP2a) on Windows NT 4.0 (SP5). All information in this post is accurate for this configuration, but it will change for other OS's and ArcServe versions.

First of all I suggest that ALL ArcServeIT Admins take a look at Document # 16112 on the CA website.

http://support.ca.com/techbases/asnt/16112.html

This document is all about the RAIMA database and how to maintain it. RAIMA is the database type that ArcServeIT (at least 6.61) uses by default. You can specify Microsoft SQL for your database type during the initial install of ArcServe if you want, in which case all database maintaining must be done by a SQL Administrator.

There are basically four things you should be doing regularly with your database. These will help with a multitude of problems including performance since the database is used for all aspects of ArcServe.

They are Prune, Check, Repair, and Pack.

Prune
What: Removes old entries from the RAIMA database.
How to: From ArcServeIT Server Admin, click the Config button (wrenck and sprocket), select Database Engine tab and check the 'Enable Database Pruning' box. Schedule it to run once a day. It can run during your production day. Currently, I prune all entries after 30 days. You do not lose your data if you have older tapes, you'll just have to do a Merge of those old tapes if you need to restore from them later.
Problem: Leaves blank spots in the database causing it to eat disk space.

Check
What: Inspects the RAIMA database for errors
How to: Run the DBMGR.EXE program from the ARCSERVEIT directory on the ArcServeIT server. Sorry, CA didn't include this one in the StartMenu icons. I suggest you put a shortcut there. Select the 'Check' tab and Start a check on All Databases.
Problem: None

Repair
What: Repairs the database errors that Check finds.
How to: Run the DBMGR.EXE program again (should have a shortcut by now...HINT). Click the 'Repair' tab and run it on all databases.
Problem: Repairs can take a while, esp. the astpsdat database

Pack
What: Compacts the RAIMA database to re-claim disk space lost due to Pruning
How to: Run the DBMGR.EXE program from the icon you created earlier in your Start Menu. Click the 'Pack' tab and do a Full Pack on All Databases. After doing this once, and IF you are diligent about maintaining the databases, you can start using the Quick Pack.
Problem: This should only be done after a Repair has been done and this too can take a while.

Again, I can not stress this enough...I suggest that ALL ArcServeIT Admins take a look at Document # 16112 on the CA website.

http://support.ca.com/techbases/asnt/16112.html

Monkeylizard
-Isaiah 35-