Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Backup fails updating database

Status
Not open for further replies.
Oct 3, 2001
76
US
Hi all,
I am having problems with Arcserve 6.61 Build 834 SP2a.
After it finishes it's backup job, it then writes to the database, the problem is is that it never finishes writing to the database, it hangs there.

Any thoughts?

Thanks in advance.
 
stop arcserve job, database, tape engines n then go to arcserveit folder-database folder, delete all the files starting with 'r' and then go to arcserveit-temp folder and delete all the .cat files..start all engines and try the backup.
also if the size of the database folder is more than 1.5 gigs then u need to initialise astpsdat..which means..losing all the database records and in case of restore u need to merge the old tapes.
thanks Happiness is a daily decision
 
Are there any left over files in arcserve$\temp? If so, then maybe one of those are corrupt?

Also, what is the size of the .CAT file(s)? If they are large (backing up a lot of files), then it can take quite a while to merge.
 
Sure this will solve the porblem:
-Make a copy of the database folder
- Make sure that no jobs are active, and stop all the engines
- restart only the database engine
- Go to Start > Programs > Arcserve > Arcserve Server Admn > go to database
engine tab > operation menu > initialize database > select 'the database
to be initialized > choose 'astpsdat' and click on initialize
- Once the initialization is successful, run a merge job and update the
database with the tape information, do the following to run merge:
Go to manager menu > utilities > merge > select the tape and submit the
job
- Now go to Restore by session and you should be able to expand the sessions
 
Errr, that was not me who wrote the above.

Anyhow, you have a corrupt database. Initialise (delete all and start again basically) should work well. Have you upgraded from Raima to VLDB at all?

g
 
I think this is the fix to my 2000 corruption as well. At least that is what I will be trying tomorrow because what started out as missing version history has been escalted to unable to access database errors etc. Just alot of fun. We have sercurity files in our tmp folder. Now we have a large db as well (we can run 30-60 jobs a night or more) so we have about a 16gb db and they are estimating days to a week to run any utility on it. What other complications can we have and/or what will I lose by doing the above (GURU) fix?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top