Backing up data from an on-premises ONTAP system to the cloud

Contributors netapp-tonacki Download PDF of this page

Complete a few steps to get started backing up data from your on-premises ONTAP system to low-cost object storage in the cloud.

A Beta feature released in January 2021 allows you to run Compliance scans on the backed up volumes from your on-prem systems. Typically, compliance scans are free up to 1 TB of data, and then a cost for the service is applied for data over 1 TB. When combining Backup and Compliance for your on-prem volumes, the cost for scans on those on-prem volumes is free. Learn more about how Cloud Compliance can get your business applications and cloud environments privacy ready.

Quick start

Get started quickly by following these steps or scroll down to the remaining sections for full details.

Number 1 Verify support for your configuration

  • You have discovered the on-premises cluster and added it to a working environment in Cloud Manager. See Discovering ONTAP clusters for details.

    • The cluster is running ONTAP 9.7P5 or later.

    • The cluster has a SnapMirror license — which is included as part of the PREM or Data Protection bundle.

  • You have subscribed to the Azure or the AWS Cloud Manager Marketplace Backup offering, or you have purchased and activated a Cloud Backup BYOL license from NetApp.

  • You have a valid cloud provider subscription for the object storage space where your backups will be located.

  • For AWS, you need to have an account that has an access key and the required permissions so the ONTAP cluster can back up data to S3.

Number 2 Enable Cloud Backup on the system

Select the working environment and click Activate next to the Backup & Compliance service in the right-panel, and then follow the setup wizard.

A screenshot that shows the Backup & Compliance Activate button which is available after you select an on-prem working environment.

Number 3 Select the cloud provider and enter provider details

Select the provider and then enter the provider details. You also need to specify the IPspace in the ONTAP cluster where the volumes reside.

Note: Backup to Google Cloud Storage from on-prem ONTAP systems is not currently supported from the UI.

Number 4 Define the backup policy

The default policy backs up volumes every day and retains the most recent 30 backup copies of each volume. Change to weekly or monthly backups, or select one of the system-defined policies that provide more options.

A screenshot that shows the Cloud Backup settings where you can choose the backup schedule and retention period.

Number 5 Select the volumes that you want to back up

Identify which volumes you want to back up from the cluster.

Number 6 Activate Compliance scans on the backed up volumes (optional)

Choose whether you want to have Cloud Compliance scan the volumes that are backed up in the cloud.

Number 7 Restore your data, as needed

Choose to restore an entire backup to a new volume, or to restore individual files from the backup to an existing volume. You can restore data to a Cloud Volumes ONTAP system that is using the same cloud provider, or to an on-premises ONTAP system.

Requirements

Read the following requirements to make sure you have a supported configuration before you start backing up on-prem volumes to object storage.

ONTAP requirements

ONTAP 9.7P5 and later.

A SnapMirror license (included as part of the PREM or Data Protection bundle).

Cluster networking requirements

An intercluster LIF is required on each ONTAP node that hosts the volumes you want to back up. The LIF must be associated with the IPspace that ONTAP should use to connect to object storage. Learn more about IPspaces.

When you set up Cloud Backup, you are prompted for the IPspace to use. You should choose the IPspace that each LIF is associated with. That might be the "Default" IPspace or a custom IPspace that you created.

Supported regions

Backups from on-prem systems are supported in all regions where Cloud Volumes ONTAP is supported.

  • For Azure, you specify the region where the backups will be stored when you set up the service.

  • For AWS, backups are stored in the region where Cloud Manager is installed.

    Note: Backup to Google Cloud Storage from on-prem ONTAP systems is not currently supported from the UI.

License requirements

For Cloud Backup PAYGO licensing, you’ll need a subscription to the Azure or the AWS Cloud Manager Marketplace Backup offering before you enable Cloud Backup. Billing for Cloud Backup is done through this subscription.

For Cloud Backup BYOL licensing, you need the serial number from NetApp that enables you to use the service for the duration and capacity of the license. See Adding and updating your Backup BYOL license.

And you need to have a subscription from your cloud provider for the object storage space where your backups will be located.

Preparing Amazon S3

When you are using Amazon S3, you must configure permissions for Cloud Manager to access the S3 bucket, and you must configure permissions so the on-prem ONTAP cluster can access the S3 bucket.

