Retry Done (failed)/Incomplete

Does both jobs are from same policy and client?

double click on both jobs, take the snap of popup window (job details) and attach to this post.

Incomplete job will go to Done state after a certain time - this is controlled by settings in the master's Global Attributes.

PS:
Why not troubleshoot the reason for failed job instead of resubmitting the same job over and over!
40 Incomplete attempts already??  

Yes, same client on MS-Windows Policy

Detailed status:

I am looking for Job overview tab..

does any of the job submitted manuallly or both or scheudle jobs?

yes.. as Marianne said.. what is the values in Global addributes.

job retry delay, number of scheudle backup attempts

and

"Move restore job from incomplete state to done state"

Indeed, set to 72 hours in my case.

The "real" problem is alredy solved.

With a big backup window, a retry set to 10 min, and a lot retry/hour, you will see a lot of attemps.

But, in all cases, if there is one errror, the first job is going to "done" instead of "incomplete"....

Only scheduled jobs.

Sorry - Clean-Up, not Global Attributes...

Again - rather troubleshoot backup failures than concentrating on when or why jobs go from Incomplete to Done state...

agreed with Marianne..

troubleshoot and fix it..

72 attempts in 12 hours is too high.... one attempt in every 10 min...

I never recommend this setting...

Job overview

I was intrigued - the best I can come up with (so far) for the reasoning regards a new job or incomplete is the following statement:

In the following situations, NetBackup starts a new job instead of resuming an incomplete job:

• If a new job is due to run, or, for calendar-based scheduling, another run day has arrived.

• If the time since the last incomplete backup was longer than the shortest frequency in any schedule for the policy.

• If the time indicated by the Clean-up property, Move backup job from incomplete state to done state, has passed.

http://www.symantec.com/business/support/index?page=content&id=HOWTO34475

The first job started (at the latest) 23:59:59 & failed the following day - so we're into another run day - but it would be dependant upon whether your schedule for this *is* actually calendar based (or maybe it doesn't really matter & NB is just being quirky?)