02-18-2014 02:03 AM
Good morning,
If a job failed, the first attempt state is "done" then a new job is submitted, if it failed too, it's going to state "incomplete", then retry.
Why not at the first job?
Best regards.
02-18-2014 02:16 AM
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.
02-18-2014 02:24 AM
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??
02-18-2014 02:34 AM
Yes, same client on MS-Windows Policy
Detailed status:
02-18-2014 02:45 AM
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"
02-18-2014 02:45 AM
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"....
02-18-2014 02:49 AM
Only scheduled jobs.
02-18-2014 02:53 AM
Sorry - Clean-Up, not Global Attributes...
Again - rather troubleshoot backup failures than concentrating on when or why jobs go from Incomplete to Done state...
02-18-2014 03:00 AM
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...
02-18-2014 03:05 AM
Job overview
02-18-2014 03:06 AM
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?)
02-18-2014 03:11 AM
Agreed with you, the error 13 is alredy solved, retry are too high.
02-18-2014 04:17 AM
Very interesting,
for the calendar based, we have the option "retries allowed after run day", nothing for frequency based.
1 day frequency for my policy, i think at 00:00 a new day start.
I'll do some test.
Thanks a lot Andy.
02-19-2014 12:35 AM
Same error today, i have changed start windows to 00:05, error 58, state done... then retrie.
02-19-2014 12:44 AM
I have no idea why you are concentrating on 'Retries'.
Rather troubleshoot the problem(s)...
You may want to start a new discussion for each error code that you are seeing.
When you do, please include as much info as possible.
e.g. Client OS (and patch level), Client NBU version, Server OS, Server NBU version, as well as all text in Job details.
02-19-2014 12:51 AM
Because it's not working as intended.
I have no idea why you are concentrating on my error code, not on my question.
02-19-2014 01:36 AM
do make sure the tme 00:05 is master server local time change.. (considering the time chage flexiblity in the GUI)
you can confirm this by running the policy list command in CLI
bppllist <policyname> --L
the time is correct..
then run the below command soon after the first attemp got failed and moved to Done state.. and before it start the next new job and attach the output
nbpemreq -subsysyems 1 screen
02-19-2014 02:27 AM
What is the Policy Type for the job going to Done state?
Is Checkpoint restart enabled in this policy?
Failed jobs will only go to Incomplete state if Checkpoint restart is enabled in the policy.
Checkpoint is only available for Standard and MS-Windows policies.
02-20-2014 02:12 AM
I can't do this, the job stay in incomplete state and go to done when the new job start.
02-20-2014 02:16 AM
MS-Windows policy, with checkpoint restart.
Wan clients, with resilient network.
Source dedup, change journal.