Replica instead of synchronized storage

[frankive]

To keep the storage cost down we want to use veeam b&r to replicate our temrinalservers to a secondary storage location daily(nightly).
We want to run the replication once each day but not to touch the production environment. We are also backing up the VMs from the production nightly and would like to use these backup files to have a replication copy ready to fire up.
I know how to seed the first time, but is it possible to Veeam to seed from the backup also on every incremental after? So the replica won't hit the production environment?

Thanks.

[foggy]

Frank, this is exactly what replica from backup does.

[frankive]

i can not see anywhere during creation of the replication job or in the manual where i can choose where to get the backup files? only at the first screen (but that is just replica seeding)

[frankive]

Just found it
It was in the window where I choose virtual machines to replicate.
Choose VM, mark it with your mouse so it turns blue, and choose source on the right side.. then pick the backup files..

[foggy]

Right, here's a bit more on that.

[frankive]

Is it possible to failover particular machines of a replication job or is the failover pr. job?

[foggy]

You can select and failover any single or several VMs.

[frankive]

so if i have a replication job with 10 vms, I can choose to only failover one particular vm in that job?

[foggy]

Correct.

[frankive]

is it possible to replicate just the vm and not the harddrives?
we are looking for to migrate a 2008 R2 hyper-v cluster to a New 2012 R2 cluster. They shared the same Storage, HP Lefthand SAN.

[foggy]

We are not talking about replicating from backup anymore, right?

If I'm understanding your scenario right, you could replicate the VM excluding all its disks, turn the VM off, re-attach disks to its replica and perform failover. However this is just in theory, never tried anything like that.

[EugeneK]

The excluded disks may be picked up by the OS completely differently once re-attached to the new VM shell on the new host - since the config will no longer match, you may run into boot issues. For the most part, it depends on how Guest OS treats those drives and what those drives are to the OS.

[frankive]

I will try to follow a best pratice migration from Microsoft for this migration to new cluster