1.Why is performing a lot of GETS if the policy is snapshot-only and nobody is performing a restore of snapshots?
My Guess -- If the local tier is at >90% capacity, cold data is read directly from the cloud tier without being written back to the local tier. By preventing cold data write-backs on heavily utilized local tiers, FabricPool preserves the local tier for active data.
2.if the object storage is down and i have snapshot-only policy can affect the access to the data on the performance tier?
-- If for any reason connectivity to the cloud is lost, the FabricPool local tier remains online, but applications receive an error message when attempting to get data from the cloud tier.
--Cold blocks that exist exclusively on the cloud tier remain unavailable until connectivity is reestablished.
Hi, Actually GET request could be also due to object fragmentation probably due to snapshot rollout.
FabricPool does not delete blocks from attached object stores. Instead, FabricPool deletes entire objects after a certain percentage of the blocks in the object are no longer referenced by ONTAP.
For example, there are 1,024 4KB blocks in a 4MB object tiered to Amazon S3. If a customer/client app makes a delete or a write to a file that has cold blocks in an object, the cold block becomes unreferenced, but it stays in the object.
This fragmentation slowly builds up until it crosses theunreclaimed space thresholdand we delete the object and fold any existing referenced blocks into a new object. Defragmentation and deletion do not occur until less than 205 4KB blocks (20% of 1,024) are being referenced by ONTAP.
When enough (1,024) blocks have zero references, their original 4MB objects are deleted, and a new object is created.