Backup sticking at 99% and then unable to initialize database

[Guest_imported]

On several occasions one of the backup jobs sticks at 99%. I have to stop the job engine service and then kill the ASRUNJOB.EXE process before it will actually stop the job. I then normally have to reboot the server before I am able to initialize the database.

The same thing has happened again - I have rebooted the server but forgot to initialize the database - the backup job stopped at 99% again last night. When I tried to initialize the database, it comes up saying "Please close other ARCserveIT applications and try again". When I click OK it comes up saying "Initialization process has been completed". Will this have initialized the database or do I need to kill another process before initializing the database?

I would prefer not to have to reboot the server again and wonder if there is a way I can do this without the reboot.

I am quite new to this so any help is gratefully appreciated

 

[ARCserveGuru]

rebooting is not necassary. also, killing the asrunjob as 99% will cause damage to the database, but if it is stuck at 99% (i.e. when it is updating the database) then you already have a problem with the database. Check and see if there are any errors in the activity log which say "unable to log in to database engine" or any similar entries. If you do then could you paste them here

Thanks,

guru

 

[Guest_imported]

Many thanks for replying. The activity log seems to suggest they were stopping at a couple of users inboxes. However, I seem to have resolved this problem (at least temporarily). I went in to Services and stopped and then started the ARCserveIT Database, Job, Message and Tape Engines. I then was able to initialize the database. On checking the job status of the backup this morning - it seems to have worked perfectly. Maybe this is just coincidence - or luck!!

 

[ARCserveGuru]

Well, keep us posted on the progress

guru

 

[iandrewmartin]

I noticed this problem on our backup box a couple of weeks ago.

Solution was to chek the permissions to make sure that the SYSTEM permission (in WInNT) had access to the ARCServe share.

For some reason (I think another operator reset permissions, though no-one will admit to it) these had changed.

Reset permissions on the share and on the cascaded folder and files in NTFS and all appears to be OK now. THis may or may not help.

Best

Andrew

 

[Guest_imported]

Thank you Andrew for taking the time to reply. I have to say, after having initialized the database, all seems well with the backup. Absolutely no problems at all. I think this seems to have been enough to fix the problem for us - however, if something goes wrong - I will let you all know!!