Managing data tiering from your clusters Edit on GitHub Request doc changes

Contributors netapp-bcammett

Now that you’ve discovered and tiered data from your first ONTAP cluster, you can tier data from additional volumes, discover additional clusters, and more.

Discovering additional clusters

Add additional ONTAP clusters at any time to start tiering inactive data from those clusters.

  1. From the Cluster Dashboard, click the following icon:

    A screenshot that shows the icon for discovering additional clusters.

  2. Enter the cluster management IP address and the user name and password of an account that has administrator-level privileges.

  3. Select an existing Service Connector that has a connection to the cluster, or create a new one and click Continue.

What’s next?

Click Set up Tiering to start tiering inactive data from the cluster.

A screenshot that shows the Set up Tiering button on the Cluster Dashboard.

Tiering data from additional volumes

Set up data tiering for additional volumes at any time—​for example, after creating a new volume.

  1. From the Cluster Dashboard, click Set up Tiering.

  2. Source Volumes: Select the volumes that you want to tier and choose a tiering policy for each volume.

    A screenshot that shows volumes selected in the Select Source Volumes page.

  3. Review: Review your selections and click Go.

    You don’t need to configure the object storage because it was already configured when you initially set up tiering for the cluster. ONTAP will tier inactive data from these volumes to the same object store.

Reviewing data tiering info for a cluster

You might want to see how much data is in the cloud tier and how much data is on disks. Or, you might want to see the amount of hot and cold data on the cluster’s disks. Cloud Tiering provides this information for each cluster.

  1. From the Cluster Dashboard, click More info for a cluster.

    A screenshot that shows the More info button

  2. Review details about the cluster.

    Here’s an example:

    A screenshot that shows the cluster report

Fixing operational health

Failures can happen. When they do, Cloud Tiering displays a "Failed" operational health status on the Cluster Dashboard. The health reflects the status of the ONTAP system and the Service Connector.

  1. Identify any clusters that have an operational health of "Failed."

    A screenshot that shows a Failed tiering health status for a cluster.

  2. Hover over the A screenshot of the i icon that shows the failure reason icon to see the failure reason.

  3. Correct the issue:

    1. Verify that the ONTAP cluster is operational and that it has an inbound and outbound connection to your object storage provider.

    2. Verify that the Service Connector is running and that it has outbound connections to the Cloud Tiering service, to the object store, and to the ONTAP clusters that it discovers.

      The name of the Service Connector instance/virtual machine is prefixed with "Service-connector."