Preparing the source and target Edit on GitHub Request doc changes

Contributors netapp-bcammett

Prepare to sync data by verifying that your source and target are supported and setup.

Supported sync relationships

Cloud Sync enables you to sync data from a source to a target (this is called a sync relationship). You should understand the supported relationships before you get started.

Source location Supported target locations

AWS EFS

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (NFS)

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

AWS S3

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (SMB)

  • Azure NetApp Files (NFS)

  • SMB Server

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

Azure Blob

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (SMB)

  • Azure NetApp Files (NFS)

  • SMB Server

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • NFS server

  • StorageGRID

Azure NetApp Files (SMB)

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (SMB)

  • SMB Server

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • StorageGRID

Azure NetApp Files (NFS)

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (NFS)

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

SMB server

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (SMB)

  • SMB Server

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • StorageGRID

Cloud Volumes Service (NFS)

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (NFS)

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

Google Cloud Storage

  • AWS EFS

  • AWS S3

  • Azure NetApp Files (SMB)

  • Azure NetApp Files (NFS)

  • SMB Server

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • NFS server

  • StorageGRID

IBM Cloud Object Storage

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (SMB)

  • Azure NetApp Files (NFS)

  • SMB Server

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

NFS server

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (NFS)

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

StorageGRID

  • AWS EFS

  • AWS S3

  • Azure Blob

  • Azure NetApp Files (SMB)

  • Azure NetApp Files (NFS)

  • SMB Server

  • Cloud Volumes Service (NFS)

  • IBM Cloud Object Storage

  • Google Cloud Storage

  • NFS server

  • StorageGRID

Notes:

  1. To sync SMB data between Cloud Volumes Service and an SMB server, you’ll need to choose SMB to SMB.

  2. You can choose a specific Azure Blob storage tier when a Blob container is the target:

    • Hot storage

    • Cool storage

  3. You can choose a specific S3 storage class when AWS S3 is the target:

    • Standard (this is the default class)

    • Intelligent-Tiering

    • Standard-Infrequent Access

    • One Zone-Infrequent Access

    • Glacier

    • Glacier Deep Archive

Networking requirements

  • The source and target must have a network connection to the data broker.

    For example, if an NFS server is in your data center and the data broker is in AWS, then you need a network connection (VPN or Direct Connect) from your network to the VPC.

  • NetApp recommends configuring the source, target, and data broker to use a Network Time Protocol (NTP) service. The time difference between the three components should not exceed 5 minutes.

NFS server requirements

  • The NFS server can be a NetApp system or a non-NetApp system.

  • The file server must allow the data broker host to access the exports.

  • NFS versions 3, 4.0, 4.1, and 4.2 are supported.

    The desired version must be enabled on the server.

  • If you want to sync NFS data from an ONTAP system, ensure that access to the NFS export list for an SVM is enabled (vserver nfs modify -vserver svm_name -showmount enabled).

    The default setting for showmount is enabled starting with ONTAP 9.2.

SMB server requirements

  • The SMB server can be a NetApp system or a non-NetApp system.

  • The file server must allow the data broker host to access the exports.

  • SMB versions 1.0, 2.0, 2.1, and 3.0 are supported.

  • If you want Cloud Sync to copy ACLs between SMB shares, run a deployment script on a Windows host and activate support when you create a sync relationship.

AWS S3 bucket requirements

Make sure that your AWS S3 bucket meets the following requirements.

Supported data broker locations for AWS S3

Sync relationships that include S3 storage require a data broker deployed in AWS or on your premises. In either case, Cloud Sync prompts you to associate the data broker with an AWS account during installation.

Supported AWS regions

All regions are supported except for the China and GovCloud (US) regions.

Permissions required for S3 buckets in other AWS accounts

When setting up a sync relationship, you can specify an S3 bucket that resides in an AWS account that isn’t associated with the data broker.

The permissions included in this JSON file must be applied to that S3 bucket so the data broker can access it. These permissions enable the data broker to copy data to and from the bucket and to list the objects in the bucket.

Note the following about the permissions included in the JSON file:

  1. <BucketName> is the name of the bucket that resides in the AWS account that isn’t associated with the data broker.

  2. <RoleARN> should be replaced with one of the following:

    • If the data broker was manually installed on a Linux host, RoleARN should be the ARN of the AWS user for which you provided AWS credentials when deploying the data broker.

    • If the data broker was deployed in AWS using the CloudFormation template, RoleARN should be the ARN of the IAM role created by the template.

      You can find the Role ARN by going to the EC2 console, selecting the data broker instance, and clicking the IAM role from the Description tab. You should then see the Summary page in the IAM console that contains the Role ARN.

      A screenshot of the AWS IAM console showing a Role ARN.

Azure Blob storage requirements

Make sure that your Azure Blob storage meets the following requirements.

Supported data broker locations for Azure Blob

The data broker can reside in any location when a sync relationship includes Azure Blob storage.

Supported Azure regions

All regions are supported except for the China, US Gov, and US DoD regions.

Connection string required for relationships that include Azure Blob and NFS/SMB

When creating a sync relationship between an Azure Blob container and an NFS or SMB server, you need to provide Cloud Sync with the storage account connection string:

Shows a connection string

If you want to sync data between two Azure Blob containers, then the connection string must include a shared access signature (SAS). You also have the option to use a SAS when syncing between a Blob container and an NFS or SMB server.

The SAS must allow access to the Blob service and all resource types (Service, Container, and Object). The SAS must also include the following permissions:

  • For the source Blob container: Read and List

  • For the target Blob container: Read, Write, List, Add, and Create

Shows a shared access signature

Google Cloud Storage bucket requirements

Make sure that your Google Cloud Storage bucket meets the following requirements.

Supported data broker locations for Google Cloud Storage

Sync relationships that include Google Cloud Storage require a data broker deployed in GCP or on your premises. Cloud Sync guides you through the data broker installation process when you create a sync relationship.

Supported GCP regions

All regions are supported.