Steps
  1. Provide the following S3 permissions (from the latest Cloud Manager policy) to the IAM role that provides Cloud Manager with permissions:

    {
                "Sid": "backupPolicy",
                "Effect": "Allow",
                "Action": [
                    "s3:DeleteBucket",
                    "s3:GetLifecycleConfiguration",
                    "s3:PutLifecycleConfiguration",
                    "s3:PutBucketTagging",
                    "s3:ListBucketVersions",
                    "s3:GetObject",
                    "s3:ListBucket",
                    "s3:ListAllMyBuckets",
                    "s3:GetBucketTagging",
                    "s3:GetBucketLocation",
                    "s3:GetBucketPolicyStatus",
                    "s3:GetBucketPublicAccessBlock",
                    "s3:GetBucketAcl",
                    "s3:GetBucketPolicy",
                    "s3:PutBucketPublicAccessBlock"
                ],
                "Resource": [
                    "arn:aws:s3:::netapp-backup-*"
                ]
            },
  2. Provide the following permissions to the IAM user so that the ONTAP cluster can back up data to S3.

    "s3:ListAllMyBuckets",
    "s3:ListBucket",
    "s3:GetBucketLocation",
    "s3:GetObject",
    "s3:PutObject",
    "s3:DeleteObject"
  3. Create or locate an access key.

    Cloud Backup passes the access key on to the ONTAP cluster. The credentials are not stored in the Cloud Backup service.

Enabling Cloud Backup

Enable Cloud Backup at any time directly from the on-premises working environment.

Steps
  1. From the Canvas, select the working environment and click Activate next to the Backup & Compliance service in the right-panel.

    A screenshot that shows the Backup & Compliance Activate button which is available after you select an on-prem working environment.

  2. Select the provider, and then enter the provider details:

    • For Azure, enter:

      1. The Azure subscription used for backups and the Azure region where the backups will be stored.

      2. The resource group - you can create a new resource group or select and existing resource group.

      3. The IPspace in the ONTAP cluster where the volumes you want to back up reside.

        A screenshot that shows the cloud provider details when backing up volumes from an on-premises cluster to an Azure Blob tier.

    • For AWS, enter:

      1. The AWS Access Key and Secret Key used to store the backups.

      2. The IPspace in the ONTAP cluster where the volumes you want to back up reside.

        A screenshot that shows the cloud provider details when backing up volumes from an on-premises cluster to an AWS S3 tier.

        Note that you cannot change this information after the service has started.

  3. Then click Continue.

  4. In the Define Policy page, select the backup schedule and retention value and click Continue.

    A screenshot that shows the Cloud Backup settings where you can choose your backup schedule and retention period.

  5. Select the volumes that you want to back up.

    • To back up all volumes, check the box in the title row (button backup all volumes).

    • To back up individual volumes, check the box for each volume (button backup 1 volume).

      A screenshot of selecting the volumes that will be backed up.

  6. Click Activate and Cloud Backup starts taking the initial backups of your volumes.

    You are prompted whether you want to run compliance scans on the backed up volumes. Cloud Compliance scans are free when you run them on the backed up volumes (except for the cost of the deployed Cloud Compliance instance).

    A screenshot of the page where you can choose to activate Cloud Compliance on your backed up volumes.

  7. Click Go to Compliance to activate compliance scans on the volumes. (If you choose Close and not to scan these backed up volumes, you can always enable this functionality later from Cloud Compliance.)

    • If an instance of Cloud Compliance is already deployed in your environment, you are directed to the Configuration page to select the volumes you want to scan in each on-premises working environment that has backups. See how to choose the volumes.

      A screenshot of the Compliance page to select volumes you want to scan.

    • If Cloud Compliance has not been deployed, you are directed to the Compliance page where you can choose to deploy Compliance in the cloud or in your premises. We strongly recommend deploying it in the cloud. Go here for installation requirements and instructions.

      A screenshot of the Compliance page to choose how you want to deploy Cloud Compliance.

      After you have deployed Compliance you can choose the volumes you want to scan as described above.

Result

Cloud Backup backs up your volumes from the on-prem ONTAP system, and optionally, Cloud Compliance runs compliance scans on the backed up volumes.

You can also view the results of the compliance scans and review other features of Cloud Compliance that can help you understand data context and identify sensitive data in your organization.

The scan results are not available immediately because Cloud Backup has to finish creating the backups before Cloud Compliance can start compliance scans.