Skip to main content
NetApp Knowledge Base

CloudSync Relationship Repeatedly Copies Same SGWS ILM Stub File to Destination

  1. Last updated
  2. Save as PDF
Views:
19
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
ds_cs
Last Updated:

Applies to

  • NetApp CloudSync (BlueXP Copy and Sync)
  • DataBroker

Issue

A scheduled CloudSync relationship configured for periodic sync (example: once daily) from an SGWS source bucket to a destination bucket repeatedly copies the same small file (typically 28 bytes) at high frequency (example:  every ~2 minutes), regardless of the configured schedule.
  • The destination bucket accumulates hundreds or thousands of noncurrent versions of the same file.
  • All repeatedly copied files are exactly 28 bytes in size.
  • DataBroker logs show continuous COPY start/complete cycles for the same file path:
[STARTING] [<relationshipID>] [COPY] entry: { path: '<directory>/<filename>', size: 28 }
[COMPLETED] [<relationshipID>] [COPY] entry: { path: '<directory>/<filename>', size: 28 }
  • DataBroker logs may also show recurring SQS queue errors for stale or deleted relationships:
[ERROR] [TRANSFERRER] Failed to receive messages from queue
The specified queue does not exist
Additional files of the same size (28 bytes) in the same directory may fail with ECONNRESET errors.

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.