New job takes the priority and the old job in queue fails

[Navadeepan_Pill]

Hi,

We have Netbackup 6 with MP3. We are facing a strange problem.

One policy is running. A new job comes to system and gets queued. After sometime, a second job kicks off and stays queued and waiting for the drive.

Now we have one job in Active state and 2 jobs queued.

When the active job completes, the second job which is in queue get started and run. So the first job which was in queue doesnt get the priority.

Prior to NB 6, this wasnt the case (i assume). The job which gets queued first, gets completed and so on.

So if i have 4 jobs in queue, the latest job which was queued run instead of the oldest one.

Pls. help

Best Regards

[Stumpr2 · Accepted solution]

If an active job is running and another job with the same volume pool and retention is queue'd then it will become active and write to the same tape that is already mounted. This cuts down on the number of mounts. Jobs that have the highest priority also become active first. It is not FIFO.

[Kelvin_Leoh]

Not only depending on whether the job is using the same pool/tape. The priority set for each job takes precedence first. For example, the 2nd queued job has higher priority, but the 1st queued job uses the same job as the active job.

It would unmount the tape and run the 2nd queued job first.

If, both priority are the same, 2nd job will be run. This is also somehow affected by the retry timeout, so happen the job is retry and the active job just completed, it will start that particular job.

Anyhow, there's a few factor that affects which jobs get started first.Message was edited by:
Kel

[Navadeepan_Pill]

Hi,

But this wasnt the case with NB5. We are facing this problem only after upgrade to 6.

Best Regards
Navadeepan