Backup Status of Crashed

[Jillaroo]

Backup job scheduled to run overnight has been crashing. It doesn't do it every night but when it does crash it is always in the same place, (i.e. Session 8 after the 1st 5 Mailboxes have been done).
It has been happening on different tapes & I've changed scheduled start times but it still happens.
Dr Watson comes up with the message WIN NT Error Code = 87 Could not attach to the application.
It causes the B/up job to hold but when I make it ready again the following morning it goes through the B/up without a problem.
I am using ArcseverIT v6.61 on a WINNT4 Exchange Server.

 

[TheLad]

I had this on an NT server running AS IT v6.61. After ages of faffing around, I deleted the job and resubmitted it from scratch and it worked ok after that. Would like to think that this is your problem, but does lightning strike twice? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[kewl]

have you applied the latest patch?

 

[Jillaroo]

Hi 'Kewl',
I haven't applied any patches. I am currently on build level 834SP2A. Can you recommend a patch that may help?

Hi 'TheLad',
In the meantime I'll try your suggestion of deleting & resubmitting the job.

 

[Guest_imported]

Do you have exchange anti-virus on the database? this could be causing some problems...

 

[Jillaroo]

Hi ARCserve guru

I don't have Exchange anti-virus on the database as the server has Sophos anti-virus installed.

 

[TheLad]

I think the latest SP for ArcserveIT 6.61 is SP2 (the Guru will correct me if I am wrong) which can be downloaded from here:

http://support.ca.com/Download/patches/arcserveitnt.html

May be worth applying the SP and seeing how you go. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Jillaroo]

I have the latest SP installed. I have deleted the backup job & re-created it and at the moment it seems to have cured the problem.
Thanks to all of you for your help.

 

[VETINO]

hi i think u can create the new job and afterwards you log out yourself from the Server. Make sure that the DB-Agent is admin from the service account in all (3) instances.
And the latest Service Pack is 2a!!!
On the page of ca support there is patch (LO76172.CAZ) which you should install. To find you can it on

http://support.ca.com