Copy Data Management in Hybrid Cloud with NetApp SnapCenter

by New Contributor on ‎2017-07-27 05:52 AM

Introduction

Cloud is a major disruptor in the storage market, and to counter this, most infrastructure verticals within the data center are undergoing a rapid evolution. Although cloud affords flexibility, it lacks the security offered by on-premise storage and proves costly when the data and its copies (Copy Data) grow over a period. NetApp Data Fabric, NetApp’s offering in hybrid cloud along with its Copy Data Management solution, can address these customer data challenges in simple and cost-effective manner.  NetApp SnapCenter is the next generation copy data management software that automates and simplifies the manual, complex and time-consuming processes associated with the backup, recovery, and cloning of the application workloads across the Data Fabric within a single pane of glass management.


Let’s explore few of the hybrid cloud models and how NetApp SnapCenter helps in protecting those applications at various Copy data infrastructures.

 

Model 1: NPS (NetApp Private storage) for Cloud solution consists of a NetApp FAS or FlexArray™ storage system, co-located in an Equinix data center, and directly connected with a service provider’s cloud compute using a dedicated, high-bandwidth, low-latency network connection. In this Example, NPS is used as a SnapMirror destination and compute is leveraged directly from the AWS Cloud. SnapCenter is used to take Backups, replicate local copies to NPS and finally Clone DEV/Test to the cloud. A good thing about this model is that you can connect to many cloud and switch cloud at any time with data control.

 

model2.JPG

 

 

 

Model 2: Software defined ONTAP is directly deployed on the AWS Cloud as a SnapMirror/DR destination for the Local Datacenter. SnapCenter has a similar role like model 1 however the only difference is that both the secondary replicated storage and compute exist in the same cloud.

 

model1.JPG

 

 

In this example, we have listed only the essential steps with Oracle database as a reference for Backup and Clone operation. The configuration steps are similar for other database workloads. 

  • Login to SnapCenter

 Login-screen.snag

 

  • Register the storage with SnapCenter: The On-Premise storage SVMs along with other SnapMirror destinations like NetApp Private storage SVMs, ONTAP Cloud SVMs are supposed to be registered with SnapCenter.

 

storage-reg.JPG

 

 

 

  • Backup policies: A new backup policy is created with SnapMirror checkbox enabled. During backup, SnapCenter imports the existing protection relationships and helps to replicate the Snapshot copy from primary storage to NPS /ONTAP Cloud storage.

 

 

bACKUP-POLICY.JPG

 

 

  • Create Backups: Once the Backup policy is created, it must be attached to a specific resource/Database. To trigger an On-demand backup the user must click on Backup now button and associate the newly created policy with the resource. 

 

 

  BACKUP-TOPOLOGY-1.JPG

 

 

BACKUP.JPG

 

 

Each job is tracked by its job id and can be monitored in the monitor page. 

 

  • Copy Infrastructure Topology: Once the backup gets completed, the topology view is updated with the latest number of backups at all the copy infrastructures. To access the backup details or to perform any operations for a specific backup, DBA must select any of these copy destination and click the backups row to list down the details. The below snippet shows the details of backup present in the NetApp Private storage.

 

COPY-INFRA.JPG

 

 

  • Clone DEV/Test to the Cloud: The first step is to bring up a RHEL compute instance in AWS and get it registered with the SnapCenter.

cLONE-FIRST.JPG

 

SC-AWS-HOST-REG.JPG

 

 

 

Once the AWS host is registered with SnapCenter, select a backup from AWS destination (Vault) and click on the clone button to invoke the clone wizard. 

 

 

 

CLONE-CLICK.JPG

 

 

 The Clone wizard will prompt for the Clone DB settings (Clone SID, Location for Mounts, DB parameters).

 

cLONE-FIRST.JPG

 

 

 

Choose AWS RHEL host from the Clone host drop-down and submit the job.

 

CLONE-HOST.JPG

 

 

Once the Clone job is successful, the resources page gets updated with an entry for the clone DB.  From the below snippet, TESTERP is a new Clone DB running in a AWS RHEL instance.

 

 

CLONE-LIST.JPG

 

 

  The topology view of the Production DB also gets updated with the new clone details as shown below.

 CLONE-TOPLOGY.JPG

 

 

Thus, SnapCenter helps to create, manage and track multiple copies at various copy infrastructures in Hybrid Cloud .  

 

  • Storage space savings:

 SPACE-SAVINGS.JPG

 

 

 

The last and the most interesting aspect of Copy Data Management is in showing a significant space savings in the overall storage consumption even after having multiple copies. In SnapCenter, NetApp Flexclone technology is fundamentally used behind every Read-Writable copies and the overall storage space savings is tracked in the dashboard against each plugin. As shown in the snippet, After running 19 similar Clones/Copies of the same production database (approx. 460G), SnapCenter had shown a tremendous space savings of overall 95%, thus making it a compelling solution for the hybrid cloud.

Comments
Member

Great article. An automation recipe using sccli would be an icing on the cake.

Member

Interesting work on Oracle hybrid cloud data management !

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.