Q: 9
Which Veeam replication failover function ensures that changes made during a failover are copied to
the original production VM?
Options
Discussion
Looks like A. Fallback is the Veeam process that actually pushes all the changes from the replica back to your original VM. Permanent failover (B) just switches prod permanently but doesn't sync changes, so that's a common gotcha. Seen this tested in practice labs-chime in if anyone's seen it act differently.
Probably A here. Backup copy job keeps the load off Site B VMs and works with the slow link setup.
A is the right move here, since fallback in Veeam actually syncs those failover changes back to your prod VM. Pretty sure that’s what official guides and labs demo too. Someone correct me if I missed a recent update.
A , fallback is the step that actually copies all the changes made on the replica VM back to the original production VM after failover. B (permanent failover) just makes the replica your new prod and doesn't sync back, so it's a bit of a trap here. Pretty confident since that's how Veeam handles DR scenarios-let me know if anyone reads it differently.
A tbh, encountered exactly similar question in my exam. Fallback is the function that syncs changes made during the failover back to the original VM, so nothing gets lost when restoring production. B is more for when you're ditching the old VM completely. Pretty sure on this but open to corrections if someone has seen otherwise.
Not sure why so many pick B, I think A is what handles syncing those changes back to the original VM. Permanent failover sounds like a trap here since it just cuts over, right?
A imo, saw a similar Q in a VMCE test, fallback syncs the changes back to prod VM.
Doesn’t fallback mean changes from the replica VM go back to production? Fallback copies the delta back so you don’t lose updates made during failover. Or am I missing something about how "permanent" works in Veeam here?
Its A in this case. Backup copy jobs read from already existing backups at Site B, so the source VMs aren’t hit again-cuts down impact a lot. Components lineup also fits the WAN setup. Pretty sure about this, but happy to hear arguments for B.
B tbh. Had something like this in a mock and picked backup job since it feels straightforward to just run daily backups across sites. Didn't factor in how much load that puts on Site B VMs though, but pretty sure B lines up with what I've seen.
Be respectful. No spam.
