| sidebar | permalink | keywords | summary |
|---|---|---|---|
sidebar |
faq_cloud_tiering.html |
faq, questions, requirements, service connector, object store, object storage, aws, azure, bucket, cluster, aggregate, s3, storage class, standard, inactive data reporting, auto, volume tiering policy, policy, tiering policy, snapshot, cold, inactive, infrequent |
This FAQ can help if you're just looking for a quick answer to a question. |
This FAQ can help if you’re just looking for a quick answer to a question.
The following questions relate to ONTAP.
It depends on where you tier the cold data. Refer to the following:
Yes, Cloud Tiering enables inactive data reporting on each aggregate. This setting enables us to identify the amount of inactive data that can be tiered to low-cost object storage.
|
Note
|
Cloud Tiering enables inactive data reporting on HDD aggregates if the cluster is running ONTAP 9.6 or later. |
You can use Cloud Tiering to tier data from NAS volumes to the public cloud and from SAN volumes to a private cloud using StorageGRID.
If you have Cloud Volumes ONTAP systems, you’ll find them in the Cluster Dashboard so you get a full view of data tiering in your hybrid cloud infrastructure.
From the Cluster Dashboard, you can view tiering information similar to an on-prem ONTAP cluster: operational health, current savings, savings opportunities, details about volumes and aggregates, and more.
Cloud Volumes ONTAP systems are read-only from Cloud Tiering. You can’t set up data tiering on Cloud Volumes ONTAP from Cloud Tiering. You’ll still set up tiering the same way: from the working environment in Cloud Manager.
The following questions relate to object storage.
Amazon S3, Azure Blob storage, Google Cloud Storage, and StorageGRID using the S3 protocol are supported.
Yes, you can. When you set up data tiering, you have the choice to add a new bucket/container or to select an existing bucket/container.
Cloud Tiering supports data tiering to the Standard, Standard-Infrequent Access, One Zone-IA, or Intelligent storage class. See Supported S3 storage classes for more details.
Cloud Tiering automatically uses the Hot access tier for your inactive data.
Cloud Tiering supports data tiering to the Standard, Nearline, Coldline, or Archive storage class. See Supported Google Cloud storage classes for more details.
One object store for the entire cluster.
The following questions relate to Connectors.
-
When tiering data to S3, a Connector can reside in an AWS VPC or on your premises.
-
When tiering data to Blob storage, a Connector must reside in an Azure VNet.
-
When tiering data to Google Cloud Storage, a Connector must reside in a Google Cloud Platform VPC.
-
When tiering data to StorageGRID, a Connector must reside on an on premises Linux host.
The following questions relate to networking.
-
The ONTAP cluster initiates an HTTPS connection over port 443 to your object storage provider.
ONTAP reads and writes data to and from object storage. The object storage never initiates, it just responds.
-
For StorageGRID, the ONTAP cluster initiates an HTTPS connection over a user-specified port to StorageGRID (the port is configurable during tiering setup).
-
A Connector needs an outbound HTTPS connection over port 443 to your ONTAP clusters, to the object store, and to the Cloud Tiering service.
For more details, see:
The following questions relate to permissions.
Permissions are required to manage the S3 bucket.
No extra permissions are needed outside of the permissions that you need to provide to Cloud Manager.
Storage Admin permissions are needed for a service account that has storage access keys.