Why ONTAP For Hybrid Cloud - v4

NOTICE
• This deck is not for direct customer consumption but for internal
use.
• Validate the details with IMT and NetApp documentation for
precise set of information.
• Customer environment are different, test the uses cases before
actual production implementation
© 2022 NetApp, Inc. All rights reserved. --- NETAPP CONFIDENTIAL ---
Why NetApp
Hybrid Cloud for
Oracle Database
Reference Architectures
Ebin Kadavy
Database Expert TME
• Overview
Agenda • Reference Architecture and Benefits

• Standard architecture
• Classic architecture
• Enterprise Architecture
• Large Enterprise Architecture
• NetApp Cloud Manager technologies

• Cloud data sense
• App template
• Cloud sync
• Cloud Tiering
• Cloud Backup
Usecases - Not covered in Version 1
Sl.no Usecase Remarks

1 Oracle Database shards across hybrid multi- Not covered in Current version
cloud
2 Third party Data protection products / Not covered in Current version
Integration
3 Databases on VMware Cloud Not covered in current version
4 Containerized Databases Not covered in Current version
5 Spot, Cloud Insight /Monitoring Not covered in Current version
Hybrid Cloud Architecture
Overview and Market
Hybrid Cloud Architecture & how it’s helpful in your Digital Transformation
• Hybrid cloud architecture is the combination of public and private clouds by a wide area network or broadband
connection, through which applications and data can be shared and which can be managed as a single IT
architecture. Hybrid cloud infrastructure is well suited to fluctuations in demand for computing resources since it
enables businesses to scale from on-premises to public cloud-based to meet increased demand, and scale back from
the public cloud to on-premises (private cloud) only once demand recedes.
• Many organizations utilize public cloud infrastructure as a service (IaaS) to process some workloads while retaining
others in their private cloud, whether for cost, regulatory compliance, technology or security reasons. Because your
infrastructure is already split between two systems, it is easier to migrate to a different public cloud when a better
model enters the market.
Hybrid Cloud Scenarios
• Dynamic or frequently changing workloads. Use an easily scalable public cloud for your dynamic workloads, while leaving less volatile,
or more sensitive, workloads to a private cloud or on-premises data center.
• Separating critical workloads from less-sensitive workloads. You might store sensitive financial or customer information on your private
cloud, and use a public cloud to run the rest of your enterprise applications.
• Big data processing. It’s unlikely that you process big data continuously at a near-constant volume. Instead, you could run some of your
big data analytics using highly scalable public cloud resources, while also using a private cloud to ensure data security and keep sensitive
big data behind your firewall.
• Moving to the cloud incrementally, at your own pace. Put some of your workloads on a public cloud or on a small-scale private cloud.
See what works for your enterprise, and continue expanding your cloud presence as needed—on public clouds, private clouds, or a mixture
of the two.
• Temporary processing capacity needs. A hybrid cloud lets you allocate public cloud resources for short-term projects, at a lower cost
than if you used your own data center’s IT infrastructure. That way, you don’t overinvest in equipment you’ll need only temporarily.
• Flexibility for the future. No matter how well you plan to meet today’s needs, unless you have a crystal ball, you won’t know how your
needs might change next month or next year. A hybrid cloud approach lets you match your actual data management requirements to the
public cloud, private cloud, or on-premises resources that are best able to handle them.
• Best of both worlds. Unless you have clear-cut needs fulfilled by only a public cloud solution or only a private cloud solution, why limit
your options? Choose a hybrid cloud approach, and you can tap the advantages of both worlds simultaneously.
Hybrid cloud market
Hybrid Cloud Networking
for Enterprise workloads
Overview and Differences
Hybrid Cloud Networking
overview
A hybrid cloud network is a network that enables data transfers between on-
premises IT resources, private clouds and public clouds, in other words, a
hybrid cloud. Hybrid cloud computing supports the movement of workloads
across these environments and is connected by telecommunication and cloud
services and the infrastructure that supports those connections.
Businesses enable hybrid cloud network connectivity through a variety of ways:

