Skip to main content
NetApp Knowledge Base

Why does the BlueXP Copy & Sync scanner fail for file transfers but not S3?

Views:
19
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • BlueXP Copy & Sync
  • Data Broker
  • SMB
  • NFS
  • S3

Answer

  • For any relationships utilizing a file based protocol (SMB or NFS), the physical memory of the data broker is used to list and compare.
    • The default memory heap allocation is 2048Mb that is configured for any workload up to 500000 files in a single directory.
  • For exclusive S3 relationships (S3 to S3), the scanner uses a local database while scanning to list and compare.

 

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.