ArcServe hanging 1

[jockbir]

Running ArcServe 2000 on a Windows 2000 Server.
When we reboot the server the backup clears and schedules to run at next scheduled time but it gets to 99% and says it cancelled but it reallly is still active at 99% and if you stop it is hangs at stopping.
What is even more frustrating we are not sure where to check for error messages just the above, but it had been working for a very long time with no problems.

 

[davidmichel]

1st update

http://supportconnectw.ca.com/premium/storage/downloads/nt/2000/arc_eng_menu.asp

Next put the Job Engine in debug mode for additional details in the activity log.

Next time it happens highlight the job in the queue and right click Properites. Check to see which file it is backing up at the time.

When there are no jobs running the ARCserve\Temp directory should be empty. If there are *.cat files run mergecat.exe to merge them into the database or just delete them if you don't care if they are meged in. If there are any tmp files just delete them.

 

[jockbir]

Thanks David. I received some more information.

We are on ARCservIT 6.61.
The backup status shows 99% completed, it does not eject the current tape or ask to load a second tape. The last enty in the job log for the backup is Next media full, ID 6F85 sequence #2. If you right click and stop the active job and it hangs at status stopping. If the server is rebooted it clears the backup job to be rescheduled for tonight but will have the same status tomorrow.

Am I reading this right that it is looking for another tape, the next tape is not overwrite but been used before and it hangs up???

If so, after reboot what????

Thanks

jockbir

 

[vschumpy]

ARCserve 6.61 isn't supported on Windows 2000 unless you have a build 897 or 914? version. These were interim versions between 6.61 and AS2000 with very basic W2K backup functionality (no system state backup). To be honest even these weren't particularly great.

If the build number in Help about begins with 834 or 885 it was never supported on W2K - most likely you'll have problems with the database engine and it's probably why it hangs at 99% trying to update the database.

 

[davidmichel]

Sad but true vschumpy is right. 6.61 is not certified for W2K. That interm release to W2K was not around very long. It was just a stop gap measure until ARCserve 2000 could be released. Once ARCserve 2000 was released that special update was pulled and no longer available.

For what it is worth here is the ARCserve 6.61 page. The link to the updates is there.

http://supportconnectw.ca.com/public/storage/asitntsupp_6.6x.asp

So for now you might want to consider reconfiguring the job so that it does not record database information. Just do a merge if you need to do a restore. That will give you time to think about the upgrade to 11.1.