Skip to main content
NetApp Knowledge Base

Question about FabricPool Mirror synchronization between two object storage tiers

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

Applies to

  • FabricPool Mirror
  • Performance tier is onprem system

Answer

Q1: Does the synchronization of FabricPool Mirrors between two object storage tiers occur via the performance tier?
A1: No, the synchronization does not take place through the performance tier.
 
Q2: Is there any perfomance impact during the synchronization?
A2: When both buckets are in a mirrored state, newly tiered data is synchronously tiered to both buckets.
         Because data is being tiered to two buckets synchronously, the effective throughput is half of standard single-bucket tiering.
         For example, if PUT operations to a single bucket take place at 600MBps, PUT operations to mirrored buckets in a FabricPool Mirror deployment take place at 300MBps.
 
Q3: How much capacity is required for the second object storage tier to ensure proper synchronization?
A3: The second object storage tier must have at least the same capacity for cold data as the first object storage tier.
 
Q4: Does the synchronization of FabricPool Mirrors between two object storage tiers go through the Intercluster LIF of the on-prem system?
A4: Yes.

Additional Information

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.