08/21/2017 18:09:20 - Critical bptm (pid=25890) sts_close_handle failed: 2060019 error occurred on network socket08/21/2017 18:09:20 - Error bptm (pid=25890) cannot write image to disk, media close failed with status 2060019I get these errors on different clients at time, and whenever i re-run the backup it runs successfully.I don't see a technote which explains a permanent fix for this/ an explanation on why 2060019 occursCan somebody help to fix such errors from further occurences. Netbackup Master Server : 7.7.3Media Server ( Netbackup 5220 appliance : 2.6.0.3)

Google found the same error here: https://www.veritas.com/connect/forums/after-upgrading-appliance-2602-backups-fail-intermittantly-error-24-and-14 and https://vox.veritas.com/t5/NetBackup/sts-close-handle-failed-2060019-error-occurred-on-network-socket/td-p/595125 Which then leads to this TN: https://www.veritas.com/support/en_US/article.TECH224031 So, the issue was introduced by upgrade/installation of 2.6.0.x: A change introduced in NetBackup appliance version 2.6.0.x disabled the kernel parameter tcp_timestamps. ..... Workaround:Until the affected NetBackup 52x0 Appliance can be patched to version 2.6.1, re-enable tcp_timestamps to resolve the issue: PLEASE upgrade your appliance to match master server software (2.7.3).All Appliance and NBU versions up to 7.6.x (2.6.x) ran out of support 6 months ago.

Hello, If you have purchased supported version license and have support contract with Veritas.You can open case with Support team for assistance. Veritas Support team will help you incase of any upgrade failure.Regards,

The problem with the unsupported Appliance is that you are going to find it very difficult to find a temporary fix or workaround. Members on this forum have suggested a few things to the best of our abilities.If none of that has helped, you are really on your own. You may want to show your management this discussion. PSI'm not sure why you believe that upgrade involves cost.The fact that your master is on a currently supported NBU version should entitle you to free upgrades that includes the Appliance software.With active support, Veritas Support will be able to assist with the upgrade and look at issues that might prevent successful upgrade.Simply log the call as 'upgrade assistance'.

Thanks for the update Marianne.I have changed the tcp_timestamps as a temporary workaround , the technotes talks about status code 24, the error which we are getting are 84 and 87 which are also related to socket errors : media close error, media write errors.The upgrade is under plan, also we are in an out of support version, so bit afraid on who would support if we encounter issues during upgrade

You never showed us all text for failed backup, right? All you gave us was error 2060019.

Error bptm (pid=214108) cannot write image to disk, media close failed with status 2060019

11 Replies

Marianne
Level 6
7 years ago
Google found the same error here:

https://www.veritas.com/connect/forums/after-upgrading-appliance-2602-backups-fail-intermittantly-error-24-and-14

and

https://vox.veritas.com/t5/NetBackup/sts-close-handle-failed-2060019-error-occurred-on-network-socket/td-p/595125

Which then leads to this TN: https://www.veritas.com/support/en_US/article.TECH224031

So, the issue was introduced by upgrade/installation of 2.6.0.x:

A change introduced in NetBackup appliance version 2.6.0.x disabled the kernel parameter tcp_timestamps.

.....

Workaround:
Until the affected NetBackup 52x0 Appliance can be patched to version 2.6.1, re-enable tcp_timestamps to resolve the issue:

PLEASE upgrade your appliance to match master server software (2.7.3).
All Appliance and NBU versions up to 7.6.x (2.6.x) ran out of support 6 months ago.
- dugga
  Level 4
  7 years ago
  Thanks for the update Marianne.
  I have changed the tcp_timestamps as a temporary workaround , the technotes talks about status code 24, the error which we are getting are 84 and 87 which are also related to socket errors : media close error, media write errors.
  The upgrade is under plan, also we are in an out of support version, so bit afraid on who would support if we encounter issues during upgrade
  - Tousif
    Level 6
    7 years ago
    Hello,
    
    If you have purchased supported version license and have support contract with Veritas.
    You can open case with Support team for assistance. Veritas Support team will help you incase of any upgrade failure.
    Regards,

Forum Discussion

Error bptm (pid=214108) cannot write image to disk, media close failed with status 2060019

11 Replies

Related Content

sts_close_handle failed: 2060019 error occurred on network socket

Error bptm (pid=214108) cannot write image to disk, media close failed with status 2060019

sts_close_handle failed: 2060019 error occurred on network socket

Status 2060019 and status 87 Killing same job

Login credentials or certificate verification failed for server cloudcatayst appliance

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date