by collinp » Wed May 21, 2014 10:33 pm people like this post
Is it possible to use Veeam VM Replication as a way to migrate VM's to a new Hyper-v cluster permanently for a one time replication? I don't want to setup a replication relationship between a primary source and destination. I want to do a one-time replication from a source to destination VM and then delete the source VM permanently. These are big 1TB VM's where Hyper-v zero shared migrations fail. I also don't want to risk doing a Veeam instant vm recovery due to performance implications of running from the slow backup storage during the migration.
by andy51585 » Mon Jul 28, 2014 9:44 pm people like this post
I would like to leverage a replication job to move from one physical data center to another. I have currently a replica made on the target vCenter server. I was wondering what the best way is do a "final" replication. Is there a way to in near real time synchronize the last changes to the source VM, bring the destination online, and shut down the source. I was looking at the permanent failover option, but that appears to commit the delta of the target. Is it possible to commit a delta of the source?
by foggy » Mon Jul 28, 2014 10:11 pm people like this post
Andrew, the best practice is to shut the source VM down, perform final replication of the latest changes, and then failover to the replica VM. This allows to avoid any data loss and provides minimum downtime.
by ssen » Wed Oct 22, 2014 2:03 am people like this post
I'm building out a new vSphere cluster that is separate from a standalone esxi 5.5 server we have. For licensing and configuration reasons I cannot add the standalone server to my new cluster. I've been playing with Veeam and I'm not sure whether I should use the backup feature or the replication feature to copy the VMs over. I understand "Quick Migration" is available BUT I need the source VMs to stay up and not turn on once it arrives on the new cluster. I want to copy the running VMs into the new cluster and eventually do a failover when we're ready. I can't run a Quick Migration because the network settings on the new cluster can't accommodate the IPs of the VMs on the standalone server.
My question is, should I be using backup or replication? I dont want any dependencies to the standalone server or Veeam once I migrate everything off.
by emilec » Wed Oct 22, 2014 1:15 pm people like this post
I have some Linux servers running PostgreSQL that I want to move to a new location.
If I wanted to get the databases over in a consistent state could I run a replication job while the servers are on to get the bulk of the data over and then shut them down for a final replication? Would my databases be consistent or should the VMs or PostgreSQL service be off from the start?
by foggy » Thu Oct 23, 2014 1:21 pm people like this post
To get transaction consistency, you can enable VMware Tools Quiescence in the replication job. But it is a good practice to shut the VM down before replicating the final changes to avoid any data loss.
by emilec » Fri Oct 24, 2014 2:58 pm people like this post
foggy wrote:To get transaction consistency, you can enable VMware Tools Quiescence in the replication job. But it is a good practice to shut the VM down before replicating the final changes to avoid any data loss.
So my plan should work then: 1) Replicate running VMs until all the data is at the remote side. 2) Shut down the VMs and run replication again.