iland and Veeam recently conducted a data protection survey of IT organizations worldwide. In this webinar, we summarize and analyze the survey responses so you canunderstand today’s data protection landscape. Then, we cover best practices that can help ensure thatyour organization, and its data,are properly protected Watch the webinar on-demand: https://www.iland.com/wb-data-protection-report/

1. The Great Disconnect of Data Protection:
Perception, Reality and Best Practices
Will Urban | Senior Marketing Technologist
Pete Benoit | Enterprise Solution Architect

2. Agenda Overview
Status Overview of Data Protection in Virtual Environments Today
Backup vs. Disaster Recovery: Understand the Differences
How to Implement a Best Practice Driven Data Protection Strategy
Overview of Best Practices and Tips for Data Protection, Backup and Disaster Recovery
1
2
3
4

3. Status Overview of Data Protection in
Virtual Environments Today

4. Data Protection – Virtual Machines
Virtual machine (VM) environments have been adopted by a majority of organizations. In fact,
many organizations even run on complete virtual environments.
Virtual machine environment data protection concerns:
● Application synchronization / data mirroring
● Efficient snapshot management
● Frequent testing of the restore process
● Frequent tracking of virtual machines

5. Expectations vs. Reality
iland and Veeam® recently teamed up to survey 300 IT
organizations worldwide to learn how they’re protecting
their virtual environments.
The respondents were separated by number of VMs – ranging
from 1 to more than 250 VMs.
Following is a quick review of the numbers…

6. Data Protection Statistics
80% of respondents have some portion
of their virtual environment in the cloud.
89% of respondents have no ability to recover
their critical applications within minutes.

7. Data Protection Statistics
Significant portion of organizations queried only tested their backups annually or at recovery –
and 50% of organizations use on-premises snapshots as one of their primary backup methods.

8. A Few Other Facts
• An average of nearly 23% of organizations backup half or less of their VMs daily.
• 44% of organizations rely on some form of replication as part of their backup and / or DR strategy.
• 24% of organizations have experienced data corruption or a ransomware attack.
• Nearly 50% of organizations protect less than half their VMs with a DR plan.
• Only 39% of organizations test their DR plans monthly or quarterly.
• 25% of organizations have a zero data loss standard.

9. Backup vs Disaster Recovery:
Understand the Differences

10. What Is a Backup?
Backups are the copies of your virtual and physical systems, including all of the data and applications in those systems.
The goal of a backup is to have a copy of your organization’s IT environment.
Backup Considerations:
• Typically done daily
• GFS retention strategy
• Often mandated by operational or regulatory requirements
• Often stored long-term for regulatory reasons
• Granularity of data decreases over time
• Testing of recovery is a manual process
Backups get your data back.

11. What Is Disaster Recovery?
Disaster recovery (DR) is a system of replication designed for IT resilience.
It continuously syncs a copy of the VM at a secondary location and enables you to fail over in seconds or minutes.
DR brings your environment online
somewhere else.
DR Considerations:
• Consistent replication throughout the day
• Designed for tighter Recovery Point Objectives (RPO)
• Quick Recovery Time Objectives (RTO)
• For known interruptions, as well as disasters
• Ability for non-disruptive testing

12. Backup and DR – an RTO and RPO Example
● Recovery Time Objective (RTO) – How long will it take to get my data back?
● Recovery Point Objective (RPO) – How much data will I lose once recovered?
Your systems are backed up every night at 7:00 p.m. You also are running a DR system with continuous replication.
Disaster strikes! At 6:00 a.m. a power outage hits the building, taking down your data center. How do you recover?
Backup Scenario
• At 6:01 a.m. you go find your backups.
• Then, you spend the next few hours finding, fixing and re-starting your
infrastructure (assuming your power is back).
• At 5:00 p.m. a few of your major systems are back online. Your RTO on
those systems is 11 hours.
• The systems are restored to the last backup time – which is 7:00 p.m.
yesterday. So, your RPO on those few systems is 22 hours.
• The remaining systems take longer, and thus have much longer RTO &
RPOs.
DRaaS Scenario
• At 6:01 a.m. you press “Fail Over” on the DR solution.
• Within 4 minutes, at 6:05 a.m., the systems are back up in the
cloud. The recovery time (RTO) is 4 minutes.
• The data replicated to the recovery site is consistent up until 5:58
a.m. – just before the power went out. So, your recovery point
(RPO) is 2 minutes.

13. Review How to Implement a Best Practice
Driven Data Protection Strategy

14. Below are four key areas to consider when developing a disaster recovery and backup plan for virtualized environments.
Framework
The first step in implementing and adopting a best practice strategy is recognizing how powerful
virtualization is for an organization’s disaster recovery efforts.
• When developing a DR strategy it is important to identify
which resources are the most important – “mission critical”
– to the organization.
• The most critical VMs need to be monitored closely for
failure, and have a higher level of protection and resilience.
• Design overlapping protection schemes from backups to DR
to match the priority tier of the system.
Identify Critical Virtual Machines
Establish Strategy for Backup and
Recovery
Test
Automate

15. Framework
• Design a policy of protection for each tier of the environment.
• When identifying software, understand the difference
between a “snapshot” (point in time virtual copies of data) a
backup and an off-site resilient solution.
• Have runbooks in place for every type of recovery solution so
the process is known.
Establish Strategy for Backup and
Recovery
Test
Identify Critical Virtual Machines
Automate
Below are four key areas to consider when developing a disaster recovery and backup plan for virtualized environments.

16. Framework
• Test, test, test!
• After your first backup, test the recovery process to ensure
everything works flawlessly and as planned.
• Test your DR plan - almost all of it is non-disruptive.
Identify Critical Virtual Machines
Establish Strategy for Backup and
Recovery
Test
Automate
Below are four key areas to consider when developing a disaster recovery and backup plan for virtualized environments.

17. Framework
• Creating processes when there isn’t a disaster saves time
when there is.
• Automation is not only a great time saver, but automating
key tasks can also prevent human error.
No disaster recovery / backup plan is foolproof.
However, taking the time to strategize a plan increases the chances of a successful recovery.
Identify Critical Virtual Machines
Establish Strategy for Backup and
Recovery
Test
Automate
Below are four key areas to consider when developing a disaster recovery and backup plan for virtualized environments.

18. Overview of Best Practices and Tips for
Data Protection, Backup and Disaster
Recovery

19. 3-2-1 Rule
Achieve data resilience with the 3-2-1 rule.

20. Automation and Orchestration
Define disaster recovery runbook scenarios within software to orchestrate macro and micro disasters.
iland Secure Cloud Console
Define Disaster Recovery Scenarios
• Create your own defined failover scenarios
• Define full site, tier 1/2/3, business unit or other plans
• Drag and drop recovery groups and applications
• Orchestrate the order in which specific applications
are brought up within a DR scenario
Test & Validate
• Runbook & application orchestration
• Virtual machine boot order

21. Verify and Validate Applications
iland Secure Cloud Console
VM Console
• Available for all VMs and applications
• Accessible on desktop and mobile devices
• HTML5 based – no plugin required
• Interact with the machines keyboard and mouse
• Available during machine boot up, and post boot
• Window / full screen mode
Use Cases
• Verify live boot process – time and detail
• Validate machine and application performance
• Validate OS integrity
• Validate application integrity
• Validate recovery point integrity
• Validate recovery point resolves disaster prior to
real failover

22. Testing and Reporting
Test Anytime, Anywhere
You can trigger the Failover Wizard in the iland Secure Cloud
Console on your laptop or mobile device.
Select to perform a test or a live failover with your DR
solution at any time. Detailed Recovery Steps
Each step is recorded with the following details:
• Start time
• End time
• Success

23. Do More With DR
Deferred Workloads
Do all of the things you wish you could do on a
perfect copy of production, without impacting
production or interfering with DR.
• User accessibility training/feedback
• Patch management testing
• New software roll-out
• Test/dev/QA/troubleshoot
• Deep file analysis for compliance or governance
Proactive Security Analysis
iland Secure Cloud provides intrusion detection,
vulnerability scanning, as well as virus/malware
scanning while VMs are running.

24. Cloud-Based Resilience
What to consider:
• OPEX model vs CAPEX model
• Easy to implement
• Location of the off-site data
• What if your environment grows?
• Clear and simple pricing
Taking the backups is easy, but storing them becomes cumbersome.
Whether you are looking at backups or DR, cloud offers a scalable and affordable option for true IT resilience.

25. Data Protection Checklist
This checklist is just a starting point. Contact us for a free assessment of your environment at iland.com/contact.

26. iland’s Capabilities

27. • Full VMware cloud stack – Bring your years of
expertise and ease the transition to the cloud.
• Centralized console – Manage everything from billing
to performance to failover in a single pane of glass.
• Full API integration – Integrate existing workflows with
a full API suite.
• Integrated security and compliance – Keep your
workloads safe and compliant.
• Wide portfolio of services – Fulfill budget and recovery
objectives.
The iland Secure Cloud Console

28. Keep Control of Cost at Every Level
Billing Summary
• Last month
• Current month
• Previous hour
• Current hour
• Estimated billing for current month
Cost Component Breakdown
• Monthly / hourly granularity
• View costs associated with individual components
• CPU, RAM, storage, bandwidth and other costs
• Export / snapshot this information and share
Usage Summary
• Monthly cost breakdown
• Monthly estimate breakdown
• Attribute spend to pool / application /VM
Track & Alert
• Track burst / ad-hoc usage in real-time / historical view
• Set cost threshold alerts to control spend across teams

29. “Leader” in Gartner Magic Quadrant for DRaaS, 2016, 2017 & 2018
22
Years delivering
IT services
8
ISO 27001 and SSAE16
global data centers
11
Years cloud and disaster
recovery expertise

30. Global Locations
• Tier III and IV data centers
• Connected to 100s of IP providers
• Clear location for data sovereignty
• Local support in each region

31. Cloud Backup Disaster Recovery
• Long-term data retention
• Ransomware mitigation
• Data corruption protection
• Recovery from macro and
micro disaster
• RPOs in seconds
• RTOs in minutes
• PAYG for compute & RAM

32. Q & A

33. Download Your Copy!
2018 Virtual Environment Data Protection Report
https://www.iland.com/data-protection-report/

34. Thank You!

35. iland USA
1235 North Loop West, Suite 800 Houston,
Texas 77008 USA
office +1.713.868.2267
facsimile +1.713.868.2268
iland Europe
Level 24/25, The Shard 32 London Bridge St
London SE1 9SG, UK
+44 (0) 20 7096 0149
iland Asia
80 Robinson Rd #02-00
Singapore 068898
+ (65) 3158 8301
iland Australia
Level 32, 101 Miller Street
North Sydney NSW 2060 Australia
+ (61) (0) 2 9056 7004
www.iland.com