Arcserve 2000 - jobs crash after installing Arcserve SP5 1

[dee16]

Problem\Symptoms:
Backup jobs last result is crashed, the job is on hold and doesnt re-schedule properly. Problem occurred after installing Arcserve Service Pack 5.

Arcserve 2000 - Workgroup Edition V7.0 Build 1110 (Service Pack 5)running on Win2K Server SP4

Windows Event Log:
The application, , generated an application error The error occurred on 02/16/2004 @ 22:13:01.778 The exception generated was c0000005 at address 77E1A415 (RegisterClassA)

Dr watson log (Start-run-drwstn32)
Application exception occurred:
App: (pid=3428)
When: 10/02/2004 @ 23:39:51.325
Exception number: c0000005 (access violation)
*----> Task List <----*
3428 asrunjob.exe

Note: pid 3428 is asrunjob.exe – the arcserve job engine

Cause:
Jobs were set to backup the system state and had CRC verification options turned on.

Solution:
Job Options - Set backup job verification to none

 

[mohamdr]

Thanks for the info....

 

[dee16]

I also emailed this problem to Computer Associates Tech Support and here's the reply:

Please change the following settings:
Manager > Backup > Options > Verifications
Change the backup verification settings to &quot;none&quot; or &quot;scan backup media contents&quot;
This will solve the problem.

 

[wjlight]

I'm suffering with the same problem. The job is shown crashed although according to the logs it has almost completed correctly. For me it is a sometimes thing although it happens more often that not.

The the last entries in a job log from a normal terminiation looks like:
Elapsed Time.................. 1h 4m 0s
Average Throughput............ 178.55 MB/min

Totals For.................... Job
Total Sessions................ 6
Total Directories............. 4,776
Total Files................... 60,232
Total Skips................... 18
Total Mismatches.............. 28
Total Size (Disk)............. 14,463.74 MB
Total Size (Media)............ 10,247.18 MB
Elapsed Time.................. 1h 15m 17s
Average Throughput............ 192.12 MB/min

Totals For.................... Job
Total Sessions................ 10
Total Directories............. 58,645
Total Files................... 158,902
Total Skips................... 0
Total Size (Disk)............. 14,549.17 MB
Total Size (Media)............ 10,730.75 MB
Elapsed Time.................. 1h 25m 4s
Average Throughput............ 171.03 MB/min

Backup Operation Successful.

The last arserve.log entries in a successful job are with detailed logging turned on:

20040219 034510 375 Number of Mismatches: 0
20040219 034510 375 5,432.81 MB Read from Media.
20040219 034510 375 Elapsed Time: 34m 37s
20040219 034510 375 Average Throughput: 179.24 MB/min
20040219 034510 375 End Impersonation.
20040219 034510 375 TAPE EXPORT: Eject Tape flag : 0, Export Mask : 0
20040219 034510 375 ** Summary for Job **
20040219 034510 375 10 Sessions.
20040219 034510 375 58,645 Directories 158,902 Files (14,549.17 MB) Backed Up to Media.
20040219 034510 375 10,730.75 MB Written to Media.
20040219 034510 375 Elapsed Time: 1h 25m 4s
20040219 034510 375 Average Throughput: 171.03 MB/min
20040219 034510 375 Backup Operation Successful.
20040219 034530 375 Run Command: &quot;c:\arcserve\winxp2.bat&quot;.
20040219 034530 Reschedule Backup Job for 2/26/04 at 1:00 AM.

The last entries in a job log from a crashed job are:

Elapsed Time.................. 1h 3m 54s
Average Throughput............ 178.83 MB/min

The last entries in the arserve.log for a crashed job are:

20040220 034330 377 337 Directories 4,315 Files (6,204.78 MB) Compared to Media.
20040220 034330 377 Number of Mismatches: 0
20040220 034330 377 5,432.81 MB Read from Media.
20040220 034330 377 Elapsed Time: 34m 33s
20040220 034330 377 Average Throughput: 179.58 MB/min

Everything is identical up to the &quot;End Impersonation.&quot;

You can see these were two identical jobs run one night apart in the same environment. 375 completed successfully. 377 crashed.

I upgraded to SP5 just because it was there to be had. I may have to tear everything apart and go back to SP4 which had been rock solid for me.

 

[dee16]

I found nothing useful in the arcserve log, have a look in the windows event log or dr watson log. Did you try turning the verify options off?

 

[wjlight]

Nothing in event log. Dr Watson identifies asrunjob.

Yes, turning verification off solves the problem. I will grant you that the chances of error may be small without verification but they do exist. Verification is part of the base application and it was working before SP5.

I wonder if there will ever be a robust solution for this problem?

 

[aeraspor]

I am having the same problem. I am a little concerned with turning off the verification though. At whch point, should I set up a seperate job to verify after the back-up is finished? And if so, how do I do that?

Please advise.

Allison

 

[wjlight]

Even though the job is shown as crashed, it is actually successful. The ArcServe database has been updated and you can do restores. It is just a nuisance to have to manually reschedule the job and I dislike from the esthic point of view having the crash symbol displayed.

I have never tried to manually do a compare after one of these crashes. You can set up a compare job from the utilities menu under the manager menu.

 

[meggaz]

Had same problem - using above comments found that problem occurs if any verification is set when a backup job that includes SYSTEM STATE is run.
My temp solution was to run 2 backups, one for the SYSTEM STATE with verification set to none followed by an appended backup of the rest of the system with verification enabled.
CA have confirmed this to be a problem and suggested keeping an eye on their support website for a patch to be published.

 

[wjlight]

meggaz - Thanks for the heads-up!

 

[richiepuk]

Stopping the verify is not really a fix, its a work around. Does anyone have a good answer, I backup a lot of servers, need to verify and don't want to setup seperate jobs.

 

[nobeta]

Looks like a patch is on the CA website today for this error.

http://support.ca.com/Download/patches/asitnt/QO52528.html

Good News. Lets hope it works.

 

[nobeta]

Ok, now I am confused. I downloaded the QO52528 and unzipped the dll's with the cazip utility. The instructions say to Rename asbackup.dll in X:\Arcserve to asbackup.dll.QO52528.Rename ascompar.dll in X:\Arcserve to ascompar.dll.QO52528.Rename asscan.dll in X:\Arcserve to asscan.dll.QO52528. Copy the asbackup.dll, ascompar.dll asscan.dll to X:\Arcserve. However the dll's included in the download are the ascompar.dll and astask.dll. There is no ascan.dll or asbackup.dll to copy to the Arcserve directory. And whats with the astask.dll included in the download? I guess I will wait for futher clarification on this.

 

[wjlight]

Also, what is Apply_PTF that is referenced in the patch writeup and how is it used?

 

[edarvas]

CA has finally published yesterday (april 4) a correction to the confusing explanations of QO52528. See QO52950:

http://support.ca.com/Download/patches/asitnt/QO52950.html

. Not tested yet, but it seems to be the the right patch.

 

[nobeta]

This is good news!

 

[dtsols]

Similar problem as above: Win2k SP4 just installed, ARCserve 2000 SP5 updated recently, backup appears to be O.K. but crashes at the end when doing verify of System State.

I am removing the verification option and rescheduling for 3AM. I'll see if it works tomorrow and let you all know!

Regards

 

[vschumpy]

well if you'd looked at the patch page here :

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

You'd see there is a post-sp5 patch for exactly this problem.