Let's Talk Webinar - Disaster Recovery for Business
•Download as PPTX, PDF•
1 like•113 views
Disaster is something we hope never strikes your organisation, but hope will not protect your business. In this webinar we will look at the true cost of recovery, looking in more detail at the importance and business benefits of Disaster Recovery and Back Up. Hosted by Novosco's Mal Toner
Recommended
Recommended
More Related Content
Similar to Let's Talk Webinar - Disaster Recovery for Business
Similar to Let's Talk Webinar - Disaster Recovery for Business (20)
More from Novosco
More from Novosco (20)
Recently uploaded
Recently uploaded (20)
Let's Talk Webinar - Disaster Recovery for Business
- 2. novosco.com • What is Disaster Recovery (DR)? • DR vs Business Continuity (BC) • DR vs Backup • Typical DR challenges • What is Novosco DRaaS ? • Q&A Agenda
- 4. novosco.com DR does not equal Backup (and vice versa!) Depending on the compelling event – one or both tools can offer a solution!
- 6. novosco.com
- 7. novosco.com DR Choices None Build Your Own (BYO) DRaaS Disaster Avoidance
- 8. novosco.com Disaster Avoidance The separation of company offices and the supporting IT infrastructure: • Move the active infrastructure to a less risky location. A tier 3 data centre for example. AND/OR • Architect for active-active (if possible) infrastructure with a second location. VPLEX for example.
- 10. novosco.com The rosy view of how DR works “A vision without the ability to execute is no different to a hallucination” -often credited to Thomas A. Edison
- 11. novosco.com BYO: DR – Technical Challenges
- 12. novosco.com BYO:DR – The Value Challenge Without an actual DR event, how can you represent value? Higher system utilisation is better for value However: Higher system utilisation is worse for risk, growth
- 13. novosco.com BYO:DR – The Value Trap Allow compromise on capability/ability to execute. Examples: Buy high end array on primary site (SSD,SAS etc) and lower end array on secondary site (SATA) Re-use older less capable equipment Build with less resilience Build with less flexibility
- 14. novosco.com Failover Considerations Recovery points are crash-consistent Most applications can recover from crash- consistent points automatically. . Deciding to failover is a business decision that the customer must make. Novosco can initiate failover – but will request written approval.
- 15. novosco.com DR – Failback Considerations Failback is simply an inverse configuration Whenever you have a functional infrastructure we replicate to you. When replication is in place, a failover/move takes place. Reverse replication is configured to resume protection you. Re-use of VMDKs means automatic “seeding”.
- 16. novosco.com DR – RPO Considerations RPO is a function of Write activity Identifying superfluous write activity can have a dramatic effect. WAN capability / configured limit The minimum limit is 5Mbps WAN utilisation VPG priority when the WAN is congested The frequency of VMware snapshot rollback This requires a re-sync (CDP history is lost)
- 17. novosco.com DR – RTO Considerations RTO is a function of Mean time to detect a failure Time to understand the failure impact and qualify a failover decision Invoke your VPG failover plans Time take to redirect clients and external services to the DR infrastructure.
- 19. novosco.com What is Novosco DRaaS? DRaaS is a managed service from Novosco designed to provide customers vSphere infrastructures with a DR capability. DRaaS combines a number of enterprise grade technologies and platforms into an easily consumable service.
- 20. novosco.com DRaaS - Service Functionality Self service failover (test or live*) Failback Access to recovered VM console via web interface Recover into a production ready environment High bandwidth/low latency connection into the Novosco Manage WAN Integrates with Novosco Manage WAN MPLS Integrates with Novosco Manage WAN Hosted Firewall
- 21. novosco.com DRaaS - Service Parameters 24 hour CDP history as standard vSphere environments only Configurable priority on VPG replication (High/Medium/Low) Daily monitoring Fault logging and troubleshooting Statement of configuration
- 22. novosco.com Why Novosco DRaaS? Predictable costs (Per VM/Month) Value for money with no waste Clear ability to execute Spend what time you have on testing DR. Novosco DRaaS provides a fully managed service of all DR service elements. Test anytime. Failover and failback
- 23. novosco.com Novosco DRaaS locations: The facility can be considered tier 3. Some highlights of the facility include: Secure access 24/7 ISO 27001 certification Electrical feeds from separate sub-stations Delivers A+B power to racks 2N UPS configuration
- 24. novosco.com
- 25. novosco.com Q&A
Editor's Notes
- Business continuity is the activity performed by an organization to ensure that critical business functions will be available to customers, suppliers, regulators, and other entities that must have access to those functions. Business continuity is not something implemented at the time of a disaster. Business Continuity refers to those activities performed daily to maintain service, consistency, and recoverability. Disaster recovery (DR) is a subset of business continuity Disaster recovery is the process, policies and procedures related to preparing for recovery or continuation of technology infrastructure critical to an organization after a natural or human-induced disaster.
- Backup solutions have continued to evolve their features and capabilities. Partially helped with improved OS backup mechanisms and leveraging game changing hypervisor snapshots There exists some overlap of capability in some use-cases only. It very much depends on the circumstances
- Invocation DR: Failover “button” initiating a pre-defined recovery plan through resource orchestration. Backup: Manual selection of data to be restored. Capability to recover DR: Defined recovery infrastructure for activated workloads Backup: Target system may need built before restore. Resources for recovery may not be immediately available. Target recovery time for a selected system DR: Minutes to system “on”. Testable to set expectations. Backup: Depends on what needs recovered and where it needs recovered (minutes to hours) Target Recovery Point DR: Granular single recovery points limited typically to last 24 hours Backup: Numerous recovery points typically separated by 24 hours Unit of Recovery DR: Whole systems Backup: Granular object and complete systems
- The principle of architecting a system to avoid the need for recovery in case of a disaster (e.g. weather, power cut):
- The principle of architecting a system to avoid the need for recovery in case of a disaster (e.g. weather, power cut):
- There exists within our industry a somewhat rosy view of DR. Effective DR is a habit, not a tick box. Requires a supporting BCP Requires interest and support from business stake holders. Requires regular maintenance and testing. DR is often seen as a pure cost centre – so there is a pressure to get it done as cheaply as possible. Minimise on CAPEX and OPEX, maximise on value. Often the last priority of day to day IT operations.
- How do you right-size the infrastructure? Does you DR site have suitable connectivity? Internet connectivity / WAN integration Throughput / Latency / Reliability Do you know how to monitor and troubleshoot the additional infrastructure elements? How supportable is your infrastructure? Lifecycle operations Licensing, warranty
- DR system value is often seen as a relationship between the amount of money spent, and the number of VMs protected – often omitting the capability to execute as a consideration. What is your unit of expansion if your circumstances change? E.g. A server blade air-conditioning unit disk tray ISP bearer Replication software license 10 pack Each change requires cost justification. It is sometimes attractive to re-use an existing secondary site though this carries its own considerations – particularly if it already has active infrastructure/users.
- DR system value is often seen as a relationship between the amount of money spent, and the number of VMs protected – often omitting the capability to execute as a consideration. What is your unit of expansion if your circumstances change? E.g. A server blade air-conditioning unit disk tray ISP bearer Replication software license 10 pack Each change requires cost justification. It is sometimes attractive to re-use an existing secondary site though this carries its own considerations – particularly if it already has active infrastructure/users.