Skip to content

Latest commit

 

History

History
40 lines (28 loc) · 2.07 KB

task_cloud_tier_data.adoc

File metadata and controls

40 lines (28 loc) · 2.07 KB
sidebar permalink keywords summary
sidebar
task_cloud_tier_data.html
netapp, ontap, FabricPool, tier, tiers, cloud data, tiering, aggregate, local tier, primary, cloud tier, storing data in tiers, storage efficiency, FabricPool, Fabric Pool, FabricPool license, volume tiering policy
Storing data in tiers can enhance the efficiency of your storage system.

Tier data to cloud

Storing data in tiers can enhance the efficiency of your storage system. You can manage storage tiers by using FabricPool to store data in a tier, based on how frequently the data is accessed.

This procedure sets up an object store as the cloud tier for FabricPool. Keep in mind that once you attach to a local tier (aggr) the cloud tier cannot be unattached.

A FabricPool license is not required when using StorageGRID or ONTAP S3 as the cloud tier or when using Amazon S3, Google Cloud Storage, or Microsoft Azure Blob Storage as the cloud tier for Cloud Volumes for ONTAP. A FabricPool license is required for other cloud tier locations.

If you are tiering to ONTAP S3, there are additional requirements:
* There must be an entry for the remote ONTAP S3 server’s hostname in the DNS server configured for the admin storage VM, including the S3 server’s FQDN name and the IP addresses on its network interfaces.
* Intercluster network interfaces must be configured on both local and remote clusters, although cluster peering is not required.

You also have the option to create a volume tiering policy in System Manager.

Steps

  1. Click Storage > Tiers > Add Cloud Tier and select the object store provider you want to use.

  2. If you want to create a cloud mirror, click Add as FabricPool Mirror.

A FabricPool mirror provides a method for you to seamlessly replace a data store, and it helps to ensure that your data is available in the event of disaster.