SRM Zerto Veeam Based on what you have provided either one of these meets your requirements. RTO of minutes is probably unrealistic, but I know nothing about your environment.


Zerto can absolutely have an RTO of minutes. The dialogue window for the failover process is a few clicks then the vms are poofed into existence and powered on. Then vmtools changes the ips, runs any scripts you might need then power cycles the vms and you're up and running. Typically, the longest part of the process is the OS booting. Sure, "all the other stuff" is crucial to you actually being up and running in your DR location, but the software can have the recovery VMs up and ready pretty much instantaneously. The rest is up to you. *not a shill, I just really like zerto. For all the products I've implemented, zerto is by far the easiest to maintain. It has one job and it does it extremely well.


I am aware all 3 can recover in minutes, but actually getting everything up in minutes is not possible for most environments. If OP has limited servers, plenty of resources and every server can be booted at the same time then it is possible.


RTO: Recovery time objective seems to be a few minutes RPO: Recovery point objective seems to be daily. So your objective is to recover yesterday's data within minutes? From a technology perspective vSphere replication + Site Recovery Manager could do this, without any sizing details.


Rep + SRM is what we use, I think we do 1-5hr sync depending on the VM. Failover can have us up and running on those within minutes.


For a free solution, you can use vSphere replication. You get no orchestration and it isn't very graceful, but it is reliable. If you want a tool to handle the entire failover event, you can look at SRM, Zerto, or Veeam's replication.


Check out Zerto.


+1 for zerto


+1 for Zerto as well. Done many a DR test and VM migration using it.


Veeam was built to do this


\+ 1 vote for Veeam. It is fantastic backup software and saved my ass a million times.


What’s you storage? Netapp? Pure? Nimble?


I like the vsphere replication idea but how can i connect the sites if vsphere cant run a vpn client


One possibility would be a hardware VPN between sites. Have a router at each site which can create a VPN tunnel between the sites and will route the networking appropriately.


Good point i had the same idea last night and set that up


There are multiple layers to this topic that you need to understand. As a whole site DR plan, it's fairly straight forward - building A burns down instantly & everything has to start at building B because there is no other data. You update public DNS bits & move forward. But in practice, it's a VM or two in building A is having issues, but you don't want to failover everything & have to deal with day old data & replicating all the other changes, then having to fail back at some point. This is where the backup points become critical - it's easier to roll back 15/30/60min on a single VM than to fail over everything.