An analytics team has cold Snapshot data consuming SSD space. They want to free high-performance tier capacity without affecting primary I/O.

An analytics team has cold Snapshot data consuming SSD space. They want to free high-performance tier capacity without affecting primary I/O.

• A. SnapMirror to object store
• B. FabricPool tiering
• C. FlexClone to NAS tier
• D. SVM DR

Answer: (B)

Tiering data to a lower-cost secondary storage while keeping hot data on the fast tier is the key idea. FabricPool does exactly this: it places cold data on an object storage backend (like an S3-compatible store) and keeps hot data on the high-performance SSD tier, with metadata on the primary system. Because the hot data remains on SSD and reads of cold data are fetched as needed, the primary I/O path isn’t disrupted while you reclaim SSD space. This makes FabricPool ideal for freeing high-performance capacity when you have lots of analytics-era snapshots or infrequently accessed data. The other options don’t provide automatic cold-data tiering to object storage within the same system to free SSD space and maintain I/O performance.

Tiering data to a lower-cost secondary storage while keeping hot data on the fast tier is the key idea. FabricPool does exactly this: it places cold data on an object storage backend (like an S3-compatible store) and keeps hot data on the high-performance SSD tier, with metadata on the primary system. Because the hot data remains on SSD and reads of cold data are fetched as needed, the primary I/O path isn’t disrupted while you reclaim SSD space. This makes FabricPool ideal for freeing high-performance capacity when you have lots of analytics-era snapshots or infrequently accessed data. The other options don’t provide automatic cold-data tiering to object storage within the same system to free SSD space and maintain I/O performance.