Internet services, a VPN or a direct interconnection
Hybrid Cloud Networking options ( Connecting on-premises with AWS)
AWS (Amazon Web Services) provides you with a variety of

services to connect your on-premises infrastructure to the
Amazon VPC (Virtual Private Cloud)
• AWS Site-to-Site VPN (Virtual Private Network)
• AWS Direct Connect
Difference b/w VPN and Direct Connect for AWS
Hybrid Cloud Networking options ( Connecting on-premises with Azure)
ExpressRoute provides direct connectivity to Azure cloud services and connecting Microsoft’s global network. All
transferred data is not encrypted, and do not go over the public Internet. This architecture is suitable for hybrid
applications running large-scale, mission-critical workloads that require a high degree of scalability and resiliency.
VPN Gateway provides secured connectivity to Azure cloud services over public Internet. All transferred data is
encrypted in a private tunnel as it crosses the internet. This architecture is suitable for hybrid applications where the
traffic between on-premises hardware and the cloud is likely to be light, or you are willing to trade slightly extended
latency for the flexibility and processing power of the cloud.
Difference b/w various Azure Networking services
NetApp Hybrid Cloud
Reference Architectures for
Oracle database
Overview and Benefits
Different types of Hybrid Cloud Reference Architectures
Each Hybrid Cloud architecture discussed here uses a distinct disaster recovery (DR) pattern (with NetApp SnapMirror,
Oracle data guard or mix of both) based on the theme of the overall architecture. The cost factor, database recovery time and load
balancing will be the key decision factors while choosing between snapmirror and oracle data guard model. Depending on your
objectives, you can mix and match the primary database and disaster recovery architectures to fit your needs. The following
architectures puts the architectures in order of increasing levels of capability, complexity, and cost.
• Standard Architecture
Simple & Standard architecture using Oracle Data guard for Data replication, and Load Balancing. Not a managed offering from Cloud
• NetApp’s Classic Architecture
Simple & Standard architecture using NetApp SnapMirror for Data replication . Not a managed offering from Cloud
• Enterprise Architecture
Mix of Data Guard and SnapMirror but managed infrastructure for their Oracle environment
• Large Enterprise Architecture
Same as Enterprise architecture but with more focus to Availability and Business continuity
Standard Reference
Architecture
Standard Reference Architecture
• Simple & Standard architecture using Oracle technologies for Data replication, Load balancing and
DR
• Data guard or Active data guard is the classic and familiar DBA tool for DR, Migration and HA / load
balancing
• NetApp can propose Cloud Volumes ONTAP as storage to host Oracle data guard standby database
• In this model, Customer has to manage everything in this hybrid cloud deployment ; their cloud
storage and compute infrastructure for their Oracle environment
• Connectivity between sites can be mostly via VPN or use AWS Direct Connect or Azure Express Route
Standard Reference Architecture
Benefits :
- Leverage CVO for secondary needs like Backup, Dev/test, reporting,

analytics, etc. using NetApp SnapCenter
- Get additional storage space efficiency by enabling fabric pool or cloud
tiering on CVO
- Not a managed service from AWS ,Azure but provides more flexibility and
secure
- Database Migration from on-premises can be performed seamlessly
- Application migration can be performed using NetApp cloud sync or other
cloud native or third-party tools
NetApp’s Classic
Architecture
Classic Architecture
Using NetApp SnapMirror
Overview
- DR Data replication using NetApp SnapMirror

