Database Corruption (Arcserve)


Jump to: navigation, search

Database corruption affects detailed session records even if a merge is done on the tape. Consequently restore by session/tree/query does not work but the backed up data itself is unaffected. For a quick work around to enable the restoration of data without investigating/fixing database corruption choose Restore by Media. This does not rely on a Arcserve database but a whole particular session will have to be restored, although file filters (such as *.doc) can be specified.


Symptoms can be any or all of the following:



Corruption is usually in the astpsdat database as this contains session data and therefore the bulk of data associated with Arcserve; therefore it is prudent to start here. Like all Arcserve databases it can be presented in chunks to the filesystem itself (.001, .002 etc.) but the database name as a whole is always supplied to the VLDB utilities.

  1. For correct operation of the VLDB utilities every service should not be running apart from the Database engine. To do this run services.msc , find the services beginning with CA Brightstor and stop all of them apart from "CA Brightstor Database Engline."
  2. Open a commend prompt and change to the Arcserve directory, type: dbdefrag -a -L casdb;admin;secret astpsdat
  3. Followed by: keybuild -k -L casdb;admin;secret astpsdat

These commands can reduce the size of the database and therefore reduce the time for checks on the database if required. Test whether the issue is resolved, if the issue is resolved, you do not have to follow the remaining steps. If the issue is not resolved, go to step 3, and then follow the remaining steps.

4. dbfix -a -L casdb;admin;secret astpsdat

Depending on the amount of corruption and the size of the database this usually takes 12 hours or even several days. If it is still running after 48 hours or if the above command does not fix the corruption the next step is to reinitialise the database.

Personal tools