After upgrading to 6.5.2a the duplication schedules wouldnt run at all. This was fixed with new nbpem engineering binaries from Symantec. Now the jobs are running as scheduled, but regardless of my settings all duplication jobs forces itself to run with priority 99999 no matter what i do. The following is true:
- Default priority level for duplication jobs are set to 0 (master server properties)
- Default priority level for staging jobs are set to 0 (master server properties)
- All disk storage units (basic disk) have their duplication schedule job priority set to 0
- Netbackup services was restarted after the settings was changed
All __DSSU jobs will show the correct priority (0), but all child Duplication jobs keeps popping up with priority 99999. The real problem is that the duplication jobs are holding all other backup jobs from access to the tape resources, and the backup jobs will eventually fail with code 196 (backup window closed).
Does anyone have a clue? Is there something ive missed, or is this just another bug in the 6.5.2a patch?
Thanks in advance :)