- Cloud volumes ONTAP (CVO) can be used as the storage to
host the DR database
- Customer should enable VPN or High-speed Network
On-premises connectivity like Azure Express route and AWS Direct connect
DataCenter between sites to keep the database synchronization process
seamless and during failover for applications to access over
Private subnet the Network if not hosted in the cloud
- Unlike Data guard, It doesn’t require Database VMs to be up
DB VM
Standby VM or and running on DR site.
Dev/Test VM
VPN - The data in SnapMirror destination is accessible only via
Flexclone ( r/w copy)
- Automation is required to break the mirror relationship,
AWS Direct
Connect perform in-place restore of database using Oracle consistent
snapshot , mount the storage, and recover the database
Data Log Redo
Benefits :
Data Log Redo snapshot
- 3-2-1 backup strategy can be met using snapcenter and cloud
Tiering / Backup backup for applications
Backup
to S3 - Snapshots replicated to CVO can be leveraged for Dev/test,
Cloud Volumes ONTAP
SnapMirror reporting, analytics etc using NetApp SnapCenter
- Storage space benefit by enabling fabric pool or cloud tiering
Availability zone
on CVO and on-premises volumes
- Significant cost reduction in cloud compute while DR VMs are
offline
Enterprise Class
Architecture
Enterprise Class Architecture - I
Fully Managed Storage service using Amazon FSxN
Overview
- DR Data replication using Oracle data guard (DG) / Active

data guard (ADG)
- Active Hot standby for quick and transparent DR failover
- Amazon FSx for NetApp ONTAP (FSxN) and Azure netapp
files (ANF) can be used as the storage to host the standby
database
On-premises - FSxN and ANF is a fully managed storage
DataCenter - Customer should enable VPN or High-speed Network
Private subnet connectivity like Azure Express route and AWS Direct
connect between sites to keep the database
DB VM
synchronization process seamless and during failover for
Oracle Active Data Guard applications to access over the Network if not hosted in the
RMAN + OSB
cloud
- Read IOs can be load balanced with Active data guard
- For ANF – Choose RMAN backups or custom scripts to
take snapshots
Data Log Redo Benefits :

VPN
snapshot
Data Log Redo - No Cloud storage patching, maintenance or manual
AWS Direct
Connect / Azure Tiering / Backup intervention required unlike CVO
Express route Azure NetApp Amazon FSX S3 /Blob - Use SnapCenter to protect Oracle database on-premises
Files for ONTAP and data guard standby separately . Use Cloud Backup for
offsite backup to Cloud object storage from FSxN storage
Availability zone - Get additional storage efficiency by enabling fabric pool or
cloud tiering
- Database / Application Migration can be done seamlessly
without much manual intervention using Data Guard.
- Better read performance for applications by load balancing
the requirement to active data guard standby environment
Enterprise Class Architecture -II
Full managed Database and Storage service using AWS RDS Custom and FSxN
Overview
- DR Data replication using Oracle data guard (DG) / Active

data guard (ADG)
- Active Hot standby for quick and transparent DR failover
- Amazon FSx for NetApp ONTAP (FSxN) can be used as the
storage to host the standby database
On-premises - FSxN is a fully managed storage service and RDS Custom is
DataCenter managed database service
- Build a RDS Custom database and then drop the database
Private subnet
and build a fresh data guard standby database
RDS Custom
DB VM EBS - Customer should enable VPN or High-speed Network
connectivity like Azure Express route and AWS Direct connect
Oracle Active Data Guard RMAN + OSB between sites to keep the database synchronization process
seamless and during failover for applications to access over
the Network if not hosted in the cloud

VPN
Data Log Redo - No maintenance or manual intervention required for Cloud

AWS Direct
Connect storage and database
Tiering / Backup
snapshot
Backup - Use SnapCenter to protect Oracle database on-premises and
to S3 data guard standby separately . Use Cloud Backup for offsite
Amazon FSX for ONTAP
backup to Cloud object storage from FSx
Availability zone - Get additional storage efficiency by enabling fabric pool or
cloud tiering
without much manual intervention using Data Guard.
- Better read performance for applications by load balancing
the requirement to active data guard standby environment
Enterprise Class Architecture - III
Fully managed service with NetApp SnapMirror replication Overview
- DR Data replication using NetApp SnapMirror

