This is a 1-time datacenter-datacenter migration of our ESXi 4.1 environment. I planned to use Veeam but, Doubletake has entered into the conversatio
To clarify, I understand the "in OS" agent based Doubletake methodolgy. They appear to be refering to a Doubletake solution methodolgy that is image based and competes with Veeam. I hadn't heard of that solution so, I wanted to know (1) does that exist? and (2) is anyone familiar with the differences and/or could provide a pros/cons list.
The growing consensus is that since we are likely using Doubletake for physical server migrations, it would make sense to use just one vendor for everything.
Personally, I would prefer to go with Veeam replicator but, without some supporting comparison argument data, I don't think I'll win the argument.
Would cost Factor in ? that usually swings it in favour of the considerably cheaper product
In this case, I wouldn't expect the cost difference between the 2 to move the needle enough to matter. It's a large 600+ VM migration so, I'm wanting to avoid building 600 destination VMs, giving them IPs, loading agents in the source machines, replicating over the source VM network, etc. That is my understanding of the Double-Takes replication methodology.
As I understand Veeam since it is image based, it is agentless, it creates the destination VM, copies the VM folder out-of-band (i.e. copies the VMDK over the management network rather than source VM network as Double-Take would).
Unless my understanding of Double-Take or Veeam is wrong, from a technical perspective, Veeam seems to be the better, cleaner choice for VM migration.
I'd appreciate any comments or correction from those with product knowledge.
Disclaimer : I currently work for Veeam.
That said I have been part of a similar project where doubletake was used for the migration. I believe we used the Doubletake livewire product which although it didn't require the building of the shell VM's , did have a number of problems with the environment I was in at the time ( didn't work with ESXi at that particular release , newer release would have required a .net update on the 900+ VM's I was trying to move etc. )
Are you moving to the same layer 2 subnet ? if not ,you will still have to change IP's on the new machines ?