Forum Discussion

Yet's avatar
Yet
Level 5
6 years ago

Restore is very slow

Backup of 50GB took only 1hr20mins but restore is 10hrs. Backup host (host1) is different than restore host (host2), but they have same disk (SAN flash disk) and network (10Gb) type. Media server i...
8.1.2
Linux
  • Marianne's avatar
    Marianne
    6 years ago

    Please try to test network transfer / connection outside of NBU (e.g. ftp or even continuous ping) between media server and destination client. 

    We see quite a number of warnings like these:

    put_length_bytes_nonblocking: could only write 18 of 87 bytes to network:  Resource temporarily unavailable (11)

Nicolai's avatar
Nicolai
Moderator

Remove NET_BUFFER_SZ, setting is no longer in use, but it is still referenced in manny of Veritas tech notes.

See Best practices for NET_BUFFER_SZ and Buffer_size, why can't NetBackup change the TCP send/receive space

https://www.veritas.com/support/en_US/article.TECH28339

Also I highly recommend you set NUMBER_DATA_BUFFERS & SIZE_DATA_BUFFERS. Tape performance will go up substantial. You are using the 64K block size. I recommend 262144 as block size and setting SIZE_DATA_BUFFERS to 256

Windows :
https://www.veritas.com/support/en_US/article.100030830.html

UNIX/Linux:
https://www.veritas.com/support/en_US/article.TECH1724

mph999's avatar
mph999
Level 6
6 years ago

I could be wrong, but I thought you had to specfically set NET_BUFFER_SZ to 0 in order to 'disable' it.

  • Nicolai's avatar
    Nicolai
    Moderator
    6 years ago

    You are correct mph999

    From tech note :

     Accordingly the best NetBackup configuration is to disable tuning by placing a zero (0) into the NET_BUFFER_SZ file on media servers and UNIX/Linux clients.   Simply deleting the file is not equivalent because some NetBackup process have default setsockopt API calls configured to overcome past external problems with various platforms and drivers.

    So either a 0 in NET_BUFFER_SZ or remove the file to get to a fuctional setup.