Disaster Recovery or Backup? Chris Snell

Size: px

Start display at page:

Download "Disaster Recovery or Backup? Chris Snell"

Hortense Andrews
8 years ago
Views:

1 Disaster Recovery or Backup? Chris Snell

2 Agenda How do you know if you need Disaster Recovery or Backup? - Service Levels - Application Performance and Impact - Retention - Automated Recovery - Reverse Replication Zerto Virtual Replication Overview Case Study: Woodforest National Bank Case Study: HAPO Community Credit Union 1

Automated Recovery - Reverse Replication Zerto Virtual Replication

3 Do you need Disaster Recovery or Backup? Disaster recovery is a subset of business continuity. Disaster recovery is preparing for recovery or continuation of technology infrastructure which are vital to an organization after a natural or human-induced disaster (i.e. the systems or applications may be available but the end users may not be). Disaster recovery ensures the data is available quickly after an outage. Backup refers to the copying and archiving of computer data so it may be used to restore the original after a data loss event. The backup system contains at least one copy of all data worth saving, the data storage requirements can be significant. Organizing this storage space and managing the backup process can be a complicated undertaking. 2

Disaster recovery ensures the data is available quickly after an outage.

seconds - Recovery time objectives of minutes Backup delivers service levels that are

4 Service Levels What do you need? Disaster Recovery delivers very aggressive service levels - Recovery point objectives of seconds - Recovery time objectives of minutes Backup delivers service levels that are better suited for a tier 3 application - Can you lose hours of data? - Can the business survive without the application for 12 hours or more? 3

5 Application Performance and Impact Disaster Recovery The replication mechanism operates continuously and does not significantly impact the application - End-user productivity is not impacted - Revenue generating activities are not slowed Backup The replication mechanism occurs at a set time(s) during the day and application performance slows - End-users notice a change in application performance - Backups usually occur in the early morning hours 4

are not slowed Backup The replication mechanism occurs at a set time(s) during the day and application

periods can be optional with a disaster recovery solution Backup years of retention

6 Data Retention how long do you need the data? Disaster Recovery shorter retention, with many recovery options - Longer retention periods can be optional with a disaster recovery solution Backup years of retention to be internal and external compliance requirements, fewer recovery options - Recovery usually take a long time extending RPOs 5

7 Automated Recovery Disaster Recovery should have minimal manual steps to ensure accuracy and speed Backup is usually a very manual process that takes some time 6

8 Reverse Protection Organizations are scared to failover, because then how do you get the data back? Disaster Recovery should deliver the ability to replicate back to the production site for simple failback when possible. VM Replication Production Site Disaster Site Backup solutions do not have this capability October 8,

Disaster Recovery should deliver the ability to replicate back to the production

9 Virtual Aware Software Only Tier-1, Enterprise Class Fully Automated Purpose-built for virtual environments and the cloud 8

10 Case Study: Woodforest National Bank Environment Disaster avoidance strategy 201 VMs, 60 TBs Challenge Complex process Inefficient use of assets Result Reduced number of LUNs 43% Reduced bandwidth requirements 44% Reduced storage footprint at target site 25% Protect VMs with a couple of clicks Automated failover, failback and testing 9

number of LUNs 43% Reduced bandwidth requirements 44% Reduced storage footprint at

Case Study: HAPO Credit Union Environment Paperless banking across the environment Array-based replication 130 VMs, 40 TBs of storage Challenge Service levels not

their configuration we knew it would improve our BC/DR process, but we got so much more. We reduced our storage footprint by more than 40%.

11 Case Study: HAPO Credit Union Environment Paperless banking across the environment Array-based replication 130 VMs, 40 TBs of storage Challenge Service levels not adequate Result Storage footprint reduced by 43% No new storage purchases for the foreseeable future RPO of seconds and RTO of minutes Simple BC/DR that did not disrupt their configuration we knew it would improve our BC/DR process, but we got so much more. We reduced our storage footprint by more than 40%. Bill Rausch, Software Engineering Manager The service levels we are delivering to the business we never thought would be possible. It really helps me sleep at night. Kevin Jackson, Senior Network Administrator 10

12 Thank you Chris Snell

13 Thank You

Virtualization & Covance Inc.

Virtualization & Covance Inc. Virtualization & Cloud Computing Environment Oleg Trigub Covance Inc. Agenda Disaster Recovery Challenges Benefits of Private Cloud DR RPO versus RTO Data Replication among Data Centers Is DR in the Cloud