Forum Discussion

Jeremiah_Window's avatar
Jeremiah_Window
Level 2
15 years ago

Netbackup KB/Sec:

Using WIndows 2K3 E Server, HP MSL6k TLD, with NBU 6.5 and my backups are writting at the bit  at an average of  KB/Sec: 6851. The job is only 228G of data on a LTO4 1.6TB compressed drive?

7.1.x and Earlier
Backup and Recovery
NetBackup
Tip-How to
Windows
  • J_H_Is_gone's avatar
    J_H_Is_gone
    15 years ago
    That is something I am happy with.

    I have to remember - that I send more then one stream to a tape drive.

    so job 1 goes to drive - then it gathers more info
    job 2 goes to drive - then it gathers more info
    job 3 goes to drive - then it gathers more info
    jobs 4 goes to drive - the it gathers more info
    jobs 1 goes to drive again

    So my tape drives is getting great usage, but the jobs may have a little delay while they wait their turn to go to the drive.   This results in slower speed.

    If you really want to test. send one job to a tape drive and see if you get better speed.

    If any one big job ( meaning more then just a few meg for a job) is below 1000 I start to worry and look look into issues.

    Some jobs get 32000 kbps some get 6000 kbps - based on network card on server and size of server and how many jobs are using the tape.

    Watch your jobs and learn what your standard seems to be, then watch for changes.  You can try to inprove with tuning.

7 Replies

Sort By
  • David_McMullin's avatar
    David_McMullin
    Level 6
    15 years ago
    Are you bragging or complaining?  LOL

    I see a wide variety of speeds from my windows clients, mostly due to file locking.
    Some are hundreds of KB/Sec. 6851 KB/Sec over network is not unreasonable.

    I am moving to VMWare since the backup speeds are fiber - closer to 70,000 KB/Sec
  • MattS's avatar
    MattS
    Level 6
    15 years ago
    Its windows, but lots of other factors come into play.  I see up to 60MB/s on our exchange servers, but most others average your speed.  I would check out this guide http://seer.entsupport.symantec.com/docs/307083.htm


  • J_H_Is_gone's avatar
    J_H_Is_gone
    Level 6
    15 years ago
    That is something I am happy with.

    I have to remember - that I send more then one stream to a tape drive.

    so job 1 goes to drive - then it gathers more info
    job 2 goes to drive - then it gathers more info
    job 3 goes to drive - then it gathers more info
    jobs 4 goes to drive - the it gathers more info
    jobs 1 goes to drive again

    So my tape drives is getting great usage, but the jobs may have a little delay while they wait their turn to go to the drive.   This results in slower speed.

    If you really want to test. send one job to a tape drive and see if you get better speed.

    If any one big job ( meaning more then just a few meg for a job) is below 1000 I start to worry and look look into issues.

    Some jobs get 32000 kbps some get 6000 kbps - based on network card on server and size of server and how many jobs are using the tape.

    Watch your jobs and learn what your standard seems to be, then watch for changes.  You can try to inprove with tuning.
  • Nathan_Kippen's avatar
    Nathan_Kippen
    Level 6
    15 years ago
    You need to make sure that you are getting enough data to the drive at a time to prevent "shoe shining".  This means that the drive has to keep stopping because it's not getting enough data fast enough to write to tape.  A solution to this would be multiplexing a few jobs to the same drive. 
  • Anton_Panyushki's avatar
    Anton_Panyushki
    Level 6
    15 years ago
    We usually send all Wintel backup to VTL (DSSU is an option too). Don't expect great backup speed when it comes to Wintel boxes. File system traversing overhead is a key factor in backup speed fall.
  • David_McMullin's avatar
    David_McMullin
    Level 6
    15 years ago
    Agree with Anton - we had to multiplex 6 to 12 windows backups to drive our tapes, we moved to a VTL and now we can let them take their time and then duplicate to tape using SLP.