Industry watchers all agree that Copy Data Management is becoming must-have technology. But not all solutions are the same. Design matters! This webinar will discuss the two major copy data solution designs, how they are different, and key use cases for both designs. Before you make any buying decisions, you¡¯ll want to understand these differences which will impact the success of your product roll out.
1 of 22
Downloaded 29 times
More Related Content
Design Matters: Why In-Place Copy Data Management is the Right Choice
1. Design Matters:
Why In-Place Copy Data
Management is the Right Choice
1
Peter Eicher
Catalogic Director of Marketing
peicher@catalogicsoftware.com
2. 2
Watch the
Webinar
To view this webinar recording, go to:
https://catalogicsoftware.com/about/webinars/
Or click the Webinars link in the upper right at
www.catalogicsoftware.com
4. IT Challenge = Copies EVERYWHERE
How: Making Copies
Production Copy
Why: Using Copies
Snapshot Copies
Full Copies
Replica Copies
Database Dumps
8 - 12 copies of each
data set*
Local Recovery
Disaster Recovery
Dev and Test
Reporting
Analytics
Compliance
Training
Sandbox, etc.
Protection
Business
Value
* Average number of
copies based on IDC
study
5. 5
Copy Data Management applies
Intelligence Automation Centralization
to copy creation & use
6. 6
And it
helps stop
the
Revenge of
the Clones
Hard Disk
LUN
Snapshot
Full Clone
Workload
Workload
Full Clone
Workload
Workload
Reserved for
Recovery
Full Clone
Workload
Workload
8. Real World Copy Example: Oracle deployment
Copy inefficiency at global bank
8
Every 20 TB of
Oracle production
storage¡
10 TB 10 TB
Initiates purchase of 340
additional TB for copies
1700% copy overhead!
10. 10
Out-of-Band
There are two main
CDM architectures
In-Place
Actifio
Catalogic DPX
Cohesity
Rubrik
Catalogic ECX
DellEMC
IBM
NetApp
11. 11
Host Server
Production Storage
CDM Appliance
Workload
Server
Controller
Copy Path
Access Path
Out-of-Band CDM
Often, but not always,
appliance-based
Typically uses a
block-
incremental
backup model
Which Catalogic did
ten years ago!
Usually has a
proprietary file
system to
support
snapshots and
scale out
13. 13
Host Server
Production Storage
CDM Appliance
Workload
Server
Controller
Copy Path
Access Path
Out-of-Band CDM: Good and Bad
Supports any
primary
storage
Adds a new storage stack
Backup storage
performance can be slow
for non-prod workloads
Dev-Test: uses
a different
storage stack
Easy access to
data copies
Backup impacts
the host
14. 14
In-Place CDM
Gains the benefits of any
array data reduction features
(varies with array)
Manages the
snap and copy
features of the
storage array
Maps to the
production
storage copy
(clone)
Host Server
Production Storage
Workload
ServerSnapshot: No
Data
Movement
Access Path
CDM
Software
Control
Plane
? Application integration
? Automation
? User self-service
? APIs
15. 15
In-Place CDM: Good and Bad
Does not require a new
storage stack
Dev-Test: uses the
same storage stack
as production
Host Server
Production Storage
Workload
ServerSnapshot: No
Data
Movement
Access Path
CDM
Software
Control
Plane
Near zero
impact to host
May not
support the
arrays you have
Easy access to
copies
Same performance as
production (assuming flash
storage)
16. 16
¡°But what if
I¡¯m not allowed
to do other
work on
production
storage?¡±Puzzled IT Dude
17. 17
In-Place CDM with Replication
Gains the benefits of any
array data reduction features
(varies with array)
Manages the
replication
features of the
array
Maps to the
production
storage copy
(clone)
Production
Storage
Workload
Server
Replication
Access Path
Non-Prod Array
(same vendor)
Clone
Uses non-prod
copy for
workloads
18. In-Place CDM Benefits to Software Development
Out-of-Band CDM
Dev-Test
Production Storage
3rd Party Storage Stack
Application Copy
Application Return
? How will application behave when developed on a different storage stack?
? How do you test performance?
In-Place CDM
Production Storage
Application Copy
Application Return
Production Storage
Dev-Test
? Develop on identical storage stack, so no surprises!
20. 20
Out-of-Band
Things to Consider
In-Place
If you are already looking for a new
backup solution
If your non-production workloads
don¡¯t require a lot of performance
If you want to better leverage the
storage investment you already made
If your non-production workloads
require same or similar performance
as prod
If you do a lot of in-house software
development
#5: The customer challenge is fairly simple to explain: there are too many copies of data.
If you look on the left side, you see that there are many processes that go into the making of data copies. Beginning with the production copy, you have full copies being made, you have snapshot copies, replication copies, database dumps in the case of database workloads. The end result is that a typical workload produces anywhere from 8 to 12 copies. But why are we making these copies?
Partly we are making copies for protection purposes. There are usually copies made for local recovery as well as remote or DR recovery. But these only form a part of the copy landscape. The truth is that most copies are created to help drive business value. These copies are used for multiple purposes, such dev and test, reporting and analytics, compliance purposes, training and so on. There are many different business drivers that result in multiple copies being created.