Jobs run twice / mystery job in queue?

[zabagar]

I have a few clients where ArcServe runs my job twice.
I have ArcServe 2000 (v7) SP4 (Build 1100). Running on a stand-alone W2K server.

I've cleared the job queue (even tried deleting the .qsd folder & letting Arc. re-make it).

If I start from a blank slate, and create a new backup job, then next morning I'll see that job "finished" in the queue plus another duplicate job with a "run now" status in it.

If I check the log, I can see this other job started as soon as my original one was completed. This second job will just run until it finishes (or more usually) fills the rest of the tape.

I can't figure out where these mystery jobs are coming from!!!

Why can't I make 1 simple full backup, have it run, then repeat the next night? Why would I be getting a second full backup job?

Any ideas?

 

[speshalyst]

Hi,

THis could possibly be a makeup job which tries to backup all the nodes\volumes that were not backed up on the first run..

Also, update AS2000 to Sp5.

So it Shall be Written!
So it Shall be Done!!

 

[zabagar]

Thanks,

I figured out what it was. Somebody made a batch file that contained command-line ArcServe backup commands in it....then they put it in the Windows Task Scheduler...so it ran every night on top of my backup.

I'm not sure what SP5 fixes...but SP4 has worked great for me. I tried downloading SP5 twice....the self-extracting file said it was corrupt & it bombed out during install.
So SP4 it is.

-z-