You create a local backup with Veeam - which of course creates a snap.... and then you do a replication with Veeam from one hypervisor to another? why are you using Veeam to do that instead of the built in hypervisor tools? But that's really beside the point.
Doing that clearly makes the server run a snap twice (unless it can be run in a single job). and put strain on the VM host while replicating to the remote site.
Backups run nightly.
Not all servers are replicated
Replication gives you more restore points throughout the day in addition to the failover capability
How do you get number 3?
It creates replication points? That's not how I've ever understood how replication works.
Even Hyper-V has this built into replication. You can choose to keep XX number of replication points. Honestly this is not much different than people keeping XX snapshots on the local host for immediate rollback needs.
you can't pick and choose roll backs, if you pick two snaps ago, you loose the one from one snap ago.
See above about replication I just posted. I'm using replication like JB in that I'm just using it for convenient backup not true replication for DR failover. JB may be doing it similarly.
Does that use 12x time disk space of the VM?
Not at all. It similar to Forward incremental. One big file with delta snaps.
Cool feature in Veeam.
Built into every replication system I am aware of.
If you are trying to use Veeam, the standard setup would to have a server running a second copy of Veeam B&R at the target site. You'll link the two and configure the replicas. You do not need to purchase a second Veeam license to do this, but you will need a running B&R at the DR site.
That was my understanding of how it works, but it has been almost two years since I talked to Veeam about it.
With what I've seen with v9, you now can do full failover scripted ahead of time to make it a bit more turn-key during a disaster.
@JaredBusch Sorry, I've missed the point. You can install VEB in unattended mode thru any distribution solution you have on board. Check this article, however, the problem of configuration remains as it has to be performed manually after the installation
Updated all my clients that use Veeam to the current version over the last couple days.
Today I setup the first endpoints using the current EndpointBackup.18.104.22.168
It works great for making backups using the the existing Veeam repositories. The plus side to using the Repository is that I get to see it in the VBR panel and status email from existing setup just like if a main backup fails.
Note: Rebooted the user's machine and initiated a backup again. running perfectly.