- Amazon FSx for NetApp ONTAP (FSxN) can be used as the storage
to host the standby database
- FSxN is a fully managed storage service and RDS Custom is
managed database service
- Customer should enable VPN or High-speed Network connectivity
like Azure Express route and AWS Direct connect between sites to
On-premises keep the database synchronization process seamless and during
DataCenter failover for applications to access over the Network if not hosted in
the cloud
Private subnet
- Build a RDS Custom database and then drop the DUMMY database.
RDS DB VM EBS Keep it ready for DR database volumes to be re-discovered and
mounted on the RDS DB VM to build DR database during outage.
VPN RMAN + OSB
- Unlike Data guard, It doesn’t require Database VMs to be up and
running on DR site.
- The data in SnapMirror destination is accessible only via Flexclone (
AWS Direct r/w copy)
Connect
- Automation is required to break the mirror relationship, perform in-
place restore of database using Oracle consistent snapshot , mount
Data Log Redo the storage, and recover the database
- Not a suitable approach as customer end up paying for RDS when it
Data Log Redo is not being used actively unless during DR failover
snapshot Tiering / Backup
Backup Benefits :
to S3
Amazon FSX for ONTAP
SnapMirror - No maintenance or manual intervention required for Cloud storage
Availability zone and for database when the production has failed over to Cloud
- 3-2-1 backup strategy can be met using snapcenter and cloud
backup for applications . Use SnapCenter to protect Oracle
database on-premises and replicate to FSx . Use Cloud Backup for
offsite backup to Cloud object storage
- Get additional storage efficiency by enabling fabric pool or cloud
tiering
Large Enterprise
Architecture
Large Enterprise
Architecture
Large Enterprise Architecture - I
Oracle data guard (sync) between on-premises and async to cloud storage
Overview
- 2 hot standbys. One is synchronous with RPO=0 and near

Zero RTO and other far distant will be asynchronous to cloud
storage
- DR Data replication using Oracle data guard / Active data
guard (ADG)
- Cloud volumes ONTAP (CVO), FSxN, ANF can be used as
the storage to host the standby database
- FSxN and ANF are managed storage offerings and
supported by cloud provider
connectivity like Azure Express route and AWS Direct
connect between sites to keep the database synchronization
process seamless and during failover for applications to
access over the Network if not hosted in the cloud
Benefits :
- Data availability percentage is high and better-read

performance
- Leverage CVO, FSxN for your secondary needs like Backup,
Dev/test, reporting, analytics etc using NetApp SnapCenter
- Get additional storage space savings by enabling fabric pool
or cloud tiering on CVO
- No Manual intervention or maintenance required for FSxN
and ANF
without much manual intervention both locally and @ cloud
Large Enterprise Architecture - II
Oracle data guard (sync) between on-premises and snapmirror async to cloud storage
Overview
- Remote DR replication using NetApp SnapMirror and local DR

solution using Oracle data guard
- Amazon FSx for NetApp ONTAP (FSxN) and CVO can be used
as the storage to host the standby database
- FSxN is a fully managed storage service
connectivity like Azure Express route and AWS Direct connect
On-premises DataCenter between sites to keep the database synchronization process
seamless and during failover for applications to access over the
Network if not hosted in the cloud
- Synchronous Data guard helps in RPO =0 and RTO near zero
Private subnet - Remote Database VMs on Cloud DR site can be kept offline or
Oracle data guard
invoked freshly from the template when the remote DR failover
VPN DB VM happens.
( Sync) - The data in remote SnapMirror destination is accessible only
via Flexclone ( r/w copy)
Azure Express
- Automation is required to break the mirror relationship, perform
Route / AWS
Data Log Redo Direct connect in-place restore of database using Oracle consistent snapshot ,
mount the storage, and recover the database

Data Log Redo
- High available solution. Improves read IOPS if local standby is
hosted on Active data guard
SnapMirror Tiering / Backup - No maintenance or manual intervention required for Cloud
Async Backup storage hosted on FSxN
snapshot to blob - 3-2-1 backup strategy can be met using snapcenter and cloud
Availability zone backup for applications . Use SnapCenter to protect Oracle
database on-premises and replicate to FSx . Use Cloud Backup
for offsite backup to Cloud object storage
- Get additional storage efficiency by enabling fabric pool or
cloud tiering
Large Enterprise Architecture - III
Snapmirror Sync between On-premises and Oracle data guard (async) for Cloud
On-premises DataCenter
 2 Level of protection and is exactly opposite to the
