NetApp ONTAP 9.8 S3 - Provisioning Object Storage

 

NetApp ONTAP 9.8 software supports the Amazon Simple Storage Service (S3). ONTAP supports a subset of AWS S3 API actions and allows data to be represented as objects in ONTAP-based systems, including AFF, FAS, and ONTAP Select.

 

The primary purpose of S3 in ONTAP is to provide support for objects on ONTAP-based systems. The ONTAP unified storage architecture now supports files (NFS and SMB), blocks (FC and iSCSI), and objects (S3).

 

Architecture Object storage is an architecture that manages data as objects, as opposed to other storage architectures such as file or block storage. Objects are kept inside a single container (such as a bucket) and are not nested as files inside a directory inside other directories.

 

ONTAP - S3 Implementation:

1. Enable S3 Service in any data-SVM.

Requirements

 Platforms

•                • NetApp AFF storage system. S3 is supported on all AFF platforms using ONTAP 9.8+.

•                • FAS storage system. S3 is supported on all FAS platforms using ONTAP 9.8+.

•                • NetApp ONTAP Select. S3 is supported on all platforms using ONTAP Select 9.8+.

•                • Cloud Volumes ONTAP. S3 is not supported on Cloud Volumes ONTAP.

 

Data LIFs

Storage virtual machines (SVMs) hosting object store servers require data LIFs to communicate with client applications using S3. When configured for remote cluster tiering, FabricPool is the client and the object store is the server.

Cluster LIFs

When configured for local cluster tiering, a local tier (also known as a storage aggregate in the ONTAP CLI) is attached to a local bucket. FabricPool uses cluster LIFs for intracluster traffic.

Configuring S3 Server (Object Storage Server)

Creating Bucket for Object Storage tiering.

In another Cluster, create a Fabric Pool use the following Steps.

Add Cloud Tier and select the ONTAP S3

Cloud Tier Added Successfully.

In cluster2 list the object server and bucket details.

Then you can attach the local tiers to this cloud tier.

NetApp ONTAP 9.8 Snapmirror Business Continuity (SM-BC) Configuration

 

  

Beginning with ONTAP 9.8, you can use SnapMirror Business Continuity (SM-BC) to protect applications with LUNs, enabling applications to fail over transparently, ensuring business continuity in case of a disaster.

 

Benefits

SnapMirror Business Continuity provides the following benefits:

• Provides continuous availability for business-critical applications

• Ability to host critical applications alternately from primary and secondary site

• Simplified application management using consistency groups for dependent write-order consistency

• The ability to test failover for each application

 

Role of Mediator

ONTAP Mediator provides an alternate health path to the peer cluster, with the intercluster LIFs providing the other health path. With the Mediator’s health information, clusters can differentiate between intercluster LIF failure and site failure. When the site goes down, Mediator passes on the health information to the peer cluster on demand, facilitating the peer cluster to fail over. With the Mediator-provided information and the intercluster LIF health check information, ONTAP determines whether to perform an auto failover, if it is failover incapable, continue or stop.

 

Hardware

• Only two-node HA clusters are supported

• Both clusters must be either AFF or ASA (no mixing)

Software

• ONTAP 9.8 or later

• ONTAP Mediator 1.2 or later

• A Linux server or virtual machine for the ONTAP Mediator running one of the following:

◦ RedHat Enterprise Linux 7.6 or 7. 7

◦ CentOS 8.0 or 8.1

Licensing

• SnapMirror synchronous (SM-S) license must be applied on both clusters

• SnapMirror license must be applied on both clusters

 

Supported protocols

• Only SAN protocols are supported (not NFS/CIFS)

• Only Fibre Channel and iSCSI protocols are supported

 

Steps to Implement SM-BC: