This document discusses factors for a successful cloud migration and provides recommendations. It identifies 5 key factors for cloud success: 1) identifying and monitoring metrics, 2) challenging the status quo, 3) keeping options open to avoid lock-in, 4) recognizing public cloud is not always the answer, and 5) understanding contractual obligations. It also provides an example use case of using public cloud for disaster recovery and discusses how to ensure IT agility with a unified approach to both public and private clouds.

1. Making Your Journey
to the Cloud a
Success
Nigel Tozer

2. 22
Agenda
• Industry Trends & the Cloud
• 5 Factors for Cloud Success
• Public Cloud Use Cases
• Ensuring Agility

3. 3
IT Change Agenda
Seismic IT Change
Modern IT
Third Platform
Enterprise Mobility
Innovation
IT as a Service
Service Continuity
Hyperconvergence
Virtualisation & Cloud
Virtualisation
Migration to the
Cloud
Next Generation Storage
& Storage Mgmt.
Big Data
Software Defined
Storage
Solid State Storage
Consolidation of
Replication, Snapshot,
& Backup Markets
Supporting The Digital Enterprise

4. 44
The IT Spending Shift: From Capex to Opex
Capital Expenditure
Operational
Expenditure
Premises
Infrastructure
Compute
Storage
Watchwords:
Strategic, Low-risk, Evolutionary
Before….

5. 55
The IT Spending Shift: How do you manage it?
Capital
Expenditure
Operational Expenditure
Cloud
Experiment
Change
Tactical
Strategic
Watchwords:
Innovate, Speculate,
Agile, Revolutionary
Now….

6. 6
Work With the Business
Establish strong links into lines of business
• Pro cloud?
• Anti-cloud?
• Either way – IT needs to be the trusted
advisor
Identify early wins
• Mobile access file sharing?
• New service in the cloud?
• Demonstrate the savings or benefits at every
stage; good metrics and record keeping is
essential
Don’t Set Yourself at Odds
With the Board

7. Five Factors for Cloud Success

8. 88
1. Identify key metrics and monitor them properly
• The Imperative of Metrics
 Get a grip on reporting
 Get a grip on sprawl
 Automate where possible
 Be mindful of ingress and
egress charges

9. 99
1. Identify key metrics and monitor them properly
• The Imperative of Metrics
Custom
Reports
Metrics
Data
Analytics
Log Monitoring
& Automation

10. 1010
1. Identify key metrics and monitor them properly
• The Imperative of Metrics
Controlling costs paves the way for new projects…
Custom
Reports
Metrics
Data
Analytics
Log Monitoring
& Automation

11. 1111
2. Challenge the Status Quo in the Cloud
• The Imperative of Staying Ahead  Public Cloud is an ideal
place to experiment
 Reducing on premise costs
will provide more funds for
‘Your Organisation 2.0’
 Use the cloud for Dev & Test

12. 12
• The Imperative of Staying Ahead
2. Challenge the Status Quo in the Cloud
Consider portability from the start…
database
Management &
Reporting for Data
Services
Leverage Dedupe to return
only changed blocks to
production site
database

13. 1313
3. Keep your options open
• The Imperative of Avoiding Lock-in  Don’t get locked-in by
hypervisors
 Don’t get locked-in by
Hardware
 Ensure you can move
workloads between clouds

14. 14
3. Keep your options open
• The Imperative of Avoiding Lock-in
Manual
Conversion
Manual
Shipping

15. 1515
3. Keep your options open
• The Imperative of Avoiding Lock-in
And then there’s the issue of governance…
IaaS/DRaaS
Common Lock-in Points
• Disk Hardware
• Snapshot Engines
• Replication Software
• Cloud Gateways or
WAN Accelerators
• Dedupe Appliances

16. 1616
4. Don’t assume Public Cloud is always the answer
• The Imperative of Right Time, Right Place
 Compliance and other
Systems of Record are good
candidates for on
premise/Private Cloud
 Fragmenting compliance
tools over multiple silos can
lead to issues
 Don’t lose important data in
the cloud

17. 1717
4. Don’t assume Public Cloud is always the answer
• The Imperative of Right Time, Right Place
Cloud choices are growing…
databases
Mobile
XaaS
compliance
Unified: Governance,
Compliance & eDiscovery compliance
compliance

18. 1818
5. Know what you are signing up to
• The Imperative of Careful Research
 What storage or compute
price models suit your
expected use cases?
 Public Cloud, IaaS, PaaS, or
other *aaS options?
 What legal implications are
there for your organisation?
Just because you start something in
one cloud, it doesn’t mean it has to
stay there

19. 1919
“If you don't know where you're going, any road
will take you there”
5. Know what you are signing up to
• The Imperative of Careful Research

20. Use Case: Public Cloud Disaster Recovery

21. 2121
Why is Public Cloud a Good Option for DR?
• Cost & Choice!
• You only Pay for what you consume
• You probably already have an account
or bundled capacity
• A wide range of DIY or integrated
service options
• Scalability
• The elastic nature of Cloud
• Always On/Utility
• Assists your own goals of Service
Continuity
IaaS/DRaaS
Service
Providers
?

22. 22
Why is Public Cloud DR Difficult?
• It’s Complicated – Lots of variables
to manage
• Hypervisor and Hardware Lock-in
• Transport – getting data to and
from it (and associated cost)
• Repatriation – once in the cloud,
will you ever get it back?

23. 2323
What?
Virtual Machine
Recovery
Physical Machine
Recovery (P2V)
File/Folder Recovery
Application Recovery
Where?
Local VM?
Local Data Center?
Remote Data Center?
DRaaS?
IaaS?
Public Cloud?
When?
Less than 15 mins?
Less than 1 hour?
Less than 4 hours?
Less than 24 hours?
Less than 48 hours?
How?
Application
Replication?
Guest Replication?
Hypervisor-Based
Replication?
Snapshots/Mirroring?
Deduplication?
Cloud?
Recovery Alignment: Data Logistics and the Cloud

24. 24
What’s more important:
The Application or the Virtual Machine?
 Application integrated protection
provides consistency, but not all
methods provide the same recovery
options
 The majority of recoveries are
applications and files, not machines
 Restoring data is not the same thing as
recovering the service/application
 The type of protection should not
sacrifice one to achieve the other
VS OR

25. 2525
Global Dedupe,
Encrypted
Commvault: Cloud Native
database
Multiple Collection Methods
• Policy based & Automated
• Agentless
• App Aware
• HW Snapshots
• Incremental Forever, OnePass
• Client Dedupe
Multi-OS
Fault Tolerant
Load Balancing
Single Point of
Management & Reporting Effective Cloud Transport
• No Gateway Appliance
Required
• Changed Blocks Only
• Encrypted
• Object Storage Support
• Manage Cloud Protection
• DASH Full Technology
• Automated Restore
Recovery, Reverse DR
Global Dedupe
• Client or Media Server
• Any disk
• Many Arrays/Sites
Cloud
IaaS/DRaaS

26. 26
Example: Live Sync in Action
Protection Operation is run against VMs to
be replicated : This will be a low impact
incremental backup
1
After Protection Operation is Complete Changed
Blocks are Shipped to Standby VMs: This can be a
synchronous or asynchronous operation
2
2
OR DASH Copy is Performed to Secondary
Site: Synthetic Full, changed blocks, deduped
3
Then Changed Blocks are Overlaid on
Replicated VMs: via Automated Restore
4
1
Primary
Datacenter Cloud/DR Site
3
DASH Copy

27. Ensuring Agility

28. 29
How Cloud is Consumed Today
Innovation
Tier
Production
Tier
Governance/
Records Tier
Public Cloud Private Cloud
Level of Cloud Use

29. 3030
Commvault: Unify Clouds with Data Services
Innovation
Tier
Production
Tier
Governance &
Records Tier
Public Cloud
&
Private Cloud
CommVault
Cloud Data Management
Reporting/Metrics
Provision/Expire VMs
DR/Portability
Dev & Test/Return
Protection/Mobility
Search/Productivity
Governance
Unified Data Services

30. 3131
Summary
• Work with your business
• Do your Cloud homework
• Keep your options open
• We are still in the early
adopter phase
• Get expert help

31. 32
MAKE YOUR DATA WORK FOR YOU.
COMMVAULT.COM | GET-INFO@COMMVAULT.COM
DATA CONVERSATIONS
HAVE CHANGED.
CLOUD
COMPLEXITY AND SPEED
MODERNISING LEGACY SYSTEMS AND APPLICATIONS
MOBILE WORKERS
BIG DATA
INNOVATION
…