previous architecture –II
 Local protection is synchronous via
Private subnet
Snapmirror / MCC providing RPO=0 and
Oracle Data Guard /ADG (Async) DB VM RTO near zero
 Remote protection is asynchronous using

Oracle Active data guard.
VPN
Azure Express  CVO / FSxN can be leveraged for secondary

Route / AWS
Direct connect Data Log Redo needs like Backup and Clones using SnapCenter
Data Log Redo Data Log Redo
 Take offsite backups to Cloud object storage like

snapshot
SMBC/ MCC/ Backup AWS S3, Azure Blob using Cloud backup for
Sync Relationship to blob applications
Availability zone
 Improves the overall READ IOPS by load
balancing between on-premises and CVO /FSxN.
Large Enterprise Architecture -IV
On-premises DataCenter  2 Level of protection and is exactly same as

architecture –III
 Local protection is synchronous via
Private subnet Snapmirror / MCC providing RPO=0 and
Oracle ADG (Async) DB VM
RTO near zero
 Remote protection is asynchronous using

Oracle Active data guard.
VPN
Azure Express  Azure NetApp Files is leverage at remote DR end.

Route
Data Log Redo Backup and Clones can be addressed using
Data Log Redo Data Log Redo Oracle RMAN or by leveraging customer scripts to
snapshot and Flexclone
 ANF provides better READ performance and

SMBC /MCC/
Azure NetApp Files READ IOPS can be load balanced between on-
Sync Relationship
premises and ANF.
Availability zone
Large Enterprise Architecture - V
On-premises DataCenter
 2 Levels of protection and the only difference to
architecture – III / IV
 Both Synchronous and asynchronous
Private subnet
replication is addressed by NetApp
DB VM SnapMirror sync/ MCC and SnapMirror
VPN async.
Azure Express
Route / AWS  CVO / FSxN can be leveraged for secondary
Direct connect
needs like Backup and Clones using SnapCenter
Data Log Redo  3-2-1 backup strategy can be met using

Data Log Redo Data Log Redo
snapcenter and cloud backup for applications .
Use SnapCenter to protect Oracle database on-
premises and replicate to FSx . Use Cloud Backup
snapshot
SMBC /MCC / Backup for offsite backup to Cloud object storage
Sync Relationship to blob
Availability zone .
SnapMirror Async
NetApp’s Cloud data
Services
NetApp Cloud Manager
services
Relevant services for Oracle application life cycle
NetApp Cloud Manager Services
List of Cloud Manager features / services presently usable for Oracle database application infrastructure
App Template
Service
NetApp App template service
No–Code automation
• Provides a framework for designing application storage

infrastructure combining multiple capabilities. Customer can
simplify their infrastructure provisioning process and customize
it according to their best practices.
• Supports provisioning for both on-premises and cloud, enable

Cloud backup, enable Snapmirror replication between volumes
etc
NetApp App template service
No–Code automation
App template Service ( Cont..)
Cloud Data sense
NetApp Cloud Data Sense for Oracle Database
• Can be deployed on-premises or in the cloud (AWS/ Azure)
• Independent instance inside customer’s network
• The customer’s data never leaves their environment and network
• Connects directly to Oracle database

• During Oracle DB scanning we are taking a sample of each table
and parsing sample’s content in order to determine which data the
column holds:
• For each column’s row in the table, we are trying to fit the relevant pattern.
• The column name does not affect the extraction results.
• The scan in not a real time, it runs once a day.
We support the extraction of:

• SSN number, BSN, CPF, Spanish Tax ident. Number, Maltese id
• Email
• Password (is planned for next release 1.11 – Check with PM on this)
We currently do not extract:

• Phone number
• Address
• CVV numbers
NetApp Cloud data sense for database
screenshots
NetApp Cloud data sense for database
screenshots
Cloud Data sense – Sample SQL Demo for reference
Cloud Tiering and
Fabric Pool
NetApp Cloud Tiering & Fabric pool
• Able to tier infrequently accessed or

