how to integrate dr services into a virtual environment
TRANSCRIPT
How to Integrate DR Services Into a Virtual Environment
Howdy • VMware Certified Design Expert (VCDX) #104
– Data Center and Network Virtualization
• Tech, Lab, Certs, Reviews, Videos
– WahlNetwork.com
• Pluralsight Author
– Upgrading your vSphere Environment
– CCNA Data Center
– vCloud Director
Snag the book!
Helping vSphere Administrators and Network Engineers work better, together.
Available in:
Paperback
Kindle
eBook
EPUB
MOBI
100% of my profits go to
Alzheimer’s Association
Agenda
• Service Level Agreements
– Stop all efforts until these are done!
• Hardware Abstraction
– Virtualization is just the start
– Further work can be done
• Orchestration Tools
– Living run books, automation, and testing
Disaster Recovery is Elusive So close, yet so far away
Service Level Agreements
Contracts Between IT and Service Owners
The First Few Questions
• Do you have documented SLAs?
• Do your SLAs clearly communicate the RPO, RTO, and Availability of your service tiers?
• Are your SLA documents readily available to everyone in the company?
The Disconnect Harassing Application Owners with Nerd Knobs
Application Owners Have Other Things To Do
Service Tiers Simplified Approach to Offering DR Services
Disaster Recovery Road Map
Service Level Agreements
Business Impact Analysis
Hardware Abstraction
Replication Topology Analysis
Orchestration Tools
Frequent Testing
Abstract Away Hardware Dependencies
Topology Strategies
Building Disaster Recovery
for Virtual Services
Sync Replication (Active / Active) Pros
• Applications can live in either data center
• Infrastructure masks single points of failure
• Requires sync replication
• “Near zero” RPO & RTO
Cons
• Insanely expensive
• Geographically challenging
• Requires sync replication
• Complex mix of skillsets
• Architecture requires talented individuals with experience and “battle scars”
Async Replication (Warm Site) Pros
• Costs become palatable
• Increased geographic choice
• Simpler skillset to acquire
• More common topology (share war stories)
• Can tier workloads (prod vs pre-prod)
Cons
• Increased RPO vs Active/Active
• Heavy focus on orchestration and automation
• Application involvement
• Workload migration requires an outage
Replication Designs Hypervisor-Based
• Abstraction of the workload from physical resources
• Ability to cross hypervisors
• Tighter integration across the workflow
• Potential for avoiding lock-in
Array-Based
• Abstraction from the application
• Supports multiple writers or other clustered tech (Oracle RAC)
• Multiple entities working in harmony
Disaster Recovery Road Map
Service Level Agreements
Business Impact Analysis
Hardware Abstraction
Replication Topology Analysis
Orchestration Tools
Frequent Testing
Orchestration
Physical Run Books Static Docs for Dynamic Services?
Self Documenting Systems
Details on the run book execution
Protection grouping, service order, write consistency
Ability to execute the run book
As one plan, or pieces of the plan (per-service)
Simple and repeatable testing without outages
Fail-over testing, optional data sync
Tests should not interrupt replication and protection
Zerto
Hypervisor-based replication and orchestration
• Licensed per protected VM
• Supports multiple hypervisors (vSphere, Hyper-V)
• Supports disparate hypervisor replication (VMW to MS)
• DRaaS cloud provider program
• RESTful APIs & PowerShell modules
• Option to store data in AWS
• Operationally friendly
Double-Take by Vision Solutions
Agent-based replication and orchestration
• Licensed per protected instance
• Supports multiple hypervisors
• Operationally friendly
• Can also re-platform the application (P2V)
• Cloud Migration Center (CMC) to move workloads to Azure
VMware SRM + VR (Site Recovery Manager)
Hypervisor-based replication and orchestration
• vSphere Replication (VR) is bundled with ESXi hypervisor
• Site Recovery Manager licensing is per VM (25 packs)
• VMware hypervisor only
• Operationally friendly
VMware SRM + SRA (Site Recovery Manager)
Array-based replication and decoupled orchestration
• Storage Replication Adapter (SRA) is a collection of vendor scripts
• Site Recovery Manager licensing is per VM (25 packs)
• Requires like-for-like hardware
• VMware hypervisor only
• Orchestration is decoupled from replication
Disaster Recovery Road Map
Service Level Agreements
Business Impact Analysis
Hardware Abstraction
Replication Topology Analysis
Orchestration Tools
Frequent Testing
Automation of Logical Configuration
Automation
• Network Configuration
– DNS, IP, BGP/OSPF routing, DHCP, etc.
• RESTful APIs are your friend
– Flexibility to use any code language
• Leverage Configuration Management
– Puppet classes, PowerShell DSC node / resources, etc.
The Future Disposable services via containers or declarative configuration
This should be your ultimate goal, but not reality for MANY orgs!
Request Details on Protected VMs
Using a “GET” RESTful API call to Zerto
Disaster Recovery Road Map
Service Level Agreements
Business Impact Analysis
Hardware Abstraction
Replication Topology Analysis
Orchestration Tools
Frequent Testing
Additional Resources Visit WahlNetwork.com for Deep Dives,
Home Lab Tips, Reviews, and More!
Check out “Networking for VMware Administrators” by VMware Press
Over 30 hours of my video training content is on Pluralsight.com
Nearly 100 free HD videos on the WahlNetwork YouTube Channel