Skip to main content
NetApp Knowledge Base

SCSQL Backups Failing Due to Resource Discovery Timeout

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
SNAPX
Last Updated:

Applies to

  • SnapCenter Plug-in for Microsoft SQL Server (SCSQL)
  • SnapCenter Plug-in for VMware vSphere (SCV)
  • SQL Server databases hosted on VMDK disks

Issue

  • SQL Server backups for specific resource groups fail in SnapCenter. The following errors are observed in SnapCenter job logs:

System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 10800 seconds elapsing.

---> System.TimeoutException: The operation was canceled.

---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.

---> System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

---> System.Net.Sockets.SocketException (10053): An established connection was aborted by the software in your host machine.

  • Additional symptoms:
    • Backups hang in “Running” state or fail with “Unable to find the database files.”
    • Disk discovery jobs for affected SQL hosts hang for hours or do not complete.
    • SnapCenter logs may show “Failed to determine LUN based on the serial number” or invalid/unknown storage targets (e.g., target “0”).
    • Other resource groups and backups may remain unaffected.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.