The disk storage unit from time to time has an image on it that has not be duplicated and when the hourly de-staging schedule runs there are entries in the job monitor, no errors but no child duplication jobs are run. This can happen two or three times before it springs into life.
Are there any conditions in which the duplication will not run that I am not seeing? I just watched it miss 3 automatic hourly attempts, and the manual reallocation does the same. (When this condition occurs a manual duplication job from the "Catalogue" in the gui does work.)
What log files should I be looking at to diagnose the issue? The Job files just look normal, as if they have not found any images to duplicate.
Job for the DSSU job shows it wizzing through in a few seconds without it picking anything up (compared with a few hours for a successful duplication)
05/12/2012 07:07:48 - requesting resource ####.NBU_CLIENT.MAXJOBS.####
05/12/2012 07:07:48 - requesting resource ####.NBU_POLICY.MAXJOBS.__DSSU_POLICY_#####-stagingA
05/12/2012 07:07:48 - granted resource ####.NBU_CLIENT.MAXJOBS.####
05/12/2012 07:07:48 - granted resource ###.NBU_POLICY.MAXJOBS.__DSSU_POLICY_#####-stagingA
05/12/2012 07:07:48 - begin Parent Job
05/12/2012 07:07:48 - begin Disk Staging, Start Notify Script
05/12/2012 07:07:48 - Info RUNCMD(pid=11280) started
05/12/2012 07:07:48 - Info RUNCMD(pid=11280) exiting with status: 0
Status 0
05/12/2012 07:07:48 - end Disk Staging, Start Notify Script; elapsed time: 00:00:00
05/12/2012 07:07:48 - begin Disk Staging, Execute Script
05/12/2012 07:07:50 - started process bpbrm (24183058)
05/12/2012 07:07:55 - end writing
Status 0
05/12/2012 07:07:55 - end Disk Staging, Execute Script; elapsed time: 00:00:07
05/12/2012 07:07:55 - begin Disk Staging, Validate Image
Status 0
05/12/2012 07:07:55 - end Disk Staging, Validate Image; elapsed time: 00:00:00
05/12/2012 07:07:55 - begin Disk Staging, End Notify Script
05/12/2012 07:07:55 - Info RUNCMD(pid=6976) started
05/12/2012 07:07:55 - Info RUNCMD(pid=6976) exiting with status: 0
Status 0
05/12/2012 07:07:55 - end Disk Staging, End Notify Script; elapsed time: 00:00:00
Status 0
05/12/2012 07:07:55 - end Parent Job; elapsed time: 00:00:07
the requested operation was successfully completed(0)
There was definitely a backup image on stageA at the time with only one copy (it is still there from 0200)
sclatstdb1:/usr/openv/netbackup/logs> bpimagelist -L -backupid sclatstdb1_1354672800
Client: ######
Backup ID: #####_1354672800
Policy: #####
Policy Type: Standard (0)
Proxy Client: (none specified)
Creator: root
Name1: (none specified)
Sched Label: Daily_Cold
Schedule Type: FULL (0)
Retention Level: 2 weeks (1)
Backup Time: Wed 5 Dec 02:00:00 2012 (1354672800)
Elapsed Time: 1968 second(s)
Expiration Time: Wed 19 Dec 02:00:00 2012 (1355882400)
Compressed: no
Client Encrypted: no
Kilobytes: 308251040
Number of Files: 36039
Number of Copies: 1
The other image that currently sits on the same staging area successfully duplicated at 02:28, which proves that the mechanism does work (most of the time) It's just on occasion there are several runs of the DSSU policy that don't kick off the duplication when it should. A manual run of the reallocation has the same effect. Help me please!
