Feature Request: Seeding a Backup Copy Job in Hyper-V

Hyper-V specific discussions

Feature Request: Seeding a Backup Copy Job in Hyper-V

Veeam Logoby cprime@medmarc.com » Thu Jul 14, 2016 7:08 pm

We recently moved VMs from one failover cluster to another and found out that Veeam treats these as new VMs, which also means the Backup Copy treats them as new VMs. It takes us 3 weeks to run a full backup copy offsite. Obviously, that's both an annoyance and a potential job killer if something happens during that time when in reality the only that that has changed are some xml files.

I've also had to restart replication this year after v8 to v9 upgrade somehow broke the replication. Again, I should be able to re-use what's already offsite to catch up the replication rather than starting from scratch.

The replication option allows for seeding and VM mapping, but the Backup Copy does not and I think it absolutely should. If I have to restart another 3-week offsite copy again I think I'll start looking for a new Hyper-V backup copy utility.
cprime@medmarc.com
Lurker
 
Posts: 2
Liked: never
Joined: Thu Jul 14, 2016 7:02 pm
Full Name: Chris

Re: Feature Request: Seeding a Backup Copy Job in Hyper-V

Veeam Logoby Vitaliy S. » Fri Jul 15, 2016 10:33 am

Hi Chris,

Do you have a possibility to use a SCVMM server? In this case even if VM is migrated between failover clusters, the VM ID will remain intact (as it will be the SCVMM one).

Thanks!
Vitaliy S.
Veeam Software
 
Posts: 19575
Liked: 1106 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 13 guests