Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Microsoft SQL Server Administrator's Guide
  3. Performance and troubleshooting
  4. SQL Server restore fails when you restore a SQL Server compressed backup image as a single stripe or with multiple stripes
NetBackup™ for Microsoft SQL Server Administrator's Guide

SQL Server restore fails when you restore a SQL Server compressed backup image as a single stripe or with multiple stripes

This issue occurs when SQL Server is busy with the buffer of compressed data and cannot process all the data that is sent within a certain length of time. By default in Windows Server, TCP connections must close after the TCP connection state has been set to FIN_WAIT_2 for two minutes. Refer to the following Microsoft article for more information:

https://support.microsoft.com/en-us/kb/923200/

Note:

If the TCPFinWait2Delay value does not exist, you must create it as a REG_DWORD registry value. Otherwise, Windows uses the default value of 240.

To increase the time that TCP connections may remain in the FIN_WAIT_2 state

  1. On the NetBackup media server, open regedit.exe.
  2. Locate and select the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  3. Double-click on TCPFinWait2Delay.
  4. Enter a value of 300.
  5. Restart the media server.
  6. After the restore completes successfully, remove the registry setting or change the setting to its original value.

    When you increase the value of this setting it has an adverse effect for all TCP/IP connections. This higher value could cause port exhaustion for other applications that run on the media server.

  7. Restart the media server.

Feedback

Was this page helpful?
Previous

About minimizing timeout failures on large SQL Server database restores

Next

Incorrect backup images are displayed for availability group clusters

Feedback

Was this page helpful?