Forum Discussion

S_Williamson's avatar
S_Williamson
Level 6
12 years ago

sts_close_handle failed: 2060019 error occurred on network socket

**** Moved to new discussion from https://www-secure.symantec.com/connect/forums/client-backups-status-87-83-5020-appliance?page=0 **** I am also getting this error 9/06/2013 9:19:53 AM - Critica...
7.5
Backing Up
Backup and Recovery
NetBackup
Troubleshooting
Windows Server (2003-2008)
  • Brook_Humphrey's avatar
    Brook_Humphrey
    12 years ago

    Ah if that is the case you may want to try increasing your client read timeouts and see if it gives you enough time to complete the backup.

     

    If you have any other questions please let me know.

    Thanks

  • Mark_Solutions's avatar
    Mark_Solutions
    12 years ago

    Do you have the \program files\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO file in place - if so what setting does it have?

    If not please create this on your Master / Media Servers and add a value of 800 into the file

    This helps keep the disk pool up and happy at very busy times when the Master could believe it has problems

    I always use this setting for any de-dupe or enterprise disk setups (but none of the other DPS_ file though)

    Hope this helps

Brook_Humphrey's avatar
Brook_Humphrey
Level 4
12 years ago

As far as the client read timeout. On some of my systems especially for large backups you have to allow the client time to walk the os and find all the files as well as sending the file list back to netbackup If you are using accelerator then it is like doing a full in this aspect. During this time if there is a large ammount of data with many files the client will time out talking to NBU.

In my cases I end up with client read timeouts of more like 3200 or 6400. Occasionally I have seen them as high as 10200 or maybe 11,200.

At any rate you should know if it takes longer for the backup ot fail.

 

Thanks