Druva SharePoint Backup: "Connection reset by peer" Error (File Skipped)

SharePoint site backups are completing with an error indicating "Connection reset by peer" in the Activity Stream logs, leading to specific files being skipped from the backup.

This intermittent error (Connection reset by peer) occurs when Druva attempts to synchronize a file during a SharePoint backup, but the network connection is unexpectedly terminated by Microsoft. When such an interruption happens, Druva logs the error for the affected file and skips that specific file from the current backup. The overall backup job, however, completes with a status of "Completed with Errors" due to these skipped files.

While the backup job completes, the file identified in the error message is not backed up in that particular cycle.

Druva's backup mechanism is designed to handle such intermittent issues. Files skipped due to "Connection reset by peer" errors are automatically retried in subsequent backup cycles.

Identify the Error: Check the Activity Stream logs for your SharePoint backup job. Look for entries similar to:

Example:

Monitor Subsequent Backups: Observe the next few backup runs for the affected SharePoint site.

📝 Note

This issue is typically intermittent and often self-resolving in subsequent backup attempts. Direct intervention may not be immediately required beyond monitoring. If the same files consistently fail to back up across multiple cycles with this specific error, or if a large number of files are consistently skipped, further investigation into network stability or SharePoint connectivity, please contact Druva Support for further support.