NBU 7.6.0.2 "duplication" jobs

[JaquesC]

Hi there,

I have a master that is doing allot of duplication jobs, I am unsure and the job history information doesnt really stipulate what its duplication and who the client is etc...

Also its not relating to a policy that I can clearly look at. I checked my policies and I am not really running inline duplication jobs on any of them, specified on the policy level atleast, they just keep failing and the odd one from time to time does go through. messages I see regarding failure is "no images available" or "doesnt match the search criteria cannot find image"

I am using Disk staging on demand, and then of course off to the tape drives once dumped on disk, could this be the "Duplication" that is happening that I see where it then writes to tape and will remove from disk afterwards?

In the global attributes of the master I also have a maximum total copies set to "2"

How can I properly get a perspective and get more in-depth details on where the duplication is coming from, as it really gives me nothing in the activity monitor.

Regards,

JC

[RamNagalla]

could you post the screenshot of the activity moniter that is filtred with duplication.

and you said you were using the Disk staging.. by any chace have you have you see the job policy with DSSU.

just filter the activity moniter and see if that is one...

you also need to check the staging schedule in the Disk staging storage unit from GUI-- storage units...and co realte the time too to get some idea..

[JaquesC]

Yes disk staging is running with the DSSU policy, unable to take screenshot right now but DSSU_Policy runs regularly and I can see it running. You seem to come towards a conclusion when talking about DSSU policy, please tell me what do you think the next steps are?

[RamNagalla]

in activity moniter DSSU job containts the storage unit name under the policy tab..

get the storage unit name and then go to GUI---> storage units ---> double click on the storage unit that you got..

in the popup .. you will find the radio button with "Staging schedule" click on that to find the the staging schedule..

that is the time when the duplication jobs get triggred...

you can alter the time of turn off the schedule time tooo if you want.. but if you take out the scheudle time , staging wil never happend and backup wills tay on disk only and never to to tape... 

[JaquesC]

Sorry, This is still an issue, I am attaching a screenshot of one of the duplication jobs that started this morning at around 8 AM.

the client is one of the media servers, now based on what we discussed the DSSU policy sends the data off to tape as per the schedule, and the only duplication jobs that fail (and in bulk, there are lots of them that fail immediately at the same time) are the media servers/master

its not a normal client duplication job to tape, its the master/media servers that tries to duplicate their "data" to tape like the others. But I dont need that do I? I dont want them to be included in the DSSU policy or do any form of duplication etc...

See screenshot, almost no information at all. Also a screenshot of the failed duplication job.

[JaquesC]

EDIT - 18/6/2014 @ 8:35AM

Please see attached 4th pic, this is a duplication job  that actually ran without issues, and as we understand the duplication is the "disk staging" piece that is happening based on the schedule, and yes the 8AM start is correct and that is when I set the staging schedule, and in the list of items, this looks more like a correct duplication to me because its writiing the images of the other jobs that have been set for disk staging. why are the other's failing and almost no information on them in terms of origin selections etc....

[RamNagalla]

hello,

I am not able to see the image 2nd and 3rd.. please post them again..

and now, you are sure that the duplication are not from the Disk staging and trying to find the tirgger for these jobs...

now its time to look into to the logs..

please attach the admin log from /usr/openv/netbackup/logs/admin

[JaquesC]

attached is everything that we need, please take a look and let me know.

[RamNagalla · Accepted solution]

hi ,
the above job is also from Disk staging..

1) job id in above screenshot :-  165677

2) image ID associated with this job ID as per log   :-zajhbdc01_1403020874

08:33:57.292 [10704.7208] <2> build_write_str: START BACKUP -jobid 165677 -c zajhbdc01 -b zajhbdc01_1403020874 -cl DC_GC_BACKUP -sl DC_Incr -shm -blksize 262144 -bt 1403020874 -st 4 -rl 3 -date -1 -ct 13 -src_cn 1 -cn 2 -df 1 -use_vnetd

3) this image ID is added to work list for the disk staging job

08:00:24.279 [10704.7208] <2> add_to_worklist: source blknum:0 ,starting blknum:0 for backup id zajhbdc01_1403020874

08:00:23.343 [10704.7208] <2> logparams: -remote -DS -src_dssu DiskStaging_ZAJHBSRV09 -number_copies 1 -priority 99999 -jobid 165621 -dstunit zajhbsrv09-hcart-robot-tld-0 -dp NetBackup -owner *ANY* -Bidfile C:\ProgramÀ Files\Veritas\NetBackup\Logs\user_ops\bpcd-08432403071219740876000000001-a05876 -cn 1 -fail_on_error 0 -rl 3 -requesting_host zajhbsrv09 -cmd_lc_messages C -cmd_lc_time C 

08:33:57.277 [10704.7208] <2> bpduplicate: Duplicating policy DC_GC_BACKUP schedule DC_Incr backup id zajhbdc01_1403020874 copy 1 created on 06/17/2014 18:01:14 on source path E:\backup_to_disk

for the image which is located in E:\backup_to_disk.

so E:\backup_to_disk is the one which is enabled with the Disk staging...