aged data to StorageGrid and cloud
object-based storage
• Cloud Tiering is based on fabric pool

COLD DATA
feature of ONTAP but with multi-
cluster management and additional
reporting
• Reporting on savings for all Cloud
Tiering instances available
• Tiers data only when the aggregate

reaches 50% and meets the cooling
period
Cloud Tiering
Cluster Dashboard view
• Shows total clusters

• Indicates on-premises and CVO
• Can show undiscovered clusters
• Each cluster reports

• Health
• Current saving
• Additional saving opportunities
• Setup tiering per cluster

• ONTAP on-premises
• Tier to StorageGRID, Azure, AWS, or GCP
• Cloud Volumes ONTAP (CVO)
• Tier only to cloud (Azure, AWS, or GCP)
Cloud Tiering – On-premises overview
NetApp Cloud Tiering for Oracle database storage
Associate specific storage volumes within on-premises cluster to a tiering policy
- Tiering should be enabled based on the

access patterns
- If you are retaining snapshots or oracle

archive logs for a longer period on your
flash storage, then Tiering is
recommended.
- Provide cooling period /days that has

nearly no chance of accessing the data
back to storage
- Active database volumes are not

recommended for direct tiering because a
table scan can still retrieve the old data
(less than 90 days old) thus causing
performance problems
- When used with Oracle ADO Storage

tiering then it’s highly recommended
Oracle ADO Storage Tiering with Fabric pool /Cloud Tiering
• Oracle storage tiering enables another

tablespace on a different storage
volume/aggregate to tier the very old data
without affecting the existing table. It is
based on table partitions.
• Fabric pool or cloud tiering can be

enabled on the Oracle ADO tiered storage
(WARM storage shown in this graphic)
thus giving the flexibility for more cooling
period and is Oracle aware
• You can also move the entire data to your

preferred object storage for better savings
• Avoid Bad queries – Full scan of large

tables may create performance problems
Cloud Sync
NetApp Cloud Sync for Oracle applications
To sync or migrate files between different storage systems
NetApp Cloud Sync for Oracle Applications
Cloud Sync
- Helpful during migration of non-oracle database volumes like Oracle Apps ,
Weblogic and other web applications
- It is not recommended for Live database volumes as it can corrupt the
database
- Supports applications hosted on NFS/ SMB volumes
Cloud Backup
NetApp Cloud Backup for Applications
Backup to AWS S3/ Azure Blob storage
Cloud Backup for Application
- Introduced in April 2022, which can allow DBAs to take offsite

backups ( snapcenter driven) to Cloud object storage.
- It supports non-virtualized databases
- Supports offsite backups from multiple snapcenter server and

restore is always in-place
- Restore to alternate location is not supported for Oracle

database
- Supports AWS S3 and Azure blob in the first release
- If you are using the regular Cloud backup service for volumes
or system manager, then you need to enable the relationship
manually for your applications volumes. You can now use
snapcenter or third-party backup products to take oracle
consistent snapshots which can then be replicated by CBS or
System manager.
Backup to AWS S3 / Azure Blob using Cloud Backup for Applications
Oracle Backup Management for Cloud
UseCase Matrix
Segment Oracle Backup Usecases SnapCenter CB Apps - SaaS Other Solutions

Hybrid Cloud On-premises Backup to S3 /Blob for Long term with SnapCenter SnapCenter + CBS volumes
(On-premises + retention in Cloud &
Limited to Backup & In-place restore
Cloud) (Offsite backup) Oracle RMAN
On-premises Oracle Backup to Cloud Volumes Scripting / Oracle RMAN
ONTAP ( CVO) as secondary storage
Backup of Oracle hosted on DR ( managed by Scripting / Oracle RMAN
Oracle Data Guard/ ADG) storage in CVO
On-premises Oracle Backup to Amazon FSxN Scripting / Oracle RMAN
as secondary storage
On-premises Local On-premises Oracle Backup Scripting / Oracle RMAN
ONTAP -> ONTAP
Public Cloud Backup of Oracle DB on Amazon FSxN Roadmap Scripting / Oracle RMAN
Backup of Oracle database hosted on CVO as Roadmap Scripting / Oracle RMAN

