Search Knowledge Base by Keyword

Network connectivity errors

← All Topics

When eazyBackup uploads files to your eazyBackup Storage Vault (or to a cloud storage provider) over the internet. Occasionally, you may see errors such as the following:

  • Couldn't save data chunk:
  • HTTP/1.x transport connection broken
  • net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  • wsarecv
  • wsasend
  • An existing connection was forcibly closed by the remote host
  • dial tcp: lookup [...]: no such host
  • connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

eazyBackup retries the upload several times, but eventually gives up. After a failed data chunk upload, you may see several more messages of the form Couldn’t save data chunk: context canceled while eazyBackup terminates the other upload threads.

Network errors have many possible causes:

  • Customer's PC
  • Customer's network
  • Customer's ISP
  • Internet outages between customer's ISP and eazyBackup

To troubleshoot these issues, please check:

  • Does the backup succeed if it is retried?
    • Many network errors are temporary and will only occur rarely. In addition, a repeated second backup job will often run faster because many of the existing data chunks have already been uploaded. (Any unused data chunks in the Storage Vault will be automatically cleaned up by the next retention pass.)
  • Does the error message always happen at a certain time of day?
    • It may be possible to reschedule the backup to avoid times of heavy internet congestion.