Forum Discussion

mgmasterv2's avatar
mgmasterv2
Level 6
8 years ago

Slow SLP Duplication Jobs

hi ,

Im using SLP policies ( backup to disk -Local Disk then duplicate to tape -IBM TS), recently duplication jobs take a lot more time to complete ( around 10-12 hours for each) when i check Netbackup i can see it will find right media right away and loads it in tape drive very fast but the duplication job will hangs at "Waiting for positioning of Media ID" for about 10 hours.

any help here would be apperciated.

thanks!

NBRB logs attached to this post.

Netbackup 7.7

Windows Server 2012 R2

IBM TS Series LTO-6

 

2008) Not Applicable
7.7
duplication
NBU
NetBackup
Performance
SLP
  • Marianne's avatar
    Marianne
    Level 6
    8 years ago

    This sounds like a hardware issue.
    I have seen something similar where the tape drives (same make/model) had different levels of firmware.
    Media that was written by newer firmware was later on loaded in a drive with older firmware. 
    The drive with older firmware was battling to position the media and eventually fail with 'media position error'. 

    Can you confirm firmware levels on tape drives?
    How old are the tapes? Can you see different behaviour between old (reused) tapes and new media? 

    By the time you see 'waiting for positioning'  bptm process on the media server is waiting for tape drive to position and report back success.
    We need bptm log to see why positioning is taking so long and not produce an error much earlier. 

    bptm log on the media server should be at fairly high logging level - 3 at a minimum. Level 5 will probably be best.

    Ensure that you also have VERBOSE entry in vm.conf on the media server.
    Restart Device Management service after adding this entry.
    Hardware issues will now be logged to Event Viewer System and Application logs. 

    • mgmasterv2's avatar
      mgmasterv2
      Level 6
      8 years ago

      thanks for your prompt reply.

      actually this is possible because Library came with one drive and after a couple of months i added an aditional drive to it.

      but backup to tape works fine it's just duplication jobs that have this problem.

      • Marianne's avatar
        Marianne
        Level 6
        8 years ago

        We still need bptm log - as well as Job details for backup job and Job details for duplication job.

        Job details will give us timestamps and bptm PIDs that we can use to trace each of the jobs in bptm log. 

        nbrb log shows at 10:09 that the robot/tape STU is busy and resource can therefore not be allocated. 

        cannot allocate, resource is busy LCM_servernbsrv01-hcart2-robot-tld-0


        Same 'resource busy' message at 10:11, 10:14, 10:19, 10:21, 10:24, 10:29, 10:31, 10:34, 10:39, 10:41, 10:44, 10:49, 10:51, etc.
        This goes on and on...

        This does not seem to be related to your issue with lengthty wait for positioning as resources are allocated at this stage and waiting for tape drive to report successful positioning. 

        What else is active and using the tape drives at this point in time? 

        Just giving us nbrb log is not helping.... 

  • mgmasterv2's avatar
    mgmasterv2
    Level 6
    8 years ago

    and it's happening to all duplicate backups VM - WIndows .... but when i run direct backup to tape everything works fine.