VMware DR a proof of concept – PAR300
September 10th, 2007 | 
Author: Session discussion questions:
Replicate using EMC SRDF
manually change ip addresses of replicated machines?
Use F5, dynamic dns to self update or auto update ip addresses.
Host based replication
Must have vm or host at both the primary and the secondary site for HBR. Must also pre-setup the networing, etc.
VMware is doing more with the SAN based relication
Site Recovery Manager will be able to interface with the replication product’s manager server
How much bandwidth do I need?
How many hops? How’s the latency? How much data is changing? Synchronous vs Asynchronous?
Impact to RTO / RPO
RTO – time to recover 24 hrs
RPO – 1 hr with lower latency
Clone / or replicting data only
most cases are true cloning and working out re-ip of vms
SQL / Exchange
SQL2005 may lose certain transactions, but mechanism in application can roll back
Virtualization is not the solution, but each application must be handled according to the reccomended process fro each application
transactional databases will have to roll back to previous times, or restarting the VM will be like a crash recovery for the OS and the application
UUID changes on SAN
Site Recovery Manager will handle this
Doesn’t have to have different UUID?
break mirror, exposes luns, esx servers already know about the luns, rescan
Planned Integration with MS CCR?
Not in first release
Advantages to booting ESX from SAN
doesn’t gain you too much. Doesn’t hurt, but no real advantages
Multiple VC2 servers
Site recovery Manager can let you have multiple VC2 servers
Business Continuity Plan
strategic apps required for the business to survive
I.d areas of customer’s concerns
match core competencies of customer to develop solutions
Show ROI and TCO – typically high cost but value of solution will be worth it
Solutions to develop around
- HA
- DRS – resource pools to manage VMs so critical vms take priority in DR event
- VCB – resource loads on ESX host
- storage replication -
- OS/app clustering – make sure not set to suto start in HA failover
- fault tolerant (hardware & software) -
Site Recovery Manager - announced today
workflow for DR failover and testing- automated and manual components
call manager / email team / prompt to get Change Control approval
using fencing technology like Lab Manager.
Large services engagement possible with this product ??!! 6 – 12 weeks.
create recovery plans
Integrate with replication
Map recovery resources
specify recovery process – custom scripts, alerts, etc.
HA – ensure high priority machines have priority when HA goes into effect
VCB – Integration with 3rd party backup software may require extra steps
full vm and file level recovery
script cutomization may be required
Clustering
Kickstart for quickly deploying ESX hosts
RTFM site – UDA appliance – Ultimate Deployment Appliance - many customers are using this tool as the current automated method of fail over.
Related Posts
Posted in breakout, dr, partner day, vmware, vmworld | 
Tags: backup, business continuity, esx, replication, SAN, vcb, vmware