Primary
Backup of Oracle DB hosted on ANF as Scripting / Oracle RMAN
primary
Backup of Oracle DB hosted on CVS as Scripting / Oracle RMAN
primary
Oracle Data Protection & Management with SnapCenter / CBS
Platform Support and Deployment
Oracle DB on Oracle DB on ORACLE DB on Oracle DB on Oracle DB on Oracle DB on Oracle DB on

Linux Linux Windows Windows AIX Solaris Hybrid Cloud
Backup Products on-premises On-premises On-premises on-premises deployments (Linux)
(Baremetal) (Vmware) ( Baremetal) (VMware)
SnapCenter • Backup to CVO /FSx

Only SAN & Limited • Primary Backup on
layouts CVO /FSx
SnapCenter plugin
Creator
SnapManager (SMO)
/ SnapCreator (SCC)
SMO - EOS ( SMO EOS)
CBS Apps
Backup to S3 /Blob
Other Solutions RMAN / RMAN / RMAN / RMAN / Partners RMAN / Partners RMAN / RMAN / Partners
Partners Partners Partners Partners
Thank You.
http://mysupport.netapp.c
om/snapcenter/resources Have query? contact: ebin.kadavy@netapp.com

Why ONTAP For Hybrid Cloud - v4

Uploaded by

Copyright:

Available Formats

You might also like

Why ONTAP For Hybrid Cloud - v4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Why ONTAP For Hybrid Cloud - v4

Uploaded by

Copyright:

Available Formats

NOTICE

Agenda • Reference Architecture and Benefits

• Large Enterprise Architecture

• NetApp Cloud Manager technologies

Sl.no Usecase Remarks

4 Containerized Databases Not covered in Current version

5 Spot, Cloud Insight /Monitoring Not covered in Current version

Businesses enable hybrid cloud network connectivity through a variety of ways:

AWS (Amazon Web Services) provides you with a variety of

• NetApp’s Classic Architecture

• Large Enterprise Architecture

- Leverage CVO for secondary needs like Backup, Dev/test, reporting,

- DR Data replication using NetApp SnapMirror

- DR Data replication using Oracle data guard (DG) / Active

Data Log Redo Benefits :

- DR Data replication using Oracle data guard (DG) / Active

Data Log Redo Benefits :

Data Log Redo - No maintenance or manual intervention required for Cloud

- DR Data replication using NetApp SnapMirror

- 2 hot standbys. One is synchronous with RPO=0 and near

- Data availability percentage is high and better-read

- Remote DR replication using NetApp SnapMirror and local DR

Data Log Redo Benefits :

 Remote protection is asynchronous using

Azure Express  CVO / FSxN can be leveraged for secondary

 Take offsite backups to Cloud object storage like

On-premises DataCenter  2 Level of protection and is exactly same as

 Remote protection is asynchronous using

Azure Express  Azure NetApp Files is leverage at remote DR end.

 ANF provides better READ performance and

Data Log Redo  3-2-1 backup strategy can be met using

• Provides a framework for designing application storage

• Supports provisioning for both on-premises and cloud, enable

• Independent instance inside customer’s network

• The customer’s data never leaves their environment and network

• Connects directly to Oracle database

We support the extraction of:

We currently do not extract:

• Able to tier infrequently accessed or

• Cloud Tiering is based on fabric pool

• Tiers data only when the aggregate

• Shows total clusters

• Each cluster reports

• Setup tiering per cluster

- Tiering should be enabled based on the

- If you are retaining snapshots or oracle

- Provide cooling period /days that has

- Active database volumes are not

- When used with Oracle ADO Storage

• Oracle storage tiering enables another

• Fabric pool or cloud tiering can be

• You can also move the entire data to your

• Avoid Bad queries – Full scan of large

Cloud Backup for Application

- Introduced in April 2022, which can allow DBAs to take offsite

- It supports non-virtualized databases

- Supports offsite backups from multiple snapcenter server and

- Restore to alternate location is not supported for Oracle